Symantec NetBackup status code 286 to status code 290
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 286 to Status Code 290 which may be received while using the Symantec NetBackup tool.
NetBackup status code: 286
Message: vault internal error
Explanation: This error should never occur.
RecommendedAction: Contact customer support and send the appropriate logs.
NetBackup status code: 287
Message: vault eject failed
Explanation: This error occurs when Vault fails to eject any of the media that
was identified for eject during a Vault Session. Potential reasons: Media and Device
Management services are down, the robot is down, or no empty slots are available
in the media access port (MAP).
Recommended Action: Ensure that the Media and Device Management services
are running, the robot is up, and empty slots are available in the media access
NetBackup status code: 288
Message: vault eject partially succeeded
Explanation: This error occurs when not all of the media that was identified for
eject during a Vault session can be ejected.
Potential reasons include the following:
¦ Some of the media is in use by NetBackup
¦ Some of the media are in a drive
¦ Not enough empty slots are available in the media access port (MAP)
Recommended Action: Ensure that the media are not loaded in a drive and in
use by other processes. Ensure that empty slots are available in the media access
NetBackup status code: 289
Message: cannot consolidate reports of sessions from container and slot-based
Explanation: This error occurs when you consolidate reports and at least one
session uses slots and another uses containers.
Recommended Action: Change the report consolidation so that only reports for
one type of vault operation are consolidated, either slots or containers.
NetBackup status code: 290
Message: one or more errors detected during eject processing
Explanation: This error occurs when more than one error is encountered during
an eject procedure by vltopmenu. Any “eject” errors that range from 291 to 300
may have occurred in any of the sessions being ejected.
Recommended Action: For detailed information, review the Vault debug log in
the following directory:
UNIX and Linux: /usr/openv/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
(where xxx is the session ID)
After the problem is identified and corrected, the media that were not ejected may
need to be ejected manually by means of vlteject or vltopmenu.
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.
Hope this was helpful.
In-Depth Blogs on SQL Server, Information about NetBackup status codes, SQL Server Frequently asked questions, SQL Server Trainings.