How to Read From a Failed Socket

Code 23 can mean too many files are being backed up.

This computer error is usually the result of a time lapse between the server and a personal computer. It also commonly occurs when you are backing up a large number of files. Most often, the “socket read failed” or "status code: 23" shows up as a pop-up window error. Next time you get this error, there are a few things you can try to determine how to read why you received the failed socket message.

Instructions

1. Pull up the Backup, Archive and Restore interface on the computer showing the error by typing in "/usr/openv/netbackup/bin/jbpSA &" -- without the quotes.
   The Backup, Archive and Restore interface is part of the NetBackup software package. This is the software needed in order to back up your files on your server. When you start a backup, your computer will request the space from the server. A status code 23 or failed socket is a message received on your computer when an error occurs.

2. Click "File/NetBackup Client Properties".

3. Increase the user-directed operation timeout to a higher value. The user-directed timeout is the number of seconds to wait for a response from the NetBackup master server when performing user-directed operations. The default is 60 seconds, the minimum setting is 0 and the maximum is 32,400 seconds.

4. Click "OK". This new setting should allow you to read files without getting a failed socket message.

Tips & Warnings

• The computer and server both must be running to start a restore.

References

• Symantec: Status Code: 23 Socket Read Failed Occurs When Attempting to do a User-directed Restore