$ man amanda.conf
DUMPTYPE SECTION
allow-split bool
TAPETYPE SECTION
part-size int
part-cache-type [ none | disk | memory ]
part-cache-dir string
part-cache-max-size int
The part-* parameter go in the tapetype section, they are the same for
all dles.
In the dumptype, you write (allow-split) if you want the dle to be split
or not.
Jean-Louis
Jon LaBadie wrote:
On Tue, Oct 26, 2010 at 11:30:04AM -0400, Jean-Louis Martineau wrote:
Jon,
What is the exact error message you get?
Where do you put the allow-split? Post the complete dumptype.
That, of course, was only one of the keywords that are not working.
Originally I had placed the following 5 lines "globally",
outside of any dumptype, just before the definition of the
first dumptypes (bsdtcp and global).
allow_split true
part_size 3gb
part_cache_type disk
part_cache_dir "/hold/amanda/PartCache"
part_cache_size 1gb
With that setup I get this from 'amcheck Daily -s':
"/etc/amanda/Daily/amanda.conf", line 441: configuration keyword expected
"/etc/amanda/Daily/amanda.conf", line 442: configuration keyword expected
"/etc/amanda/Daily/amanda.conf", line 443: configuration keyword expected
"/etc/amanda/Daily/amanda.conf", line 444: configuration keyword expected
"/etc/amanda/Daily/amanda.conf", line 445: configuration keyword expected
amcheck: errors processing config file
Based on your question, I tried them in "dumptype global" and got this:
"/etc/amanda/Daily/amanda.conf", line 480: dumptype parameter expected
"/etc/amanda/Daily/amanda.conf", line 480: end of line is expected
"/etc/amanda/Daily/amanda.conf", line 481: dumptype parameter expected
"/etc/amanda/Daily/amanda.conf", line 482: dumptype parameter expected
"/etc/amanda/Daily/amanda.conf", line 482: end of line is expected
"/etc/amanda/Daily/amanda.conf", line 484: dumptype parameter expected
"/etc/amanda/Daily/amanda.conf", line 484: end of line is expected
"/etc/amanda/Daily/amanda.conf", line 486: dumptype parameter expected
"/etc/amanda/Daily/amanda.conf", line 486: end of line is expected
"/etc/amanda/Daily/amanda.conf", line 487: dumptype parameter expected
amcheck: errors processing config file
The relevant section of the file (starting with line 437 is:
# Note that you may specify previously defined dumptypes as a shorthand way of
# defining parameters.
#
#
#allow_split true
#part_size 3gb
#part_cache_type disk
#part_cache_dir "/hold/amanda/PartCache"
#part_cache_size 1gb
#
define dumptype bsdtcp {
auth "bsdtcp"
}
define dumptype global {
comment "Global definitions"
# This is quite useful for setting global parameters, so you don't have
# to type them everywhere. All dumptype definitions in this sample file
# do include these definitions, either directly or indirectly.
# There's nothing special about the name `global'; if you create any
# dumptype that does not contain the word `global' or the name of any
# other dumptype that contains it, these definitions won't apply.
# Note that these definitions may be overridden in other
# dumptypes, if the redefinitions appear *after* the `global'
# dumptype name.
# You may want to use this for globally enabling or disabling
# indexing, recording, etc. Some examples:
# index yes
# record no
# split_diskbuffer "/raid/amanda"
# fallback_splitsize 64m
index yes
record yes
estimate calcsize
maxdumps 2
maxpromoteday 4
bsdtcp
# split_diskbuffer "/hold/amanda/SplitBuf"
# fallback_splitsize 100M
exclude file append "./*/.gvfs"
exclude file append "./var/run"
allow_split true
part_size 3gb
part_cache_type disk
part_cache_dir "/hold/amanda/PartCache"
part_cache_size 1gb
}
Jon LaBadie wrote:
My amanda server is running Fedora 13. I recently
updated the amanda package from 3.1.3 to 3.2.0.
Both versions were Zmanda-built packages for Fedora 12.
When amcheck or amdump is run with the amanda.conf I
was using for 3.1.3, they report several "deprecated"
keywords. Most, maybe all, dealt with tape splitting.
However, when I try to modify amanda.conf to use the
replacement directives (eg. allow-split), neither
command recognizes the replacements (keyword expected).
Anyone else seeing similar behavior in their 3.2.0
versions?
Jon
End of included message <<<
