Symantec NetBackup status code 57 to status code 64


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

NetBackup status code: 57
Message: client connection refused
Explanation: The client refused a connection on the port number for bpcd.
This error can occur because of the following:
No process listening activity occurs on the bpcd port
The number of connections to the bpcd port is more than the network
subsystem can handle with the listen() call

NetBackup status code: 58
Message: can’t connect to client
Explanation: The server was unable to connect to the client.
Recommended Action: Resolve network communication problems.
See “Resolving network communication problems” in the Troubleshooting Guide.

NetBackup status code: 59
Message: access to the client was not allowed
Explanation: The master or the media server tries to access the client, but the
client does not recognize the server as a valid server.
For the Enterprise Vault Agent: The names of all of the media servers among the
Enterprise Vault servers are not specified in the client configuration.

NetBackup status code: 60
Message: client cannot read the mount table
Explanation: The backup process on the client did not read the list of mounted
file systems.
Recommended Action: Do the following, as appropriate:
Run a df to see if the system can read the mount table.
On an SCO system, code 60 can occur because the mount-point path name
exceeds 31 characters (the maximum number on an SCO system). The bpbkar
debug log on the client shows a message similar to the following:
bpbkar build_nfs_list: FTL – cannot statfs net Errno: 42406
To eliminate these errors for future backups, create a mount point with a
shorter name and symbolically link the long name to the short name.
For detailed troubleshooting information, create a bpbkar debug log directory.
Then retry the operation and check the resulting log.

NetBackup status code: 63
Message: process was killed by a signal
Explanation: A kill signal was sent to the client process.
RecommendedAction: The usual cause for this error is that someone intentionally
terminated a backup.

NetBackup status code: 64
Message: timed out waiting for the client backup to start
Explanation: The client did not send a ready message to the server within the
allotted time.
Recommended Action: Do the following, as appropriate:
On all clients, enable bpcd debug logging as follows:
Create a bpcd debug log directory on the client.
On a UNIX or Linux client, add the VERBOSE option to the
/usr/openv/netbackup/bp.conf file.
On PC clients, increase the debug or log level.
See “Changing the logging level on Windows and NetWare clients” in the
Troubleshooting Guide.
On a UNIX, Linux, or Windows client, create the bpbkar debug log directory
on the client.
On Windows clients, verify that the NetBackup Client service is running.
On a UNIX or Linux client, use the ps command to check for a client process
that uses too much CPU time.
Retry the backup and examine the debug logs for clues on the cause of the

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 *