NetBackup™ for NDMP Administrator's Guide
- 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
- Attributes tab options for an NDMP policy
- Schedules tab options for an NDMP policy with Accelerator for NDMP enabled
- Clients tab options for an NDMP policy
- Backup selection options for 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)
- 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)
ndmp_end_path_notify.cmd script (Microsoft Windows)
For Windows media servers, you can create the batch scripts that provide notification whenever the client is finished writing to tape. These scripts must reside on the media server in the same directory as the NetBackup binaries:
install_path\NetBackup\bin
where install_path is the directory where NetBackup is installed.
You can create ndmp_end_path_notify scripts that provide notification for all backups or only for backups of a specific policy or schedule.
To create an ndmp_end_path_notify script that applies to all backups, name the script:
install_path\netbackup\bin\ndmp_end_path_notify.cmd
To create a script that applies only to a specific policy or policy and schedule combination, add a .policyname or .policyname.schedulename suffix to the script name. The following are two examples:
The following script applies only to a policy named days:
install_path\netbackup\bin\ndmp_end_path_notify.days.cmd
The following script applies only to a schedule that is named fulls, which is in a policy named days:
install_path\netbackup\bin\ndmp_end_path_notify.days.fulls. cmd
The first script affects all scheduled backups in the policy named days. The second script affects scheduled backups in the policy named days only when the schedule is named fulls.
For a given backup, NetBackup calls only one ndmp_end_path_notify script and checks for them in the following order:
ndmp_end_path_notify.policy.schedule.cmd ndmp_end_path_notify.policy.cmd ndmp_end_path_notify.cmd
For example, if there are both ndmp_end_path_notify.policy.cmd and ndmp_end_path_notify.policy.schedule.cmd scripts, NetBackup uses only ndmp_end_path_notify.policy.schedule.cmd.
Note:
If you also use ndmp_end_notify scripts, they can provide a different level of notification than the ndmp_end_path_notify scripts. For example, if you had one of each, they could be ndmp_end_notify.policy.cmd and ndmp_end_path_notify.policy.schedule.cmd.
When the backup completes, NetBackup passes the following parameters to the script:
Table: Script parameters for ndmp_end_path_notify.cmd (Microsoft Windows)
Parameter | Description |
|---|---|
%1 | Specifies the name of the client from the NetBackup catalog. |
%2 | Specifies the policy name from the NetBackup catalog. |
%3 | Specifies the schedule name from the NetBackup catalog. |
%4 | Specifies one of the following: FULL INCR CINC |
%5 | Specifies the status of the operation. It is the same as the status sent to the NetBackup server. This status is 0 for successful backups and 1 for partially successful backups. If an error occurs, the status is the value associated with that error. |
%6 | Note: The following file is not checked when using ndmp_end_path_notify. Specifies the results file that NetBackup checks for a return code from the script. NetBackup uses %6 to pass the file name and then expects the script to create the file in the same directory as the script. If the script applies to a specific policy and schedule, the results file must be named install_path\NetBackup\bin\NDMP_END_PATH_NOTIFY_RES.policy.schedule If the script applies to a specific policy, the results file must be named install_path\netbackup\bin\NDMP_END_PATH_NOTIFY_RES.policy If the script applies to all backups, the results file must be named install_path\NetBackup\bin\NDMP_END_PATH_NOTIFY_RES An echo 0> %6 statement is one way for the script to create the file. NetBackup deletes the existing results file before it calls the script. After the script runs, NetBackup checks the new results file for the status. The status must be 0 for the script to be considered successful. If the results file does not exist, NetBackup assumes that the script was successful. |
%7 | Specifies the pathname being backed up. |