Please enter search query.
Search <book_title>...
Veritas NetBackup™ Vault Administrator's Guide
Last Published:
2021-01-01
Product(s):
NetBackup (9.0.0.1, 9.0)
- About Vault
- Installing Vault
- Best Practices
- About preferred vaulting strategies
- About how to ensure that data is vaulted
- About not Vaulting more than necessary
- About preparing for efficient recovery
- About avoiding resource contention during duplication
- About how to avoid sending duplicates over the network
- About increasing duplication throughput
- About organizing reports
- Configuring NetBackup Vault
- Configuring Vault
- About Vault configuration
- About configuring Vault Management Properties
- About creating a vault
- About creating profiles
- Configuring a profile
- Vaulting and managing media
- About Vault sessions
- About monitoring a Vault session
- About the list of images to be vaulted
- About ejecting media
- About injecting media
- About using containers
- About vaulting additional volumes
- About using notify scripts
- Creating originals or copies concurrently
- Reporting
- Administering Vault
- About administering access to Vault
- About NetBackup Vault session files
- Using the menu user interface
- Troubleshooting
- Debug logs
- Appendix A. Recovering from disasters
- Appendix B. Vault file and directory structure
About using a separate volume pool for each Vault
Jobs within the same vault are queued and then run when resources are available. However, if multiple profiles from different vaults run simultaneously and use the same off-site volume pool for duplication, those jobs could all pick the same target media. This selection would circumvent the queuing mechanism and cause undesirable results. (For example, it can cause a deadlock condition when multiple jobs try to use the same drive at the same time).
Therefore, you should configure Vault so that every vault has its own off-site volume pool.