On Monday 11 July 2005 23:08, Ludovic Strappazon wrote:
> Kern Sibbald a écrit :
> >On Monday 11 July 2005 19:01, Alan Brown wrote:
> >>On Fri, 8 Jul 2005, Kern Sibbald wrote:
> >>>Bacula should never prune and hence recycle the last valid Full,...
> >>>backup it has done.
> >>>
> >>>For some strange reason, I never implemented code to check and no one
> >>>complained until recently. There is already an open bug report on this.
> >>
> >>*wishlist: last complete Full backup by default, but user-defineable
> >>number would be even better (to allow for 2 complete sets in safe, etc)
> >
> >I'll implement something after 1.38 is released. There is not enough time
> > to make sure that no new bug is introduced by any change at this point.
> >
> >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.
>
> So, what do you think of "don't prune a full if there is a non prunable
> diff or inc refering to it, and don't prune a diff if there is a non
> prunable inc refering to it" ?
I'm concidering not pruning the last Full and anything after it -- i.e. only
prune before the last Full AND if the last full is more than a month past
your retention period, go ahead and prune it.
--
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
