> > However, doing a "setdisk /data/mm5_uw/calmm5" produces the
> > same result (appended to the debug file):
> >
> > > DISK /data/mm5_uw/calmm5/
> > < 501 No index records for disk: /data/mm5_uw/calmm5/. Invalid?
>
> Bingo (maybe!).
>
> I think you did:
>
> amrecover> setdisk /data/mm5_u
> > amrecover> setdisk /data
> > 501 No index records for disk: /data. Invalid?
> >
> > Nope, doesn't work.
>
> You disklist entry is exactly "/data"?
Well, I simplified things a bit, in addition to naming the server "foo".
It's actually:
% grep data /usr/local/etc/amanda/Daily/disklist
foo /d
> > [root]% amrecover
> > AMRECOVER Version 2.4.2p2. Contacting server on foo.bar.com ...
> > 220 foo AMANDA index server (2.4.2p2) ready.
> > 200 Access OK
> > Setting restore date to today (2003-01-10)
> > 200 Working date set to 2003-01-10.
> > 200 Config set to Daily.
> > 501 No index records
Ok, it appears lots of people successfully use amrecover with indexing, so
here's my sob story...
For the first time ever (after testing during setup, that is) I need to
recover a file from my amanda tapes (Amanda version 2.4.2p2). The same
machine holds the disks, is the amanda server, and is t
