Re: [Veritas-bu] Network Connection time out (41)

We had similar problems with some systems behind a firewall that could not handle the backup traffic. Symantec gave us some
regristry hacks that changed how Windows handles TCP timeouts. It solved our problem.

If you think it might help, let me know and I'll send the regristry hacks.

=============================
Carl Stehman
IT Distributed Services Team
Pepco Holdings, Inc.
202-331-6619
Pager 301-765-2703
ckstehman AT pepco DOT com

"Cornely, David" <David_Cornely AT intuit DOT com>
Sent by: veritas-bu-bounces AT mailman.eng.auburn DOT edu

05/29/2008 04:38 PM

To	<veritas-bu AT mailman.eng.auburn DOT edu>
cc
Subject	Re: [Veritas-bu] Network Connection time out (41)

A while ago we saw similar issues with duplications, at least it was the same “Connection reset by peer” error (although different error code).
It was fixed by changing our TCP keepalive value on the media server. Perhaps someone changed a timeout value on the firewall. Play with this value on the media server to see if it helps.
http://sunsolve.sun.com/search/document.do?assetkey=1-30-2876-1
For windows, probably a registry change.

From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Jimenez, Daniel
Sent: Thursday, May 29, 2008 13:01
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Network Connection time out (41)

Hey guys

I am receiving a Network Connection time out (41) on a consistent basis when I run a backup on two of our servers. The servers are behind a DMZ but I have set the BPCD connect-back to use the VNETD port and it worked for a long time but now all I receive are 41 errors. The servers do write some data but eventually error out. I am able to telnet to port 13724 on both servers so there is no blocking on the firewall for that port. Any assistance would be appreciated.

CLIENT BPBKAR LOG:
12:28:31.007 PM: [648.3824] <16> dtcp_write: TCP - failure: send socket (1864) (TCP 10054: Connection reset by peer)
12:28:31.038 PM: [648.3824] <16> dtcp_write: TCP - failure: attempted to send 125 bytes
12:28:31.038 PM: [648.3824] <16> dtcp_write: TCP - failure: send socket (1864) (TCP 10054: Connection reset by peer)
12:28:31.038 PM: [648.3824] <16> dtcp_write: TCP - failure: attempted to send 171 bytes
12:28:31.569 PM: [648.3824] <16> dtcp_write: TCP - failure: send socket (1864) (TCP 10054: Connection reset by peer)
12:28:31.569 PM: [648.3824] <16> dtcp_write: TCP - failure: attempted to send 171 bytes
12:28:31.757 PM: [648.3824] <16> dtcp_read: TCP - failure: recv socket (376) (TCP 10053: Software caused connection abort)
12:28:31.804 PM: [648.3824] <2> tar_base::V_vTarMsgW: FTL - tar file write error (40)
12:28:31.804 PM: [648.3824] <16> dtcp_write: TCP - failure: send socket (1864) (TCP 10054: Connection reset by peer)
12:28:31.804 PM: [648.3824] <16> dtcp_write: TCP - failure: attempted to send 6 bytes
12:28:31.804 PM: [648.3824] <16> dtcp_write: TCP - failure: send socket (1864) (TCP 10054: Connection reset by peer)
12:28:31.804 PM: [648.3824] <16> dtcp_write: TCP - failure: attempted to send 26 bytes
12:28:31.866 PM: [648.3824] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 14: file write failed
12:28:31.866 PM: [648.3824] <16> dtcp_write: TCP - failure: send socket (1864) (TCP 10054: Connection reset by peer)
12:28:31.866 PM: [648.3824] <16> dtcp_write: TCP - failure: attempted to send 6 bytes
12:28:31.866 PM: [648.3824] <16> dtcp_write: TCP - failure: send socket (1864) (TCP 10054: Connection reset by peer)
12:28:31.866 PM: [648.3824] <16> dtcp_write: TCP - failure: attempted to send 34 bytes
12:28:31.882 PM: [648.3824] <4> tar_backup::backup_done_state: INF - Not waiting for server status
12:28:31.929 PM: [648.3824] <16> dtcp_write: TCP - failure: send socket (1864) (TCP 10054: Connection reset by peer)
12:28:31.929 PM: [648.3824] <16> dtcp_write: TCP - failure: attempted to send 6 bytes
12:28:31.929 PM: [648.3824] <16> dtcp_write: TCP - failure: send socket (1864) (TCP 10054: Connection reset by peer)
12:28:31.929 PM: [648.3824] <16> dtcp_write: TCP - failure: attempted to send 33 bytes
12:28:37.585 PM: [648.3824] <4> OVStopCmd: INF - EXIT - status = 0
12:28:39.726 PM: [648.3824] <2> ov_log::V_GlobalLog: INF - BEDS_Term() Enter InitFlags:0x1
12:28:40.351 PM: [648.3824] <16> dtcp_read: TCP - failure: recv socket (376) (TCP 10053: Software caused connection abort)
12:28:40.366 PM: [648.3824] <4> OVShutdown: INF - Finished process
12:28:40.366 PM: [648.3824] <4> WinMain: INF - Exiting C:\Program Files\VERITAS\NetBackup\bin\bpbkar32.exe
12:28:42.382 PM: [648.3824] <4> ov_log::OVClose: INF - Closing log file: C:\Program Files\VERITAS\NetBackup\logs\BPBKAR\052908.LOG

Daniel Jimenez
Systems Analyst II
Data Protection Team
_______________________________________________ Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT eduhttp://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

This Email message and any attachment may contain information that is proprietary, legally privileged, confidential and/or subject to copyright belonging to Pepco Holdings, Inc. or its affiliates ("PHI"). This Email is intended solely for the use of the person(s) to which it is addressed. If you are not an intended recipient, or the employee or agent responsible for delivery of this Email to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this Email is strictly prohibited. If you have received this message in error, please immediately notify the sender and permanently delete this Email and any copies. PHI policies expressly prohibit employees from making defamatory or offensive statements and infringing any copyright or any other legal right by Email communication. PHI will not accept any liability in respect of such communications.

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu