On Monday 29 March 2010, Craig Constantine wrote:
>I have an /etc/amanda/foo/amanda.conf which starts with:
>
>define holdingdisk "external_holding" {
> directory "/media/amanda_holdingdisk"
>}
>
>...and amcheck complains:
>
>amandabac...@backupserver:/etc/amanda/foo$ amcheck foo
>"/etc/amanda/foo/amanda.conf", line 2: DUMPTYPE, INTERFACE, TAPETYPE,
>APPLICATION-TOOL, SCRIPT-TOOL, DEVICE, or CHANGER expected
>"/etc/amanda/foo/amanda.conf", line 2: end of line is expected
>"/etc/amanda/foo/amanda.conf", line 3: configuration keyword expected
>"/etc/amanda/foo/amanda.conf", line 4: configuration keyword expected
>"/etc/amanda/foo/amanda.conf", line 5: configuration keyword expected
>amcheck: errors processing config file
>
>...line 2 is the "define holdingdisk . . ." line. Isn't this how I
>define a holdingdisk?
>
I don't think it needs the 'define' above, here is mine that has been in
continuous use for several years now:
holdingdisk hd1 {
comment "main holding disk"
directory "/dumps" # where the holding disk is
use -500 Mb # how much space can we use on it
# a non-positive value means:
# use all space but that value
chunksize 2000Mb # size of chunk if you want big dump to be
# dumped on multiple files on holding disks
# N Kb/Mb/Gb split images in chunks of size N
# The maximum value should be
# (MAX_FILE_SIZE - 1Mb)
# 0 same as INT_MAX bytes
}
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Didn't I buy a 1951 Packard from you last March in Cairo?
