ASR Failover

Hello Handian Sudianto, In Azure Site Recovery (ASR), the “Complete Migration” option is separate from the basic failover flow.

Based on the provided docs, here’s the key behavior:

• Failover (to Azure) is what creates/starts the replica VM in Azure from the selected recovery point (for example, Latest, Latest processed, etc.).
  • If you choose Latest, ASR creates a recovery point from whatever data has been sent to the service at the time failover was triggered (lowest RPO).
  • After failover finishes, you’ll see the replica VM in Azure Portal > Virtual Machines.
  • You still need to Commit to finish the failover. The docs note that committing deletes all available recovery points.
• Replication after failover:
  • The docs indicate that after you commit failover, the VMs in the disaster recovery region remain unprotected.
  • A subsequent re-protect operation then performs a fresh initial seeding of disks and previously replicated data can’t be reused in the reverse direction.

So if you do failover but don’t do “Complete Migration”, the main practical implication is that you’re essentially stopping at the stage where the VM is active in Azure, but you’re not completing the full “re-protect / make the other side primary” lifecycle. You should expect that future direction changes (re-protect/failback) will behave like a new seeding/initial sync, and the workflow won’t be as streamlined as a full migration process.

What to check in your specific case

From the screenshot you shared, it looks like:

• Replication Health is Healthy
• Failover committed is shown
• Configuration issues: No issues
• Agent version looks fine

If you tell us what you’re trying to do next (e.g., failback, re-protect, reconnect apps, etc.), we can help you on that.

Reference list (all relevant docs from the provided material)

https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-failover

https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-failover-to-azure-troubleshoot?tabs=28031%2Cconnect-button

https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-failover-to-azure-troubleshoot?tabs=28031%2Cconnect-button#failover-failed-with-error-id-28031

https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-test-failover-to-azure

Hope this helps. If the information was useful, please consider accepting the answer and upvoting. Feel free to reach out if you need any further assistance. Thank you.

Hi..

Previously i have onprem VM and this VM replicated to azure via ASR. Some weeks ago the VM is broken and we decided to migrate the VM to azure and for that reason i do the ASR failover.

Created VM in azure is working normally but in the ASR i still not push the complete migration and just want to know the negative impact if i not doing that.

Hello Handian Sudianto,

Thanks for the details, there is no negative impact to your running Azure VM. Since your failover is already committed and replication health shows Healthy with no configuration issues, the migrated VM will continue to run normally whether or not you click Complete Migration.

Here's what "Complete Migration" actually does and why it matters in your scenario:

What the failover did already

• Failover created and started the replica VM in Azure from your selected recovery point.
• Commit finalized the failover (note: committing removes the older available recovery points).

What "Complete Migration" adds

• Complete Migration is a clean-up/lifecycle action, not a data action. Internally it performs Commit + Disable Replication, which permanently stops replication and releases the ASR configuration for that item.
• It's intended for exactly your situation — when you do not plan to go back to the original on-prem source.

If you do NOT run Complete Migration

• The item stays in a disaster-recovery (DR) state rather than a completed migration.
• ASR keeps the replicated item and its configuration (so re-protect/failback could be set up later).
• The DR-region VM remains unprotected until you re-protect, and any future re-protect/failback would perform a fresh initial seeding (previous replicated data can't be reused in reverse).
• Practically: no harm to the VM, but you continue to hold an ASR replication object/config you no longer need.

Reference docs:

• Run a failover: https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-failover
• Failover/failback overview (Modernized): https://learn.microsoft.com/en-us/azure/site-recovery/failover-failback-overview-modernized
• Failover troubleshooting: https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-failover-to-azure-troubleshoot?tabs=28031%2Cconnect-button

Hope this helps. If the information was useful, please consider accepting the answer and upvoting. Feel free to reach out if you need any further assistance. Thank you.