Veritas NetBackup™ Vault Administrator's Guide
- About Vault
- Installing Vault
- Best Practices
- About best practices
- About vaulting paradigms
- About preferred vaulting strategies
- About how to ensure that data is vaulted
- About not Vaulting more than necessary
- About preparing for efficient recovery
- About media ejection recommendations
- About avoiding resource contention during duplication
- About how to avoid sending duplicates over the network
- About increasing duplication throughput
- About maximizing drive utilization during duplication
- About scratch volume pools
- About organizing reports
- About generating the lost media report regularly
- Configuring NetBackup Vault
- Configuring Vault
- About configuring Vault
- About Vault configuration
- About configuration methods
- About configuring Vault Management Properties
- Configuring robots in Vault
- Vault Robot dialog box options
- About creating a vault
- Media access ports dialog box
- Creating retention mappings
- About creating profiles
- Creating a profile
- Configuring a profile
- Vaulting and managing media
- About Vault sessions
- About previewing a Vault session
- Stopping a Vault session
- About resuming a Vault session
- About monitoring a Vault session
- About the list of images to be vaulted
- About ejecting media
- About injecting media
- About using containers
- Assigning multiple retentions with one profile
- About vaulting additional volumes
- Revaulting unexpired media
- About tracking volumes not ejected by Vault
- Vaulting non-NetBackup media managed by Media Manager
- About notifying a tape operator when an eject begins
- About using notify scripts
- About clearing the media description field
- Restoring data from vaulted media
- Replacing damaged media
- Creating originals or copies concurrently
- Reporting
- Administering Vault
- About setting up email
- About administering access to Vault
- About printing Vault and profile information
- Copying a profile
- About moving a vault to a different robot
- About changing volume pools and groups
- About NetBackup Vault session files
- Operational issue with disk-only option on Duplication tab
- Operational issues with the scope of the source volume group
- Using the menu user interface
- Troubleshooting
- About troubleshooting Vault
- About printing problems
- About errors returned by the Vault session
- About media that are not ejected
- About media that is missing in robot
- Reduplicating a bad or missing duplicate tape
- About the tape drive or robot offline
- No duplicate progress message
- About stopping bpvault
- About ejecting tapes that are in use
- About tapes not removed from the MAP
- Revaulting unexpired tapes
- Debug logs
- Appendix A. Recovering from disasters
- Appendix B. Vault file and directory structure
- Index
About running multiple sessions simultaneously
Multiple Vault sessions can run at the same time. Vault uses a global setting as a threshold for queuing jobs from any vault. A Vault job runs if resources are available and the maximum number of Vault jobs has not been reached. If resources are not available to run jobs, Vault queues jobs until the resources are available.
Vault also uses locks on the duplication and eject steps of a job to enforce queueing for the jobs that contend for those resources.
Vault queues jobs as follows:
If is reached, any subsequent vault job is queued and its status is shown as Queued in the Activity Monitor.
If a job needs to duplicate images and another job from the same vault is duplicating images, the job is queued and shown as Active in the Activity Monitor. More detailed information about the status of these Active jobs appears in the Detailed Status tab of the Job Details dialog box.
If a job needs to eject media and another job from any vault is ejecting media in the same robot, the job is queued and shown as Active in the Activity Monitor.
Queued jobs are scheduled or run when the resources that are required for them become available.
For jobs that run simultaneously, the following restrictions exist:
Vaults should not share on-site and off-site volume pools. Profiles within the same vault can use the same volume pools, but profiles from one vault cannot use the same volume pools as profiles from another vault.
Vaults should not share off-site volume groups. Profiles within the same vault can use the same off-site volume groups, but profiles from one vault cannot use the same off-site volume groups as profiles from another vault.
More Information