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
Volume pool and volume group examples
The following three examples show the relationship between volume pools and volume groups.
See Figure: Volume pool with multiple volume groups. for an example of one volume pool (named NB_pool) and several volume groups.
You can move volumes between the groups in the robotic library and any groups that are off site. All volumes, however, remain in the same pool.
Media in the same volume pools are in different volume groups. Note that the data is stored on separate volumes by assigning different volume pools. The volumes in a pool can be in more than one physical location and in more than one volume group.
See Figure: Volume groups with multiple volume pools. for examples of how the volumes in the pool NB_pool_dept_1 are spread among the rob_A, standalone1, and off-site volume groups.
These groups also have volumes from more than one pool (though the volumes in each group must all be the same type).You also can configure a scratch pool from which NetBackup can transfer volumes when a volume pool has no media available.
See Figure: Scratch pool example. for an example where the scratch pool is named Scratch_pool. The three robots contain volumes from that pool in addition to those from other pools.
Assume the following sequence of events:
A backup job requires a DLT volume, so NetBackup attempts to assign one from NB_pool_dept_1 in Robot C.
Robot C has no unassigned volumes available in the NB_pool_dept_1 pool.
NetBackup searches the scratch pool for an unassigned DLT volume in Robot C. If a volume is available, NetBackup moves it to NB_pool_dept_1. Otherwise, NetBackup logs a media unavailable status.