Symantec NetBackup status code 131 to status code 135


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

NetBackup status code: 131
Message: client is not validated to use the server
Explanation: The client name, as determined from the connection to the server,
did not match any client name in the NetBackup configuration. No altnames
configuration for this client exists on the master server. A client and server with
multiple network connections can encounter this problem in the following
situation: the name by which the client is configured is not the one by which its
routing tables direct connections to the server.
Recommended Action: Do the following, as appropriate:
¦ Examine the NetBackup Problems report.
¦ Create a debug log directory for bprd and retry the operation. Check the
resulting debug log to determine the connection and the client names.
Depending on the request type (restore, backup, and so on), you may need or
want to do the following:
¦ Change the client’s configured name.
¦ Modify the routing tables on the client.
¦ On the master server, set up an altnames directory and file for this client
See the NetBackup Administrator’s Guide, Volume I.
¦ On a UNIX or Linux master server, create a soft link in the NetBackup image
¦ See Verifying host names and services entries in the Troubleshooting Guide.

NetBackup status code: 132
Message: user is not validated to use the server from this client
Explanation: None
Recommended Action: None

NetBackup status code: 133
Message: invalid request
Explanation: One of two explanations exist.
¦ A request was made that is not recognized. This lack of recognition usually
results from different versions of NetBackup software being used together.
¦ If a client receives this error in response to a list or restore request, then the
in the bp.conf file on a UNIX or Linux NetBackup server or in the registry on
a Windows NetBackup server. These options deny list and restore requests
from all NetBackup clients.
Recommended Action: Do the following, as appropriate:
¦ If you suspect that the software versions are the problem, verify that all
NetBackup software is at the same version level.
¦ On UNIX and Linux NetBackup servers and clients, check the
/usr/openv/netbackup/bin/version file.
¦ On Windows NetBackup servers, check the
install_path\netbackup\version.txt file or the AboutNetBackup item
on the Help menu.
¦ On Microsoft Windows clients, check the About NetBackup item on the
Help menu.
¦ On NetWare target clients, check the Version entry in the bp.ini file.
¦ On Macintosh clients, check the version file in the bin folder in the
NetBackup folder in the Preferences folder.
¦ If the server denies list and restore requests, remove the
the bp.conf file on a UNIX or Linux NetBackup server or from the registry on
a Windows NetBackup server. Then, stop and restart the NetBackup request
daemon (UNIX and Linux) or NetBackup Request Manager service (Windows).
¦ For detailed troubleshooting information, create bpdbm, bprd, and admin debug
log directories. Retry the operation and check the resulting debug logs.

NetBackup status code: 134
Message: unable to process request because the server resources are busy
Explanation: Status code 134 is an informational message that indicates that all
drives in the storage unit are currently in use. If all drives are in use, NetBackup
automatically tries another storage unit. If one is not available, NetBackup
re-queues the job with a status of 134 and retries it later.
Recommended Action: None.
The 134 code is an informational message only and is not considered an error. It
can occur for a number of reasons in normal operation. The 134 status code can
occur more frequently in an SSO environment. No action is necessary.
Astatus 134 is not logged in the error logs.A134 status causes a new try to appear
in the Activity Monitor. It does not increase the retry count that is associated with
the allowed number of retries.

NetBackup status code: 135
Message: client is not validated to perform the requested operation
Explanation: An alternate client restore was tried that did not come from the
root user (on UNIX and Linux) or the administrator (on Windows).
Recommended Action: Retry the operation as a root user (on UNIX and Linux)
or as an administrator (on Windows) on the master server. Also see status code

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 *