Thanks Joshua and Frank! It worked...

Get past last issue, however any reason why NO index records are found? Any
file I need to create or modify? Where's this index referencing to? Any
relation to the change on the amanda.conf and adding "index yes", would
backups need to be dumped after this change for the new index to be
created??? 

Actually looks like looking for index on the client (localhost). Where does
it look for on client based on the output from the amrecover command.

Just some thoughts???... 

-------------

[root@filer luser]# amrecover -s backup -C DailySet2
AMRECOVER Version 2.4.3. Contacting server on backup ...
220 backup AMANDA index server (2.4.3) ready.
200 Access OK
Setting restore date to today (2003-05-12)
200 Working date set to 2003-05-12.
200 Config set to DailySet2.
501 No index records for host: filer.indyme.local. Invalid?
Trying host filer.indyme.local ...
501 No index records for host: filer.indyme.local. Invalid?
Trying host localhost.localdomain ...
501 No index records for host: localhost.localdomain. Invalid?
Trying host localhost ...
501 No index records for host: localhost. Invalid?

------------



-----Original Message-----
From: Joshua Baker-LePain [mailto:jlb17 AT duke DOT edu]
Sent: Monday, May 12, 2003 4:07 PM
To: Gibran Marquez
Cc: Amanda Users (E-mail)
Subject: Re: Amanda: amrecover on amanda cient fails


On Mon, 12 May 2003 at 3:55pm, Gibran Marquez wrote

> Amrecover from client where testing files that need to be restored (client
> is "filer" and amanda server is "backup"):
> -------------
> [root@filer luser]# amrecover -s backup
> AMRECOVER Version 2.4.3. Contacting server on backup ...
> 220 backup AMANDA index server (2.4.3) ready.
> 500 Access not allowed: [access as amanda not allowed from root@filer]
> amandahostsauth failed
> -------------

You need a line in ~amanda/.amandahosts that looks like this:

filer    root

-- 
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University