Dave Miner wrote: > Sarah Jelinek wrote: >>>>> -Who manages the retention policies? libbe? The text says that libbe >>>>> will provide a way to delete, display, create snapshots, but if a >>>>> policy indicates a retention of say 5 hours, who goes back and >>>>> deletes this? In >>> libbe enforces the retention policy, but its more of a "passive" >>> enforcement. i.e. we won't be having a be-daemon running around >>> checking statuses of BE snapshots. Instead, on each invocation of >>> BE or BE snapshot creation, we run through the snapshots and delete >>> the ones that have outstayed their policy. >>> >> Ah, ok, I see. I assume users can create agents to handle this policy >> management more actively if they wanted? >> > > We might want to provide a cron job or something which can be simply > enabled to implement the policy actively. The problem I see with doing > this purely passively is that the cleanup can be slightly > time-consuming, and as a result I think you'd need to offer options on > the BE management to defer it from happening automatically at BE > creation/snapshotting when it would be inconvenient for the user.
Thanks for the suggestion. If its purely a performance concern, this may be something we'll defer to Phase II. -ethan > > Dave > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
