Steve Ramage wrote: > I don't believe that only the most recent should be the only preserved > backup, but I fail to see the harm in having an option to set this. > Different setups require different needs. I would personally also like > to see dirvish-expire carry forward or backwards the expire time for > failed backups, and trump smaller values. I.E. If every monday the > backup is preserved for one year, and monday fails, then either Sunday > is modified to have a one year backup (if it is less than a year) > backup, or Tuesday is.
I agree with your sentiment and especially with the notion that the backups in such a scenario constitute separate but related streams. But it does make it a little clearer how tricky the rules might need to be and so how thorough the testing of any change would need to be before people who really depend on their backups (e.g. business or career at stake) could risk using it. And the difficulty of stress testing dirvish has been dicussed several times before. I think you could make a configuration that did what you want by using separate vaults (or maybe branches??) for the different backup streams. The cost would be a little extra disk space. But perhaps using Keith's failsafe scheme wouldn't cost much more! Cheers, Dave _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
