I would forget about trying to get amrecover to recognize index records. I
was never able to do it. And to this day, I don't use amrecover, I use
amrestore instead.

Michael Martinez


-----Original Message-----
From: John Oliver [mailto:joliver AT john-oliver DOT net] 
Sent: Tuesday, December 31, 2002 6:07 PM
To: amanda-users AT amanda DOT org
Cc: amanda-users AT amanda DOT org
Subject: Re: Still get "No index records"...

On Mon, Dec 30, 2002 at 09:24:33PM -0500, Gene Heskett wrote:
> On Monday 30 December 2002 19:26, John Oliver wrote:
> >[root@backup root]# amrecover
> >AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
> >220 backup AMANDA index server (2.4.2p2) ready.
> >200 Access OK
> >Setting restore date to today (2002-12-30)
> >200 Working date set to 2002-12-30.
> >200 Config set to DailySet1.
> >501 No index records for host: backup.indyme.local. Invalid?
> >Trying backup.indyme.local ...
> >501 No index records for host: backup.indyme.local. Invalid?
> >Trying backup ...
> >501 No index records for host: backup. Invalid?
> >
> >I do have "index yes" in amanda.conf.  Why is it still unhappy?
> 
> Where specifically in amanda.conf?  This is supposed to be a 
> dumptype by dumptype configuration option.  That leaves the 
> posibility that someplace in the chain of defines, its turned back 
> off by your choice of dumptypes.

Yes, I put it in the dumptype I'm using.

> There may be a dim possibility that your particular tar is fubar, 
> what version are you useing?  Minimum generally speaking is 
> 1.13-19, with 1.13-25 being in wide use now. 1.13 with no suffix is 
> usually grounds enough to replace it with the newer release.  Get 
> 1.13-25 from alpha.gnu.org.

I have 1.13-25

-- 
John Oliver, CCNA                            http://www.john-oliver.net/
Linux/UNIX/network consulting         http://www.john-oliver.net/resume/
***               sendmail, Apache, ftp, DNS, spam filtering         ***
****                Colocation, T1s, web/email/ftp hosting          ****