Symantec NetBackup status code 301 to status code 305

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

NetBackup status code: 301
Message: vmchange api_eject command failed
Explanation: During the eject process, the vmchange command is called with an
-api_eject call to begin the process to eject media. This command call 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
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)
When the problem is resolved, rerun the Vault session, vlteject command, or
vltopmenu command.

NetBackup status code: 302
Message: error encountered trying backup of catalog (multiple tape catalog
backup)
Explanation: This error occurs when the NetBackup command that was used for
stage one of the two-stage catalog backup fails.
Recommended Action: For the actual error that caused the failure, review the
Vault debug log in the following directory:
UNIX and Linux: /usr/openv/netbackup/logs/vault
Windows: install_path\NetBackup\logs\vault
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)
In addition, review the admin debug log in the following directory:
UNIX and Linux: /usr/openv/netbackup/logs/admin
Windows: install_path\NetBackup\logs\admin
Correct the error and rerun the Vault session.

NetBackup status code: 303
Message: error encountered executing Media Manager command
Explanation: This error occurs when a Media and Device Management command
fails during a Vault job.
Recommended Action: For the actual error that caused the command to fail,
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)
Try running the command (with the same arguments as in the log file) to see the
actual error. Ensure that the Media and Device Management daemons are running.
Also ensure that the robot is functional and you can communicate with it (for
example, inventory the robot through the GUI).

NetBackup status code: 304
Message: specified profile not found
Explanation: This error occurs when the profile name that is specified on the
Vault command is not defined in the Vault configuration.
Recommended Action: Rerun the Vault command with a profile name that is
defined in the Vault configuration.

NetBackup status code: 305
Message: multiple profiles exist
Explanation: This error may occur when duplicate profile names are defined in
multiple Vault configurations and only the profile name is specified on the Vault
command.
Recommended Action: Rerun the Vault command with the triplet
robot_name/vault_name/profile_name. The triplet uniquely identifies the profile
in your Vault configuration.

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 *