Support matrix for Azure VM disaster recovery between Azure regions

This article summarizes support and prerequisites for disaster recovery of Azure VMs from one Azure region to another, using the Azure Site Recovery service.

Deployment method support

Deployment Support
Azure portal Supported.
PowerShell Supported. Learn more
REST API Supported.
CLI Not currently supported

Resource support

Resource action Details
Move vaults across resource groups Not supported
Move compute/storage/network resources across resource groups Not supported.

If you move a VM or associated components such as storage/network after the VM is replicating, you need to disable and then re-enable replication for the VM.
Replicate Azure VMs from one subscription to another for disaster recovery Supported within the same Azure Active Directory tenant.
Migrate VMs across regions within supported geographical clusters (within and across subscriptions) Supported within the same Azure Active Directory tenant.
Migrate VMs within the same region Not supported.
Azure Dedicated Hosts Not supported.

Region support

Azure Site Recovery allows you to perform global disaster recovery. You can replicate and recover VMs between any two Azure regions in the world. If you have concerns around data sovereignty, you may choose to limit replication within your specific geographic cluster. The various geographic clusters are as follows:

Geographic cluster Azure regions
America Canada East, Canada Central, South Central US, West Central US, East US, East US 2, West US, West US 2, West US 3, Central US, North Central US
Europe UK West, UK South, North Europe, West Europe, South Africa West, South Africa North, Norway East, France Central, Switzerland North, Germany West Central, UAE North, UAE Central (UAE is treated as part of the Europe geo cluster)
Asia South India, Central India, West India, Southeast Asia, East Asia, Japan East, Japan West, Korea Central, Korea South
JIO JIO India West
Australia Australia East, Australia Southeast, Australia Central, Australia Central 2
Azure Government US GOV Virginia, US GOV Iowa, US GOV Arizona, US GOV Texas, US DOD East, US DOD Central
Germany Germany Central, Germany Northeast
China China East, China North, China North2, China East2
Brazil Brazil South
Restricted Regions reserved for in-country disaster recovery Switzerland West reserved for Switzerland North, France South reserved for France Central, Norway West for Norway East customers, JIO India Central for JIO India West customers, Brazil Southeast for Brazil South customers, South Africa West for South Africa North customers, Germany North for Germany West Central customers.

Note

  • For Brazil South, you can replicate and fail over to these regions: Brazil Southeast, South Central US, West Central US, East US, East US 2, West US, West US 2, and North Central US.
  • Brazil South can only be used as a source region from which VMs can replicate using Site Recovery. It can't act as a target region. Note that if you fail over from Brazil South as a source region to a target, failback to Brazil South from the target region is supported. Brazil Southeast can only be used as a target region.
  • If the region in which you want to create a vault doesn't show, make sure your subscription has access to create resources in that region.
  • If you can't see a region within a geographic cluster when you enable replication, make sure your subscription has permissions to create VMs in that region.

Cache storage

This table summarizes support for the cache storage account used by Site Recovery during replication.

Setting Support Details
General purpose V2 storage accounts (Hot and Cool tier) Supported Usage of GPv2 is not recommended because transaction costs for V2 are substantially higher than V1 storage accounts.
Premium storage Not supported Standard storage accounts are used for cache storage, to help optimize costs.
Region Same region as virtual machine Cache storage account should be in the same region as the virtual machine being protected.
Subscription Can be different from source virtual machines Cache storage account need not be in the same subscription as the source virtual machine(s).
Azure Storage firewalls for virtual networks Supported If you are using firewall enabled cache storage account or target storage account, ensure you 'Allow trusted Microsoft services'.

Also, ensure that you allow access to at least one subnet of source Vnet.

Note: Do not restrict virtual network access to your storage accounts used for Site Recovery. You should allow access from 'All networks'.

The table below lists the limits in terms of number of disks that can replicate to a single storage account.

Storage account type Churn = 4 MBps per disk Churn = 8 MBps per disk
V1 storage account 300 disks 150 disks
V2 storage account 750 disks 375 disks

As average churn on the disks increases, the number of disks that a storage account can support decreases. The above table may be used as a guide for making decisions on number of storage accounts that need to be provisioned.

Please note that the above limits are specific to Azure to Azure and zone to zone DR scenarios.

Replicated machine operating systems

Site Recovery supports replication of Azure VMs running the operating systems listed in this section. Note that if an already replicating machine is subsequently upgraded (or downgraded) to a different major kernel, you need to disable replication and re-enable replication after the upgrade.

Windows

Operating system Details
Windows Server 2019 Supported for Server Core, Server with Desktop Experience.
Windows Server 2016 Supported Server Core, Server with Desktop Experience.
Windows Server 2012 R2 Supported.
Windows Server 2012 Supported.
Windows Server 2008 R2 with SP1/SP2 Supported.

From version 9.30 of the Mobility service extension for Azure VMs, you need to install a Windows servicing stack update (SSU) and SHA-2 update on machines running Windows Server 2008 R2 SP1/SP2. SHA-1 isn't supported from September 2019, and if SHA-2 code signing isn't enabled the agent extension won't install/upgrade as expected. Learn more about SHA-2 upgrade and requirements.
Windows 10 (x64) Supported.
Windows 8.1 (x64) Supported.
Windows 8 (x64) Supported.
Windows 7 (x64) with SP1 onwards From version 9.30 of the Mobility service extension for Azure VMs, you need to install a Windows servicing stack update (SSU) and SHA-2 update on machines running Windows 7 with SP1. SHA-1 isn't supported from September 2019, and if SHA-2 code signing isn't enabled the agent extension won't install/upgrade as expected.. Learn more about SHA-2 upgrade and requirements.

Linux

Operating system Details
Red Hat Enterprise Linux 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6,7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3
CentOS 6.5, 6.6, 6.7, 6.8, 6.9, 6.10
7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9 pre-GA version, 7.9 GA version is supported from 9.37 hot fix patch**
8.0, 8.1, 8.2, 8.3
Ubuntu 14.04 LTS Server Includes support for all 14.04.x versions; Supported kernel versions;
Ubuntu 16.04 LTS Server Includes support for all 16.04.x versions; Supported kernel version

Ubuntu servers using password-based authentication and sign in, and the cloud-init package to configure cloud VMs, might have password-based sign in disabled on failover (depending on the cloudinit configuration). Password-based sign in can be re-enabled on the virtual machine by resetting the password from the Support > Troubleshooting > Settings menu (of the failed over VM in the Azure portal.
Ubuntu 18.04 LTS Server Includes support for all 18.04.x versions; Supported kernel version

Ubuntu servers using password-based authentication and sign in, and the cloud-init package to configure cloud VMs, might have password-based sign in disabled on failover (depending on the cloudinit configuration). Password-based sign in can be re-enabled on the virtual machine by resetting the password from the Support > Troubleshooting > Settings menu (of the failed over VM in the Azure portal.
Ubuntu 20.04 LTS server Includes support for all 20.04.x versions; Supported kernel version
Debian 7 Includes support for all 7. x versions Supported kernel versions
Debian 8 Includes support for all 8. x versions Supported kernel versions
Debian 9 Includes support for 9.1 to 9.13. Debian 9.0 is not supported. Supported kernel versions
Debian 10 Supported kernel versions
SUSE Linux Enterprise Server 12 SP1, SP2, SP3, SP4, SP5 (Supported kernel versions)
SUSE Linux Enterprise Server 15 15, SP1, SP2(Supported kernel versions)
SUSE Linux Enterprise Server 11 SP3

Upgrade of replicating machines from SP3 to SP4 isn't supported. If a replicated machine has been upgraded, you need to disable replication and re-enable replication after the upgrade.
SUSE Linux Enterprise Server 11 SP4
Oracle Linux 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3 (running the Red Hat compatible kernel or Unbreakable Enterprise Kernel Release 3, 4, 5, and 6 (UEK3, UEK4, UEK5, UEK6)

8.1 (running on all UEK kernels and RedHat kernel <= 3.10.0-1062.* are supported in 9.35. Support for rest of the RedHat kernels is available in 9.36)

Note

For Linux versions, Azure Site Recovery does not support custom OS kernels. Only the stock kernels that are part of the distribution minor version release/update are supported.

**Note: To support latest Linux kernels within 15 days of release, Azure Site Recovery rolls out hot fix patch on top of latest mobility agent version. This fix is rolled out in between two major version releases. To update to latest version of mobility agent (including hot fix patch) follow steps mentioned in this article. This patch is currently rolled out for mobility agents used in Azure to Azure DR scenario.

Supported Ubuntu kernel versions for Azure virtual machines

Release Mobility service version Kernel version
14.04 LTS 9.40, 9.41, 9.42, 9.43, 9.44 3.13.0-24-generic to 3.13.0-170-generic,
3.16.0-25-generic to 3.16.0-77-generic,
3.19.0-18-generic to 3.19.0-80-generic,
4.2.0-18-generic to 4.2.0-42-generic,
4.4.0-21-generic to 4.4.0-148-generic,
4.15.0-1023-azure to 4.15.0-1045-azure
16.04 LTS 9.44 4.4.0-21-generic to 4.4.0-206-generic,
4.8.0-34-generic to 4.8.0-58-generic,
4.10.0-14-generic to 4.10.0-42-generic,
4.11.0-13-generic to 4.11.0-14-generic,
4.13.0-16-generic to 4.13.0-45-generic,
4.15.0-13-generic to 4.15.0-140-generic
4.11.0-1009-azure to 4.11.0-1016-azure,
4.13.0-1005-azure to 4.13.0-1018-azure
4.15.0-1012-azure to 4.15.0-1111-azure
16.04 LTS 9.43 4.4.0-21-generic to 4.4.0-206-generic,
4.8.0-34-generic to 4.8.0-58-generic,
4.10.0-14-generic to 4.10.0-42-generic,
4.11.0-13-generic to 4.11.0-14-generic,
4.13.0-16-generic to 4.13.0-45-generic,
4.15.0-13-generic to 4.15.0-140-generic
4.11.0-1009-azure to 4.11.0-1016-azure,
4.13.0-1005-azure to 4.13.0-1018-azure
4.15.0-1012-azure to 4.15.0-1111-azure
16.04 LTS 9.42 4.4.0-21-generic to 4.4.0-206-generic,
4.8.0-34-generic to 4.8.0-58-generic,
4.10.0-14-generic to 4.10.0-42-generic,
4.11.0-13-generic to 4.11.0-14-generic,
4.13.0-16-generic to 4.13.0-45-generic,
4.15.0-13-generic to 4.15.0-140-generic
4.11.0-1009-azure to 4.11.0-1016-azure,
4.13.0-1005-azure to 4.13.0-1018-azure
4.15.0-1012-azure to 4.15.0-1111-azure
16.04 LTS 9.41 4.4.0-21-generic to 4.4.0-201-generic,
4.8.0-34-generic to 4.8.0-58-generic,
4.10.0-14-generic to 4.10.0-42-generic,
4.11.0-13-generic to 4.11.0-14-generic,
4.13.0-16-generic to 4.13.0-45-generic,
4.15.0-13-generic to 4.15.0-133-generic
4.11.0-1009-azure to 4.11.0-1016-azure,
4.13.0-1005-azure to 4.13.0-1018-azure
4.15.0-1012-azure to 4.15.0-1106-azure
4.4.0-203-generic, 4.4.0-204-generic, 4.4.0-206-generic, 4.15.0-136-generic, 4.15.0-137-generic, 4.15.0-139-generic, 4.15.0-140-generic, 4.15.0-1108-azure, 4.15.0-1109-azure, 4.15.0-1110-azure, 4.15.0-1111-azure through 9.41 hot fix patch**
16.04 LTS 9.40 4.4.0-21-generic to 4.4.0-197-generic,
4.8.0-34-generic to 4.8.0-58-generic,
4.10.0-14-generic to 4.10.0-42-generic,
4.11.0-13-generic to 4.11.0-14-generic,
4.13.0-16-generic to 4.13.0-45-generic,
4.15.0-13-generic to 4.15.0-128-generic
4.11.0-1009-azure to 4.11.0-1016-azure,
4.13.0-1005-azure to 4.13.0-1018-azure
4.15.0-1012-azure to 4.15.0-1102-azure
4.15.0-132-generic, 4.4.0-200-generic, 4.15.0-1106-azure, 4.15.0-133-generic, 4.4.0-201-generic through 9.40 hot fix patch**
18.04 LTS 9.45 4.15.0-1123-azure
5.4.0-1058-azure
4.15.0-156-generic
18.04 LTS 9.44 4.15.0-20-generic to 4.15.0-140-generic
4.18.0-13-generic to 4.18.0-25-generic
5.0.0-15-generic to 5.0.0-65-generic
5.3.0-19-generic to 5.3.0-72-generic
5.4.0-37-generic to 5.4.0-70-generic
4.15.0-1009-azure to 4.15.0-1111-azure
4.18.0-1006-azure to 4.18.0-1025-azure
5.0.0-1012-azure to 5.0.0-1036-azure
5.3.0-1007-azure to 5.3.0-1035-azure
5.4.0-1020-azure to 5.4.0-1043-azure
4.15.0-1114-azure
4.15.0-143-generic
5.4.0-1047-azure
5.4.0-73-generic
4.15.0-1115-azure
4.15.0-144-generic
5.4.0-1048-azure
5.4.0-74-generic
4.15.0-1121-azure
4.15.0-151-generic
4.15.0-153-generic
5.3.0-76-generic
5.4.0-1055-azure
5.4.0-80-generic
4.15.0-147-generic
4.15.0-153-generic
5.4.0-1056-azure
5.4.0-81-generic
4.15.0-1122-azure
4.15.0-154-generic
18.04 LTS 9.43 4.15.0-20-generic to 4.15.0-140-generic
4.18.0-13-generic to 4.18.0-25-generic
5.0.0-15-generic to 5.0.0-65-generic
5.3.0-19-generic to 5.3.0-72-generic
5.4.0-37-generic to 5.4.0-70-generic
4.15.0-1009-azure to 4.15.0-1111-azure
4.18.0-1006-azure to 4.18.0-1025-azure
5.0.0-1012-azure to 5.0.0-1036-azure
5.3.0-1007-azure to 5.3.0-1035-azure
5.4.0-1020-azure to 5.4.0-1043-azure
4.15.0-1114-azure
4.15.0-143-generic
5.4.0-1047-azure
5.4.0-73-generic
4.15.0-1115-azure
4.15.0-144-generic
5.4.0-1048-azure
5.4.0-74-generic
4.15.0-1121-azure
4.15.0-151-generic
4.15.0-153-generic
5.3.0-76-generic
5.4.0-1055-azure
5.4.0-80-generic
4.15.0-147-generic
18.04 LTS 9.42 4.15.0-20-generic to 4.15.0-140-generic
4.18.0-13-generic to 4.18.0-25-generic
5.0.0-15-generic to 5.0.0-65-generic
5.3.0-19-generic to 5.3.0-72-generic
5.4.0-37-generic to 5.4.0-70-generic
4.15.0-1009-azure to 4.15.0-1111-azure
4.18.0-1006-azure to 4.18.0-1025-azure
5.0.0-1012-azure to 5.0.0-1036-azure
5.3.0-1007-azure to 5.3.0-1035-azure
5.4.0-1020-azure to 5.4.0-1043-azure
4.15.0-1114-azure
4.15.0-143-generic
5.4.0-1047-azure
5.4.0-73-generic
4.15.0-1115-azure
4.15.0-144-generic
5.4.0-1048-azure
5.4.0-74-generic
18.04 LTS 9.41 4.15.0-20-generic to 4.15.0-135-generic
4.18.0-13-generic to 4.18.0-25-generic
5.0.0-15-generic to 5.0.0-65-generic
5.3.0-19-generic to 5.3.0-70-generic
5.4.0-37-generic to 5.4.0-59-generic
5.4.0-60-generic to 5.4.0-65-generic
4.15.0-1009-azure to 4.15.0-1106-azure
4.18.0-1006-azure to 4.18.0-1025-azure
5.0.0-1012-azure to 5.0.0-1036-azure
5.3.0-1007-azure to 5.3.0-1035-azure
5.4.0-1020-azure to 5.4.0-1039-azure
4.15.0-136-generic, 4.15.0-137-generic, 4.15.0-139-generic, 4.15.0-140-generic, 5.3.0-72-generic, 5.4.0-66-generic, 5.4.0-67-generic, 5.4.0-70-generic, 4.15.0-1108-azure, 4.15.0-1111-azure, 5.4.0-1040-azure, 5.4.0-1041-azure, 5.4.0-1043-azure, 4.15.0-1109-azure, 4.15.0-1110-azure through 9.41 hot fix patch**
18.04 LTS 9.40 4.15.0-20-generic to 4.15.0-129-generic
4.18.0-13-generic to 4.18.0-25-generic
5.0.0-15-generic to 5.0.0-63-generic
5.3.0-19-generic to 5.3.0-69-generic
5.4.0-37-generic to 5.4.0-59-generic
4.15.0-1009-azure to 4.15.0-1103-azure
4.18.0-1006-azure to 4.18.0-1025-azure
5.0.0-1012-azure to 5.0.0-1036-azure
5.3.0-1007-azure to 5.3.0-1035-azure
5.4.0-1020-azure to 5.4.0-1035-azure
4.15.0-1104-azure, 4.15.0-130-generic, 4.15.0-132-generic, 5.4.0-1036-azure, 5.4.0-60-generic, 5.4.0-62-generic, 4.15.0-1106-azure, 4.15.0-134-generic, 4.15.0-135-generic, 5.4.0-1039-azure, 5.4.0-64-generic, 5.4.0-65-generic through 9.40 hot fix patch**
20.04 LTS 9.45 5.4.0-1058-azure
5.4.0-84-generic
20.04 LTS 9.44 5.4.0-26-generic to 5.4.0-60-generic
5.4.0-1010-azure to 5.4.0-1043-azure
5.4.0-1047-azure
5.4.0-73-generic
5.4.0-1048-azure
5.4.0-74-generic
5.4.0-81-generic
5.4.0-1056-azure
20.04 LTS 9.43 5.4.0-26-generic to 5.4.0-60-generic
5.4.0-1010-azure to 5.4.0-1043-azure
5.4.0-1047-azure
5.4.0-73-generic
5.4.0-1048-azure
5.4.0-74-generic
20.04 LTS 9.42 5.4.0-26-generic to 5.4.0-60-generic
5.4.0-1010-azure to 5.4.0-1043-azure
5.4.0-1047-azure
5.4.0-73-generic
5.4.0-1048-azure
5.4.0-74-generic
20.04 LTS 9.41 5.4.0-26-generic to 5.4.0-65-generic
5.4.0-1010-azure to 5.4.0-1039-azure
5.4.0-66-generic, 5.4.0-67-generic, 5.4.0-70-generic, 5.4.0-1040-azure, 5.4.0-1041-azure, 5.4.0-1043-azure through 9.41 hot fix patch**
20.04 LTS 9.40 5.4.0-26-generic to 5.4.0-59-generic
5.4.0-1010-azure to 5.4.0-1035-azure
5.4.0-1036-azure, 5.4.0-60-generic, 5.4.0-62-generic, 5.4.0-1039-azure, 5.4.0-64-generic, 5.4.0-65-generic

**Note: To support latest Linux kernels within 15 days of release, Azure Site Recovery rolls out hot fix patch on top of latest mobility agent version. This fix is rolled out in between two major version releases. To update to latest version of mobility agent (including hot fix patch) follow steps mentioned in this article. This patch is currently rolled out for mobility agents used in Azure to Azure DR scenario.

*Note: For Ubuntu 20.04, we had initially rolled out support for kernels 5.8. but we have since found issues with support for this kernel and hence have redacted these kernels from our support statement for the time being.

Supported Debian kernel versions for Azure virtual machines

Release Mobility service version Kernel version
Debian 7 9.40 , 9.41, 9.42, 9.43 9.44 3.2.0-4-amd64 to 3.2.0-6-amd64, 3.16.0-0.bpo.4-amd64
Debian 8 9.40, 9.41, 9.42, 9.43, 9.44 3.16.0-4-amd64 to 3.16.0-11-amd64, 4.9.0-0.bpo.4-amd64 to 4.9.0-0.bpo.11-amd64
Debian 9.1 9.44 4.9.0-1-amd64 to 4.9.0-15-amd64
4.19.0-0.bpo.1-amd64 to 4.19.0-0.bpo.16-amd64
4.19.0-0.bpo.1-cloud-amd64 to 4.19.0-0.bpo.16-cloud-amd64
Debian 9.1 9.43 4.9.0-1-amd64 to 4.9.0-15-amd64
4.19.0-0.bpo.1-amd64 to 4.19.0-0.bpo.16-amd64
4.19.0-0.bpo.1-cloud-amd64 to 4.19.0-0.bpo.16-cloud-amd64
Debian 9.1 9.42 4.9.0-1-amd64 to 4.9.0-15-amd64
4.19.0-0.bpo.1-amd64 to 4.19.0-0.bpo.16-amd64
4.19.0-0.bpo.1-cloud-amd64 to 4.19.0-0.bpo.16-cloud-amd64
Debian 9.1 9.41 4.9.0-1-amd64 to 4.9.0-14-amd64
4.19.0-0.bpo.1-amd64 to 4.19.0-0.bpo.14-amd64
4.19.0-0.bpo.1-cloud-amd64 to 4.19.0-0.bpo.14-cloud-amd64
4.9.0-15-amd64, 4.19.0-0.bpo.16-amd64, 4.19.0-0.bpo.16-cloud-amd64 through 9.41 hot fix patch**
Debian 9.1 9.40 4.9.0-1-amd64 to 4.9.0-14-amd64
4.19.0-0.bpo.1-amd64 to 4.19.0-0.bpo.13-amd64
4.19.0-0.bpo.1-cloud-amd64 to 4.19.0-0.bpo.13-cloud-amd64
Debian 10 9.44 4.19.0-6-amd64 to 4.19.0-16-amd64
4.19.0-6-cloud-amd64 to 4.19.0-16-cloud-amd64
5.8.0-0.bpo.2-amd64
5.8.0-0.bpo.2-cloud-amd64
Debian 10 9.43 4.19.0-6-amd64 to 4.19.0-16-amd64
4.19.0-6-cloud-amd64 to 4.19.0-16-cloud-amd64
5.8.0-0.bpo.2-amd64
5.8.0-0.bpo.2-cloud-amd64
Debian 10 9.42 4.19.0-6-amd64 to 4.19.0-16-amd64
4.19.0-6-cloud-amd64 to 4.19.0-16-cloud-amd64
5.8.0-0.bpo.2-amd64
5.8.0-0.bpo.2-cloud-amd64
Debian 10 9.41 4.19.0-6-amd64 to 4.19.0-14-amd64
4.19.0-6-cloud-amd64 to 4.19.0-14-cloud-amd64
5.8.0-0.bpo.2-amd64
5.8.0-0.bpo.2-cloud-amd64
4.19.0-10-cloud-amd64, 4.19.0-16-amd64, 4.19.0-16-cloud-amd64 through 9.41 hot fix patch**
Debian 10 9.40 4.19.0-6-amd64 to 4.19.0-13-amd64
4.19.0-6-cloud-amd64 to 4.19.0-13-cloud-amd64
5.8.0-0.bpo.2-amd64
5.8.0-0.bpo.2-cloud-amd64

**Note: To support latest Linux kernels within 15 days of release, Azure Site Recovery rolls out hot fix patch on top of latest mobility agent version. This fix is rolled out in between two major version releases. To update to latest version of mobility agent (including hot fix patch) follow steps mentioned in this article. This patch is currently rolled out for mobility agents used in Azure to Azure DR scenario.

Supported SUSE Linux Enterprise Server 12 kernel versions for Azure virtual machines

Release Mobility service version Kernel version
SUSE Linux Enterprise Server 12 (SP1,SP2,SP3,SP4, SP5) 9.44 All stock SUSE 12 SP1,SP2,SP3,SP4,SP5 kernels are supported.

4.4.138-4.7-azure to 4.4.180-4.31-azure,
4.12.14-6.3-azure to 4.12.14-6.43-azure
4.12.14-16.7-azure to 4.12.14-16.56-azure
4.12.14-16.65-azure
4.12.14-16.68-azure
SUSE Linux Enterprise Server 12 (SP1,SP2,SP3,SP4, SP5) 9.43 All stock SUSE 12 SP1,SP2,SP3,SP4,SP5 kernels are supported.

4.4.138-4.7-azure to 4.4.180-4.31-azure,
4.12.14-6.3-azure to 4.12.14-6.43-azure
4.12.14-16.7-azure to 4.12.14-16.56-azure
4.12.14-16.65-azure
SUSE Linux Enterprise Server 12 (SP1,SP2,SP3,SP4, SP5) 9.42 All stock SUSE 12 SP1,SP2,SP3,SP4,SP5 kernels are supported.

4.4.138-4.7-azure to 4.4.180-4.31-azure,
4.12.14-6.3-azure to 4.12.14-6.43-azure
4.12.14-16.7-azure to 4.12.14-16.56-azure
SUSE Linux Enterprise Server 12 (SP1,SP2,SP3,SP4, SP5) 9.41 All stock SUSE 12 SP1,SP2,SP3,SP4,SP5 kernels are supported.

4.4.138-4.7-azure to 4.4.180-4.31-azure,
4.12.14-6.3-azure to 4.12.14-6.43-azure
4.12.14-16.7-azure to 4.12.14-16.44-azure
4.12.14-16.47-azure through 9.41 hot fix patch**
SUSE Linux Enterprise Server 12 (SP1,SP2,SP3,SP4, SP5) 9.40 All stock SUSE 12 SP1,SP2,SP3,SP4,SP5 kernels are supported.

4.4.138-4.7-azure to 4.4.180-4.31-azure,
4.12.14-6.3-azure to 4.12.14-6.43-azure
4.12.14-16.7-azure to 4.12.14-16.38-azure
4.12.14-16.41-azure through 9.40 hot fix patch**

Supported SUSE Linux Enterprise Server 15 kernel versions for Azure virtual machines

Release Mobility service version Kernel version
SUSE Linux Enterprise Server 15, SP1, SP2 9.44 By default, all stock SUSE 15, SP1, SP2 kernels are supported.

4.12.14-5.5-azure to 4.12.14-5.47-azure

4.12.14-8.5-azure to 4.12.14-8.55-azure
5.3.18-16-azure
5.3.18-18.5-azure to 5.3.18-18.58-azure
SUSE Linux Enterprise Server 15, SP1, SP2 9.43 By default, all stock SUSE 15, SP1, SP2 kernels are supported.

4.12.14-5.5-azure to 4.12.14-5.47-azure

4.12.14-8.5-azure to 4.12.14-8.55-azure
5.3.18-16-azure
5.3.18-18.5-azure to 5.3.18-18.58-azure
SUSE Linux Enterprise Server 15, SP1, SP2 9.42 By default, all stock SUSE 15, SP1, SP2 kernels are supported.

4.12.14-5.5-azure to 4.12.14-5.47-azure

4.12.14-8.5-azure to 4.12.14-8.55-azure
5.3.18-16-azure
5.3.18-18.5-azure to 5.3.18-18.47-azure
SUSE Linux Enterprise Server 15, SP1, SP2 9.41 By default, all stock SUSE 15, SP1, SP2 kernels are supported.

4.12.14-5.5-azure to 4.12.14-5.47-azure

4.12.14-8.5-azure to 4.12.14-8.55-azure
5.3.18-16-azure
5.3.18-18.5-azure to 5.3.18-18.35-azure
5.3.18-18.38-azure through 9.41 hot fix patch**
SUSE Linux Enterprise Server 15, SP1, SP2 9.40 By default, all stock SUSE 15, SP1, SP2 kernels are supported.

4.12.14-5.5-azure to 4.12.14-5.47-azure

4.12.14-8.5-azure to 4.12.14-8.58-azure
5.3.18-16-azure
5.3.18-18.5-azure to 5.3.18-18.29-azure
5.3.18-18.32-azure, 4.12.14-8.58-azure through 9.40 hot fix patch**

**Note: To support latest Linux kernels within 15 days of release, Azure Site Recovery rolls out hot fix patch on top of latest mobility agent version. This fix is rolled out in between two major version releases. To update to latest version of mobility agent (including hot fix patch) follow steps mentioned in this article. This patch is currently rolled out for mobility agents used in Azure to Azure DR scenario.

Replicated machines - Linux file system/guest storage

  • File systems: ext3, ext4, XFS, BTRFS
  • Volume manager: LVM2

Note

Multipath software is not supported.

Replicated machines - compute settings

Setting Support Details
Size Any Azure VM size with at least 2 CPU cores and 1-GB RAM Verify Azure virtual machine sizes.
RAM Azure Site Recovery driver consumes 6% of RAM.
Availability sets Supported If you enable replication for an Azure VM with the default options, an availability set is created automatically, based on the source region settings. You can modify these settings.
Availability zones Supported
Hybrid Use Benefit (HUB) Supported If the source VM has a HUB license enabled, a test failover or failed over VM also uses the HUB license.
Virtual machine scale sets Not supported
Azure gallery images - Microsoft published Supported Supported if the VM runs on a supported operating system.
Azure Gallery images - Third party published Supported Supported if the VM runs on a supported operating system.
Custom images - Third party published Supported Supported if the VM runs on a supported operating system.
VMs migrated using Site Recovery Supported If a VMware VM or physical machine was migrated to Azure using Site Recovery, you need to uninstall the older version of Mobility service running on the machine, and restart the machine before replicating it to another Azure region.
Azure RBAC policies Not supported Azure role-based access control (Azure RBAC) policies on VMs are not replicated to the failover VM in target region.
Extensions Not supported Extensions are not replicated to the failover VM in target region. It needs to be installed manually after failover.
Proximity Placement Groups Supported Virtual machines located inside a Proximity Placement Group can be protected using Site Recovery.
Tags Supported User generated tags applied on source virtual machines are carried over to target virtual machines post test failover or failover. Tags on the VM(s) are replicated once every 24 hours for as long as the VM(s) is/are present in the target region.

Replicated machines - disk actions

Action Details
Resize disk on replicated VM Resizing up on the source VM is supported. Resizing down on the source VM is not supported. Resizing should be performed before failover. No need to disable/re-enable replication.

If you change the source VM after failover, the changes aren't captured.

If you change the disk size on the Azure VM after failover, changes aren't captured by Site Recovery, and failback will be to the original VM size.

If resizing to >=4TB, please note Azure guidance on disk caching here.
Add a disk to a replicated VM Supported
Offline changes to protected disks Disconnecting disks and making offline modifications to them require triggering a full resync.
Disk caching Disk Caching is not supported for disks 4 TiB and larger. If multiple disks are attached to your VM, each disk that is smaller than 4 TiB will support caching. Changing the cache setting of an Azure disk detaches and re-attaches the target disk. If it is the operating system disk, the VM is restarted. Stop all applications/services that might be affected by this disruption before changing the disk cache setting. Not following those recommendations could lead to data corruption.

Replicated machines - storage

This table summarized support for the Azure VM OS disk, data disk, and temporary disk.

  • It's important to observe the VM disk limits and targets for managed disks to avoid any performance issues.
  • If you deploy with the default settings, Site Recovery automatically creates disks and storage accounts based on the source settings.
  • If you customize, ensure you follow the guidelines.
Component Support Details
OS disk maximum size 2048 GB Learn more about VM disks.
Temporary disk Not supported The temporary disk is always excluded from replication.

Don't store any persistent data on the temporary disk. Learn more.
Data disk maximum size 32 TB for managed disks

4 TB for unmanaged disks
Data disk minimum size No restriction for unmanaged disks. 2 GB for managed disks
Data disk maximum number Up to 64, in accordance with support for a specific Azure VM size Learn more about VM sizes.
Data disk change rate Maximum of 20 MBps per disk for premium storage. Maximum of 2 MBps per disk for Standard storage. If the average data change rate on the disk is continuously higher than the maximum, replication won't catch up.

However, if the maximum is exceeded sporadically, replication can catch up, but you might see slightly delayed recovery points.
Data disk - standard storage account Supported
Data disk - premium storage account Supported If a VM has disks spread across premium and standard storage accounts, you can select a different target storage account for each disk, to ensure you have the same storage configuration in the target region.
Managed disk - standard Supported in Azure regions in which Azure Site Recovery is supported.
Managed disk - premium Supported in Azure regions in which Azure Site Recovery is supported.
Disk subscription limits Up to 3000 protected disks per Subscription Ensure that the Source or Target subscription does not have more than 3000 Azure Site Recovery-protected Disks (Both Data and OS).
Standard SSD Supported
Redundancy LRS and GRS are supported.

ZRS isn't supported.
Cool and hot storage Not supported VM disks aren't supported on cool and hot storage
Storage Spaces Supported
NVMe storage interface Not supported
Encryption at host Supported See detailed information to create a VM with end-to-end encryption using Encryption at host.
Encryption at rest (SSE) Supported SSE is the default setting on storage accounts.
Encryption at rest (CMK) Supported Both Software and HSM keys are supported for managed disks
Double Encryption at rest Supported Learn more on supported regions for Windows and Linux
FIPS encryption Not supported
Azure Disk Encryption (ADE) for Windows OS Supported for VMs with managed disks. VMs using unmanaged disks are not supported.

HSM-protected keys are not supported.

Encryption of individual volumes on a single disk is not supported.
Azure Disk Encryption (ADE) for Linux OS Supported for VMs with managed disks. VMs using unmanaged disks are not supported.

HSM-protected keys are not supported.

Encryption of individual volumes on a single disk is not supported.

Known issue with enabling replication. Learn more.
SAS key rotation Not Supported If the SAS key for storage accounts is rotated, customer needs to disable and re-enable replication.
Host Caching Supported
Hot add Supported Enabling replication for a data disk that you add to a replicated Azure VM is supported for VMs that use managed disks.

Only one disk can be hot added to an Azure VM at a time. Parallel addition of multiple disks is not supported.
Hot remove disk Not supported If you remove data disk on the VM, you need to disable replication and enable replication again for the VM.
Exclude disk Support. You must use PowerShell to configure. Temporary disks are excluded by default.
Storage Spaces Direct Supported for crash consistent recovery points. Application consistent recovery points are not supported.
Scale-out File Server Supported for crash consistent recovery points. Application consistent recovery points are not supported.
DRBD Disks that are part of a DRBD setup are not supported.
LRS Supported
GRS Supported
RA-GRS Supported
ZRS Not supported
Cool and Hot Storage Not supported Virtual machine disks are not supported on cool and hot storage
Azure Storage firewalls for virtual networks Supported If restrict virtual network access to storage accounts, enable Allow trusted Microsoft services.
General purpose V2 storage accounts (Both Hot and Cool tier) Supported Transaction costs increase substantially compared to General purpose V1 storage accounts
Generation 2 (UEFI boot) Supported
NVMe disks Not supported
Azure shared disks Not supported
Secure transfer option Supported
Write accelerator enabled disks Not supported
Tags Supported User generated tags are replicated every 24 hours.

Important

To avoid performance issues, make sure that you follow VM disk scalability and performance targets for managed disks. If you use default settings, Site Recovery creates the required disks and storage accounts, based on the source configuration. If you customize and select your own settings,follow the disk scalability and performance targets for your source VMs.

Limits and data change rates

The following table summarizes Site Recovery limits.

  • These limits are based on our tests, but obviously don't cover all possible application I/O combinations.
  • Actual results can vary based on you app I/O mix.
  • There are two limits to consider, per disk data churn and per virtual machine data churn.
  • The current limit for per virtual machine data churn is 54 MB/s, regardless of size.
Storage target Average source disk I/O Average source disk data churn Total source disk data churn per day
Standard storage 8 KB 2 MB/s 168 GB per disk
Premium P10 or P15 disk 8 KB 2 MB/s 168 GB per disk
Premium P10 or P15 disk 16 KB 4 MB/s 336 GB per disk
Premium P10 or P15 disk 32 KB or greater 8 MB/s 672 GB per disk
Premium P20 or P30 or P40 or P50 disk 8 KB 5 MB/s 421 GB per disk
Premium P20 or P30 or P40 or P50 disk 16 KB or greater 20 MB/s 1684 GB per disk

Replicated machines - networking

Setting Support Details
NIC Maximum number supported for a specific Azure VM size NICs are created when the VM is created during failover.

The number of NICs on the failover VM depends on the number of NICs on the source VM when replication was enabled. If you add or remove a NIC after enabling replication, it doesn't impact the number of NICs on the replicated VM after failover.

The order of NICs after failover is not guaranteed to be the same as the original order.

You can rename NICs in the target region based on your organization's naming conventions. NIC renaming is supported using PowerShell.
Internet Load Balancer Not supported You can set up public/internet load balancers in the primary region. However, public/internet load balancers are not supported by Azure Site Recovery in the DR region.
Internal Load balancer Supported Associate the preconfigured load balancer using an Azure Automation script in a recovery plan.
Public IP address Supported Associate an existing public IP address with the NIC. Or, create a public IP address and associate it with the NIC using an Azure Automation script in a recovery plan.
NSG on NIC Supported Associate the NSG with the NIC using an Azure Automation script in a recovery plan.
NSG on subnet Supported Associate the NSG with the subnet using an Azure Automation script in a recovery plan.
Reserved (static) IP address Supported If the NIC on the source VM has a static IP address, and the target subnet has the same IP address available, it's assigned to the failed over VM.

If the target subnet doesn't have the same IP address available, one of the available IP addresses in the subnet is reserved for the VM.

You can also specify a fixed IP address and subnet in Replicated items > Settings > Compute and Network > Network interfaces.
Dynamic IP address Supported If the NIC on the source has dynamic IP addressing, the NIC on the failed over VM is also dynamic by default.

You can modify this to a fixed IP address if required.
Multiple IP addresses Not supported When you fail over a VM that has a NIC with multiple IP addresses, only the primary IP address of the NIC in the source region is kept. To assign multiple IP addresses, you can add VMs to a recovery plan and attach a script to assign additional IP addresses to the plan, or you can make the change manually or with a script after failover.
Traffic Manager Supported You can preconfigure Traffic Manager so that traffic is routed to the endpoint in the source region on a regular basis, and to the endpoint in the target region in case of failover.
Azure DNS Supported
Custom DNS Supported
Unauthenticated proxy Supported Learn more
Authenticated Proxy Not supported If the VM is using an authenticated proxy for outbound connectivity, it cannot be replicated using Azure Site Recovery.
VPN site-to-site connection to on-premises

(with or without ExpressRoute)
Supported Ensure that the UDRs and NSGs are configured in such a way that the Site Recovery traffic is not routed to on-premises. Learn more
VNET to VNET connection Supported Learn more
Virtual Network Service Endpoints Supported If you are restricting the virtual network access to storage accounts, ensure that the trusted Microsoft services are allowed access to the storage account.
Accelerated networking Supported Accelerated networking must be enabled on source VM. Learn more.
Palo Alto Network Appliance Not supported With third party appliances, there are often restrictions imposed by the provider inside the Virtual Machine. Azure Site Recovery needs agent, extensions and outbound connectivity to be available. But the appliance does not let any outbound activity to be configured inside the Virtual Machine.
IPv6 Not supported Mixed configurations that include both IPv4 and IPv6 are also not supported. Please free up the subnet of the IPv6 range before any Site Recovery operation.
Private link access to Site Recovery service Supported Learn more
Tags Supported User generated tags on NICs are replicated every 24 hours.

Next steps