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
Accelerator messages in the NDMP backup job details log
This topic provides explanations of some specific messages that appear in an NDMP job details log when Accelerator for NDMP is enabled.
The messages in the NetBackup job details include messages that are generated directly from the filer. To find the messages from the filer, look for the NDMP host name in the message following the PID number as in the following example:
mm/dd/yyy hh:mm:ss - Info ndmpagent (pid=10780) [NDMP_host_name]: Filetransfer: Transferred 146841088 bytes in 2.855 seconds throughput of 50231.929 KB/s
Note:
Some messages that are generated directly from the filer, such as filer volume is full, may require your immediate attention. Consult the documentation for the filer to determine how to resolve any issues with the filer that are indicated by a message from the filer in the job details.
Messages similar to the following appear in the job details log for the first full NDMP backup that uses Accelerator for NDMP.
mm/dd/yyyy 1:28:47 PM - Info bpbrm(pid=3824) accelerator enabled ... ... mm/dd/yyyy 1:28:53 PM - Info ndmpagent(pid=10556) accelerator optimization is <off>, unable to locate accelerator tracklog ... ... mm/dd/yyyy 1:29:05 PM - Info ndmpagent(pid=10556) accelerator sent 1310720 bytes out of 1310720 bytes to server, optimization 0.0%
Note the following items about messages for the first Accelerator-enabled full backup:
accelerator enabled
This message indicates that the Accelerator option is being used.
accelerator optimization is <off>, unable to locate accelerator tracklog
Because this is the first full backup, NetBackup creates a new track log. More information about the locations of the track log is available:
accelerator sent 1310720 bytes out of 1310720 bytes to server, optimization 0.0%
Because this is the first full backup, all data is backed up and no optimization occurs yet.
Messages similar to the following appear in the job details log for subsequent incremental NDMP backups that use Accelerator for NDMP.
mm/dd/yyyy 2:01:58 PM - Info ndmpagent(pid=8652) accelerator optimization is <on> mm/dd/yyyy 2:01:58 PM - Info ndmpagent(pid=8652) BASE_DATE will be used to determine changed files for accelerator mm/dd/yyyy 2:01:58 PM - Info ndmpagent(pid=8652) please ignore references to LEVEL in future messages ... ... mm/dd/yyyy 2:14:14 PM - Info ndmpagent(pid=10044) accelerator sent 1104896 bytes out of 100310720 bytes to server, optimization 15.7%
Note the following items about messages for the subsequent incremental accelerator backups:
accelerator optimization is <on>
This message indicates that a track log exists and the backup shall perform with the Accelerator option.
BASE_DATE will be used to determine changed files for accelerator and please ignore references to LEVEL in future messages
These messages are a reminder that Accelerator for NDMP uses BASE_DATE and DUMP_DATE rather than dump levels to identify changed data. Messages that refer to dump levels come from the filer. However, the message to ignore references to LEVEL also appears in the job detail logs as a reminder that dump levels are not used with Accelerator for NDMP.
accelerator sent 1104896 bytes out of 100310720 bytes to server, optimization 15.7%
This message provides the amount of data that was sent to the server and the percentage of optimization that was realized.
Messages similar to the following appear in the job details log for subsequent full NDMP backups that use Accelerator for NDMP.
mm/dd/yyyy 2:01:58 PM - Info ndmpagent(pid=8652) accelerator optimization is <on> mm/dd/yyyy 2:01:58 PM - Info ndmpagent(pid=8652) BASE_DATE will be used to determine changed files for accelerator mm/dd/yyyy 2:01:58 PM - Info ndmpagent(pid=8652) please ignore references to LEVEL in future messages ... ... mm/dd/yyyy 1:40:27 PM - Info ndmpagent(pid=12244) accelerator sent 887296 bytes out of 1159725056 bytes to server, optimization 99.9%
Note the following items about messages for the subsequent incremental accelerator backups:
accelerator optimization is <on>
This message indicates that a track log exists and the backup shall perform with the Accelerator option.
BASE_DATE will be used to determine changed files for accelerator and please ignore references to LEVEL in future messages
These messages are a reminder that Accelerator for NDMP uses BASE_DATE and DUMP_DATE rather than dump levels to identify changed data. Messages that refer to dump levels come from the filer. However, the message to ignore references to LEVEL also appears in the job detail logs as a reminder that dump levels are not used with Accelerator for NDMP.
accelerator sent 887296 bytes out of 1159725056 bytes to server, optimization 99.9%
This message provides the amount of data sent to the server and the percentage of optimization that was realized.
Messages similar to the following appear in the job details log for full NDMP backups that use Accelerator for NDMP with the Accelerator forced rescan option.
mm/dd/yyyy 2:13:43 PM - Info bpbrm(pid=8628) Accelerator enabled backup with "Accelerator forced rescan", all data will be scanned and processed.Backup time will be longer than a normal Accelerator enabled backup. ... ... mm/dd/yyyy 2:13:46 PM - Info ndmpagent(pid=10044) accelerator optimization is <on> but 'forced rescan' is enabled
Note the following items about messages for accelerator forced rescan backups:
Accelerator enabled backup with "Accelerator forced rescan", all data will be scanned and processed. Backup time will be longer than a normal Accelerator enabled backup and accelerator optimization is <on> but 'forced rescan' is enabled
These messages indicate that a forced rescan is enabled and that the job shall run longer than a normal Accelerator full backup. Though accelerator optimization is on, the job may run slightly longer than accelerated full backups.