Ah ha! At first it gave a warning for each of my virtual tapes, there
are 80 of them. So then I used rsync to replicate
/var/log/amanda/DailySet1/ from the real backup server to the backup
backup server. At that point, "amadmin DailySet1 find" showed a list of
backups. And now amrecover works
Oops, I mislead you. There is an error message displayed. It is the
classic no dumps available before this date. I am blind and I just
didn't hear it. I am still as puzzled as ever though. I've cut/pasted a
screen cap of my amrecover session. I'll paste in the amindexd log as well.
I see
I tried both "localhost backup" and "localhost root" in the amandahosts
file. No difference. It is odd -- everything seems to work. I can
connect to the localhost, issue sethost and setdisk commands. In fact,
if I give an invalid host or disk name, I get an error message. But the
ls command
Is this related to the .amandahosts file on the server, which needs to have
a line for each client, allowing it to access the index-process
and maybe the tape-process?I have entries like this:
node.FQDN root amindexd amidxtaped
I’m not certain that both of those are still needed, but
Well, that got me a lot closer. I gave user backup read permission to
/etc/amanda/DailySet1/amanda.conf on the "backup" backup server. Now
when I run amrecover, I can do a sethost and a setdisk. But after doing
so, an ls gives me an empty list. No error message. It's just that there
are no
