NetBackup™ NAS Administrator's Guide
- Section I. About NAS backups
- Section II. Using NAS-Data-Protection (D-NAS)
- D-NAS overview
- D-NAS Planning and Tuning
- Pre-requisites for D-NAS configuration
- Volume multi-host backup
- Configure D-NAS policy for NAS volumes
- Using accelerator
- Using Vendor Change Tracking
- Replication using D-NAS policy
- Restoring from D-NAS backups
- Troubleshooting
- Section III. Using NDMP
- Introduction to NetBackup for NDMP
- About NetBackup for NDMP
- Types of NDMP backup
- About assigning tape drives to different hosts
- Installation Notes for NetBackup for NDMP
- Configuring NDMP backup to NDMP-attached devices
- About Media and Device Management configuration
- About creating an NDMP policy
- About enabling or disabling DAR
- Configuring NDMP backup to NetBackup media servers (remote NDMP)
- Configuring NDMP DirectCopy
- Accelerator for NDMP
- Remote NDMP and disk devices
- Using the Shared Storage Option (SSO) with NetBackup for NDMP
- NAS appliance information for NDMP
- Vendor-specific information
- EMC Celerra
- NetApp
- Using NetBackup with NetApp's Data ONTAP 8.2 cluster mode
- Using NetBackup with NetApp's Data ONTAP 8.2 cluster mode
- Backup and restore procedures
- Troubleshooting
- Using NetBackup for NDMP scripts
- Introduction to NetBackup for NDMP
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.