sts_close_handle failed: 2060019 error occurred on network socket

[yobole]

aam getting the error when trying to back up a server accross the firwall to MSDP pool with client dedupe enalbed

I have made the following changes

Putty onto Netbackup appliance and ruin the command below on command prompt.

$ sysctl -w net.ipv4.tcp_keepalive_time=900

remote client

Make the following as a registry file to import. It will create values to change the retry time on timed-out connections to 30 seconds (from a default of ~4 minutes); and a ~15 minute wait to check on established connections (default is hours-days).

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"KeepAliveTime"=dword:000dbba0
"TCPTimedWaitDelay"=dword:0000001e

the backups are still failing with error 87

[Marianne]

Have you verified that all necessary firewall ports are opened in both directions between client and MSDP server?

1556
10082
10102

See NetBackup Network Ports Reference Guide 
 

[yobole]

Yes .. Smaller size backup are working fime its the long backup  that fail after 19/20 hrs

 sts_close_handle failed: 2060022 software error    and then sts_close_handle failed: 2060019 error occurred on network socket   

[yobole]

Its alomost impossible to turn on logging at the logs are so big its alomost crashing the server .. so a bit blind also

[Marianne · Accepted solution]

These entries on Windows Client worked for a fellow Connect User:

https://www-secure.symantec.com/connect/forums/experiences-changing-keepalivetime-windows-master-med... 

Important to know what firewall timout is and set KeepAlive to a lower value than firewall timeout.

See: https://www-secure.symantec.com/connect/articles/tuning-windows-2003-and-2008-symantec-netbackup

[yobole]

the firewall timeout is 1hr hence why i set the keep alive to 15mins

[Marianne]

You will unfortunately need logs to troubleshoot....

[yobole]

ok I have created a new STU and changed the maximum Fragment sixe from 50GB to 10GB and running another test

[yobole]

We seem to have isolated the problem as being down to windows firewall . We had to completey turn windows firewall off to get it to work . The initial setting we had in place for both inbound and outboud rulles were

Symantec Netbackup Client TCP - local ports: 1556, 13724, 13782, 111, 7394, 2049, 443,10102, 10082

we would like to turn windows firewall on, any ideas on what the settings should be. the client is a windows server 2012 R2