Using a data Vserver LIF as the NDMP client name in non-CAB-aware versions of NetBackup
With this method, node-scope-mode is disabled on the cluster and a data Vserver name is configured as the client name in an NDMP policy in NetBackup
Pros
Because the NetBackup catalog tracks backups by client name, it is easier to track down data from that Vserver when restoring.
Assuming that care has been taken if a volume moves to another node, all volumes backed up using a Vserver name will be displayed when performing a restore.
Cons
The cDOT filer will only send data from volumes that are associated with a Vserver and are hosted on the same node as the data Vserver LIF. Therefore, if only a volume moves to another node without its corresponding LIF, it will not be backed up. This is not an error. Users will need to very carefully monitor backups to ensure that all of their data was backed up.
If a volume moves to another node, the vserver LIF must be moved to the other node as well using the following command:
net int migrate -vserver <vserver_name> -lif <vserver-LIF> -dest-node <dest-node> -dest-port <dest-port>
Because a data Vserver cannot see any tape drives attached to the cluster, every backup of a data Vserver will be a three-way backup.