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
About SCSI reserve limitations
The NetBackup implementation of SCSI persistent reserve and SPC-2 reserve has the following limitations:
SCSI persistent reserve and SPC-2 reserve do not apply to NDMP drives.
The NDMP filer is responsible for providing exclusive device access.
Third-party copy configurations must be configured correctly.
To retain reservation of a tape device during a third-party copy backup, configure the NetBackup mover.conf file.
Do not use SCSI persistent reserve on the drive paths that are used for third-party copy backups.
See the NetBackup Snapshot Client Administrator's Guide, available at the following URL:
With SPC-2 SCSI reserve, devices may remain reserved after a failover in cluster environments or multi-path environments with failover capability.
You cannot use SPC-2 SCSI reserve if the following factors are true: The failover does not break the device reservations and those devices that were in use during the failover must be available without manual intervention. Use SCSI persistent reserve.
If the drive path changes, the backup jobs and the restore jobs fail.
Therefore, jobs fail in cluster environments or any multi-path environments that share paths dynamically. If you cannot disable dynamic path sharing, you cannot use SPC-2 SCSI reserve or SCSI persistent reserve in NetBackup.