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
General NetBackup for NDMP operating notes and restrictions
Before you try to troubleshoot a suspected problem, review the following operating notes:
A tape that was created on an NDMP storage unit is in backup format. It cannot be restored from a non-NDMP storage unit. If you duplicate an NDMP backup image, the new copy is still in backup format. It cannot be used for restores on a non-NDMP storage unit.
In the backup selections list for an NDMP policy, you can include only directory paths. Individual file names are not allowed. Wildcard characters are allowed in backup selections, though some limitations apply to some filers. More information about wildcards in NDMP backup selections is available:
See Wildcard characters in backup selections for an NDMP policy.
In a NetBackup NDMP policy, you cannot include a path in the file list that is more than 1024 characters long. This limitation may be further restricted for certain vendors. See About NAS appliances support. for path name length information for specific filers.
Observe the following restrictions to the use of the ALL_FILESYSTEM directive and the VOLUME_EXCLUDE_LIST directive:
A VOLUME_EXCLUDE_LIST statement may include a maximum of 256 characters. Create multiple VOLUME_EXCLUDE_LIST statements if necessary to avoid exceeding the limit of 256 characters. If you specify more than 256 characters, the volume list is truncated. A truncated statement may result in a backup job failure, and the error message Invalid command parameter(20) is displayed. VOLUME_EXCLUDE_LIST applies only to ALL_FILESYSTEMS. It does not apply to explicit backup selections or wildcard-based backup selections.
With NetBackup Replication Director, if the backup selection includes read-only volumes or full volumes, an NDMP backup job fails with the status code 20 (Invalid command parameter(20)). If you encounter a similar NDMP backup job error, review the
ostfilogs to identify the volumes for which the failure occurred. You can use VOLUME_EXCLUDE_LIST statements with the ALL_FILESYSTEMS statement to exclude the read-only volumes and the volumes with insufficient space.Note:
This restriction applies only to NetBackup Replication Director environments.
More information about these directives is available:
On UNIX systems, the NetBackup avrd process uses Internet Control Message Protocol (ICMP) to ping NDMP hosts to verify network connectivity. This protocol is required for the NetBackup for NDMP product.
If backup jobs or restore jobs are running slowly, verify that the network interface cards (NIC) are set to full duplex. Half-duplex often causes poor performance. For assistance viewing and resetting duplex mode for a particular NAS host, consult the documentation that the manufacturer provides. You may be able to use the ifconfig (or ipconfig) command, as explained in the NetBackup Troubleshooting Guide.
Do not perform incremental backups of the same NDMP data from two different policies. Incremental backups performed by one of the policies may be incomplete, because NDMP filers perform level-based incremental backups instead of time-based incremental backups. Consider the following example:
Policy A performs a full backup of /vol/vol1 (level 0).
Policy B then performs a full backup of /vol/vol1 (level 0). The filer now considers the policy B backup to be the last full (level 0) backup of /vol/vol1.
Policy A performs an incremental backup of /vol/vol1 (level 1). The policy A incremental backup captures only the data that changed since the full backup that was done by policy B. The incremental backup misses any changes that occurred between the policy A full backup and the policy B full backup.
NDMP restore jobs may complete successfully even though no data (0 KB) has been restored. This situation can occur when a target volume does not have enough space for an image you are trying to restore.
Workaround: Check the restore job details for entries similar to the following messages:
mm/dd/yyy hh:mm:ss PM - Info ndmpagent(pid=11071) fas2050c1: RESTORE: We recommend that 19 inodes and 907620 kbytes of disk space be available on the target volume order to restore this dump. You have 466260 inodes and 5316 kbytes of disk space on volume /vol/abc_15gb mm/dd/yyy hh:mm:ss PM - Info ndmpagent(pid=11071) fas2050c1: RESTORE: This restore will proceed, but may fail when it runs out of inodes and/or disk space on this volume.
Confirm that the target volume does not have enough space for the restore image. If it does not, either free up enough space on the volume to complete the restore job successfully or specify a different restore volume.