Symantec NetBackup status code 291 to status code 295

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 291 to Status Code 295 which may be received while using the Symantec NetBackup tool.

NetBackup status code: 291
Message: number of media has exceeded capacity of MAP; must perform manual
eject using vltopmenu or vlteject
Explanation: This error occurs in the following situation: a Vault job is run for a
profile that selected automatic eject mode and the number of media to be ejected
exceeds the MAP capacity.
RecommendedAction: Use vltopmenu to manually eject the media for the selected
profile and session ID. The vltopmenu option lets you eject the selected media, a
MAP-full (or less) at a time.

NetBackup status code: 292
Message: eject process failed to start
Explanation: This error occurs when the following cannot start the eject process:
the Vault job, the vlteject command, or the use of the vltopmenu.
Recommended Action: For detailed information about the problem, 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)
Use the robtest utility to ensure that you can communicate with the Vault robotic
library. After the problem is resolved, rerun the Vault session, vlteject command,
or vltopmenu command.

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.

NetBackup status code: 294
Message: vault catalog backup failed
Explanation: During a Vault job, the catalog backup step failed.
RecommendedAction: 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
To find the actual problem that caused the catalog backup (bpbackupdb) to fail,
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)
Correct the problem and rerun the Vault job.

NetBackup status code: 295
Message: eject process could not obtain information about the robot
Explanation: This error occurs when the eject process cannot collect information
about the robotic library and its associated MAPs and volumes.
Recommended Action: For detailed information about why the process fails,
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)
Correct the error and rerun the Vault session, vlteject command, or vltopmenu
eject command.

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 *