After scouring all AMANDA resources I could find, I'm still stumped.
Does anyone out there have advice on using AMANDA in a heterogeneous
network with this mix of hosts: Debian x86 (server and some clients),
FreeBSD x86, BSDI x86, Red Hat x86, and Red Hat MIPS (Cobalt RaQ)?
I've tried using the Debian packages, and they work like a dream for the
Debian hosts only. I've tried building the client binaries for FreeBSD
both directly on the box (from the /usr/ports tree) and on the server box
but with the configure option, "--target=i686-pc-freebsd" and I've tried
using both an RPM package and binaries I compiled myself on the Red Hat
x86 box. Still, for all the hosts but Debian, I get something like:
<quote but-with-hostnames-changed>
# su backup -c "/usr/sbin/amcheck -c Daily1"
Amanda Backup Client Hosts Check
--------------------------------
send req failed: Connection refused
send req failed: Connection refused
ERROR: raq3: [access as operator not allowed from backup@debian0]
protocol packet receive: Connection refused
protocol packet receive: Connection refused
WARNING: raq4: selfcheck request timed out. Host down?
WARNING: freebsd1: selfcheck request timed out. Host down?
Client check: 8 hosts checked in 30.207 seconds, 3 problems found.
(brought to you by Amanda 2.4.1p1)
</quote>
I've changed the host names to be more descriptive, and to be sure I
understood each line.
The ra3 box has the RPM binaries. I've tried fussing with .amandahosts to
get the mismatched users to work, with no luck.
The ra4 box is another Red Hat x86 box, but with my binaries and with
"backup" as the user.
The mars box runs FreeBSD 3.3-RELEASE.
What should I be doing differently?
Thanks.
- Iain
--
Iain O'Cain
OA Net Operations Centre
