>Also, I've read other messages in the archive with this problem and it seems
>to relate to firewall settings. The remote system is not behind any type of
>firewall, but the amanda backup server dis behin a firewall on the local
>network. What kind of timeout setting would i have to set on the
>firewall...if it was related to a timeout?
Amanda uses two or three network connections to process an image.
One is for data and should be very active. Another is for the index and
will be active in spurts, depending on how many files are involved and
whether you use dump or GNU tar. The third is for messages and can be
completely idle during an entire run as it is primarily for errors.
I suspect what's happening is that your firewall is timing out the message
connection after maybe an hour of inactivity. So that's the kind of
control (inactive connection) in your firewall I'd be looking for.
You'll need to set it up large enough to cover the longest backup you do.
There are a couple of possible solutions to this on the Amanda side, but
I don't know of anyone with enough time to work on them. One would send
an "I'm still here" ping on any path that goes idle to keep them active.
The other (probably better) would be to have Amanda multiplex the three
streams on one network connection. Both will require protocol changes
of one type or another, which is one reason nobody has jumped into
the project.
>Nathanael
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
