Sounds a lot like what I am going through, but I know what my problem is, I just havn't fixed it yet. Basically the client tries to open a random UDP connection to the server between the 1-1024 port range. For security reasons, it uses a 'trusted' port range. You can set the port range when you compile Amanda, but that isn't the issue. The issue seems to be that the client MUST be able to contact the server's address on that range in order to work. This means that if the server is sitting behind a NAT device, the client must be able to reach the 'reverse NAT' address.
Hope this make sense, or help a little. Sorry if it doesn't! -James -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Lee Fellows Sent: Thursday, May 16, 2002 6:04 AM To: [EMAIL PROTECTED] Subject: Failed backups Hi, Since setting amanda up, I have constantly run into failed backups with timeouts reported. If I run amdump on the configuration, it works fine, but if I let the cron job call it during the night, it fails. We have a local network with a vpn to our remote servers. The tape server is only tasked with backing up some files on its hard drive and a share from an NT box. Both machines are local. The total size of the backups being requested are less than 5 Gig. and the tape capacity is 40 Gig. The NT box is also the dns server of first resort. Apparently, if/when the vpn goes down, sendsize gets lost and times out in reporting to amandad (if I understand correctly). If the vpn is up, sendsize has no difficulty whatsoever. I found this be seeing amandad and sendsize still running on the tape server at 7:30 AM when the cron job started at 1:00 AM. When I discovered that the vpn was down and restarted it, amandad and sendsize happily finished, reporting the timeout error. Unfortunately, the vpn goes down most nights, although not by design. Any ideas why sendsize would (mis)behave in this manner? Any ideas what I can do to work around this? Thank you. Lee
