Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and usage reporting
- 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
- DELETE 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
NetBackup notify scripts
NetBackup provides scripts or batch files that can collect information and be used to notify administrators of specific events.
All of the NetBackup notify scripts are located in the goodies directory, which contains sample shell scripts to modify. Three volmgr notify scripts are installed in the volmgr goodies directory. The scripts in the goodies directories are not supported but are intended as examples to customize.
The goodies directories are found in the following locations:
On Windows: Install_path\NetBackup\bin\goodies\
On UNIX: /usr/openv/netbackup/bin/goodies
Ensure that others can run the script after modifying. To do so, run chmod ugo+rx script_name, where script_name is the name of the script.
If you use either the bpstart_notify or bpend_notify scripts, do not include any commands that write to stdout. NetBackup sends the output that is written to stdout to the server as part of the backup. The resulting backup can abort with an error message that pertains to block sizes.
Also, ensure that all commands in the scripts are appropriate to the client platform. For example, the -s parameter is invalid for the UNIX mail command on some UNIX platforms. Its use can cause data to be written to stdout or stderr.
Many NetBackup processes set a limit on the number of concurrently open file descriptors that are allowed. That limit is inherited by the notify scripts run by the process. In the rare event that a command invoked by a notify script requires many additional file descriptors, the script must increase the limit appropriately before invoking the command.
The following topics describe the scripts that are active on the master server and those that are active on the client.
To use the client scripts, first create the script on the client.
Additional comments appear in the scripts.