Symantec NetBackup status code 296 to status code 300

SQLServerF1

Symantec NetBackup product is a backup and recovery product designed for enterprise users. Symantec NetBackup tool can be used to perform backups of SQL Server databases and provides various features.

Below are some of the NetBackup status error codes from Status Code 296 to Status Code 300 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 296
Message: process called but nothing to do
Explanation: This error occurs in the following situations:
¦ vlteject is called with -eject but the system has no tapes to eject
¦ vlteject is called with -eject and the eject is already done
¦ vlteject is called with -report and the reports are already done
¦ vlteject is called with -eject and -report, and both the eject and the reports
are done
RecommendedAction: This error is an informative one and does not require any
action.

NetBackup status code: 297
Message: all volumes are not available to eject
Explanation: This error occurs when an try is made to eject a non-existent or bad
media ID during the eject phase of the following: a Vault session, a vlteject
command, or a vltopmenu command.
Possible reasons for this error are as follows:
¦ The bad media ID was added by means of the vlt_ejectlist_notify script.
¦ The bad media ID is already in the MAP or not in the robotic library.
¦ The bad media ID is in a robotic drive.
¦ The bad media ID is in transit in the robotic library.
Recommended Action: Remove or correct the defective media ID from the
vlt_ejectlist_notify script and rerun the Vault session. If the bad media ID is
in the MAP or a drive or in transit, something is misconfigured.

NetBackup status code: 298
Message: the library is not ready to eject volumes
Explanation: This error occurs if the robotic library is not in a state to support
ejecting media.
Possible reasons for this error include the following:
¦ Currently, the library ejects media
¦ The library waits to eject media
¦ Currently, the library injects media
¦ The library waits to inject media
RecommendedAction: Wait until the robotic library can support the eject action
and rerun the Vault session, vlteject command, or vltopmenu command.

NetBackup status code: 299
Message: there is no available MAP for ejecting
Explanation: The robotic library you vault from does not have a MAP available
for use and so media cannot be ejected.
Recommended Action: Wait until the robotic library’s MAP is available for use
and rerun the Vault session, vlteject command, or vltopmenu command.

NetBackup status code: 300
Message: vmchange eject verify not responding
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:
UNIXand 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 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.

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *