This time the mahine I need to amrecover some bits & pieces to is "shop"
an alias for shop.coyote.den in the /etc/hosts files.
I have made the passwd and group files match those on the lathes box,
where that last time I needed it, /usr/sbin/amrecover Daily appeared to
work, I got all my linuxcnc tree gcode files and configurations back,
and its Just Working(TM) now.
>From here at the server machine;
root@coyote:~# su amanda -c "/usr/local/sbin/amcheck Daily"
Amanda Tape Server Host Check
-----------------------------
Holding disk /usr/dumps: 748040 MB disk space available, using 747540 MB
Searching for label 'Dailys-2':found in slot 2: volume 'Dailys-2'
Will write to volume 'Dailys-2' in slot 2.
NOTE: skipping tape-writable test
Server check took 0.630 seconds
Amanda Backup Client Hosts Check
--------------------------------
WARNING: shop: selfcheck request failed: tcpm_recv_token: invalid
size: "amandad: running as user \"amandabackup\" instead of
\"backup\"\n"
Client check: 3 hosts checked in 4.098 seconds. 1 problem found.
(brought to you by Amanda 3.3.7p1)
============================
Now, on lathe, /etc/xinetd.d/amandaclient:
ervice amanda
{
disable = no
flags = IPv4
socket_type = stream
protocol = tcp
wait = no
user = amandabackup
group = disk
groups = yes
server = /usr/libexec/amanda/amandad
server_args = -auth=bsdtcp amdump
}
========================================
On shop /etc/xinetd.d/amandaclient;
service amanda
{
disable = no
flags = IPv4
socket_type = stream
protocol = tcp
wait = no
user = amandabackup
group = disk
groups = yes
server = /usr/lib/amanda/amandad
server_args = -auth=bsdtcp amdump amindexd amidxtaped
}
=================================
On the lathe box, root session of amrecover:
root@lathe:/tmp/amanda# /usr/sbin/amrecover Daily
AMRECOVER Version 3.3.7. Contacting server on coyote.coyote.den ...
220 coyote AMANDA index server (3.3.7p1) ready.
Setting restore date to today (2015-05-18)
200 Working date set to 2015-05-18.
200 Config set to Daily.
200 Dump host set to lathe.
Use the setdisk command to choose dump disk to recover
So that looks like its working.
====================================
On the shop box (runs a milling machine), a root session of amrecover:
root@shop:/tmp/amanda# /usr/sbin/amrecover Daily
AMRECOVER Version 3.3.1. Contacting server on localhost ...
[request failed: tcpm_recv_token: invalid size: "amandad: running as user
\"amandabackup\" instead of \"backup\"\n"]
.amandahosts on lathe:
root@lathe:/tmp/amanda# cat /var/lib/amanda/.amandahosts
coyote.coyote.den root amindexd amidxtaped
coyote.coyote.den root amindexd amidxtaped
coyote.coyote.den amandabackup amdump
coyote.coyote.den amandabackup amdump
coyote.coyote.den amanda amdump
Which works but I didn't figure it needed 2 of everything, so..
.amandahosts on shop:
root@shop:/tmp/amanda# cat /var/lib/amanda/.amandahosts
coyote.coyote.den root amindexd amidxtaped
coyote.coyote.den amandabackup amdump
coyote.coyote.den amanda amdump
So, other than I haven't found an amandabackup-client-3.3.7p1 for the
shop box so its running amanda-client-3.3.1 from the debian wheezy
repo's.
So whats the next thing to check?
The passwd, group and shadow files are AFAIK, all up to date (I think)
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
