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
How to redirect track logs for Accelerator for NDMP
Track log size is relative to the size and number of files in a backup. In some cases, you may need to relocate the track logs to a different volume because of space issues. In these cases, it is recommended that you "redirect" the track logs to a volume where there is sufficient disk space.
One copy of the track log exists on the primary server and another copy exists on a media server in the following directories:
Primary server:
UNIX:
/usr/openv/netbackup/db/trackWindows:
install_path\NetBackup\db\trackMedia server:
UNIX:
/usr/openv/netbackup/trackWindows:
install_path\NetBackup\track
To redirect these directories, complete the appropriate procedures in this topic. After completion, the next Accelerator-enabled backup that is executed redirects the track logs it creates to the directory you specified.
To redirect the track log directories on UNIX systems:
Rename the track log directories to make backup copies:
On the primary server:
# mv /usr/openv/netbackup/db/track /usr/openv/netbackup/db/track.sv
On the media server:
# mv /usr/openv/netbackup/track /usr/openv/netbackup/track.sv
Copy the backup to a new location:
On the primary server:
# cp -rp /usr/openv/netbackup/db/track.sv/* <path to new destination directory for track logs>
On the media server:
# cp -rp /usr/openv/netbackup/track.sv/* <path to new destination directory for track logs>
Create symbolic links from track log directories to the desired locations. For example, if the desired directory is /vol1/track, enter the following command:
On the primary server:
# ln - s /vol1/track /usr/openv/netbackup/db/track
On the media server:
# ln - s /vol1/track /usr/openv/netbackup/track
- After you have verified that everything works properly, you can remove the backup
track.svdirectory to free up space on the original volume.
To redirect the track log directories on systems with Windows Server:
Rename the track log directories to make backup copies:
On the primary server:
> move "install_path\NetBackup\db\track" "install_path\NetBackup\db\track.sv"
On the media server:
> move "install_path\NetBackup\track" "install_path\NetBackup\track.sv"
Copy the backup to a new location:
On the primary server:
> xcopy /e "install_path\NetBackup\db\track.sv" "<path to new destination directory for track logs>"
On the media server:
> xcopy /e "install_path\NetBackup\track.sv" "<path to new destination directory for track logs>"
- Before performing an Accelerator-enabled backup, use mklink to link the <install_dir>\NetBackup\track directory to the desired directory. For example, if the desired directory is
E:\track, enter the following command:> mklink /D "<install_dir>\NetBackup\track" E:\track
- After you have verified that everything works properly, you can remove the backup
track.svdirectory to free up space on the original volume.
More information about Accelerator for NDMP is available: