Creating an Archiving Subclient for NFS Exports

When you add content to a subclient, the backup and restore operations can automatically mount the appropriate NFS export if the content path uses the following format: file_server_interface:/NFS_export_path. The file server interface can be the host name or the IP address. To add content to the default subclient or to additional subclients, you can browse for content or you can manually add content.

Procedure

From the CommCell Browser, expand Client Computers > network_share_client > File System.
Right-click the archive_set, point to All Tasks, and then click New Subclient.

The New Subclient dialog box appears.
Specify the basic settings for the subclient:
1. In the Subclient Name box, type a name.
2. On the Content tab, click Add Paths to add the content you want to back up.

Option to add a path	Steps
Browse and select the NFS exports that are available on the on file server	Click Browse. The Browse Configuration dialog box appears. In the File Server Interface box, review the default value (the client host). You can update the client host to an NFS interface on the file server. From the Proxy list, click the proxy to use to browse for the shares. Click OK. The Browsing contents dialog box appears. Click the NFS export that you want to back up, and then click Add.
Manually add a path	Click Add Paths. The Add Multiple Contents dialog box appears. Type the following command: file_server_interface:/NFS_export_path /////// //////where:- file_server_interface is the NFS interface from the file server used when the NFS export is automatically mounted. The file server interface can be the host name or the IP address.- NFS_export_path is the path to the NFS export. You can include wildcards to define the subclient content. For example, to archive all export paths that start with Dep on your file server Server1, enter Server1:/Dep. To archive all export paths from Dep1 to Dep10, enter Server1:/Dep[1-10]. For information about supported wildcards, see Wildcards for the UNIX/Linux File System Agent.Leaf-level wildcards are not supported. You cannot include wildcard content under the share. For example, if /Dep1 contains folder1-folder5. Adding content by specifying server1:/Dep1/folder[1-5] does not expand the content to folder1-folder5.Mid-level wildcards are supported only for directories. For example, if /Dep1 contains folder1-folder5. Adding content by specifying Server1:/Dep1/folder/confidential will expand folder1-folder5, and then archive the confidential directory under each folder.You can exclude files or folders with specific extensions from archiving. For example, to exclude files or folders with .git extension, enter file_server_interface:/NFS_export_path/*/.git. ///// //// ///To archive your files, on the Archiving Rules tab:On the General subtab, set the rules based on the file access time, modified time, and file size. For more information about archiving rules, see Archiving Rules. Optional: On the Advanced subtab, configure delayed stubbing and set additional archiving rules. To perform a data redundancy check, see Enabling Redundancy Check for Files that Qualify for Archiving. For more information about advanced archiving rules, see Stub Pruning. To specify the retention period for your archived files, on the Retention subtab, set the time period. For more information about retention period, see Retention Options for Archiving. On the Data Access Nodes tab, under Available Data Access Nodes, select the data access nodes that will participate in the archive operation, and then click Add.NoteYou can set data access nodes at the agent level or at the subclient level. The nodes set at the subclient level take precedence in such cases.You can select a client or a client group (containing UNIX clients) from the available nodes list.Ensure that you select the Allow multiple readers within a drive or mount point check box on the Performance tab and increase the number of data readers as needed based on the number of data access nodes added.Ensure that you select the Reconcile Backup check box on the Advanced Options tab.All of the participating backup nodes must be at the same service pack level. On the Storage Device tab, select a storage policy from the Storage Policy list. On the Retention tab, choose one of the following radio buttons to specify the retention criteria. Archiving subclient honors only subclient retention.NotePrior to maintenance release 11.26.6, the Retention tab was not displayed on the subclient and archiving jobs followed storage policy retention. Retain Jobs for n years, n months, and n daysWhen you select this option, the default value is set to 5 years. However, you can modify the value based on your requirements. Between storage policy copy retention and the subclient retention value, the retention that retains items for the longest period takes precedence. Retention is only considered for copies that contain the job. If you specify storage policy copy retention as x days and y cycles, then the Commvault software compares the x days to the number of days you specify for subclient Job-Based Retention and keeps the items for the longest number of days specified. However, cycle value plays no role in retention.Example 1:Set the Retain Jobs for n years, n months, and n days to 0 years, 1 month, 20 days. There are 2 storage policy copies (A and B) and both copies contain the archive jobs. The retention of A and B is as follows: A: 45 days 3 cycles B: 17 days 4 cyclesSince the subclient retention has a longer retention period than the storage policy retention, the archive jobs will be available for 50 days in copy A. Example 2:Set the Retain Jobs for n years, n months, and n days to 0 years, 0 month, 15 days.There are 2 storage policy copies (A and B) and both copies contain the archive jobs. The retention of A and B is as follows: A: 45 days 3 cycles B: 17 days 4 cyclesSince copy A has a longer retention period than copy B and the subclient retention value, the archive jobs will be available for 45 days in copy A.Example 3:Set the Retain Jobs for n years, n months, and n days to 0 years, 0 month, 25 days. There are 3 storage policy copies (A, B, and C). The retention of A, B, and C is as follows: A: 45 days 3 cycles B: 17 days 4 cycles C: 91 days 2 cyclesOnly copies A and B contain the archive job. Since archive jobs were not scheduled, Copy C does not contain the archive job. Copy A has a longer retention time period than copy B and than the subclient retention options. Thus, the archive jobs will be available for 45 days in copy A.Example 4:Set the Retain Jobs for n years, n months, and n days to 0 years, 6 month, 0 days.There are 2 storage policy copies (A and B) and both copies contain the archive jobs. The retention of A and B is as follows: A: 45 days 3 cycles B: 45 days 4 cyclesSince, copies A and B have same retention period, the archive jobs will be available for 6 months in both the copies. Retain Jobs IndefinitelyThis is the default option with indefinite retention period. When you select this option, the archive jobs are retained indefinitely in the storage policy copy.Example 1:Set to Retain Jobs indefinite. There are 2 storage policy copies (A and B) and both copies contain the archive jobs. The retention of A and B are as follows: A: 15 days 3 cycles B: 45 days 4 cyclesSince the subclient retention is indefinite, the archive jobs will be available in copy B indefinitely. Click OK. It is highly recommended to have a storage policy with multiple synchronous copies with longer retention period than the primary copy. Data Aging prunes archive jobs that have exceeded the retention period of the copies.

