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 recovery priorities
Your organization must decide between recovery cost (the infrastructure and testing) and the level of functionality that must be recovered. You may choose to recover only the most critical business functions immediately and then recover other functions later. Although all functions of an organization should be valuable and necessary for the organization to operate, it may be acceptable to operate at a reduced level for a specific period of time. The longer your organization can operate without a function, the easier and less expensive it becomes to recover that function. Therefore, given the higher cost of rapid recovery, only those functions that are required for immediate operation need to be recovered quickly. Delaying recovery of some functions can be a good business decision.