Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- Creating and viewing the licensing report
- Reviewing a capacity licensing report
- Reconciling the capacity licensing report results
- Reviewing a traditional licensing report
- Additional configuration
- About dynamic host name and IP addressing
- About busy file processing on UNIX clients
- About the Shared Storage Option
- About configuring the Shared Storage Option in NetBackup
- Viewing SSO summary reports
- About the vm.conf configuration file
- Holds Management
- Menu user interfaces on UNIX
- About the tpconfig device configuration utility
- About the NetBackup Disk Configuration Utility
- Reference topics
- Host name rules
- About reading backup images with nbtar or tar32.exe
- Factors that affect backup time
- NetBackup notify scripts
- Media and device management best practices
- About TapeAlert
- About tape drive cleaning
- How NetBackup reserves drives
- About SCSI persistent reserve
- About the SPC-2 SCSI reserve process
- About checking for data loss
- About checking for tape and driver configuration errors
- How NetBackup selects media
- About selecting media in robots
- About selecting media in standalone drives
- About Tape I/O commands on UNIX
The backup_exit_notify.cmd script (on Windows) and the backup_exit_notify script (on UNIX) run on the master server. It's called to perform site-specific processing when an individual backup completes.
The scripts are located in the following directories:
On Windows: Install_path\NetBackup\bin\backup_exit_notify.cmd
On UNIX: /usr/openv/netbackup/bin/backup_exit_notify
NetBackup passes the following parameters to the script:
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 (differential incremental), CINC (cumulative incremental), UBAK, UARC
Specifies the exit code for the entire backup job.
Specifies the backup stream number for a job.
0 = The backup job is not running multiple data streams.
-1 = The job is a parent job.
Specifies whether the job will retry.
0 = The job is not complete and will retry.
1= The job is complete and will not retry.
If the system is configured to make 3 attempts in 12 hours, the job could run this script up to 3 times. On the final attempt, the done_trying flag is set to 1. The job has either completed successfully or has failed and exhausted the number of tries.
See the following UNIX example:
backup_exit_notify clientname1 pol_prod sched_fulls FULL 0 -1 1
backup_exit_notify clientname2 pol_prod sched_incr INCR 73 0 1