On Tuesday 12 July 2005 11:53, Alan Brown wrote:
> On Mon, 11 Jul 2005, Kern Sibbald wrote:
> >> *wishlist: last complete Full backup by default, but user-defineable
> >> number would be even better (to allow for 2 complete sets in safe, etc)
> >
> > The problem I have with this is: suppose you backup a Client containing a
> > terabyte of data. You set your retention time to 1 month because after
> > that the data is of no use. You don't do any more backups because the
> > Client is taken off line. If the last Full backup + others are not
> > pruned, the terabyte of useless data will remain forever.
>
> In our case we'd keep the data at least a year anyway, however in the case
> of a dead client where the data is of no further use, I would expect
> people to explicitly purge the client's jobs at commandline.
OK, keeping data a year is easy -- simply set the expiration period for the
Volumes so they will not be reused as well as for the jobs.
I'm not much of a fan of manual intervention.
>
> The other obvious alternative is to allow Bacula to automagically
> prune/purge all time-expired backup sets which are no longer defined in
> bacula-dir.conf - and in the case of a permanently dead client(*) it is
> logical to expect it would be removed from there, else error messages will
> be generated.
Unfortunately, old unused Client definitions often remain in the
bacula-dir.conf (at least this is the case for me). This seems to complicate
the problem and doesn't resolve my concern that Bacula is currently too
agressive doing pruning. Normally this over zelous pruning is not obvious
unless you set pruning times very short as a few people do so that they can
rotate through a very small set of tapes.
>
>
> (*) I have a couple of clients right now which are dead on hardware
> issues, their schedule has been altered from "daily" to "never"
The issue here is what to do to the catalog when the retention period expires.
As it stands, Bacula will prune the records after the retention expires. I'm
proposing "extending" what currently happens to something more logical.
That is: regardless of the retention period, Bacula will not prune the last
Full, Diff, or Inc File data until a month after the retention period for the
last Full backup that was done.
This is additional security for your data and also "automagically" prunes the
database as you define, but in a slightly more intelligent manner.
Unless someone can find some really good points against this, it is what I
plan to implement.
--
Best regards,
Kern
(">
/\
V_V
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
