Veritas NetBackup™ Vault™ Administrator's Guide
- About Vault
- About the Vault process
- Installing Vault
- About installing and configuring Vault on UNIX and Linux systems
- About installing and configuring Vault on Microsoft Windows systems
- Best Practices
- About preferred vaulting strategies
- About how to ensure that data is vaulted
- About not Vaulting more than necessary
- About preparing for efficient recovery
- About avoiding resource contention during duplication
- About two processes trying to use the same drive
- About load balancing
- About how to avoid sending duplicates over the network
- About increasing duplication throughput
- About organizing reports
- Configuring NetBackup for Vault
- About off-site volume pools
- About creating catalog backup schedules for Vault
- About setting master server properties for Vault
- Configuring Vault
- About Vault configuration
- About configuring Vault Management Properties
- General tab (Vault Management Properties)
- Alternate Media Server Names tab (Vault Management Properties)
- Retention Mappings tab (Vault Management Properties)
- Reports tab (Vault Management Properties)
- About creating a vault
- About creating profiles
- Configuring a profile
- Duplication tab
- Catalog backup tab (Profile dialog box)
- Eject tab (Profile dialog box)
- Reports tab (Profile dialog box)
- Vaulting and managing media
- About Vault sessions
- About monitoring a Vault session
- About the list of images to be vaulted
- About ejecting media
- About injecting media
- About using containers
- About vaulting media in containers
- About managing containers and media
- About vaulting additional volumes
- About using notify scripts
- Creating originals or copies concurrently
- About the continue or fail for concurrent copies
- About creating duplicate images concurrently
- About generating reports
- About consolidating reports
- Vault report types
- Reports for media going off site
- Reports for media coming on-site
- Inventory reports
- Administering Vault
- About administering access to Vault
- About NetBackup Vault session files
- Using the menu user interface
- Debug logs
- Appendix A. Recovering from disasters
- About disaster recovery
- 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
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.