Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- How capacity licensing works
- Creating and viewing the licensing report
- Reviewing a capacity licensing report
- Reconciling the capacity licensing report results
- Reviewing a traditional licensing report
- Reviewing an NEVC 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
bpstart_notify.bat script (Windows clients)
To use this script, copy the following file from the server:
Then place the file on the client in the same directory as the NetBackup client binaries:
Where Install_path is the directory where NetBackup is installed.
You can create bpstart_notify scripts that provide notification for all backups or for backups of a specific policy or schedule.
To create a script that applies to all backups, name the script bpstart_notify.bat.
To create a bpstart_notify 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 examples of bpstart_notify script names:
The following script applies only to a policy named days:
The following script applies only to a schedule that is named fulls in a policy named days:
The bpstart_notify script also runs for NetBackup catalog backups if a .policyname[.schedule] is not specified.
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 bpstart_notify script and checks for them in the following order:
bpstart_notify.policy.schedule.bat bpstart_notify.policy.bat bpstart_notify.bat
For example, if there are both bpstart_notify.policy.bat and bpstart_notify.policy.schedule.bat scripts, NetBackup uses only the bpstart_notify.policy.schedule.bat script.
bpend_notify scripts can provide a different level of notification than the bpstart_notify scripts. For example, to use one of each, the script names might be bpstart_notify.policy.bat and bpend_notify.policy.schedule.bat.
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, CINC, UBAK, UARC
Specifies that the status of the operation is always 0 for bpstart_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
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.
The server expects the client to respond with a continue message within the time that the BPSTART_TIMEOUT option specifies on the server. The default for BPSTART_TIMEOUT is 300 seconds. If the script needs more time than 300 seconds, increase the value to allow more time. (The BPSTART_TIMEOUT option corresponds to the Backup start notify timeout on the host properties.)