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 using containers
A container is a box in which you can place media and then transfer that box to your off-site storage location. When you configure a vault, you select whether the media are stored in containers or slots at your off-site storage location. Vault tracks, reports, and recalls your media regardless of how the media are transferred and stored off site.
After the media are ejected from your robot, you must add the media logically to containers by using either the Vault Operator Menu or the vltcontainers command.
The options available for adding media to containers are as follows:
Enter the container ID and media IDs by typing them in with the keyboard. Using this method, you can add media to more than one container.
Scan the container ID and media IDs by using a keyboard interface barcode reader. (Keyboard interface readers are also known as keyboard wedge readers because they connect, or wedge, between the keyboard and the keyboard port on your computer.) Using this method, you can add media to more than one container.
Read an input file that contains the IDs or numeric equivalents of barcodes of all the media to be added to one container. If you have a barcode reader that can write to a file, you can scan media barcodes and use that output file as input for the vltcontainers command.
Add all the media that is ejected by a specific session to one container.
The default return date of a container is the date of the volume in the container that is returned the latest. You can change the return date during the container ID and media ID entry process or at any time thereafter before a container is recalled.
You also can delete a container from the NetBackup and Media Manager databases. The following describes when you should delete an empty container:
If a container becomes empty due to moving media to other containers, Vault deletes that empty container.
If a container becomes empty due to a media inject, the empty container remains and the user will have to manually delete it using the vltcontainers command. The following example shows you how to delete container ABC123 from the NetBackup and Media Manager catalogs.
vltcontainers -delete -vltcid ABC123
Note:
The container must be empty before it can be deleted.
If you use containers, Vault reports on the containers and media outside the context of a profile or session.