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
- Troubleshooting
- Setting the log level
- Logging directories for Linux platforms
- Logging folders for Windows platforms
- Logging folders for multi-stream restore
- Restore from a snapshot fails with status 133
- Backup from snapshot fails with error 50
- Backup from snapshot parent job fails with error 4213: Snapshot import failed
- Backup host pool creation fails with the error "Failed to fetch host list"
- Snapshot job fails and the snapshot command does not recognize the volume name
- Accelerator enabled incremental backup of NetApp NAS volume
- Snapshot method: Auto
- Backup from snapshot jobs for NAS-Data-Protection policy fail with error 4213
- A full VCT-enabled indexing job runs, when followed by a non-VCT indexing job with a backup host prior to version to 10.3
- Backup from snapshot jobs for NAS data protection policy fail with error 927
- Error code: 930: No supported media server is available in the All_Media_Server_Pool to use to backup the NAS shares.
- Multi-stream restore from NAS array volume fails with the status: 174 Media manager - system error occurred.
- NAS job fails with the error: Crawler process timed out after 600 seconds waiting for streams to attach with shared memory.
- Section III. Using NDMP
- Introduction to NetBackup for NDMP
- About NetBackup for NDMP
- About Network Data Management Protocol (NDMP)
- Types of NDMP backup
- About NDMP policies in NetBackup
- About NetBackup storage units
- About assigning tape drives to different hosts
- About the NDMP backup process
- About the NDMP restore process
- About Direct Access Recovery (DAR)
- Snapshot Client assistance
- About NDMP multiplexing
- About NDMP support for Replication Director
- Limitations of Replication Director with NDMP
- About NDMP support for NetApp clustered Data ONTAP (cDOT)
- Installation Notes for NetBackup for NDMP
- Configuring NDMP backup to NDMP-attached devices
- About configuring NDMP-attached devices
- Authorizing NetBackup access to a NAS (NDMP) host
- About access for three-way backups and remote NDMP
- About Media and Device Management configuration
- Using the Device Configuration Wizard to configure an NDMP filer
- About adding volumes
- About verifying NDMP password and robot connection
- Adding NDMP storage units
- About creating an NDMP policy
- About environment variables in the backup selections list
- About appropriate host selection for NetApp cDOT backup policies
- About backup types in a schedule for an NDMP policy
- About enabling or disabling DAR
- Configuring NetBackup for NDMP in a clustered environment
- 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
- About NAS appliances support
- Non-vendor-specific information
- Vendor-specific information
- Dell EMC Isilon
- Dell EMC VNX
- Dell EMC Unity
- EMC Celerra
- Hitachi HDI/VFP
- Hitachi NAS (HNAS)
- HP X9000 NAS
- Huawei OceanStor V3
- IBM System Storage Nxxxx
- NEC Storage NV series
- NetApp
- Using NetBackup with NetApp's Data ONTAP 8.2 cluster mode
- Using a node name as the NDMP client name in all versions of NetBackup
- Using a data Vserver LIF as the NDMP client name in non-CAB-aware versions of NetBackup
- Using a cluster_mgmt vserver LIF as the NDMP client name in non-CAB-aware versions of NetBackup
- Using a cluster_mgmt Vserver LIF as the NDMP client name in CAB-aware versions of NetBackup
- Using NetBackup with NetApp's Data ONTAP 8.2 cluster mode
- Nexenta
- Nexsan
- Oracle Axiom Series
- Oracle Solaris Server
- Stratus V Series
- Backup and restore procedures
- Troubleshooting
- Using NetBackup for NDMP scripts
- About the NetBackup for NDMP scripts
- ndmp_start_notify script (UNIX)
- ndmp_start_notify.cmd script (Microsoft Windows)
- ndmp_end_notify script (UNIX)
- ndmp_end_notify.cmd script (Microsoft Windows)
- ndmp_start_path_notify script (UNIX)
- ndmp_start_path_notify.cmd script (Microsoft Windows)
- ndmp_end_path_notify script (UNIX)
- ndmp_end_path_notify.cmd script (Microsoft Windows)
- ndmp_moving_path_notify script (UNIX)
- ndmp_moving_path_notify.cmd script (Microsoft Windows)
- Introduction to NetBackup for NDMP
Using VCT for indexing
When Vendor Change Tracking (VCT) is enabled for a D-NAS policy, NetBackup does not perform any file system traversal for indexing a NAS volume. Instead, NetBackup uses the change list from the difference engine of the storage array to perform indexing of files and directories.
D-NAS policy supports the VCT-enabled index backups for NetApp, Dell EMC PowerScale (Isilon), Nutanix Files, and Qumulo NAS arrays.
Index job for the first full schedule:
When the index from snapshot for the first full schedule runs for a NAS volume. Then, NetBackup performs the file system traversal and generates an image catalog file.
File system traversal happens as the array vendors do not have any previous snapshot to get the change list.
Index job for the subsequent full schedule using VCT:
When VCT is enabled in the policy and a subsequent full schedule is run, NetBackup uses the following:
Previous full image catalog.
change list provided by the array vendor's difference engine from NBSM.
Using the previous catalogs, a synthetic catalog is created for the subsequent full schedule.
If number of streams per volume is changed from the last successful full index from snapshot, then NetBackup performs a file system traversal.
Index job for an incremental schedule using VCT:
When VCT is enabled in the policy and incremental schedule runs:
Differential incremental schedule: The change list is identified using the current snapshot and the snapshot of the last successful index job.
Cumulative incremental schedule: The change list is identified using the current snapshot and the snapshot of the last successful full index job.
Following are the file entries that are added to the image catalog for index operation as per the schedule:
Full schedule: The full set of files.
Differential incremental schedule: Files that are added or modified after the last index job run for any schedule.
Cumulative incremental schedule: Files that are added or modified after the index job run for the last full schedule.
For a VCT-enabled D-NAS policy, the Snapshot or Replication retention period in SLP must be greater than the policy's schedule frequency.
VCT is not applicable if the base snapshot is not available.
The expiration period of the previous full and subsequent incremental snapshots is postponed until the next full schedule is completed.
For non-VCT supported arrays, the index job continues to use mount and file system crawl method.