On Fri, Jul 2, 2010 at 11:23 PM, Jon LaBadie <j...@jgcomp.com> wrote:
> If the 'define holdingdisk "name"' syntax is used, are you saying
> the 'holdingdisk "name"' directive must be used to specify which
> defined hd to use?
No, and actually this is just an extension of the existing
terminology. For forever, the following syntax has worked to specify
a holding disk:
holdingdisk "foo" {
directory "/foo"
# ...
}
But unlike tapetypes or other config subsections, there was no way to
define a holdingdisk that was not subsequently used -- and for some
unusually contorted Amanda configurations, this flexbility was useful
(I don't recall who requested this or what the use-case was). So we
designed the *additional* ability to write
define holdingdisk "foo" {
directory "/foo"
# ...
}
and to put a holding disk "into play" with
holdingdisk "foo"
> If multiple 'define holdingdisk "name"' are specified, can a
> dumptype use any collection of them with multiple 'holdingdisk "name"'
> directives? Or, can multiple "name(s)" go on the same line?
This is not a dumptype directive - particular DLEs can not be directed
to a particular holding disk.
> Is there a reason that holdingdisk {yes|required} does not imply
> use any and all defined holdingdisks?
It means use any and all "active" holding disks.
This probably isn't clear in the documentation. Can you send along an
adjusted version that is clearer, and I'll take care of getting it
translated to docbook and committed? (You're certainly welcome to
send me a docbook patch too, if you're so inclined!)
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
