--On Friday, December 12, 2003 12:38:26 -0500 jessica blackburn <[EMAIL PROTECTED]> wrote:...
Here is my amanda.conf file:
tpchanger "chg-multi" # the tape-changer glue script tapedev "file:/backup/" # the no-rewind tape device to be used
I've never used the file driver in production, only played with it a little, but I think this needs to be a file, not a directory. Perhaps someone else can clarify this. More comments way below.
From "man amanda", section OUTPUT DRIVERS, item "file":
This driver emulates a tape device with a set of files in a directory. The drive-info field must be the name of an existing directory. The driver will test for a subdirectory of that named data and return offline until it is present.
In English this means: create a directory /backup. Insert a tape by creating a subdirectory /backup/data, or make a symlink "data" to an existing directory, e.g. /backup/tape01: ln -s tape01 data
But when using a changer, the tapedev specified here is not important. More important is the contents of the chg-multi.conf file you specified below.
changerfile "/etc/amanda/DailySet1/chg-multi.conf" changerdev "/dev/null"
...
...
tapetype HARD-DISK # what kind of tape it is define tapetype HARD-DISK{ comment "20GB Hard disk" length 20000 mbytes }
holdingdisk hd1 {
comment "main holding disk"
directory "/var/tmp" # where the holding disk is
use 290 Mb chunks
}
Not really a problem, but I would avoid using a directory as holdingdisk where other program dump their garbage in. Amanda will complain about "garbage" if it encounters files in the holdingdisk dir that amanda did not create.
Instead use a dedicated directory for the amanda config, something like "/var/amandahold/DailySet1", asuming you your /var disk is where the spare space is.
...
define tapetype MIMSY-MEGATAPE { comment "Megatape (Exabyte based) drive through Emulex on Vax 8600" length 2200 mbytes filemark 2130 kbytes speed 170 kbytes # limited by the Emulex bus interface, ugh }
--exclude-from="filename"
define dumptype global { comment "Global definitions"
}
What's the "--exclude-from..." doing between the dumptypes? May be copy-paste error?
On Thu, 2003-12-11 at 19:29, Frank Smith wrote:
--On Thursday, December 11, 2003 15:21:19 -0500 jessica blackburn <[EMAIL PROTECTED]> wrote:
I am very new to this amanda system and am trying to run amrecover. here is what I start with:
[EMAIL PROTECTED] RECOVER]# /usr/sbin/amrecover -C DailySet1 -s hccweb AMRECOVER Version 2.4.3. Contacting server on hccweb ... 220 hccweb AMANDA index server (2.4.3) ready. 200 Access OK Setting restore date to today (2003-12-11) 200 Working date set to 2003-12-11. 200 Config set to DailySet1. 200 Dump host set to hccweb. Trying disk / ... Trying disk rootfs ... Can't determine disk and mount point from $CWD '/var/tmp/RECOVER' amrecover> sethost hccweb 200 Dump host set to hccweb. amrecover> setdisk /etc Scanning /var/tmp... RECOVER: skipping cruft directory, perhaps you should delete it. 200 Disk set to /etc. amrecover> add syslog.conf Added /syslog.conf amrecover> extract
Extracting files using tape drive file:/backup/ on host localhost. The following tapes are needed: DailySet109
Restoring files into directory /var/tmp/RECOVER Continue [?/Y/n]? Y
Extracting files using tape drive file:/backup/ on host localhost.
Now, if you have REAL tapes, you should now change the tapedrive from the default with the "settape" command something like: settape /dev/nrst0 If it really is a backup made with the file driver, you should now insert the tape in file:/backup by creating a symlink to the DailySet109 directory, something like: cd /backup rm data ln -s /backup/DailySet109 data
Load tape DailySet109 now Continue [?/Y/n/t]? Y EOF, check amidxtaped.debug file on localhost. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1
It seems amanda finds nothing in the file:/backup device...
Continue [?/Y/n]? n amrecover> exit 200 Good bye.
-- Paul @ Home