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
- Configuring Storage Lifecyle Policies for D-NAS
- About storage lifecycle policies
- Snapshot operation in SLP
- Creating a storage lifecycle policy for snapshots and snapshot replication
- Replication operation in the SLP
- Index from snapshot operation in an SLP
- Backup from snapshot operation in an SLP
- Duplication operation in an SLP
- Retention types for SLP operations
- Volume multi-host backup
- Configure D-NAS policy for NAS backups
- About policies for NAS backups
- Planning for policies
- Prerequisites for D-NAS policies
- Configure D-NAS policy for NAS volumes
- Policy attributes
- Creating schedule attributes for policies
- Configuring the Start window
- Configuring the exclude dates
- Configuring clients
- Configuring backup selections
- Configuring exclude lists
- Ordering of backup from snapshot jobs
- About mixed mode volumes
- Configuring include and exclude lists
- Auto-resume backup for incomplete backup jobs
- Using Accelerator
- Using Vendor Change Tracking
- Using true image restore
- Replication using D-NAS policy
- Restoring from D-NAS backups
- Multi-stream restores from D-NAS backups
- Considerations for restoring from D-NAS backups
- About the Overwrite existing file option during restore
- RBAC role for D-NAS restores
- Scanning for malware
- Restore everything to a different location
- Restore individual files and folders to different locations
- Original location restores for D-NAS Policy
- Point-in-time rollback
- Multi-stream restores 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
- Exclude list is not working during backup
- Restore from a snapshot fails with status 133
- Backup from snapshot jobs do not start after the snapshot job completes successfully
- 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.
- 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.
- D-NAS backup fails with the error: The file system crawler process timed-out waiting for streams to attach with shared memory. (3003)
- Isilon backup from snapshot failed with the Snapshot cannot be mounted error.
- Discovery and snapshot operations fail with the errors 156 and 1542
- 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 creating an NDMP policy
- About appropriate host selection for NetApp cDOT backup policies
- Attributes tab options for an NDMP policy
- Schedules tab options for an NDMP policy with Accelerator for NDMP enabled
- About backup types in a schedule for an NDMP policy
- Clients tab options for an NDMP policy
- Backup selection options 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
About NetBackup Accelerator for NDMP
Note:
Currently only NetApp filers and Isilon filers are supported with the NetBackup Accelerator for NDMP option. (See the NetBackup Compatibility List for all Versions for the most recent list of supported versions of each NAS vendor.)
For NetApp filers, Accelerator for NDMP supports only the DUMP format. Consult your NetApp documentation for specific details about its DUMP format.
NetBackup's Accelerator option makes NDMP backups for NetApp and Isilon filers run faster than normal NDMP backups. NetBackup Accelerator increases the speed of full backups by using the filer's change detection techniques to identify the modifications that occurred since the last backup. After an initial full backup that protects all data from the filer, NetBackup Accelerator backs up only the changed data from the filer to the media server. The media server combines the changed data with any previous backup images to create a new full backup image; if a file or portion of a file is already in storage and has not been changed, the media server uses the copy in storage rather than reading it from the filer to complete the backup image. The end result is a faster NetBackup NDMP backup.
Note:
For NetApp filers, you can expect to see Accelerator optimization in both full backups (regular and forced rescan) and incremental backups. For Isilon filers, you can expect to see Accelerator optimization only in full backups (regular - not forced rescan).
Accelerator for NDMP has the following advantages:
Supports all NetBackup NDMP features, such as replication, DAR restores, and multiplexing.
Creates a compact backup stream that uses less network bandwidth between the filer and NetBackup servers.
Reduces the I/O and CPU overhead on the media server.
To configure Accelerator for NDMP, select the check box that is found on the NDMP policy Attributes tab. No change to the filer is required.
Note:
For Isilon filers only, note the following behaviors with environmental variables:
With Isilon filers, if you set the HIST environment variable in a NetBackup NDMP backup policy with Accelerator enabled, you may specify only the value D (that is, SET HIST=D). D specifies a directory/node file history format. If you specify any other value for the HIST variable, NetBackup generates a message that asks you to change the value to D. If you do not use a HIST variable in the policy, the backup should complete successfully.
If you change any of the variables in a NetBackup NDMP backup policy with Accelerator enabled, the Accelerator optimization will be 0% until you run a second full backup with the same variables. When the policy's variables change, a new baseline image is created with the first full backup. You will see Accelerator optimization only after the second full backup with the same variables.
More information about environmental variables in NDMP policies is available:
See About environment variables in the backup selections list.
Note:
If you include the smtape environment variable for NetApp filers in an NDMP backup policy, no optimization is seen with Accelerator for NDMP enabled. The smtape environment variable always backs up an entire volume as if it is a full backup of a single file. Consult your NetApp filer documentation for specific details about smtape. See About NAS appliances support. for information about smtape in a NetBackup backup policy is available in the NetApp section.
If your NDMP policies include combinations of filers from NetApp, Isilon, and filers from other vendors, only the NetApp and Isilon filers use the Accelerator option. Messages in the job details identify which filers use the Accelerator option and when the option is used. More information about these job detail messages is available:
See Accelerator messages in the NDMP backup job details log.
Note:
Unlike non-accelerated NDMP backups, accelerated NDMP backups do not use NDMP dump levels 0-9 to determine changed files. Instead, BASE_DATE and DUMP_DATE are used to determine changed files. BASE_DATE provides the timestamp of the most recent full or incremental backup. DUMP_DATE provides the timestamp of the currently running backup. Only the data that has changed between the BASE_DATE and the DUMP_DATE is backed up when Accelerator for NDMP is enabled.
Dump level messages from the filer continue to be included in the job detail log. However, the message please ignore references to LEVEL in future messages also appears in the job details as a reminder that dump levels are not used with Accelerator for NDMP.
How Accelerator works with NDMP backups:
First full backup with Accelerator
The first full NDMP backup job with the Accelerator option enabled is similar to a normal full backup. It may run slightly longer than a non-Accelerator backup. It backs up all of the data from the filer, provides a baseline backup image, and creates an initial track log.
Note:
If you first enable Accelerator when the next scheduled backup is an incremental backup, NetBackup does not automatically trigger a full backup image, as is the case with NetBackup Accelerator for non-NDMP policies. With Accelerator for NDMP, incremental backups continue to run as scheduled. An initial track log is also created after the option is enabled, and with NetApp filers, you should see faster incremental backups. The next full backup runs only when it is scheduled.
Incremental backups with Accelerator
Subsequent incremental backup jobs back up only the data that changed since the last backup job.
Next full backups with Accelerator
Subsequent full backup jobs back up only the data that changed since the last backup job. The track log is used to determine what data can be included from previous backups, including the previous full backup and all of the incremental backups that follow it. NetBackup then creates a full backup image that includes all of the filer's data.
Forced rescan full backups with Accelerator
The option provides a safety net by establishing a new baseline for the next Accelerator backup. When you include this option, which is found on the policy's Schedules tab, all the data on the filer is backed up. This backup is similar to the first full backup with Accelerator; it provides a new baseline for the backups that follow. If you set up a weekly full backup schedule with the option, you can supplement the policy with another schedule that enables Accelerator forced rescan. You can set the schedule to run every 6 months or whenever it is appropriate for your environment. With NetApp filers, expect backups with Accelerator forced rescan to run slightly longer than accelerated full backups. With Isilon filers, backups with Accelerator forced rescan may run as longer as a first full backup with Accelerator. More information about these options is available: