I'm trying to use amrecover to restore a file but it can't seem to find the index records. Here's a snippet of the amrecover session:
AMRECOVER Version 2.4.2p2-tapeio. ... 220 net-cf9a5425 AMANDA index server (2.4.2p2-tapeio) ready. 200 Access OK ... amrecover> sethost 10.0.0.17 200 Dump host set to 10.0.0.17. amrecover> setdate 2002-01-21 200 Working date set to 2002-01-21. amrecover> setdisk hda1 200 Disk set to hda1. No index records for disk for specified date If date correct, notify system administrator Note that I am running amrecover on the backup server (we moved servers and the reverse DNS lookups are not all in place yet). However, the index files *do* exists: # ls /var/amanda/daily/index/10.0.0.17/hda1/ -l -rw------- 1 tape disk 10292 Jan 21 03:39 20020120_1.gz -rw------- 1 tape disk 10919 Jan 22 03:10 20020121_1.gz -rw------- 1 tape disk 10545 Jan 23 02:55 20020122_1.gz The log amindex log file has this: > HOST 10.0.0.17 < 200 Dump host set to 10.0.0.17. > DATE 2002-01-21 < 200 Working date set to 2002-01-21. > DISK hda1 - 2002-01-22 1 daily2 16 - 2002-01-21 1 daily1 19 - 2002-01-20 1 daily8 8 - 2002-01-19 1 daily7 9 < 200 Disk set to hda1. > OISD / Uncompress command: /usr/bin/gzip -dc '/var/amanda/daily/index/10.0.0.17/hda1/20020121_1.gz' 2>/dev/null | sort > '/var/amanda/daily/index/10.0.0.17/hda1/20020121_1' f /var/amanda/daily/index/10.0.0.17/hda1/20020121_1 < 500 "/" is an invalid directory > QUIT Removing index file: /var/amanda/daily/index/10.0.0.17/hda1/20020121_1 < 200 Good bye. I can't really figure out what's going on but it appears that it's not able to read the index file because it's compressed? the Uncompress command would send to stdout, not /var/amanda/daily/index/10.0.0.17/hda1/20020121_1. Any thoughts as to what the problem might be? TIA, -- Jeremy Wadsack Wadsack-Allen Digital Group
