NetBackup status code: 293

Message: eject process has been aborted

Explanation: This error occurs when the eject process is canceled. This error can be encountered during a Vault job or with the vlteject or the vltopmenu eject command.

This error can occur because of one of the following conditions:

Could not open a pipe to vmchange -verify_eject call.
Unexpected output from vmchange -verify_eject call.
No MAP elements exist to eject media into.
The robotic library had problems putting media into the MAP.
The user pressed Return in interactive mode and did not first remove the media from the MAP. In this case, the media that were in the MAP are put back into their original slots in the robotic library.

Recommended Action: For detailed information about why the process was canceled, review the Vault debug log in the following directory:

	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

(where xxx is the session ID)

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 robotic library.
Inventory the robotic library. 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.