Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- About NetBackup licensing models
- nbdeployutil utility options
- Creating and viewing the licensing report
- After creating a traditional licensing report
- After creating a capacity licensing report
- Reconciling the capacity licensing report results
- 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 Tape I/O commands on UNIX
drive_mount_notify script (on UNIX)
The NetBackup tpreq command runs the drive_mount_notify
script (if it exists) immediately after media is mounted in a pre-selected, robotic drive. This script is not valid for standalone drives.
Each time a tape volume is mounted, this script gathers information on the drive that is mounted. This script also lets you perform special-handling. For example, you can use the script to gather log sense or other data from a drive and place it in an output file. You can change the information that the script gathers by modifying the script.
After the script runs, control is then returned to NetBackup to resume processing.
This script is located in the following directory:
/usr/openv/volmgr/bin/goodies
To use this script, activate it and place it into the /usr/openv/volmgr/bin directory. See the script for instructions about how to activate it and how to modify it.