[Dirvish] Expire removes most recent backup?

[Eric Mountain]

On Friday 04 Jan 2008, Barton C Massey spake thus:
> That's very helpful---thanks much!  I imagine I'll go ahead
> and just make dirvish-expire do the right thing here,

I disagree with your perception of the "right thing".  See Paul's responses on 
this thread - they are spot on.

The only thing I might add is that virtually the only situation in which I can 
see the most recent image being removed at an undesirable time despite good 
expiry rule configuration, is for instance when I come back from a few weeks 
holiday and turn on my home PC (which also seems to have been Tony's 
problem).  I won't even get hit by that though since my cron jobs basically 
do "dirvish-runall && dirvish-expire" which makes sure that all backups run 
successfully at least once with the most recent image still present.

On Friday 04 Jan 2008, Tony spake thus:
> > > Normally this might not happen but I have a system that I only backup
> > > once a week - retaining the backups for a month.  Recently I ran into
> >
> > an
> >
> > > issue where I was travelling and the system was turned off.

See above: invert the runall/expire order.

Also, make sure retention periods are higher than the longest expected time 
you will go without backing up.  What's the point in only having a recent 
backup if the file you want to restore was in older ones which have been 
expired?

-- 
Eric Mountain