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 just shows no backups. It just gives an empty list. I feel I
am tantilizingly close to making this work.
On 10/31/2016 03:00 PM, Debra S Baddorf wrote:
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 there was at one time
a reason I put them there.
Deb Baddorf
On Oct 31, 2016, at 12:35 PM, John G Heim <jh...@math.wisc.edu> wrote:
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 files listed. On the real backup
server, where the backups are actually being made, I do get a list of files, just as
normal. I checked the permissions on the index and info files. They look right.
Actually, I moved the location of the indexdir and infofile to be on the same
remote nfs share as the virtual tapes themselves. So when I run amrecover on
the backup backup server, it is reading the same files as it is when I run it
on the real backup server. I think moving those files to the remote nfs server
was a good thing, not just for this use but also, now amanda's index and info
files are in another building. I would still like to be able to use amrecover
on two different hosts in my buildijng though.
On 10/28/2016 10:52 AM, Jean-Louis Martineau wrote:
It is the amindexd process that report the error.
Look at its debug file.
It is run as your amanda user, did it have permission to read
/etc/amanda/DailySet1/amanda.conf.
Jean-Louis
On 28/10/16 11:08 AM, John G Heim wrote:
I am using the ubuntu amanda-server and amanda-client packages (3.3.6) on
ubuntu server 16.04 to backup to virtual tapes on an NFS mounted file system.
Everything is great on the backup server. I can run amrecover locally and
recover files. But I thought I'd try mounting the NFS share on a client
machine to see if I could recover files that way. I thought if the backup
server ever goes down, I might still be able to recover files on the client
machine.
So I installed amanda-server on the client machine and copied the contents of
/etc/amanda/DailySet1/ to the client. Then I ran:
# amrecover DailySet1 -o auth=local -s localhost
That gives me the error message, ""501 Could not read config file for
DailySet1!". I amd doing this as root. Root does have permission to open/read
/etc/amanda/DailySet1/amanda.conf.
--
--
John G. Heim; jh...@math.wisc.edu; sip://jh...@sip.linphone.org
--
--
John G. Heim; jh...@math.wisc.edu; sip://jh...@sip.linphone.org
