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.
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.
(*) I have a couple of clients right now which are dead on hardware
issues, their schedule has been altered from "daily" to "never"
-------------------------------------------------------
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
