Symantec NetBackup status code 306 to status code 310


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

NetBackup status code: 306
Message: vault duplication partially succeeded
Explanation: This error occurs when all selected images are not duplicated
Recommended Action: Check the Vault and induplicate logs for cause of the

NetBackup status code: 307
Message: eject process has already been run for the requested Vault session
Explanation: This error occurs when vlteject is run to eject media for a session
ID for which media has already been ejected.
Recommended Action: Rerun vlteject for another session ID for which media
has not been ejected.

NetBackup status code: 308
Message: no images duplicated
Explanation: This error occurs when Vault failed to duplicate any images.
Recommended Action: For more information, 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:
UNIXand Linux: /usr/openv/netbackup/vault/sessions/<vault_name/>sidxxx
Windows: install_path\NetBackup\vault\sessions\vault_name\sidxxx
(where vault_name is the name of the vault, and xxx is the session ID)
Look for the log entry that gives the total number of images processed.Acommon
cause of failure is a lack of resources, such as no more media available in the
specified pools for duplication. Correct the problem and rerun the Vault job. Note
that the NetBackup scheduler retries a Vault job that terminates with this error.
Review the admin debug log for induplicate entries and the bptm debug log.

NetBackup status code: 309
Message: report requested without eject being run
Explanation: This error occurs when a report is run that requires media to have
been ejected first.
Recommended Action: Perform one of these actions:
¦ Rerun vlteject or vltopmenu to eject the media for the session before you
generate the reports.
¦ Reconfigure the profile to allow the eject step to be performed when the next
Vault session for this profile runs.
¦ Disable the report generation in the profile for the reports that require media
to be ejected.

NetBackup status code: 310
Message: Updating of Media Manager database failed
Explanation: This error occurs when Vault physically ejects tapes but fails to
update the EMM database to reflect the eject operation. A typical reason for this
failure is that EMM detected a mismatch between the media type and its volume
RecommendedAction: To find the root cause of the error, review the Vault debug
logs in the following directory:
UNIX and Linux: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
To fix the issue may involve making configuration changes.

Hope this was helpful.

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 *