Just a couple shots in the dark. Could the issue be network congestion? Many older firewalls can't keep up with the data transfer and start doing bad things to packets. How about traffic shaping? Nothing like low priority backup traffic to ruin your day. And as always - patches, nic drivers etc? -Jonathan
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jimenez, Daniel Sent: Thursday, May 29, 2008 4:01 PM To: veritas-bu@mailman.eng.auburn.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@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
