Hi John, sorry I did not get back to you right away, I have been out.
I tried cleaning everything up and starting a new amdump & amrecover. My
results of the amrecover are below. Testing with amanda-2.4.2 and
amanda-2.4.2p2 using localhost. Running amrecover under amanda-2.4.2
things work, but not under amanda-2.4.2p2 (the 2.4.2p2 version is on a
redhat system, an dthe amanda-2.4.2 is ona SuSe system). The one that
fails has the following directory structure:
/usr/adm/amanda/DailySet1/index/localhost/__myshare_install/20010618_0.gz
Here are the results from running amrecover (I must have done things in a
different order since I did not get the "No index records for
>cwd on new date" error, but this time I got a "No index records for disk
for specified date" error):
[rootl@mysystem]# amrecover -C DailySet1
AMRECOVER Version 2.4.2p2. Contacting server on localhost ...
220 mysystem AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2001-06-18)
200 Working date set to 2001-06-18.
200 Config set to DailySet1.
501 No index records for host: mysystem.imation.com. Invalid?
Trying mysystem.imation.com ...
501 No index records for host: mysystem.imation.com. Invalid?
Trying mysystem...
501 No index records for host: mysystem. Invalid?
Trying localhost.localdomain ...
501 No index records for host: localhost.localdomain. Invalid?
Trying localhost ...
200 Dump host set to localhost.
Can't determine disk and mount point from $CWD
amrecover> sethost localhost
200 Dump host set to localhost.
amrecover> setdate 2001-06-18
200 Working date set to 2001-06-18.
amrecover> setdisk //myshare/install
Scanning /dumps/amanda...
20010618: found Amanda directory.
200 Disk set to //myshare/install.
No index records for disk for specified date
If date correct, notify system administrator
amrecover>quit
>The original error message you reported was "No index records for
>cwd on new date". Did you get that message as a result of entering
>the "setdate" command, or did it show up as part of a normal startup?
>Looking at the date it/you tried to set and the host and disk amrecover
>picked, do you have index records for that combination?
>
>You said you've been testing, so I'm wondering if you have old information
>laying around in the index area that is confusing things.
>
>You might post the amrecover output you're seeing.
>
>John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
, Dan
