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
Alternative C: one robot as both a backup and Vault robot
In a multi-robot environment, configure all of the robots as backup robots and configure one of the backup robots as a Vault robot also. (One of the robots functions as both a backup robot and a Vault robot.) Configure one vault for the Vault robot, and in that vault configure one profile for each of the backup robots. In each profile, specify the backup robot in the field of the Choose Backups tab and specify a destination storage unit that is in the Vault robot.
For example, if you have three robots that each have four drives, configure the three profiles as follows:
In the profile for robot one (a backup robot only), specify the volume group in robot one as the Source Volume Group, specify four read drives, and specify a destination storage unit in robot three (robot three is the Vault robot). Images in robot one are read by four drives and written to four drives in robot three. Four duplication jobs run simultaneously.
In the profile for robot two (a backup robot only), specify the volume group in robot two as the Source Volume Group, specify four read drives, and specify a destination storage unit in robot three. Images in robot two are read by four drives and written to four drives in robot three. Four duplication jobs run simultaneously.
In the profile for robot three (a backup and Vault robot), specify the volume group in robot three as the Source Volume Group, specify two read drives, and specify a destination storage unit in robot three. Images in robot three are read by two drives and written to two drives. Two duplication jobs run simultaneously.
All images are duplicated to robot three and ejected from robot three.
This method works well with backup policies that use storage unit. Using storage unit in your backup policies sends backup images to media in any storage unit available. This configuration selects backup images on all the robots and duplicates them to the Vault robot.
Note:
The destination robot must have at least two drives if that robot is used for both read and write functions.