How to configure periodic replication using Resource mover

Question

Prakash Rawat 20

Can we configure continues replication using Azure resource mover.

As I understand from documentation and testing, it performs one time replication from source to target region.

It also shut-down the source VM during replication to avoid any changes on source.

This is leading higher downtime for source VM as it has more than 8 to 15 TB of Data disks attached.

Any suggestions.

Thanks

SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2023-04-03T07:23:31.1366667+00:00

@Prakash Rawat Just checking in to see if you got a chance to see my response and if it helped, I would request you to "Accept Answer and Upvote" so that the relevancy of this post will improve when anyone in the community search for a similar query.

Accepted answer

0 additional answers

SadiqhAhmed-MSFT 49,326 Reputation points Microsoft Employee Moderator

2023-04-03T07:23:31.1366667+00:00

@Prakash Rawat Just checking in to see if you got a chance to see my response and if it helped, I would request you to "Accept Answer and Upvote" so that the relevancy of this post will improve when anyone in the community search for a similar query.

Answer 1

Hello @Prakash Rawat Thank you for contacting us on Microsoft Q&A platform. Happy to help you!

I see that you have couple of questions about resource mover. I will try to answer them below.

Q1. Can we configure continues replication using Azure resource mover.

Resource Mover replication is continuous and it leverages ASR replication technology underneath. So, you are already getting what you want :-)

Q2. The source VM has more than 8 to 15 TB of Data disks attached. This is leading to higher downtime.

- Once you prepare the VM and the prepare operation is done, the state changes to Initiate move pending, in this stage the source VM is still running and available to use, and periodic replication keeps happening. Once you click Move then we shut down the VM and Create VM in target region using the latest replicated data. There is a brief downtime after you click the Move button, around 3 minutes and then the target VM comes up. In short, we don’t shutdown the VM and copy the entire 15TB , we copy the 15TB while the VM is running and just before creating the new Target VM we shutdown source.
Since it’s a continuous replication in Mover, the downtime is not proportional to the Disk size. It should be more or less the same time if it is a 1 TB disk or a 10 TB disk.

Hope this clarifies! Please reply if you have any questions.

If the response helped, do "Accept Answer" and up-vote it