Wednesday, February 27, 2019

NetBackup status code: 54 - Error Code details and Solution (Recommended Actions to resolve)

9:38 PM Posted by Sandy No Comments

NetBackup status code: 54

Message: timed out connecting to client

Explanation: The server did not complete the connection to the client. The accept system or winsock call timed out after 60 seconds.

Some third-party software packages (for example, a personal firewall product) can affect the TCP/IP stack in Windows. This action can cause a loss of connection between the NetBackup server and the bpcd process on the client. NetBackup tries to set SO_REUSEADDR (allow local address reuse) on the inbound socket connection so that the port can be handed off from bpinetd.exe (the NetBackup Client Service) to bpcd.exe. Some products may not allow this functionality due to the various methods that can be used to violate system security.

Recommended Action: Do the following, as appropriate:

For a Macintosh or NetWare target client: Verify that the server does not try to connect when a backup or restore is already in progress on the client. These clients can handle only one NetBackup job at a time.
On a Macintosh, check for activity by examining the NetBackupListen file in the following folder on the startup disk of the Macintosh client:
```
:System Folder:Preferences:NetBackup:logs:inetd:log.mmddyy  
```
Perform the following procedure:
See "Resolving network communication problems" in the Troubleshooting Guide.
On UNIX and Linux clients, verify that the /usr/openv/netbackup/bin/bpcd binary exists and that it is the correct size.
Check the /etc/inetd.conf file to make sure the bpcd path is correct in the following entry:
```
bpcd stream tcp nowait root /usr/openv/netbackup/bin/bpcd bpcd  
```
On the systems that include the following, make sure that the client name is in the master's /etc/hosts file: NetBackup master, media, and clients (with NetBackup database extension products installed on one or more clients).
Completely uninstall the third-party software package on the client that causes the failure. Or, contact the software manufacturer to investigate if other configuration options or workarounds are possible.