In message <[EMAIL PROTECTED]> you wrote:
> On Thu 03 Jan 2008, Barton C Massey wrote:
>
> > It looks like dirvish-expire has no qualms about removing
> > the most recent image in a vault. This seems to me to be a
> > bad idea.
>
> Well, if that's a problem, then you need to fix your expire rules.
Is there some semantic I can give in the expire rules that
guarantees that the most recent backup will be preserved,
regardless of its date? I wasn't aware of one, but maybe I
missed it...
> > I considered whether to just run dirvish-expire after the
> > backup period, but that leads to potential for the other
> > kind of scary scenario, especially if dirvish-expire is
> > happy to remove the latest image.
>
> If the expire would remove the backup that dirvish just --
> minutes ago -- created, then there's something *SERIOUSLY*
> wrong with your expire rules!
Put it the other way round---if there was ever something
seriously wrong with my expire rules, it would move from
being an annoyance to a disaster.
> > Any chance someone could fix this so that dirvish-expire
> > will leave the most recent bits alone, at least as an
> > option?
>
> Apart from the fact that it basically only does what you
> (albeit indirectly) tell it to do, this may actually be
> useful, recent changes would have to be transferred again,
> as you say.
I'll take a look at doing this sometime in the indefinite
near future unless someone beats me to it.
Bart
_______________________________________________
Dirvish mailing list
[email protected]
http://www.dirvish.org/mailman/listinfo/dirvish
