Symantec NetBackup status code 23 to status code 27

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

NetBackup status code: 23
Message: socket read failed
Explanation: A read operation from a socket failed.

NetBackup status code: 24
Message: socket write failed
Explanation: A write operation to a socket failed.

NetBackup status code: 25
Message: cannot connect on socket
Explanation: A process that timed out while it connects to another process for a
particular operation. This problem can occur in the following situation: when a
process tries to connect to the NetBackup request daemon (bprd) or database
manager daemon (bpdbm) and the daemon is not running. (On Windows, these
daemons are the NetBackup Request Manager and NetBackup database manager
services.)
It can also occur in the following situations: the network or server is heavily loaded
and has slow response time or an evaluation license key for NetBackup expired.
However, the most common cause of this error is a host name resolution problem.
The following are other possible causes of this error caused by network
connectivity issues or a required process such as pbx_exchange not running.
nbjm is unable to connect to bpcd on the media server
nbpem is unable to connect to nbproxy
bptm on the media server is unable to connect to nbjm on the master server.
You cannot perform an immediate backup operation.
These errors are caused either by network connectivity issues or if a required
process such as pbx_exchange is not running.

NetBackup status code: 26
Message: client/server handshaking failed
Explanation: Aprocess on the server encountered an error when it communicated
with the client. This error indicates that the client and server were able to initiate
communications, but encountered difficulties and the communications did not
complete. This problem can occur during a backup or a restore.
Recommended Action: Determine which activity encountered the handshake
failure by examining the All Log Entries report for the appropriate time period.
Determine the client and server that had the handshake failure.
For detailed troubleshooting information, create a debug log directory for the
process that returned this status code. Then retry the operation and check the
resulting debug log.

NetBackup status code: 27
Message: child process killed by signal
Explanation: A child of the process that reported this error was terminated. This
error may occur if the backup job was terminated or another error terminated the
child process. This problem may also occur if a NetBackup process was terminated
through Task Manager or another utility.
Recommended Action: Check the NetBackup All Log Entries report for clues on
where and why the failure occurred. For detailed troubleshooting information,
create a debug log directory for the process that you think may have returned
this status code. Then, retry the operation and check the resulting debug log.

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 *