1. Support
  2. Knowledge base
  3. 100016999

STATUS CODE: 23 "Socket Read Failed" occurs when attempting to do a user-directed restore.

Article: 100016999
Last Published: 2019-01-15
Ratings: 3 8
Product(s): NetBackup

Problem

STATUS CODE: 23 "Socket Read Failed" occurs when attempting to do a user-directed restore.

 

Error Message

Socket Read Failed (23) - NetBackup Error

Timed out waiting for acknowledgement.
The restore may or may not have initiated.
Check the status of the NetBackup Client Service;
it must be running in order to start a restore.
The server returned error code 23, more information can be
found in the NetBackup Troubleshooting Guide.

 

Cause

Overview:
STATUS CODE: 23 "Socket Read Failed" occurs when attempting to do a user-directed backup or restore.

Troubleshooting:
This sort of behavior can be seen when there is a latency in the network connection between the client and the master server. It can also be seen if the backup set in question contains a very high file count, as in excess of 1 million files. The status 23 may appear in the activity monitor, or it may appear as a pop up error on the client (Figure1).

Figure 1:  A status 23 condition is seen
 

 

Solution

In addition to investigating any possible network latency, change the user-directed operation timeout to a higher value by doing the following:
 
1. Pull up the Backup, Archive and Restore interface on the client machine in question
2. Click File | NetBackup Client Properties
3. Increase the user-directed operation timeout (Figure 2)
 
Figure 2: Changing the user-directed operation timeout to a higher value can resolve the Status 23 error on a user-directed operation.
 
 
 
The User-directed operation timeout is the number of seconds to wait for a response from the NetBackup master server when performing user-directed operations. If exceeded, the user receives a "socket read failed" error even if the server is still processing the user's request. The default is 60 seconds. The minimum setting is 0. The maximum setting is 32,400 seconds.
 
Also, increasing the File List Timeout (also seen in Figure 2), can resolve issues with listing files that are available for restore.

 
 

 

Was this content helpful?

Article Languages