Veritas NetBackup™ Vault Administrator's Guide
- 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 two processes trying to use the same drive
Careful configuration of your environment can help avoid resource contention during Vault duplication. Resource contention can occur when two processes try to use the same drive at the same time.
To avoid resource contention, use one of the following alternatives:
Alternative A: dedicated robot for Vault processing
Alternative B: each robot as a Vault robot
Alternative C: one robot as both a backup and Vault robot
See Alternative C: one robot as both a backup and Vault robot.
These alternative configurations work well for multi-robot environments. They use available resources efficiently and are unlikely to cause resource allocation problems.
Note:
If you vault original backups, you do not have to use practices that avoid or reduce Vault resource contention.