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 tracking volumes not ejected by Vault
Eject is the event that Vault uses to update the NetBackup database for the location of volumes and to recall volumes. In normal operation, Vault must eject volumes so they are tracked and recalled from off-site storage after they expire.
If you ejected volumes or removed them from your robot without using a Vault eject method, it is still possible to use Vault to track them if they are in a volume pool you are using for off-site media. Using commands, you can change the attributes for volumes that were not ejected by Vault so they appear in the Vault reports and are recalled when they expire.
This process works only if the volumes already are in a volume pool on the Eject tab of a profile. You cannot change the pool of an assigned volume.
To track volumes not ejected by Vault do the following:
Use the vmchange command to change the volume group of the volumes, which Vault uses to track their location. For example, the following vmchange command changes the volume group of volume A00001:
vmchange -new_v offsite_volgrp -m A00001
vltoffsitemedia -change -m A00001 -vltname offsite_vault -vltsent 07/03/2004 -vltreturn 0 -vltslot 99 -vltsession 33
A catalog volume is processed the same except the return date is set to the date the volume should be recalled.
If you are adding the volumes to slots at your off-site storage location, you can use the vltoffsitemedia command with the -list option to find empty slots into which you can add the volumes.
If you are placing the volumes in containers, use the vltcontainers command to add the volumes logically to containers after you specify the off-site volume group and the vault attributes.
The default return date of a container is the date of the volume in the container that is returned the latest. You may have to change the container return date if the volume you add expires later than any volume already in the container.
The following are the vltoffsitemedia options you can use to set the necessary volume attributes:
The name of the vault.
Set the return date to 0. Vault uses the latest expiration date of the images on the volume as the return date. Exception: if the volume is a NetBackup catalog backup volume, set the date the volume should be recalled from off-site.
Set the sent date to the date the volume was ejected. The format of the date depends on your locale setting. For the C locale, the date syntax is mm/dd/ yyyy [hh[:mm[: ss]]].
The ID of the session that vaulted the volume or container. Set it to a nonzero number that is different from existing session IDs
The ID of the slot in which the volume resides in the off-site vault. Ensure that this is an empty slot at your off-site storage location. If you are placing the volume in a container, do not specify this option.