Option to add a path

Steps

Browse and select the NFS exports that are available on the on file server

Click Browse.

The Browse Configuration dialog box appears.
In the File Server Interface box, review the default value (the client host).

You can update the client host to an NFS interface on the file server.
From the Proxy list, click the proxy to use to browse for the shares.
Click OK.

The Browsing contents dialog box appears.
Click the NFS export that you want to back up, and then click Add.

Manually add a path

Click Add Paths.

The Add Multiple Contents dialog box appears.

Type the following command:

file_server_interface:/NFS_export_path /////// //////where:- file_server_interface is the NFS interface from the file server used when the NFS export is automatically mounted. The file server interface can be the host name or the IP address.- NFS_export_path is the path to the NFS export. You can include wildcards to define the subclient content. For example, to archive all export paths that start with Dep on your file server Server1, enter Server1:/Dep*. To archive all export paths from Dep1 to Dep10, enter Server1:/Dep[1-10]. For information about supported wildcards, see Wildcards for the UNIX/Linux File System Agent.Leaf-level wildcards are not supported. You cannot include wildcard content under the share. For example, if /Dep1 contains folder1-folder5. Adding content by specifying server1:/Dep1/folder[1-5] does not expand the content to folder1-folder5.Mid-level wildcards are supported only for directories. For example, if /Dep1 contains folder1-folder5. Adding content by specifying Server1:/Dep1/folder*/confidential will expand folder1-folder5, and then archive the confidential directory under each folder.You can exclude files or folders with specific extensions from archiving. For example, to exclude files or folders with .git extension, enter file_server_interface:/NFS_export_path/**/*.git. ///// //// ///To archive your files, on the Archiving Rules tab:On the General subtab, set the rules based on the file access time, modified time, and file size. For more information about archiving rules, see Archiving Rules. Optional: On the Advanced subtab, configure delayed stubbing and set additional archiving rules. To perform a data redundancy check, see Enabling Redundancy Check for Files that Qualify for Archiving. For more information about advanced archiving rules, see Stub Pruning. To specify the retention period for your archived files, on the Retention subtab, set the time period. For more information about retention period, see Retention Options for Archiving. On the Data Access Nodes tab, under Available Data Access Nodes, select the data access nodes that will participate in the archive operation, and then click Add.NoteYou can set data access nodes at the agent level or at the subclient level. The nodes set at the subclient level take precedence in such cases.You can select a client or a client group (containing UNIX clients) from the available nodes list.Ensure that you select the Allow multiple readers within a drive or mount point check box on the Performance tab and increase the number of data readers as needed based on the number of data access nodes added.Ensure that you select the Reconcile Backup check box on the Advanced Options tab.All of the participating backup nodes must be at the same service pack level. On the Storage Device tab, select a storage policy from the Storage Policy list. On the Retention tab, choose one of the following radio buttons to specify the retention criteria. Archiving subclient honors only subclient retention.NotePrior to maintenance release 11.26.6, the Retention tab was not displayed on the subclient and archiving jobs followed storage policy retention. Retain Jobs for n years, n months, and n daysWhen you select this option, the default value is set to 5 years. However, you can modify the value based on your requirements. Between storage policy copy retention and the subclient retention value, the retention that retains items for the longest period takes precedence. Retention is only considered for copies that contain the job. If you specify storage policy copy retention as x days and y cycles, then the Commvault software compares the x days to the number of days you specify for subclient Job-Based Retention and keeps the items for the longest number of days specified. However, cycle value plays no role in retention.Example 1:Set the Retain Jobs for n years, n months, and n days to 0 years, 1 month, 20 days. There are 2 storage policy copies (A and B) and both copies contain the archive jobs. The retention of A and B is as follows: A: 45 days 3 cycles B: 17 days 4 cyclesSince the subclient retention has a longer retention period than the storage policy retention, the archive jobs will be available for 50 days in copy A. Example 2:Set the Retain Jobs for n years, n months, and n days to 0 years, 0 month, 15 days.There are 2 storage policy copies (A and B) and both copies contain the archive jobs. The retention of A and B is as follows: A: 45 days 3 cycles B: 17 days 4 cyclesSince copy A has a longer retention period than copy B and the subclient retention value, the archive jobs will be available for 45 days in copy A.Example 3:Set the Retain Jobs for n years, n months, and n days to 0 years, 0 month, 25 days. There are 3 storage policy copies (A, B, and C). The retention of A, B, and C is as follows: A: 45 days 3 cycles B: 17 days 4 cycles C: 91 days 2 cyclesOnly copies A and B contain the archive job. Since archive jobs were not scheduled, Copy C does not contain the archive job. Copy A has a longer retention time period than copy B and than the subclient retention options. Thus, the archive jobs will be available for 45 days in copy A.Example 4:Set the Retain Jobs for n years, n months, and n days to 0 years, 6 month, 0 days.There are 2 storage policy copies (A and B) and both copies contain the archive jobs. The retention of A and B is as follows: A: 45 days 3 cycles B: 45 days 4 cyclesSince, copies A and B have same retention period, the archive jobs will be available for 6 months in both the copies. Retain Jobs IndefinitelyThis is the default option with indefinite retention period. When you select this option, the archive jobs are retained indefinitely in the storage policy copy.Example 1:Set to Retain Jobs indefinite. There are 2 storage policy copies (A and B) and both copies contain the archive jobs. The retention of A and B are as follows: A: 15 days 3 cycles B: 45 days 4 cyclesSince the subclient retention is indefinite, the archive jobs will be available in copy B indefinitely. Click OK. It is highly recommended to have a storage policy with multiple synchronous copies with longer retention period than the primary copy. Data Aging prunes archive jobs that have exceeded the retention period of the copies.

Creating an Archiving Subclient for NFS Exports

Procedure

Page contents