|
|
vltinject injects volumes into a robot and updates the Enterprise Media Manager Database. It runs vmupdate and assigns it the robot number, robot type, and robotic volume group from the vault configuration that matches the specified profile.
If the following directory exists and has public write access, vltinject writes to the daily debug log file:
Windows systems:
install_path\netbackup\logs\vault
The daily debug log file is log.DDMMYY; the DDMMYY is the current date.
You then can use this file for troubleshooting. Public-write access is needed because not all executables that write to this file can run as administrator or root.
Any authorized user can run this command.
For more information about NetBackup authorization, refer to the NetBackup Security and Encryption Guide.
The name of a profile or a robot number, vault, and profile that are nested within the vault configuration file. If profile is used without robot and vault, the profile must be unique. vltinject executes vmupdate with the robot number, robot type, and robotic volume group from this profile's configuration.
To inject the volumes that the Payroll profile has vaulted and that were returned from the off site vault, enter the following:
# vltinject Payroll
To inject the volumes that the Weekly profile (in the Finance vault) vaulted and that the off-site vault has returned, the user enters the following:
# vltinject 8/Finance/Weekly
0 The EMM Database was successfully updated. not = 0 There was a problem updating the EMM Database.
Vault may exit with a status code greater than 255. Such status codes are called extended exit status codes. For such a case, the exit status that is returned to the system is 252. The actual exit status is written to stderr in the format, EXIT status = exit status
The extended exit status values are documented in the NetBackup Troubleshooting Guide and in the NetBackup Troubleshooting Wizard.