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 ACS MAP
The following applies to NetBackup Enterprise Server only.
Automated cartridge system (ACS) robots can have multiple library storage modules (LSMs), each with multiple media access ports (MAPs). When you configure a vault that uses an ACS robot, you can specify any MAP or a subset of MAPs to use for media ejection. Vault ejects media to as few of the configured MAPs as possible based on a nearest MAP algorithm. The algorithm considers the volumes to be ejected, the MAPs configured for ejecting in the vault, and the configuration of the LSMs. The algorithm assumes that the LSMs are connected in a line. If your LSMs are connected in a configuration other than a line, see the following two sections within the NetBackup Administrator's Guide:
See "Adjacent LSM Specification for ACS Robots" in the NetBackup Administrator's Guide.
See "Media Access Port Default for ACS Robots" in the NetBackup Administrator's Guide.
The option does not mean all MAPs; media are not ejected to all MAPs, media are ejected to the nearest MAP in each LSM.
If you specify any MAP:
MAPs that have only one element are not used.
Vault selects from MAPs that are on-line when the eject begins; MAPs that are offline are not considered for eject operations.
If only a subset of MAPs are used during ejection, all MAPs are busy and unavailable. For example, if the media are ejected to only two MAPs in one LSM, all MAPs are still busy.
For all other robot types that have MAPs, media are ejected to the default MAP. NetBackup does not support ejecting to multiple MAPs for other robot types.