Hi Paul, I understand now. Thanks.
However, I 've got another problem : when I run amrecover -C "DailySet1" ... Setting restore date to today (2006-01-05) 200 Working date set to 2006-01-05. Scanning /var/tmp... 200 Config set to DailySet1. 200 Dump host set to myhost.mynetwork.com. Trying disk / ... Trying disk rootfs ... Can't determine disk and mount point from $CWD '/usr/local/amanda-2.4.5p1' amrecover> setdisk /etc/amanda 200 Disk set to /etc/amanda. No index records for disk for specified date If date correct, notify system administrator My amanda configuration, includes this ... ... indexdir "/var/lib/amanda/DailySet1/index" # index directory define dumptype hard-disk-tar { comment "Back up to hard disk instead of tape - using tar" holdingdisk no index yes priority high program "GNUTAR" strategy noinc } and my disklist file content: myhost.mynetwork.com /etc/amanda hard-disk-tar ... This is the content of /var/lib/amanda/DailySet1/index/myhost.mynetwok.com/_etc_amanda -rw------- 1 amanda disk 115 Jan 5 16:50 20060105_0.gz It was okay before I do chmod 755 to amaespipe and amgtar files Following are the files: -rwxr-xr-x 1 root root 2244 Jan 5 12:06 amaespipe -rwxr-xr-x 1 root root 554 Jan 5 12:04 amgtar I thought it was a script, so I need to do chmod, am I right? Because amanda was complaining about GNUTAR program, which should execute amgtar instead of tar. Since then, it got index problem. I don't understand why? Then I thought I might need to reconfigure and recompile amanda, which I did, but the problem still persists. Did I miss something? On Tue, 2006-01-03 at 12:53 +0100, Paul Bijnens wrote: > Ong Loeng Seng wrote: > > amrecover> settape > > myhost.mynetwork.com:amanda.conf:/var2/amandadumps/tape02 > > Using tape "amanda.conf:/var2/amandadumps/tape02" from server > > myhost.mynetwork.com. > > What is this??? Is that the name of your tape device??? > > When you are using the "FILE" driver, the name is: > myhost.mynetwork.com:file:/var2/amandadumps/tape02 > > (where "tape02" is the parent of the "data" subdirectory) > > > [...] > > Continue [?/Y/n/s/t]? Y > > EOF, check amidxtaped.<timestamp>.debug file on myhost.mynetwork.com > > amrecover: short block 0 bytes > > UNKNOWN file > > amrecover: Can't read file header > > Indeed, that's exactly what is to be expected. > > [...] > > amidxtaped: time 0.000: > DEVICE=disklist:/var2/amandadumps/tape02 > > THis time, you tried something else! This file is not from the same > run as the script above. But it is wrong just as well. > > > > The backup file is definitely in /var2/amandadumps/tape02 directory. > > I don't understand why amrestore says no such file or directory? > > If /var2/amandadumps/tape02 has a subdirectory named "data" which > contains the backup file, then the syntax is: > > settape myhost.mynetwork.com:file:/var2/amandadumps/tape02 > > The word "file" in the middle is not a placeholder, but is needed > litterally. > > > If you are using the chg-disk changer, then it is best to add these > lines to amanda.conf: > > amrecover_changer "changer" > amrecover_do_fsf true > amrecover_check_label true > > and then you can just do from within amrecover: > > settape changer > > > See: http://wiki.zmanda.com/index.php/File_driver >