
UNSOLVED
Can VNX snapshot still work after primary LUN is deleted?
My customer asked me if VNX snapshot will work after primary LUN is deleted, according to him, NetApp has feature called FLEXClone and my customer states that if he takes snapshot and deletes primary LUN on NetApp storage he can use snapshot to restore or to make clone of the orginal LUN.
Does anyone know if we can do the same thing on VNX?
Responses (1)
Solutions (0)

AdamFox
254 Posts
488
0
Posted November 13th, 2013 13:00
Ok. I'll clarify a few things.
FlexClone doesn't involve restoring a deleted LUN. You can split off a clone and thus disassociate it from it's parent LUN, then if you delete the parent LUN, it doesn't matter. If you somehow deleted a LUN, the volume level snapshot could be used to recover it. However, you'd have to delete in a weird way because you can't just call 'lun delete ...' on a LUN that is mapped up and being used (and probably if it has snaps associated with it). However, since in NetApp-land, all LUNs are really just files, it may be possible to map up the filesystem via NFS and force a delete of the .lun file.
VNX doesn't really have this problem because aren't a file sitting in a volume (at least not explicitly like NetApp.). What we do, however, is prevent you from deleting the LUN that has snaps associated with it, unless you *specifically* tell it to do so (i.e. there is an option to remove a LUN with all of it's snaps, but you're not going to do that by accident). See my screen shot below:
So, we don't let you do what they are trying to protect you from doing and you can't mount up a filesystem to manually delete it outside of the system because we aren't designed that way. This feature on NetApp is there to protect you against doing something that you can only do because of the way they do LUNs (implemented as files on exportable filesystems)
Hope this helps.