Looks like you didn't specify "index yes" in your dumptype definition (near the end of the amanda.conf file). I ran into this yesterday when I was trying to run amrecover from a client. Maybe you could do what I did-- - redefine the dumptype (add 'index yes') - use amadmin to force a level 0 dump on an example file system - run amdump (an index will be created during this run)
N�nighoff, Leonie, NUE wrote: >Hello mailinglist, > >I have a strange problem with amrecover. >This afternoon I have a presentation about amanda backup service and nothing >works (murphy's task...) > >When I start amrecover as root, the following error occurs: > >shakira:/ # amrecover -C rtec -s shakira.r-tec.int -t shakira.r-tec.int -d >/dev/nst0 >AMRECOVER Version 2.4.2p2. Contacting server on shakira.r-tec.int ... >220 shakira AMANDA index server (2.4.2p2) ready. >200 Access OK >Setting restore date to today (2002-04-10) >200 Working date set to 2002-04-10. >200 Config set to rtec. > >501 No index records for host: shakira. Invalid? <----- !!! > > >Trying shakira.r-tec.int ... >200 Dump host set to shakira.r-tec.int. >Can't determine disk and mount point from $CWD >amrecover> > >terrible. >If I try to set the disk default by using >setdisk /backup/client1 (client1 is the holding disk of a client) >In this directory I find the data of the /etc-directory of this client1. > >Have a look what happens: > >amrecover> setdisk /backup/client1 >501 No index records for disk: /backup/client1. Invalid? >amrecover> > >The same error occurs if I only set the mountpoint /backup as disk, not >/backup/client1 . >It happens with all my holding disks. > >Can you imagine what's my problem? >Please help me...I will really get in trouble if I fail my presentation... > >Thank you so much, > >best regards > >Leonie Nuenighoff > > > >
