non-disruptive volume move fibre channel

[scole7626]

I would like to know if there is any information into the details behind the scenes regarding a non-disruptive volume move.  What happens on the backend to ensure that the volume is moved without incedent?  How do the volume WWNs move between arrays?  Is the NCM on the ESX hosts as critical as with the iSCSI arrays?  Also any other pertinent information that could be provided...

[Nick_Dyer · Accepted solution]

Hello Stanton,

Non-Disruptive Volume Move with Fibre Channel is a feature of the new NimbleOS 3.1 (currently in early access release) and as such not many of us have had a chance to test it in the field, however i'm sure that the backend processes of how we migrate data between hosts has not changed from the iSCSI method we launched in NimbleOS 2.0 back in 2014.

I can tell you that Nimble Connection Manager is critical to building the Unified Flash Fabric regardless of the protocol being Fibre Channel or iSCSI.