Explanation: During the eject process, the vmchange command is called with a "-verify_eject" call until all of the volumes for the request are in the MAP. This command call failed. Or it did not return the proper information to the Vault eject process.
Recommended Action: Do the following, as appropriate:
Review the Vault debug log in the following directory for detailed information about why the process failed:
UNIX and Linux: /usr/openv/netbackup/logs/vault Windows: install_path\NetBackup\logs\vault
Also review the summary.log in each of the sidxxx directories that had problems:
UNIX and Linux: /usr/openv/netbackup/vault/sessions/vault_name/sidxxx Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
This error often indicates that the media were left in the off-site Vault volume group but physically reside in the robot or the robotic MAP. To solve this problem, do one of the following:
Manually remove any media that are in the off-site Vault volume group but are still in the robot.
Inventory the robot. An inventory puts any media that were in the off-site Vault volume group back into the robotic volume group. Then, rerun the Vault sessions that failed.