DCs Upgraded to Server 2003 R2, and now backups fail.

[flinttown]

Recently updated 3 Domain Controllers to Server 2033 R2. Previously they were just standard 2003 SP2. Was able to backup this machines with no problems prior to upgrade, now they fail with a "socket read failed", "socket operation failed", and "unable to read from client socket." We are currently running Netbackup Enterprise 6.0 MP4. Has anyone seen this before or encountered this same type of problem?

[Mouse]

Very frequent problem with TOE (TCP Offload Engine) and Windows 2003 implementation of software TOE support.
Usually it comes with Broadcom NICs (NIC could be any brand, but networking chip matters)

Try to go thru this article
Document ID: 304578
http://support.veritas.com/docs/304578
 

Network connectivity tuning to avoid network read/write failures and increase performance

---

Details:

TCP Offload Engine is an emerging technology which is designed to offload TCP stack handling from the main system CPU to a processor built into NIC cards.  This technology is still relatively new, and when engaged, has been known to cause unstable connections.  This results in dropped sockets, dropped packets, packet reordering, packet retransmits and ultimately slow or failed NetBackup backups.


 

[Zahid_Haseeb]

 Mouse i am using a PC which has the realtech brand NIC and i am still facing this problem. i know the chip will definately different from the broadcom NIC.....

I am using win2003 with service pack1 on my client machine which was being backed up by Netbackup server and i am facing this issue as well even i am not using win2003 with SP2
Activity Monitor

10/28/2009 10:20:17 AM - requesting resource TpsbdcPVCSbackup

10/28/2009 10:20:17 AM - requesting resource tpsbkp.NBU_CLIENT.MAXJOBS.tpsbdc

10/28/2009 10:20:17 AM - requesting resource tpsbkp.NBU_POLICY.MAXJOBS.Man_of_TpsBdcPVCSbackup

10/28/2009 10:20:18 AM - granted resource tpsbkp.NBU_CLIENT.MAXJOBS.tpsbdc

10/28/2009 10:20:18 AM - granted resource tpsbkp.NBU_POLICY.MAXJOBS.Man_of_TpsBdcPVCSbackup

10/28/2009 10:20:18 AM - granted resource MediaID=@aaaay;Path=E:\Netbackup\TpsBdcPVCSbackup;MediaServer=tpsbkp

10/28/2009 10:20:18 AM - granted resource TpsbdcPVCSbackup

10/28/2009 10:20:18 AM - estimated 0 kbytes needed

10/28/2009 10:20:18 AM - started process bpbrm (2672)

10/28/2009 10:20:31 AM - connecting

10/28/2009 10:21:05 AM - connected; connect time: 00:00:34

10/28/2009 10:21:28 AM - begin writing

10/28/2009 10:21:55 AM - Error bptm(pid=708) socket operation failed - 10054 (at child.c.1294)      

10/28/2009 10:21:55 AM - Error bptm(pid=708) unable to perform read from client socket, connection may have been broken 

10/28/2009 10:21:59 AM - end writing; write time: 00:00:31

network read failed(42) 

[J_H_Is_gone]

Make sure the upgrade did not close the ports you were using to back it up with.

[Mouse]

the error "socket operation failed - 10054" is windows WINSOCK error that means "windows has dropped TCP connection".
Why Windows does it, ask you Windows guy.

[Zahid_Haseeb]

Mouse it helped me...
I disabled the offload checksum and offload_TCP_Largesend from the client side

http://seer.entsupport.symantec.com/docs/304578.htm