Veritas NetBackup™ for NDMP Administrator's Guide
- Introduction to NetBackup for NDMP
- About NetBackup for NDMP
- Types of NDMP backup
- About assigning tape drives to different hosts
- Installation Notes for NetBackup for NDMP
- Configuring NDMP backup to NDMP-attached devices
- About Media and Device Management configuration
- About creating an NDMP policy
- Backup selection options for an NDMP policy
- About enabling or disabling DAR
- Configuring NDMP backup to NetBackup media servers (remote NDMP)
- Configuring NDMP DirectCopy
- About NDMP DirectCopy
- Using NDMP DirectCopy to duplicate a backup image
- Accelerator for NDMP
- Remote NDMP and disk devices
- Using the Shared Storage Option (SSO)
- Backup and restore procedures
- About NetBackup for NDMP logs
- NetBackup for NDMP troubleshooting suggestions
- About robot tests
- Using NetBackup for NDMP scripts
ndmp_end_notify.cmd script (Microsoft Windows)
For Windows media servers, you can create the batch scripts that provide notification whenever the client completes a backup. These scripts must reside on the media server in the same directory as the NetBackup binaries:
where install_path is the directory where NetBackup is installed.
You can create ndmp_end_notify scripts that provide notification for all backups or only for backups of a specific policy or schedule.
To create an ndmp_end_notify script that applies to all backups, name the script:
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:
The following script applies only to a schedule that is named fulls, which is in a policy named days:
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_notify script and checks for them in the following order:
ndmp_end_notify.policy.schedule.cmd ndmp_end_notify.policy.cmd ndmp_end_notify.cmd
For example, if there are both ndmp_end_notify.policy.cmd and ndmp_end_notify.policy.schedule.cmd scripts, NetBackup uses only ndmp_end_notify.policy.schedule.cmd.
If you also usendmp_start_notify scripts, they can provide a different level of notification than the ndmp_end_notify scripts. For example, if you had one of each, they could be ndmp_start_notify.policy.cmd and ndmp_end_notify.policy.schedule.cmd.
When the backup completes, NetBackup passes the following parameters to the script:
Table: Script parameters for ndmp_end_notify.cmd (Microsoft Windows)
Specifies the name of the client from the NetBackup catalog.
Specifies the policy name from the NetBackup catalog.
Specifies the schedule name from the NetBackup catalog.
Specifies one of the following:
FULL INCR CINC
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.
The following file is not checked at the end of a backup.
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
If the script applies to a specific policy, the results file must be named
If the script applies to all backups, the results file must be named
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.