We had this problem with a remote storage node that connected across the
country to the master via a VPN. The problem was TCP timeout settings. The
backup would take longer than one hour and during that time the firewalls
would drop the connection that's used solely for telling the server that
"backup is done". Then when the backup finished, it would just sit there and
do nothing since it couldn't connect. Networker definitely does not handle
TCP errors gracefully.

The solution was to add the following TCP parameters on both the storage
node and the master server:

/usr/sbin/ndd -set /dev/tcp tcp_keepalive_interval 1800000

This sets the keepalive to 30min instead of the default 2 hours and fixed
the problem for us.

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER