Gary Goldberg wrote:

As for problem 1, I'd guess it's a firewall problem
although other clients work fine through the same
firewall. Does all backups fail or only
incremental/level backups?

The problem is limited (apparently) to clients behind
four firewalls I recently deployed. Although it doesn't
happen every time, and to every client behind them. And
some of the clients have never had the problem. But it does
happen to both images (taken Sundays) and incrementals (rest
of week).

You probably have stateful firewalls, and your Networker traffic on
these certain hosts on certain jobs is probably sporadic enough such
that the firewall considers that network session "timed out". I'd check
your firewall settings and up the settings on what constitutes a
timed-out session, and increase it if possible.

You can get timeout errors like this is when doing backups (esp.
incrementals) on filesystems with thousands of files which don't change
very often. In that case Networker will eventually assume the client
save process has died, even though it hasn't died, it's just been slow
in responding. Your problem might be a special case of this, but the
firewall is dropping the session before Networker has a chance to drop it.

But with It's a bit unusual that this would happen when taking full
backups, but not impossible. The only way to confirm exactly what is
happening is catch one of these failed backups in action and get packet
traces on the client and the Networker server, and the firewall access logs.



cheers,
andrew

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=