Here are the hacks
?The 10060 and 10054 errors in the NetBackup logs can be related to
dropped connections due to a timeout, which can occur quite often under
congested networks. It is possible to increase the likelihood of keeping
client connections alive in the event of temporary congestion by
increasing the value of the TcpMaxDataRetransmissions parameter in the
server registry.
1. Start Registry Editor (Regedt32.exe).
2. Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. On the Edit menu, click Add Value , and then add the following registry
value:
Value Name: TcpMaxDataRetransmissions
Data Type: REG_DWORD
Value: 6
4. Quit Registry Editor and reboot for the changes to take effect.
The default value for this is 5 and should gradually be increased until
you find the desired result.
It is also possible to increase the TcpMaxConnectRetransmissions. This
parameter determines the number of times TCP will retransmit a connect
request (SYN) before aborting the attempt. The retransmission timeout is
doubled with each successive retransmission in a given connect attempt.
1. Start Registry Editor (Regedt32.exe).
2. Locate the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
3. On the Edit menu, click Add Value , and then add the following registry
value:
Value Name: TcpMaxConnectRetransmissions
Data Type: REG_DWORD
Value: Default: 3 (in Windows NT)
Default: 2 (in Windows 2000)
4. Quit Registry Editor and reboot for the changes to take effect.
This value should be increased by incrementals of
=============================
Carl Stehman
IT Distributed Services Team
Pepco Holdings, Inc.
202-331-6619
Pager 301-765-2703
[EMAIL PROTECTED]
"WEAVER, Simon \(external\)" <[EMAIL PROTECTED]>
05/30/2008 10:01 AM
To
<[EMAIL PROTECTED]>, "Cornely, David" <[EMAIL PROTECTED]>
cc
<[email protected]>,
<[EMAIL PROTECTED]>
Subject
RE: [Veritas-bu] Network Connection time out (41)
increase client timeouts perhaps ?
CLIENT_CONNECT_TIMEOUT 32000
HKey_Local_Machine\Software\Veritas\NetBackup\Current Version\Config !
Simon
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Friday, May 30, 2008 1:30 PM
To: Cornely, David
Cc: [email protected];
[EMAIL PROTECTED]
Subject: 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
[EMAIL PROTECTED]
"Cornely, David" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
05/29/2008 04:38 PM
To
<[email protected]>
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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jimenez,
Daniel
Sent: Thursday, May 29, 2008 13:01
To: [email protected]
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 - [email protected]
http://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.
This email (including any attachments) may contain confidential and/or
privileged information or information otherwise protected from disclosure.
If you are not the intended recipient, please notify the sender
immediately, do not copy this message or any attachments and do not use it
for any purpose or disclose its content to any person, but delete this
message and any attachments from your system. Astrium disclaims any and
all
liability if this email transmission was virus corrupted, altered or
falsified.
---------------------------------------------------------------------
Astrium Limited, Registered in England and Wales No. 2449259
REGISTERED OFFICE:-
Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
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 - [email protected]
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
