If the server can't back up itself, I'd start there. I just checked on my system and IP's seem to work, at least with amcheck, so perhaps that will solve your problem. If you used the FBSD port (/usr/ports) system on your server to build Amanda, I think it automatically required FQDN for the hosts. Check the debug files on the server to confirm what amandad reports for the defaults.
I use FQDN for all machines, but that's just me ;) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Doug Silver Network Manager Quantified Systems, Inc ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ On Mon, 18 Mar 2002, Lee Parsons wrote: > Can I use IP addresses in the disklist files rather than the FQDNs? If I > could do that then I wouldn't have to worry about DNS to begin with. I > haven't seen anything explicitly say we can or cannot but every disklist > file I've seen always has the FQDN. Although the other thing I notice i > that I can ping the NAT servers from the amanda server by their names > without a problem. I'll try IPs in the disklist file and see what > happens. > > > ----------- > Lee Parsons > LAN Administrator > The Minnesota Daily > www.mndaily.com > > On Mon, 18 Mar 2002, Doug Silver wrote: > > > On Mon, 18 Mar 2002, Lee Parsons wrote: > > > > > We began using NAT addresses on our network a few months ago, but at first > > > we kept all of our systems that were backed up by amanda outside the NAT > > > range. As time moved on we started bringing some of them inside, and it > > > seemed that the easiest way to get both the inside (translated) and > > > outside (nontranslated) addresses would be to build an amanda server and > > > place it inside. After building a system with FreeBSD 4.5 and amanda, we > > > found that it was able to connect to the machines outside, but none of the > > > machines inside, including itself. Is there something we missed? We > > > enabled the "operator" accounts on all the systems, we used inetd to start > > > amanadad as operator on all the systems, and added the UDP and the two TCP > > > ports into /etc/services. But yet we still cannot get the new amanda > > > server to get anything inside, including itself. When we run amcheck it > > > reports all the systems inside to be "host down?". Any ideas would be > > > much appreciated. > > > > > > ----------- > > > Lee Parsons > > > LAN Administrator > > > The Minnesota Daily > > > www.mndaily.com > > > > > > > I would check your DNS settings (and /etc/resolv.conf) and if they > > correspond to what you have listed in your disklist file. If the amanda > > server has a problem with the user it will complain about that in > > particular (i.e. root/operator/etc). In your case, start with one machine > > and get that one working -- it's probably the same problem everywhere. > > Perhaps you aren't using the correct FQDN? > > > > Debug files will be in /tmp/amanda. > >
