Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Handshake failed (status 26) possible timeout issue

Updated: 21 May 2010 | 2 comments
thrahn's picture
0 0 Votes
Login to vote

Gentlemen,

I see duplication jobs continously die with status 26 from one of my media servers. Duplication is going from disk over WAN to another media server to tape.

Source media server is "sitting" behind a firewall. (Firewall in between duplication source media and master server but no firewall in between target media server and master.)

Duplication jobs work fine but always break after around 2 hours (2:15 h exactly).

From the bpdm log on the source media server I can see that the remote host (the master server) has closed the connection.

On the master server I cannot seem to find meaningfull log entries, neither in the bpdbm log nor in the vnetd log. I assume it's a timeout when the source media server is sending meta data to the master when a fragment or backup image has been completed.

Media Servers are on Windows Server 2003, Master is running on Solaris 10 Sparc.

NetBackup version is 6.5.4

I cannot remember or find a sensible timeout for my 7200 seconds (2h) finding. It's not even a sensible multiple of anything, is it?

I cannot see the firewall closing an idle connection (my first guess).

Is there a TCP/IP setting on Solaris that could cause the connection being closed?

Any hint is welcome.

Kind regards,
Thomas

Comments

Nicolai's picture
11
Nov
2009
0 Votes 0
Login to vote

tcp idle timeout

One hint :  Check the firewall's tcp idle timeout setting

A Cisco firewall will per default close any unused TCP sessions after two hours. I had a simelar SAP backup issues that was resolved by increasing the tcp idle timeout.

Assumption is the mother of all mess ups.

If this post solved you’re questions please send a gratitude by marking it as a solution.

 

Yasuhisa Ishikawa's picture
11
Nov
2009
0 Votes 0
Login to vote

SP2 applied on Windows Server 2003?

I had a trouble on Windows Server 2003 that TCP connection become suddenly broken. In my case, restore failed after some delay.
After applying SP2, it become work fine.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan