Veritas NetBackup™ Vault Administrator's Guide
- About Vault
- Installing Vault
- 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 how to avoid sending duplicates over the network
- About increasing duplication throughput
- About organizing reports
- Configuring NetBackup Vault
- Configuring Vault
- About Vault configuration
- About configuring Vault Management Properties
- About creating a vault
- About creating profiles
- Configuring a profile
- 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 additional volumes
- About using notify scripts
- Creating originals or copies concurrently
- Reporting
- Administering Vault
- About administering access to Vault
- About NetBackup Vault session files
- Using the menu user interface
- Troubleshooting
- Debug logs
- Appendix A. Recovering from disasters
- Appendix B. Vault file and directory structure
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.