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 Tape I/O commands on UNIX
MAP_CONTINUE_TIMEOUT entry in vm.conf
This entry applies only when the vmchange command is used and the -w option is specified.
MAP_CONTINUE_TIMEOUT = seconds
The default timeout value for seconds is 300 (5 minutes). seconds cannot be zero and values greater than 1200 (20 minutes) can cause the robotic daemon to cancel the operation.
If this entry is specified in vm.conf, the SCSI robotic daemons wait the specified number of seconds before they time out. A timeout can occur while the daemons wait for user reply after the user removes volumes from the media access port. If a timeout occurs, NetBackup aborts the operation.
This entry is read and interpreted on the host on which the SCSI-controlled robotic daemon or process runs.
Note:
Non-mount activities such as a robotic inventory cannot occur during this timeout period.