Symantec NetBackup status code 351 to status code 405

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

NetBackup status code: 351
Message: all configured vault steps failed
Explanation: This error occurs when multiple Vault steps are configured for a
session and all of them fail.
RecommendedAction: For duplication and catalog backup steps, use the Activity
Monitor to check the status of the respective jobs that Vault started. For Eject
step status, check the Detailed Status tab of the Job Details dialog box for the
Vault job.

NetBackup status code: 400
Message: Server Group Type is Invalid
Explanation: The creation of a server group fails because the server group type
is invalid.
Recommended Action: Do the following, as appropriate:
¦ Select a valid server group type: MediaSharing, Symantec OpsCenter, or
AltServerRestore.
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator ID 111), which uses
unified logging.

NetBackup status code: 401
Message: Server Group Already Exists
Explanation: The attempt to create a server group failed. The server group already
exists.
Recommended Action: Do the following, as appropriate:
¦ Verify that the specified server group name is not in use.
¦ Create the server group by specifying a name that is not currently in use.
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator ID 111), which uses
unified logging.

NetBackup status code: 402
Message: Server Group Already Exists with a different type
Explanation: The attempt to create a server group failed. The server group name
is already in use by a server group with a different group type.
Recommended Action: Do the following, as appropriate:
¦ Verify that the specified server group name is not in use.
¦ Try to create the server group by specifying a name that is not currently in
use.
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator ID 111), which uses
unified logging.

NetBackup status code: 403
Message: Server Group Active State is not valid
Explanation: The attempt to create a server group failed. The server group state
was invalid.
Recommended Action: Do the following, as appropriate:
¦ Valid server group states are: ACTIVE and INACTIVE
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator ID 111), which uses
unified logging.

NetBackup status code: 404
Message: Server Group does not exist
Explanation: An operation was tried by using a server group that does not exist.
Recommended Action: Do the following, as appropriate:
¦ Verify that the specified media is correct.
¦ Verify the media ownership.
¦ Verify that the server group exists.
¦ Verify that the server where the operation is performed is a member of the
owning server group. If not, try the operation from a server that is a member
of the server group.
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator IDs 111 and 143),
which uses unified logging.

NetBackup status code: 405
Message: Member’s server type not compatible with Server Group
Explanation: The attempt to add or update a server group failed. A member’s
server type was not valid for the specified server group type.
Recommended Action: Do the following, as appropriate:
¦ The Media Sharing server group can contain the following types of servers:
Master, Media, NDMP, and cluster.
¦ For detailed troubleshooting information, create the admin debug log directory
and retry the operation. Check the resulting debug logs. Additional debug
information can be found in the log for nbemm (originator IDs 111 and 143),
which uses unified logging.

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 *