Jon LaBadie <j...@jgcomp.com> (Mo 25 Feb 2013 21:43:29 CET): … > >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.
Until some days ago I thought "amandates" is the client configuration
option to use. But unfortunately it's only used by GNUTAR.
I start looking into the source of the client…
(Something else I discovered: the server is able to tell the client the
last dump date. But as far as I understand form the source, this
dumpdate is only passed on non-xml communication between the server and
the client. Probably when the server talks to a very ancient client.
This date could be used for dump(8)'s "-T" option. It would make dump(8)
independend on the dumpdates file. But I'm still not sure about the
origin of this time - if it's the servers time, it's not very useful for
incremental backups - But this timestamp (dumpdate) looks most
attractive to me :-)
Best regards from Dresden/Germany
Viele Grüße aus Dresden
Heiko Schlittermann
--
SCHLITTERMANN.de ---------------------------- internet & unix support -
Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
gnupg encrypted messages are welcome --------------- key ID: 7CBF764A -
gnupg fingerprint: 9288 F17D BBF9 9625 5ABC 285C 26A9 687E 7CBF 764A -
(gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2 7E92 EE4E AC98 48D0 359B)-
signature.asc
Description: Digital signature
