STATUS CODE 23: Schedule initiated Client backups fail with a NetBackup Status Code 23 (socket read failed).

Problem

STATUS CODE 23: Schedule initiated Client backups fail with a NetBackup Status Code 23 (socket read failed).

Error Message

socket read failed

Solution

Overview:  Schedule initiated Client backups fail with a NetBackup Status Code 23 (socket read failed).  

Troubleshooting:
Use the bpclntcmd command to test the connectivity between the master server and the client.  Specifically, be sure to use the bpclntcmd -pn command.  

The following commands can be run to test both forward and reverse hostname lookups in Windows & Unix

The following commands can be used to test the short name alias and the fully qualified long name

of the system.

% <install path>\netbackup\bin\bpclntcmd –hn <ShortName>

% <install path>\netbackup\bin\bpclntcmd –hn <LongName>

 

#/usr/openv/netbackup/bin/bpclntcmd –hn <ShortName>

#/usr/openv/netbackup/bin/bpclntcmd –hn <LongName>

 

The following command can be used to test reverse IP lookup of the system.

#/usr/openv/netbackup/bin/bpclntcmd –ip <IP Address returned by –hn command>

 

These commands should be run from the master server and also the media server that is handling the backup. The results should display the correct hostname and IP address for the host.

 

 UNIX forward and reverse lookups:

The following commands can be run to test both forward and reverse hostname lookups in UNIX.

The following commands can be used to test the short name alias and the fully qualified long nameof the system.

 

# /usr/openv/netbackup/bin/bpclntcmd –hn <name exactly as it is in the policy>

The following command can be used to test reverse IP lookup of the system.

# /usr/openv/netbackup/bin/bpclntcmd –ip <IP Address returned by –hn command>

These commands should be run from the master server and also the media server that is handling the backup. The results should display the correct hostname and IP address for the host.



Log files:  N/A

Resolution:
This problem is caused by incomplete name resolution information in either the hosts file or the DNS.  Be sure the client's name and IP address are in the master server's hosts file, and the master server's name and IP address are in the client's hosts file.  

The hosts files are located:
 
- in the %SystemRoot%\system32\drivers\etc directory (Windows)
 
- in the SYS:etc directory (NetWare)
 
- in the /etc directory (UNIX/Linux)
 


 

Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)