Veritas NetBackup™ Vault Administrator's Guide
- About Vault
- Installing Vault
- Best Practices
- About preferred vaulting strategies
- About how to ensure that data is vaulted
- About not Vaulting more than necessary
- About preparing for efficient recovery
- About avoiding resource contention during duplication
- About how to avoid sending duplicates over the network
- About increasing duplication throughput
- About organizing reports
- Configuring NetBackup Vault
- Configuring Vault
- About Vault configuration
- About configuring Vault Management Properties
- About creating a vault
- About creating profiles
- Configuring a profile
- Vaulting and managing media
- About Vault sessions
- About monitoring a Vault session
- About the list of images to be vaulted
- About ejecting media
- About injecting media
- About using containers
- About vaulting additional volumes
- About using notify scripts
- Creating originals or copies concurrently
- Reporting
- Administering Vault
- About administering access to Vault
- About NetBackup Vault session files
- Using the menu user interface
- Troubleshooting
- Debug logs
- Appendix A. Recovering from disasters
- Appendix B. Vault file and directory structure
About using notify scripts
A Vault job can call notify scripts at specific points during the execution of the job. Vault includes template notify scripts that you can customize for your use. You can use a script for a robot, a vault, or a profile.
The template notify scripts are in the following directory:
UNIX
/usr/openv/netbackup/bin/goodies
Windows
install_path\NetBackup\bin\goodies
On Windows systems, the names of the scripts include a .cmd extension. They include instructions that can help you edit them for your needs.
To call and run a script, it must be copied to the NetBackup bin directory. A script must return a normal status (0) for the Vault job to continue processing. In case of failure, the script must return a nonzero status code to cause the Vault job to stop. On UNIX systems, the return status is communicated to the Vault job through the exit call. On Windows systems, the scripts communicate the return status in a file that is defined by the EXIT_STATUS environment variable, which is set by Vault.
The following scripts are provided with Vault:
Called by the Vault session after it starts. For example, you can use it to send notification when the Vault job begins. | |
Called by the Vault session before the list of media to be ejected (the eject.list) is built. Use this script to add media managed by Media Manager but not created by NetBackup or Vault to the eject list. The script writes media IDs to the addon_medialist file. Vault reads the addon_medialist file and ejects the media that is listed in that file during the current Vault session if the volume pool in which that media resides is in the list on the Eject tab of the Profile dialog box. | |
Called by the Vault session after the | |
Called at the end of eject processing. Use this script to send notification when the eject process ends. If the eject step is not configured for the profile, the vlt_endeject_notify script is not called. | |
Called by the Vault session immediately before it exits. One use for this script is to start another vault job. Then run Vault jobs in succession and avoid resource contention. |
Before you use a notify script, ensure that your systems are set up properly for email.
For information on how to use the notify script, see the following: