Hi Colin,  Your proposed procedure will *not* work due to the fact that the host is sending writes (making changes) to blocks of storage on V7000 after VPLEX has copied those blocks to the VNX2.   The VPLEX does not receive the new host writes and the data you end up with on the VNX2 will be inconsistent / corrupted / unusable.  If the ESXi host and/or corresponding VM's are not writing data to the V7000 (aka making changes to the disk) then the scenario you describe would likely work. To guarantee success you'd want the datastore or RDM to be unmounted prior to performing the mobility as you've described it.   Note: If the V7000 was encapsulated through VPLEX, then you could perform the migration using mobility central without any issues.  Regards,    -Don
Hi,  Would it be possible to use a VPLEX as a migration tool but not have the host connected to the VPLEX at all?  So lets say I have a ESX host with VM's using RDM's connected to a IBM V7000. I want to migrate them to a EMC VNX2, but I don't have the VPLEX licensing to host all of the storage.   Would I be able to leave the ESX host connected to the IBM V7000. Connect the LUNs to the VPLEX while they are connected to the ESX host. Connect the the target LUNs of the EMC VNX2 to the VPLEX. Use the Data Mobility to mirror the data from the V7000 to the VNX2. Shutdown the VM with the RDM and remove the RDM from the VM. Commit the Data Mobility Job. Remove the VNX2 LUN from VPLEX Attach the new VNX2 LUN to the ESX host. Finally attach the RDM to the VM and power on.  Thanks Colin
Using VPLEX as a storage migration tool