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 overlapping the time window in the profile
To ensure that all data is vaulted, overlap the time window in the profile.
A Vault profile uses a time range as one of the criteria for choosing the backup images to be vaulted. Vault does not duplicate or eject a backup image that already has a copy in the off-site Volume Group; therefore, Vault does not process images that are already vaulted by a previous session. Perhaps more importantly, backups that were not processed if a previous session failed are processed when the profile runs again if the time window is long enough.
Therefore, configure the time window to be the sum of the following:
The longest expected downtime for a server or robot
Twice the length of the frequency at which the profile runs
For example, if you have a profile that duplicates images daily and your longest expected downtime is three days, configure the time window to be at least five days. If a robot fails and requires three days to repair, the next time the profile runs, it selects backup images that were not vaulted during the three-day downtime. Configuring the window to be longer, such as seven days, provides even more resiliency. A longer time window forces Vault to search a larger list of images for vault candidates. Although that consumes more processing time, the extra time may not be a problem in your environment because Vault is a batch process that does not demand immediate system response.