This article describes how to enable replication for on-premises VMware virtual machines to Azure, using the Azure Site Recovery service in the Azure portal.
Post comments and questions at the bottom of this article, or on the Azure Recovery Services Forum.
Before you start
- VMware VMs must have the Mobility service component installed. - If a VM is prepared for push installation, the process server automatically installs the Mobility service when you enable replication.
- Your Azure user account needs specific permissions to enable replication of a VM to Azure
- When you add or modify VMs, it can take up to 15 minutes or longer for changes to take effect, and for them to appear in the portal.
- You can check the last discovered time for VMs in Configuration Servers > Last Contact At.
- To add VMs without waiting for the scheduled discovery, highlight the configuration server (don’t click it), and click Refresh.
Exclude disks from replication
By default all disks on a machine are replicated. You can exclude disks from replication. For example you might not want to replicate disks with temporary data, or data that's refreshed each time a machine or application restarts (for example pagefile.sys or SQL Server tempdb). Learn more
Before you start, watch a quick video overview
- Click Step 2: Replicate application > Source.
- In Source, select the configuration server.
- In Machine type, select Virtual Machines.
- In vCenter/vSphere Hypervisor, select the vCenter server that manages the vSphere host, or select the host.
Select the process server. If you haven't created any additional process servers this will be the configuration server. Then click OK.
In Target, select the subscription and the resource group in which you want to create the failed over VMs. Choose the deployment model that you want to use in Azure (classic or resource management), for the failed over VMs.
Select the Azure storage account you want to use for replicating data. If you don't want to use an account you've already set up, you can create a new one.
Select the Azure network and subnet to which Azure VMs will connect, when they're created after failover. Select Configure now for selected machines, to apply the network setting to all machines you select for protection. Select Configure later to select the Azure network per machine. If you don't want to use an existing network, you can create one.
In Virtual Machines > Select virtual machines, click and select each machine you want to replicate. You can only select machines for which replication can be enabled. Then click OK.
- In Properties > Configure properties, select the account that will be used by the process server to automatically install the Mobility service on the machine.
By default all disks are replicated. Click All Disks and clear any disks you don't want to replicate. Then click OK. You can set additional VM properties later.
- In Replication settings > Configure replication settings, verify that the correct replication policy is selected. If you modify a policy, changes will be applied to replicating machine, and to new machines.
Enable Multi-VM consistency if you want to gather machines into a replication group, and specify a name for the group. Then click OK. Note that:
- Machines in replication groups replicate together, and have shared crash-consistent and app-consistent recovery points when they fail over.
- We recommend that you gather VMs and physical servers together so that they mirror your workloads. Enabling multi-VM consistency can impact workload performance, and should only be used if machines are running the same workload and you need consistency.
- Click Enable Replication. You can track progress of the Enable Protection job in Settings > Jobs > Site Recovery Jobs. After the Finalize Protection job runs the machine is ready for failover.