This sounds like another task that would be easier if we could load servlets onto the filers.
On Sep 11, 6:05, Daniel Quinlan wrote:
Subject: snapshot scheduling One of our filers has high data turn-around so I have limited the snapshot lifetime to 2 days (the default) to keep usage at about 10%. We use 4 days on our other filer because it experiences a lower rate of data turn-around.
snap list
working........................ %/used %/total date name
1% ( 1%) 0% ( 0%) Sep 10 20:01 hourly.0 3% ( 3%) 2% ( 2%) Sep 10 16:01 hourly.1 5% ( 3%) 4% ( 2%) Sep 10 12:01 hourly.2 6% ( 3%) 5% ( 2%) Sep 10 08:01 hourly.3 8% ( 4%) 6% ( 3%) Sep 10 00:01 nightly.0 8% ( 4%) 6% ( 3%) Sep 09 20:01 hourly.4 10% ( 4%) 7% ( 3%) Sep 09 16:02 hourly.5 12% ( 5%) 10% ( 3%) Sep 09 00:01 nightly.1
Unfortunately, 2 days means that if someone deletes a file on Friday, it will be gone by the next work day, Monday. There is also a lower rate of data turn-around on the weekend. 3 days would be ideal, except on weekdays where it can sometimes push the snapshot usage higher than I want.
Is there some way (other than a remote cron job twice a week) to acheive what I want -- variable snapshot lifetimes according to the day of the week?
If not, it would be a nice feature. Either that, or options to force deletion of n number of nightly snapshots (over m days old) when snapshot usage goes over some percentage.
Dan
-- Daniel Quinlan (at work) Linux, our last best hope for Unix quinlan@transmeta.com http://www.pathname.com/~quinlan/ ... (Got BOFH? Looking for good ones.) -- End of excerpt from Daniel Quinlan