> I get this error every time I run amrecover from a directory that isn't
> in my disklist, or from a host that isn't the backup server.
>
> Try using the sethost, setdisk, and setdate commands in amrecover.
Yep. I've tried that before. It's still no good, as you can see:
# /usr/local/sbin/amrecover
AMRECOVER Version 2.4.2p2. Contacting server on mullet1 ...
220 mullet1 AMANDA index server (2.4.2p2) ready.
200 Access OK
Setting restore date to today (2002-10-04)
200 Working date set to 2002-10-04.
200 Config set to DailySet1.
200 Dump host set to mullet1.
Can't determine disk and mount point from $CWD
amrecover> setdisk /usr/local
Scanning /export/home/amanda/dumps...
200 Disk set to /usr/local.
No index records for disk for specified date
If date correct, notify system administrator
amrecover> setdate 2002-10-04
200 Working date set to 2002-10-04.
No index records for cwd on new date
Setting cwd to mount point
DailySet1 is indeed the config, and mullet1 is the correct host.
Here's a snippet of the index file for /usr/local on mullet1 for 10/4:
[begin snippet]
./apache/htdocs/ttweb/
./apache/htdocs/ttweb/docs/
./apache/htdocs/ttweb/docs/images/
./apache/htdocs/ttweb/docs/wwhdata/
./apache/htdocs/ttweb/docs/wwhdata/common/
./apache/htdocs/ttweb/docs/wwhdata/js/
./apache/htdocs/ttweb/docs/wwhdata/js/search/
./apache/htdocs/ttweb/docs/wwhelp/
[end]
Again, this is after the perl-fix-up removing the leading numerals.
