On Fri 04 Jan 2008, Barton C Massey 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'm just saying that if you configure it such that an image that's just been created is already eligible for deletion, then dirvish-expire is correct in doing that. This has nothing to do with expire rules that would override the expiry time listed in the image -- they don't exist. > > 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. If I do "rm -rf / tmp/bla" as root, that would be a disaster too. However, I wouldn't want to see the rm command modified to stop me from doing so. Doing backups is an important task. You *need* to know what you're doing. Using appropriate logging and check scripts as can be found in the wiki or faq are useful for detecting failed backups, so that you won't end up in the situation that the most recent (successful!) backup was weeks or months ago. If, on the other hand, your most recent backup was yesterday, and dirvish-expire wants to remove that, then you've made en error in the expire rules, there's no other way this could happen (barring the system time being set forward by days / weeks / months). If you don't get fancy with the expiry rules and just go for e.g. a plain +1 month, then by design the most recent backup simply can't be the first to be removed. And if the backup breaks without you noticing it, the most recent one will in fact be the only one that dirvish-expire will already refuse to remove. Perhaps you need to show the list your configuration and the relevant lines of the image summary files (where the expiry time is stored). Paul Slootman _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
