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 VSM media
- 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 issues with Vaulting Storage migrator 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 retention mapping
Retention mapping lets you assign a retention level to a duplicate image that is based on the retention level of the original image. For example, if the retention of an original image is two weeks, you can configure the mapping so that the duplicate image that is transferred off-site has a retention level of seven years.
You configure retention mappings in the following places:
The Vault Management Properties dialog box Retention Mappings tab (global)
The Vault dialog box Retention Mappings tab (vault specific)
By default, each retention level maps to itself (that is, retention level 0 maps to 0, 1 maps to 1, and so on).
To use the retention mappings, you must specify for the retention level during duplication. You can specify normal retention calculation for some duplication rules and alternative retention mappings for other duplication rules. Vault uses the retention mappings in specific-to-global order. If vault-specific retention mappings do not exist, Vault uses the global retention mappings.
The retention level for a duplicate image is based on the retention level of the primary backup image. The retention period begins on the date the primary backup image was created, not on the date the duplicate image was created.
If the backup policy that created the primary backup image no longer exists, duplication of that image fails and the job continues but reports a status 306 (vault duplication partially succeeded).
Retention mapping applies to duplication only; it does not apply if you vault original NetBackup images.