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 for 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
 
About fail all copies
The behavior of the fail option and the default settings depend on whether the concurrent copies operation was configured in Vault or in NetBackup:
In Vault, if you choose , all copies of that image fail, independent of the success or failure of other image copy operations. The next time the Vault profile runs, Vault again tries to duplicate the image if the following conditions are true:
The image is selected.
The Vault profile did not eject the primary backup.
In NetBackup, if you choose , the entire backup job fails and no copies are made. In this case, normal NetBackup behavior ensures that a successful backup for this policy eventually occurs. That is, NetBackup automatically retries the backup if time permits and, the next time the backup window for the policy opens, NetBackup again tries to run the backup (regardless of the frequency of the schedule). NetBackup retries until the backup succeeds, although one or more backup windows may pass before the backup is successful.