Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Error code 24 Socket read failed

Created: 20 Nov 2010 • Updated: 28 Mar 2013 | 3 comments
vinods's picture
This issue has been solved. See solution.

I have been getting backup failure with status code 24 intermittently. Even by using a cross cable.

 

Master server :- Windows 2008 7.0.1

Client :- Windows 2003 7.0.1

File backup

 

 

Comments 3 CommentsJump to latest comment

Marianne's picture

Have a look at these TN's:

http://www.symantec.com/docs/TECH60844

http://www.symantec.com/docs/TECH56950

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
Zahid.Haseeb's picture

This may help you

Netbackup Troubleshooting Guide: (Page # 176)

ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/348472.pdf

 

NetBackup status code: 24
 
Message: socket write failed
 
Explanation: A write operation to a socket failed.
 
Recommended Action: Do the following, as appropriate:
■ Check the NetBackup Problems report for clues on where and why the failure
occurred. If you cannot determine the cause from the Problems report, create
debug log directories for the processes that could have returned this status
code. Then retry the operation and check the resulting debug logs.
■ A possible cause is a high network load. For example, this problem occurs with
Cannot write to STDOUT when a Windows system that monitors network
load detects a high load. It then sends an ICMP packet to other systems to
inform them that the route those systems use was disconnected. The log
messages were similar to the following:
01/31/96 14:05:23 ruble crabtree.null.com from client
crabtree.null.com: ERR - Cannot write to STDOUT. Err no= 242: No
route to host
01/31/96 14:05:48 ruble crabtree.null.com successfully wrote
backup id crabtree.null.com_0823125016, copy 1, fragment 1,
440864 Kbytes at 628.538 Kbytes/sec
01/31/96 14:05:51 netbackup crabtree.null.com CLIENT
crabtree.null.com POLICY Remote3SysFullW SCHED Sirius EXIT
STATUS 24 (socket write failed)
■ The following information applies only to Sun Solaris:
Verify that all operating system patches are installed.
See the Operating Notes section of the NetBackup Release Notes.
■ The following information applies only to Windows systems:
Verify that the recommended service packs are installed.
■ This error may occur during a restore to a Novell client.
Note the following possible actions:
■ By default, the value for Novell "Maximum Packet Receive Buffers" may
be too low (such as 100). To improve the restore performance, change this
value to 2000. To change it, issue "SET Maximum Packet Receive
Buffers=<value>" at the console, or enter the value in either of the following
Novell files: sys:system\startup.ncf or sys:system\autoexec.ncf.
■ Change to or add the following settings in the Novell
sys:system\autoexec.ncf file:
 
SET Maximum Packet Receive Buffers = 4000
SET Maximum Directory Cache Buffers = 4000
SET Maximum Concurrent Disk Cache Writes = 2000
SET Maximum Concurrent Directory Cache Writes = 2000
SET Maximum Physical Receive Packet Size = 1514

Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb

zahidhaseeb.wordpress.com

vinods's picture

Backup is done succesfully .

 I have made chnages NIC card seeting both master and client .

Thanks & Regards

Vinod N.Shinde

Netbackup Technical Executive

*****************************************************************