About managing VMware Storage vMotion in Resiliency Platform
Resiliency Platform now supports VMware Storage vMotion. With Storage vMotion, you can migrate a virtual machine from one datastore to another while the virtual machine is running. This lets you move the virtual machines off the arrays for maintenance or for upgrade. Consider the following while performing Storage vMotion using Resiliency Platform.
When using 3rd party replication technology, depending on which datastore the virtual disk is moved to, you may need to edit the resiliency group. The scenarios are listed below.
Scenario
Edit the resiliency group (Yes/No)
Virtual disk moves within the same datastore cluster
No
Virtual disk moves to a datastore that is part of the same consistency group
No
Virtual disk moves to a datastore that is not a part of the same consistency group
Yes. Or move the virtual disk to any datastore that is part of the consistency group.
During Storage vMotion, ensure that the new datastore is accessible to all the ESX servers in the cluster including the one hosting the Replication Gateway. This is applicable when the replication technology is Resiliency Platform Data Mover.
Note:
When a risk for Storage vMotion is raised, all operations are blocked. You can only edit or delete the resiliency group.
When the resiliency group is online on cloud data center and you have upgraded to version 3.2 or later, then do not perform Storage vMotion for the on-premises Replication Gateway. Migrate back to the on-premises data center, edit the resiliency group, and only then you should perform Storage vMotion.
If you perform Host vMotion, then during the subsequent Storage vMotion operation ensure that the movement happens to the datastore which is accessible to all the ESX servers including the one hosting the gateway.
For more information on VMware Storage vMotion feature, refer to VMware documentation.