Veritas NetBackup™ Administrator's Guide, Volume II
- NetBackup licensing models and the nbdeployutil utility
- About NetBackup licensing models
- About the capacity licensing model
- 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 selecting media in robots
- About selecting media in standalone drives
- About Tape I/O commands on UNIX
About reserving or releasing shared devices
The Shared Storage Option does not load firmware in SAN devices or communicate with hub or switch APIs. The Shared Storage Option can communicate with hub or switch APIs if you use the NetBackup shared_drive_notify script.
NetBackup runs the shared_drive_notify script when a shared drive is reserved or released.
The script requires the following parameters:
The name of the shared drive.
The name of the current scan host.
The operation, which is one of the following:
The host on which the script is executed needs SCSI access to the drive until it's released.
Informational only. It does not change the fact that the host that reserved the drive needs SCSI access.
Only the scan host needs SCSI access to the drive.
The host that executes the script has become the scan host. A host should not become a scan host while the drive is RESERVED.
The scan host may change between a RESERVED operation and a RELEASED operation.
The shared_drive_notify script resides in the following directory:
On Windows: install_path\VERITAS\Volmgr\bin
On UNIX/Linux: /usr/openv/volmgr/bin/shared_drive_notify
The script must be executable by the root user.
The script exits with status 0 upon successful completion.