Configure replication of on-premises virtual machines

You’ve completed discovery and assessment and have identified the specific servers you plan to migrate for the pilot. You’ve also ensured that required prerequisites are in place for the Azure Migrate project and your on-premises VMs.

Having completed these preparations, you’re ready to migrate your selected Hyper-V workloads to Azure.

In this unit, you’ll review Azure Migrate Server Migration and how to configure replication for specific workloads to Azure.

Set up replication

The first step in migrating servers is to replicate them. In this task, you configure and enable the replication of your on-premises virtual machines from Hyper-V to the Azure Migrate Server Migration service.

In the Azure Migrate Server Migration tool, click Replicate.

Screenshot of the Azure Migrate: Server Migration panel with the Replicate button highlighted in red. The screenshot shows the number of discovered servers at 5 and the number of replicating servers at 0.

In Source settings, select the Hyper-V workload.

Screenshot of the Source settings options in the Replicate blade. The dropdown option for Are your machines virtualized? is highlighted in red and the option is set to Yes with Hyper-V.

Although you can import migration settings from an existing assessment, you decide to specify the migrations settings for the VMs manually. This lets you change VM sizing and OS disk settings as needed.

Screenshot of the Virtual machines settings options in the Replicate blade. Virtual machines is highlighted with a red border. The dropdown option for the Import migration settings from an assessment? Is shown as set to No, I’ll specify the migration settings manually and also highlighted with a red border.

In Virtual Machines, select the VMs you plan to migrate. You can replicate up to 10 machines together. You’ve selected 20 machines for the pilot, so you’ll replicate them in 2 batches of 10.

citrix certification malaysia

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *