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. > Since dirvish-expire is run before the actual backups, > there's a period when there may be no recent backup on the > disk---that seems to me like an unecessary and scary Again, if you choose to configure it like that, then that's what you get. > vulnerability, especially given the propensity of a good > backing-up to expose flaws in the underlying filesystems and > whatnot. The expire won't normally save much space anyway, > since presumably the next incremental will put most of it > back anyhow. > > 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! > 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. Paul Slootman _______________________________________________ Dirvish mailing list [email protected] http://www.dirvish.org/mailman/listinfo/dirvish
