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 Vault catalog backups
NetBackup catalogs are databases that contain information about the NetBackup configuration and backups, including the files that are backed up and the media on which they are stored. Vault creates a new catalog backup with up-to-date information. It does not duplicate an existing NetBackup catalog backup. A NetBackup catalog backup is not a substitute for a Vault catalog backup because it does not include the latest information about duplicated media and media location. Therefore, you should perform a catalog backup in Vault.
To perform a Vault catalog backup, Vault uses a special schedule of type Vault Catalog Backup in an NBU-Catalog policy. (NetBackup uses a special backup policy of type NBU-Catalog to perform catalog backups.)
A Vault catalog backup occurs when a profile that performs catalog backup runs. It does not occur on the schedule that is defined in the NBU-Catalog policy. A Vault Catalog Backup schedule always performs a full backup of the entire NetBackup catalog.
You can create multiple copies concurrently of a Vault catalog backup.
Vault does not duplicate existing catalog images, but it ejects the media on which those images are stored if both of the following are true:
Those images are selected during the choose backups step.
The media is assigned to the dedicated Vault catalog volume pool.
If the catalog backup fails but the remainder of the Vault job succeeds, the session ends with a status 294 (vault catalog backup failed). Data is vaulted with no associated catalog backup. Veritas believes that it is better to vault the data without a catalog backup than to fail the job and vault nothing at all for that session.
The Recovery Report for Vault shows the three most recent Vault catalog backups. If you vault your regular NetBackup catalog backups, they do not appear on the Recovery Report but do appear on other reports.
See the NetBackup Administrator's Guide, Volume I for information about the location of the NetBackup catalog and the files that are included in a catalog backup.