Move Azure VM across regions

Question

We plan to migrate a VM from East Asia (Zone 1) to Southeast Asia using Azure Resource Mover. Below are my clarified questions:

1. Replication Behavior of Azure Site Recovery Mobility Agent

"During the prepare process, the Azure Site Recovery Mobility agent is installed on the VMs to replicate them."

Question:

Does this mean replication continues indefinitely until the move is initiated? For example, if we pause at the preparation stage for several days, will data synchronization persist?

2. New Public IP Assignment

Scenario:

Since our customer/service provider must be notified of the new IP 1–2 weeks in advance.
We will create a new Southeast Asia public IP first then attach new IP to new VM after the commit process.

Steps Proposed:

Create the Southeast Asia public IP resource pre-migration.

Attach the new IP to the VM after committing the move (post-migration).

Question:

After committing the move, what is the status of source and new VM.

For example:

Does the source VM remain operational/running after the commit process completes?

Will the new VM start automatically after the commit process?

Answer 1

Hi @Andrew Chan,

Welcome to Microsoft Q&A Forum, thank you for posting your query here!

Replication Behavior of Azure Site Recovery Mobility Agent: The replication process doesn't go on forever. In the preparation stage, the Azure Site Recovery Mobility agent is installed to copy the VM data to the target region at regular intervals. This replication is set up to avoid impacting the source VM. If you stop at the preparation stage, the data will continue to sync until you decide to start the move.

New Public IP Assignment: After committing the move, the source VM will be in a state of "Delete source pending," meaning it will not be operational and will be shut down. The new VM, which is created in the Southeast Asia region, will start automatically after the commit process is completed.

Refer below MS links for More Information: -

https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-migrate#discard

https://learn.microsoft.com/en-us/azure/resource-mover/move-region-availability-zone#initiate-the-move

https://learn.microsoft.com/en-us/azure/resource-mover/about-move-process

It's important to note that there may be some downtime during the move process, especially for stateful resources like VMs1. The commit process can result in source resources becoming inaccessible, so plan accordingly and ensure you have communicated the expected downtime to your customers or service providers

Let us know if any help, we will always help as you needed.!

Please do not forget to "Accept the answer” and upvote it wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.