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
Non-vendor-specific information
The NetBackup operating systems compatibility lists provide the most up-to-date list of supported operating systems, with notes on supported hardware platforms. NDMP compatibility is listed as a column in the NetBackup Server section for each operating system in the compatibility list:
http://www.netbackup.com/compatibility
Note:
NetBackup for NDMP is installed on a master or media server, not on a client.
The information in this document may apply to many different NetBackup releases. To find if your device and its features are supported at a particular NetBackup level, refer to the NetBackup Hardware Compatibility List (HCL) for the version of NetBackup that you are running:
http://www.netbackup.com/compatibility
Use the tpconfig and tpautoconf commands as described under "Example Configuration Sequence" in each of the following sections of this document for particular NDMP hosts.
For NAS hosts that support Direct Access Recovery (DAR), NetBackup enables DAR by default.
When restoring files from NetBackup backups of NAS filers that use older versions of the NDMP protocol (V2 and V3), the destination path for the restore must end with the original folder and file name, even if you are restoring the files to a different location. (This restriction does not apply to NAS filers that use the NDMP protocol V4.)
If the original backup path was /vol/vol1/mydir/myfile
, the destination path for restore to a different location must end with /mydir/myfile
. Otherwise, NetBackup appends /mydir/myfile
to the end of the destination path.
For example, to restore /vol/vol1/mydir/myfile
to a folder under/vol/vol2/
, specify /vol/vol2/mydir/myfile
as the destination.
For NAS filers that use NDMP V4, you can specify a different subfolder or file name. For example, /vol/vol1/mydir/myfilecan
be restored to /vol/vol2/mydir2/myfile_restored
.
For any restrictions unique to a particular NAS filer, see the appropriate section in this document for your filer.
The NDMP protocol specification uses environment variables to control backup and restore operations. These variables are defined by each vendor individually, with some amount of adherence to a common, defined set. NetBackup controls the setting of some of those variables without the ability for a user to change them (such as LEVEL and USER), and some of them are modified by NetBackup settings and policy configuration (such as DIRECT and FILESYSTEM). It is possible to change some of the variables in the include list of a NetBackup policy, such as variables for which NetBackup just passes a default value (HIST, TYPE) and for those variables that are vendor-specific.
With such a large set of possibly vendor-specific implementations of environment variables, it is impossible to provide an exhaustive list in this document. An attempt has been made to document those variables that were found during testing to have the most impact. Refer to vendor documentation for more information.