For programatic removal of the snaps, I recommend utilizing a Snap Autodelete configuration on the volumes that you need to delete the "normal" snapshots from. It has options that allow you to remove those before the busy ones.
Matt
On Oct 3, 2011, at 1:50 PM, Learmonth, Peter wrote:
Yes, sir. That's what busy means. Even if there was a bug in FilerView, the filer won't let you delete the backing snapshot until all dependent clones are split or deleted.
Share and enjoy!
Peter
From: Fletcher Cocquyt [mailto:fcocquyt@stanford.edu] Sent: Monday, October 03, 2011 1:34 PM To: toasters@teaparty.net Subject: Cleaning up snapshots while leaving flexclones
Hi, We routinely cleanup snapshots via filerview and recently started using flexclones, which show up in the snapshot view as “busy,vclone – Busy” For this volume there are similarly named snapshots listed as “normal” We’d like to delete those to reclaim the space, but want confirmation they are not going to affect the mounted vclone(flexclone) volumes. Basically I am asking will filerview prevent me from deleting these snapshots if they are associated with an actively mounted flexclone? (
<image001.png>
Thanks
-- Fletcher Cocquyt <image002.jpg> http://vmadmin.info _______________________________________________ Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters