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 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
- Index
About injecting media
In a normal volume rotation, you have to inject media back into a robot after media expires and is returned from your off-site storage location so that it is available for reuse. You also may need to inject unexpired media for restore or disaster recovery operations.
Injecting media updates the NetBackup and Media Manager catalogs so that the correct location of the media is recorded. If the robot does not have a barcode reader to identify the media being injected, you still must use an inject option so the location of the media is updated in the databases.
How you accomplish the process of injecting the media depends on the robot library as follows:
If your library has a media access port (MAP), you insert the media to be injected into the MAP. Then use one of the injecting options that is discussed in this topic to move that media from the MAP to the library slots. If the library has a barcode reader, the appropriate database changes are made automatically.
If the library does not have a MAP, you insert the media into the library slots or into a cartridge which is then placed into the robot. If the library has a barcode reader, the appropriate database changes are made automatically.
If your library does not have a barcode reader, you must use the option of the NetBackup Administration Console so the databases are updated.
You can inject media as follows:
The vault fields in the Media Manager database are cleared when the media are unassigned while in a robotic volume group or moved into a robotic volume group and then unassigned (that is, injected back into the robot).
The following are the Media Manager database fields dedicated to Vault information:
vltcid | The ID of the container (container vaulting only). |
vltname | The name of the vault. |
vltreturn | The date the volume or container should be returned from the off-site vault. |
vltsent | The date the volume or container was sent off-site. |
vltsid | The ID of the session that vaulted the volume or container. |
vltslot | The ID of the slot in which the volume resides in the off-site vault (slot vaulting only). |
Volume pool, volume group, and media description fields are used for all volumes, not only the volumes that Vault uses. So, they are not cleared when media are injected back into a robot. You can, however, configure NetBackup so that the media description field is cleared.