After installing the Linux File System Core and Linux File System packages on the data access nodes, you must configure a network share pseudo-client, a backup set, and a subclient to manage your network file system data.
When you configure the network share pseudo-client to back up NFS exports, make sure to select only Linux clients as data access nodes.
Important
For existing network share clients and subclients, we recommend that you continue to use single node (proxy) for backup and restore operations. Use multiple nodes for back and restore operations only on newly created clients and subclients.
When you add data access nodes to a network share pseudo-client, you can select a client or a client group from the available nodes list. We recommend that you create separate client groups for Linux clients to quickly associate the required data access nodes for backup and restore operations.
Support for Archiving
Multiple node backup for network share clients supports archiving on UNIX.
Scanning and stubbing phases are run from the first node of the list of selected data access nodes for the pseudo-client; backup operation is run from all selected data access nodes.
For more information about OnePass for UNIX File Systems, see OnePass for UNIX File Systems.
Note
-
Multiple node archiving is supported only on Linux and AIX.
-
Multiple node archiving with the NFS server data access node as a backup node is not supported because recall operations that are run from other backup nodes might tend to hang.
Scripts for Pre-Processes and Post-Processes
The scripts for pre-processes and post-processes must be present in the same location on all data access nodes.
Optimized Backup of Hard Link Files
To enable optimized backup of hard link files for NFS Exports, see Configuring Optimized Backups for Hard Links.