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 for 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
Vaulting VSM media
Vault can eject and track Veritas Storage Migrator (VSM) media if it is in a VSM volume pool that is configured on the profile Eject tab and it has a return date from vault set by VSM. Vault assigns vendor slot or container IDs to the media. The media appears on the Picking List for Robot when they are ejected and on the Picking List for Vault that covers their return dates.
Note:
Veritas Storage Migrator (VSM) 6.5 is the final release of the product and is not supported in NetBackup 7.0 and later versions. However, VSM is supported for the life of NetBackup 6.5 and all NetBackup 6.5 release updates. This means only NetBackup 6.5 GA and 6.5.x media servers support VSM media and this version of Vault will manage those media. Starting with the next major release of NetBackup, Vault will no longer support VSM media eject and report functionality. In addition, if you have VSM media vaulted off-site after the next major release you must track that media manually.
You can vault VSM media by using a profile specifically for VSM media or by using a profile that also ejects NetBackup media. If you use a profile that you already use for ejecting media and generating reports, you do not have to run a VSM-specific profile. The VSM media is ejected, vaulted, and recalled as part of your normal Vault operations.
Vault suspend options do not affect VSM media; VSM media are never suspended.
Prerequisites to vaulting VSM media in Vault are as follows:
Configure vaulting properties in VSM.
The VSM media must have a return date from Vault set by VSM.
See Eject tab (Profile dialog box).
To vault VSM media
- Configure a Vault profile so it includes the dedicated VSM volume pool(s) from which you want to eject media. For a VSM-specific profile, accept the defaults on the Choose Backups tab and skip the duplication and catalog backup steps.
- On the Eject tab, select Eject Media from VSM Volume Pools and then add the VSM volume pool(s) to the eject list. The VSM media must be in a volume pool that is dedicated to VSM.
For a VSM-specific profile, select (at a minimum) the following reports on the Reports tab:
Picking List for Robot
Picking List for Vault
- Run the profile so that VSM media are ejected and reports are generated.
You can schedule both the VSM vaulting session and the Vault session so they run at a regular interval.