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 bar code 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:

You can inject media as follows:

On UNIX systems, you also can inject media by using the vmadm command.

See the NetBackup Administrator's Guide.

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:


The ID of the container (container vaulting only).


The name of the vault.


The date the volume or container should be returned from the off-site vault.


The date the volume or container was sent off-site.


The ID of the session that vaulted the volume or container.


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 just volumes used by Vault, 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.

More Information

About clearing the media description field