On 02/22/2013 05:38:50 AM, Heiko Schlittermann wrote:
>Hello,
>
>I've multiple backup sets. The dumptype
>
>define dumptype ??? {
> program DUMP
> record yes
> index yes
>}
>
>My DLE use the dump type above. It works. But now I start using
>multiple configs, using the same DLE, the same dump types - but
>a completly different set of backup media.
>
>In other words - boths backup sets should be completly independend of
>each other.
>
>But they aren't. Every run of dump(8) updates the "dumpdates" file on
>the client side (because of "record yes"). This file is shared
>among all
>configurations and even other dump(8) invocations. I do not see any
>configuration option to specify location of the "dumpdates" file
>(similiar to the "amandates" config option for the client side
>config).
>
>How should this be solved?
Dump, but not ufsdump, has a "-D filepath" option to specify the
location of the dumpdates file if different than the standard
/etc/dumpdates. Perhaps amanda could be coerced into using
something like "-D /etc/dumpdates-$AmandaConfig". If not, you
could use your own wrapper to call "dump" with the extra option.
jon
>
>According the the sources and the debug output there is the date
>of the
>last dump passed from the server to the client, but only if non-XML
>communication is used. I'm not sure if the client would use this date.
>Using ths date "dump" would not need the "dumpdates" file.
>
--
Jon H. LaBadie [email protected]
11226 South Shore Rd. (703) 787-0688 (H)
Reston, VA 20190 (609) 477-8330 (C)
