Well, after reading all of the answers up to this time, nobody yet had a *policy *to offer...
Some thoughts:
* If you attach a new policy to the volume(s), it will create *new *snapshots, but not necessarily delete the old ones, even if you tell it to keep none. _*It's all in the names...*_ * So, to delete the snapshots with a policy you'll have to o change the policy (if it's used ONLY for those volumes, where the snapshots need to be deleted) or o copy the policy (sort of manually), and apply them to said volume(s) o set the "Retained Snapshot Count" to 0 o wait for the schedule to execute the first time... ALL GONE
I tested it with a 'default'-cloned policy of
* Hourly, 0 * Daily, 0 * Weekly, 0
waited until 5 past the hour (as usual, I didn't change that) and ALL the snapshots were gone, including the daily and weekly... (Lab system...)
Hope that helps
Sebastian
On 3/3/2015 5:25 PM, Mark Flint wrote:
So, I have a user who want me to turn of snapshots, and delete the old ones, across about 100 areas, all of over 10TB in size. No problem says I….. then my poor brain starts to think about how I could do this using the available policies. A colleague suggested altering the specific protection policy applied to these areas, so that the policy has zero snapshots kept, with the thought that it would slowly ‘age them out’. Turns out not, or that’s the way it looks at the moment. So, I’m left with a couple of options, basically, manually delete all the snapshots via script, and turn off snapshotting completely on those areas, and reduce the snap reserve to zero…..or hope the policy will do some magic for me overnight.
Anyone think of a better way to do this?
Happy Tuesday!
~Mark
mark.flint@sanger.ac.uk mailto:mark.flint@sanger.ac.uk
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters