Replicate Azure virtual machines to another Azure region
Site Recovery replication for Azure virtual machines is currently in preview.
This article describes how to enable replication of Azure VMs, from one Azure region to another.
This article assumes that you've already set up Site Recovery for this scenario, as described in the Azure to Azure tutorial. Make sure that you've prepared the prerequisites, and created the Recovery Services vault.
Enable replication. This procedure assumes that the primary Azure region is East Asia, and the secondary region is South East Asia.
- In the vault, click +Replicate.
Note the following fields:
- Source: The point of origin of the VMs, which in this case is Azure.
- Source location: The Azure region from where you want to protect your virtual machines. For this illustration, the source location is 'East Asia'
- Deployment model: Azure deployment model of the source machines.
Resource Group: The resource group to which your source virtual machines belong. All the VMs under the selected resource group are listed for protection in the next step.
In Virtual Machines > Select virtual machines, click and select each VM that you want to replicate. You can only select machines for which replication can be enabled. Then, click OK.
In Settings, you can optionally configure target site settings:
- Target Location: The location where your source virtual machine data will be replicated. Depending upon your selected machines location, Site Recovery will provide you the list of suitable target regions. We recommend that you keep the target location the same as the Recovery Services vault location.
- Target resource group: The resource group to which all your replicated virtual machines belong. By default Azure Site Recovery creates a new resource group in the target region with name having "asr" suffix. In case resource group created by Azure Site Recovery already exists, it is reused. You can also choose to customize it as shown in the section below.
- Target Virtual Network: By default, Site Recovery creates a new virtual network in the target region with name having "asr" suffix. This is mapped to your source network, and used for any future protection. Learn more about network mapping.
- Target Storage accounts: By default, Site Recovery creates a new target storage account mimicking your source VM storage configuration. In case storage account already exists, it is reused.
- Cache Storage accounts: Site Recovery needs extra storage account called cache storage in the source region. All the changes happening on the source VMs are tracked and sent to cache storage account before replicating those to the target location.
- Availability set: By default, Azure Site Recovery creates a new availability set in the target region with name having "asr" suffix. In case availability set created by Azure Site Recovery already exists, it is reused.
Replication Policy: It defines the settings for recovery point retention history and app consistent snapshot frequency. By default, Azure Site Recovery creates a new replication policy with default settings of ‘24 hours’ for recovery point retention and ’60 minutes’ for app consistent snapshot frequency.
Customize target resources
You can modify the default target settings used by Site Recovery.
Click Customize: to modify default settings:
- In Target resource group, select the resource group from the list of all the resource groups in the target location of the subscription.
- In Target virtual network, select the network from a list of all the virtual network in the target location.
- In Availability set, you can add availability set settings to the VM, if they're part of an availability set in the source region.
In Target Storage accounts, select the account you want to use.
Click Create target resource > Enable Replication.
- After the VMs are enabled for replication, you can check the status of VM health under Replicated items
During initial replication the status might take some time to refresh, without progress. Click the Refresh button, to get the latest status.
Learn more about running a test failover.