Customer wants to retain snapshots if possible
#Anyone rehost an FC LUN in an NVMeOF namespace? This is for VMware
late silo
fathom depot
converting LUNs to Namespaces happens in-place, so the volume snapshots will be left intact (however, in the snapshots, it will still be a LUN, so after, say, a SnapRestore you will need to convert it again)
(I don't understand the picture in that context though, maybe I misunderstood something)
late silo
(I don't understand the picture in that context though, maybe I misunderstood so...
just a pic for attention... That said; so an existing FC lun can easily be converted, correct and is it non disruptive? There are no labs to try this
fathom depot
it will be disruptive of course. You have to unmap the LUN first, then convert it, then map the resulting namespace. You cannot map something you don't (yet) have 😉
If it helps you, you can familiarize yourself with the process by testing it with a small test LUN first
late silo
awesome I told the customer it likely would be and they should create the namespace and try it out on a test server first
fathom depot
if you want a non-disruptive solution you would need to create a new namespace and then use Storage VMotion to migrate the VMs from the LUN to the namespace. That takes longer, requires more space, but will be nondisruptive
late silo
right but snaps are gone then... 🙂
they use snapcenter and netapp snaps and vaults as their only data protection
fathom depot
well you can keep the old volume around for as long as you need though