Using a node name as the NDMP client name in all versions of NetBackup
With this method, node-scope-mode is enabled on the cluster, and the name of each node is provided as a client name in an NDMP policy in NetBackup.
Pros
Volumes can be backed up to locally attached tape drives, instead of over a network connection (3-way).
Using NetBackup 7.6 and higher, with the introduction of the ALL_FILESYSTEMS file list directive, it is not necessary to modify the NetBackup policy if a volume moves to another node.
Cons
When a volume moves to another node, the moved volume and data is now tracked by that other node name in NetBackup. When performing a restore, NetBackup will display all backups from the current selected node. However, to restore data from backups taken when the volume was under a different node, you will need either to maintain a list of those prior nodes or search the other nodes in the cluster for that specific nodename and volume combination.
Once a volume has been moved, three-way backups from the current node to the original node may occur depending on policy and storage unit configuration.
If using a version of NetBackup before 7.6, or not using the ALL_FILESYSTEMS file list directive, and if a volume moves to a different node in the cluster, the NDMP host name in the NetBackup policy must be modified to that of the node now hosting the volume, using the following command:
/usr/openv/netbackup/bin/admincmd/bpplclients policy_name -rename old_host_name new_host_name