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
Injecting media by using the vltinject command
The vltinject command injects volumes into a robot and updates the Media Manager volume database. It requires as an option the name of a profile (if unique) or a robot number, vault, and profile name.
The following is the format of the vltinject command:
vltinject profile|robot/vault/profile
The following example command injects volumes that were vaulted by the Payroll profile and that were returned from the off-site vault:
vltinject Payroll
Note:
If you use the same profile name across vaults in your vault configuration, then you should specify the robot/vault/profile attributes.
The following example injects volumes that were vaulted by the Weekly profile in the Finance vault and that were returned from the off-site vault:
vltinject 8/Finance/Weekly
See the NetBackup Commands Reference Guide for more information about the vltinject command.
See also "Using NetBackup Commands" in the NetBackup Administration Console help.
To inject media by using the vltinject command
In a terminal window or command window, change to the directory in which the vltinject command resides, as follows:
UNIX
/usr/openv/netbackup/bin
Windows
install_path\NetBackup\bin
- Load the media to be injected into the robot's media access port.
- Run the command, using the appropriate options and parameters.
- Repeat until all media are injected.