[Dirvish] expiry rules

Paul Slootman paul at debian.org
Wed Mar 16 18:28:34 UTC 2011

On Wed 16 Mar 2011, Jon Radel wrote:
> I really don't see any way for dirvish to fix this without recognizing 
> that an "event" has happened and adjusting expiration dates to 
> compensate.  The only other fix I can think of is to use only a single 
> retention period, in which case, the last image remaining should always 
> be the most recent.  But even that won't save you if what you wanted was 
> to keep the last image made before a big break in backups.

The question I'm asking myself is how much administrative policy do you
want to program into dirvish.

Once you've set up dirvish to do its work, and have considered that you
want to keep some images for longer than other images, then you should
also be smart enough to realize that if you start getting daily emails
that backups are failing, then you should also realize that you should
take precautions to prevent the last successful backup from expiring.

In other words, if you're smart enough to set up different expiry rules,
you should also be smart enough to work around dirvish's cleaning up of
expired images when the need arises.

Of course, if someone wants to code something up for this situation,
I'd not have any problems with such a feature; as long as it's well
documented (and perhaps made optional?).


More information about the Dirvish mailing list