[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amanda-hackers
Subject:    dumpdates file per config
From:       Heiko Schlittermann <hs () schlittermann ! de>
Date:       2013-02-28 12:49:31
Message-ID: 20130228124931.GB16797 () jumper ! schlittermann ! de
[Download RAW message or body]


Hello,

I'm using multiple configs for backups. These configs use dump(8) for
creating the backup. And they all use "record yes". Unfortunately all
these dump(8)s share the same "dumpdates" file. 

I'd like to have an own "dumpdates" file for each of the configurations.
To achieve this, I've patched the client-src/* files to allow a
client-config option "dumpdates", its value is passed to dump
(param/key "D"). I'd be happy if I could send this patch upstream.

But first some questions arise:

    - are there any portability issues with "dump"?
    - what about xdump, vfsdump, and all these other *dumps?

Some more thoughts: What, if the default location of all these state
information files (amandates, gnutar-list-dir, and my new dumpdates) is
could be choosen automatically - depending on the configurion that is
running?  

Why - you may ask. Imagine, the backup operator changes the name of the
configs used, suddently the well prepared $config/amanda-client.conf
doesn't apply anymore and the state files are shared - leading to
incomplete dumps, and tars.

Any opinions anybody?

    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" (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]