When you move a VM to the cloud, a base snapshot is taken. When you move a VM back to the source, different behaviors take place, depending on the storage policy configured for that VM.
- Forced move back: If there is a sustained cloud outage, you can force the VM to run on-premises or on the source. For VMs that use the write back policy, this moves the VM back to on-premises using its latest consistency checkpoint. This results in data loss up to the last stored checkpoint.
- As a safety measure, the base snapshot of a VM that runs in the cloud using the write back policy is not deleted automatically, when the Force option is used. The base snapshot can be deleted manually when verified to be no longer needed.
- When moving from AWS to GCP, write-back is not available. In this case, moving the VM back to AWS restarts the original VMs with disks as they were when beginning migration.
Using Velostrata Manager
- Login to your Velostrata Manager.
- Click the Migration Waves tab.
- When prompted for a username and password, use apiuser as the username.
- Click the monitor icon of the relevant Wave.
- Select the VM you wish to return on-premises and click Move Back.
- In the vSphere Web Client, select the virtual machine.
- Right-click the VM and select Velostrata Operations > Run On-Premises.
- If there has been a prolonged cloud outage, and you want to force a run on-premises, check the box next to Force run on-premises.
- Enter the displayed confirmation code to approve the action.
- Click OK. VMs returning from the cloud are automatically started on-premises.
To view the process of running the VM on source, you can use the Cloud Instance Information portlet on the VM Summary page. You can also monitor the vSphere task.