Article number
000003839
Affected Versions
All
Source Hypervisor
All
Target Hypervisor
Azure

Cannot Commit a Failover after VM migration to Azure

Viewed 125 times

Root Cause

During the Failover live before the VM was committed -  the IP was changes to this VM (DHCP to static)
The expected is first to commit before changing those kind of VM settings. (network and disks).

Symptoms

Cannot Commit a Failover after VM migration to Azure - getting error: Failed: Failed to get reflection data for VM

During the Failover live before the VM was committed -  the IP was changes to this VM (DHCP to static)
after that seems to be an issue getting reflection data for that newly created VM on the Azure side.

Solution

In an attempt to prevent a rollback to the fail-over and run another one again, we revered all VM changes back to the original to be identical as it was during the VPG replication (same IP, Subnets, and Security groups). As well as validate that no disk size changes are done.

Once revert was completed the commit worked as expected.