Support matrix for Azure VM disaster recovery between Azure regions
Caution
This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and plan accordingly. For more information, see the CentOS End Of Life guidance.
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 move/migrate 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 Microsoft Entra tenant. |
| Migrate VMs across regions within supported geographical clusters (within and across subscriptions) | Supported within the same Microsoft Entra tenant. |
| Migrate VMs within the same region | Not supported. |
| Azure Dedicated Hosts | Not supported. |
Region support
Azure Site Recovery allows you to perform disaster recovery. You can replicate and recover VMs between any two Azure regions in China. 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 |
|---|---|
| China | China East, China North, China North2, China East2, China North3 |
Note
- For China North, you can replicate and fail over to these regions: China East, China East 2, China North 2, and China North3.
- China North 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 China North as a source region to a target, failback to China North from the target region is supported. China East 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 recommended because GPv1 doesn't support ZRS (Zonal Redundant Storage). |
| 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're using firewall enabled cache storage account or target storage account, ensure you 'Allow trusted Azure services'. Also, ensure that you allow access to at least one subnet of source Vnet. Note: Don't restrict virtual network access to your storage accounts used for Site Recovery. You should allow access from 'All networks'. |
| Soft delete | Not supported | Soft delete isn't supported because once it is enabled on cache storage account, it increases cost. Azure Site Recovery performs frequent creates/deletes of log files while replicating causing costs to increase. |
| Encryption at rest (CMK) | Supported | Storage account encryption can be configured with customer managed keys (CMK) |
| Managed identity | Not supported | The cached storage account must allow shared key access and Shared Access Signatures (SAS) signed by the shared key. |
The following table 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.
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 later 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 2022 | Supported. |
| 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 11 (x64) | Supported (From Mobility Agent version 9.56 onwards). |
| Windows 10 (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
Note
Mobility service versions 9.58 and 9.59 are not released for Azure to Azure Site Recovery.
| 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, 8.4 (4.18.0-305.30.1.el8_4.x86_64 or higher), 8.5 (4.18.0-348.5.1.el8_5.x86_64 or higher), 8.6, 8.7, 8.8, 8.9, 8.10, 9.0, 9.1, 9.2, 9., 9.4 RHEL 9.x is supported for the following kernel versions. |
| 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, 8.4 (4.18.0-305.30.1.el8_4.x86_64 or later), 8.5 (4.18.0-348.5.1.el8_5.x86_64 or later), 8.6, 8.7. |
| 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 |
| Ubuntu 22.04 LTS server | Includes support for all 22.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 isn't supported. Supported kernel versions |
| Debian 10 | Supported kernel versions |
| Debian 11 | Supported kernel versions |
| Debian 12 | Supported kernel versions |
| SUSE Linux Enterprise Server 12 | SP1, SP2, SP3, SP4, SP5 (Supported kernel versions) |
| SUSE Linux Enterprise Server 15 | 15, SP1, SP2, SP3, SP4, SP5 (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 |
Rocky Linux | See supported versions.
Note
For Linux versions, Azure Site Recovery doesn't 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 kernel versions for Red Hat Enterprise Linux for Azure virtual machines
Note
Enable replication through create virtual machine deployment workflow isn't supported for virtual machines with OS RHEL 9* and above.
| Release | Mobility service version | Red Hat kernel version |
|---|---|---|
| RHEL 9.0 RHEL 9.1 RHEL 9.2 RHEL 9.3 RHEL 9.4 |
9.62 | 5.14.0-70.97.1.el9_0.x86_64 5.14.0-70.101.1.el9_0.x86_64 5.14.0-284.62.1.el9_2.x86_64 5.14.0-284.64.1.el9_2.x86_64 5.14.0-284.66.1.el9_2.x86_64 5.14.0-284.67.1.el9_2.x86_64 5.14.0-284.69.1.el9_2.x86_64 5.14.0-284.71.1.el9_2.x86_64 5.14.0-427.13.1.el9_4.x86_64 5.14.0-427.16.1.el9_4.x86_64 5.14.0-427.18.1.el9_4.x86_64 5.14.0-427.20.1.el9_4.x86_64 5.14.0-427.22.1.el9_4.x86_64 |
| RHEL 9.0 RHEL 9.1 RHEL 9.2 RHEL 9.3 |
9.61 | 5.14.0-70.93.2.el9_0.x86_64 5.14.0-284.54.1.el9_2.x86_64 5.14.0-284.57.1.el9_2.x86_64 5.14.0-284.59.1.el9_2.x86_64 5.14.0-362.24.1.el9_3.x86_64 |
| RHEL 9.0 RHEL 9.1 RHEL 9.2 RHEL 9.3 |
9.60 | 5.14.0-70.13.1.el9_0.x86_64 5.14.0-70.17.1.el9_0.x86_64 5.14.0-70.22.1.el9_0.x86_64 5.14.0-70.26.1.el9_0.x86_64 5.14.0-70.30.1.el9_0.x86_64 5.14.0-70.36.1.el9_0.x86_64 5.14.0-70.43.1.el9_0.x86_64 5.14.0-70.49.1.el9_0.x86_64 5.14.0-70.50.2.el9_0.x86_64 5.14.0-70.53.1.el9_0.x86_64 5.14.0-70.58.1.el9_0.x86_64 5.14.0-70.64.1.el9_0.x86_64 5.14.0-70.70.1.el9_0.x86_64 5.14.0-70.75.1.el9_0.x86_64 5.14.0-70.80.1.el9_0.x86_64 5.14.0-70.85.1.el9_0.x86_64 5.14.0-162.6.1.el9_1.x86_64 5.14.0-162.12.1.el9_1.x86_64 5.14.0-162.18.1.el9_1.x86_64 5.14.0-162.22.2.el9_1.x86_64 5.14.0-162.23.1.el9_1.x86_64 5.14.0-284.11.1.el9_2.x86_64 5.14.0-284.13.1.el9_2.x86_64 5.14.0-284.16.1.el9_2.x86_64 5.14.0-284.18.1.el9_2.x86_64 5.14.0-284.23.1.el9_2.x86_64 5.14.0-284.25.1.el9_2.x86_64 5.14.0-284.28.1.el9_2.x86_64 5.14.0-284.30.1.el9_2.x86_64 5.14.0-284.32.1.el9_2.x86_64 5.14.0-284.34.1.el9_2.x86_64 5.14.0-284.36.1.el9_2.x86_64 5.14.0-284.40.1.el9_2.x86_64 5.14.0-284.41.1.el9_2.x86_64 5.14.0-284.43.1.el9_2.x86_64 5.14.0-284.44.1.el9_2.x86_64 5.14.0-284.45.1.el9_2.x86_64 5.14.0-284.48.1.el9_2.x86_64 5.14.0-284.50.1.el9_2.x86_64 5.14.0-284.52.1.el9_2.x86_64 5.14.0-362.8.1.el9_3.x86_64 5.14.0-362.13.1.el9_3.x86_64 5.14.0-362.18.1.el9_3.x86_64 |
Supported Ubuntu kernel versions for Azure virtual machines
Note
Mobility service versions 9.58 and 9.59 are not released for Azure to Azure Site Recovery.
| Release | Mobility service version | Kernel version |
|---|---|---|
| 14.04 LTS | 9.62 | No new 14.04 LTS kernels supported in this release. |
| 14.04 LTS | 9.61 | No new 14.04 LTS kernels supported in this release. |
| 14.04 LTS | 9.60 | No new 14.04 LTS kernels supported in this release. |
| 14.04 LTS | 9.57 | No new 14.04 LTS kernels supported in this release. |
| 14.04 LTS | 9.56 | No new 14.04 LTS kernels supported in this release. |
| 16.04 LTS | 9.62 | No new 16.04 LTS kernels supported in this release. |
| 16.04 LTS | 9.61 | No new 16.04 LTS kernels supported in this release. |
| 16.04 LTS | 9.60 | No new 16.04 LTS kernels supported in this release. |
| 16.04 LTS | 9.57 | No new 16.04 LTS kernels supported in this release. |
| 16.04 LTS | 9.56 | No new 16.04 LTS kernels supported in this release. |
| 18.04 LTS | 9.62 | 4.15.0-226-generic 5.4.0-1131-azure 5.4.0-186-generic 5.4.0-187-generic |
| 18.04 LTS | 9.61 | 5.4.0-173-generic 4.15.0-1175-azure 4.15.0-223-generic 5.4.0-1126-azure 5.4.0-174-generic 4.15.0-1176-azure 4.15.0-224-generic 5.4.0-1127-azure 5.4.0-1128-azure 5.4.0-175-generic 5.4.0-177-generic 4.15.0-1177-azure 4.15.0-225-generic 5.4.0-1129-azure 5.4.0-1130-azure 5.4.0-181-generic 5.4.0-182-generic |
| 18.04 LTS | 9.60 | 4.15.0-1168-azure 4.15.0-1169-azure 4.15.0-1170-azure 4.15.0-1171-azure 4.15.0-1172-azure 4.15.0-1173-azure 4.15.0-214-generic 4.15.0-216-generic 4.15.0-218-generic 4.15.0-219-generic 4.15.0-220-generic 4.15.0-221-generic 5.4.0-1110-azure 5.4.0-1111-azure 5.4.0-1112-azure 5.4.0-1113-azure 5.4.0-1115-azure 5.4.0-1116-azure 5.4.0-1117-azure 5.4.0-1118-azure 5.4.0-1119-azure 5.4.0-1120-azure 5.4.0-1121-azure 5.4.0-1122-azure 5.4.0-152-generic 5.4.0-153-generic 5.4.0-155-generic 5.4.0-156-generic 5.4.0-159-generic 5.4.0-162-generic 5.4.0-163-generic 5.4.0-164-generic 5.4.0-165-generic 5.4.0-166-generic 5.4.0-167-generic 5.4.0-169-generic 5.4.0-170-generic 5.4.0-1123-azure 5.4.0-171-generic 4.15.0-1174-azure 4.15.0-222-generic 5.4.0-1124-azure 5.4.0-172-generic |
| 18.04 LTS | 9.57 | No new 18.04 LTS kernels supported in this release. |
| 18.04 LTS | 9.56 | No new 18.04 LTS kernels supported in this release. |
| 20.04 LTS | 9.62 | 5.15.0-1065-azure 5.15.0-1067-azure 5.15.0-113-generic 5.4.0-1131-azure 5.4.0-1132-azure 5.4.0-186-generic 5.4.0-187-generic |
| 20.04 LTS | 9.61 | 5.15.0-100-generic 5.15.0-1058-azure 5.4.0-173-generic 5.4.0-1126-azure 5.4.0-174-generic 5.15.0-101-generic 5.15.0-1059-azure 5.15.0-102-generic 5.15.0-105-generic 5.15.0-1061-azure 5.4.0-1127-azure 5.4.0-1128-azure 5.4.0-176-generic 5.4.0-177-generic 5.15.0-106-generic 5.15.0-1063-azure 5.15.0-1064-azure 5.15.0-107-generic 5.4.0-1129-azure 5.4.0-1130-azure 5.4.0-181-generic 5.4.0-182-generic |
| 20.04 LTS | 9.60 | 5.15.0-1054-azure 5.15.0-92-generic 5.4.0-1122-azure 5.4.0-170-generic 5.15.0-94-generic 5.4.0-1123-azure 5.4.0-171-generic 5.15.0-1056-azure 5.15.0-1057-azure 5.15.0-97-generic 5.4.0-1124-azure 5.4.0-172-generic |
| 20.04 LTS | 9.57 | 5.15.0-1052-azure 5.15.0-1053-azure 5.15.0-89-generic 5.15.0-91-generic 5.4.0-1120-azure 5.4.0-1121-azure 5.4.0-167-generic 5.4.0-169-generic |
| 20.04 LTS | 9.56 | 5.15.0-1049-azure 5.15.0-1050-azure 5.15.0-1051-azure 5.15.0-86-generic 5.15.0-87-generic 5.15.0-88-generic 5.4.0-1117-azure 5.4.0-1118-azure 5.4.0-1119-azure 5.4.0-164-generic 5.4.0-165-generic 5.4.0-166-generic |
| 22.04 LTS | 9.62 | 5.15.0-1066-azure 5.15.0-1067-azure 5.15.0-112-generic 5.15.0-113-generic 6.5.0-1022-azure 6.5.0-1023-azure 6.5.0-41-generic |
| 22.04 LTS | 9.61 | 5.15.0-100-generic 5.15.0-1058-azure 6.5.0-1016-azure 6.5.0-25-generic 5.15.0-101-generic 5.15.0-1059-azure 6.5.0-1017-azure 6.5.0-26-generic 5.15.0-102-generic 5.15.0-105-generic 5.15.0-1060-azure 5.15.0-1061-azure 6.5.0-1018-azure 6.5.0-1019-azure 6.5.0-27-generic 6.5.0-28-generic 5.15.0-106-generic 5.15.0-1063-azure 5.15.0-1064-azure 5.15.0-107-generic 6.5.0-1021-azure 6.5.0-35-generic |
| 22.04 LTS | 9.60 | 5.19.0-1025-azure 5.19.0-1026-azure 5.19.0-1027-azure 5.19.0-41-generic 5.19.0-42-generic 5.19.0-43-generic 5.19.0-45-generic 5.19.0-46-generic 5.19.0-50-generic 6.2.0-1005-azure 6.2.0-1006-azure 6.2.0-1007-azure 6.2.0-1008-azure 6.2.0-1011-azure 6.2.0-1012-azure 6.2.0-1014-azure 6.2.0-1015-azure 6.2.0-1016-azure 6.2.0-1017-azure 6.2.0-1018-azure 6.2.0-25-generic 6.2.0-26-generic 6.2.0-31-generic 6.2.0-32-generic 6.2.0-33-generic 6.2.0-34-generic 6.2.0-35-generic 6.2.0-36-generic 6.2.0-37-generic 6.2.0-39-generic 6.5.0-1007-azure 6.5.0-1009-azure 6.5.0-1010-azure 6.5.0-14-generic 5.15.0-1054-azure 5.15.0-92-generic 6.2.0-1019-azure 6.5.0-1011-azure 6.5.0-15-generic 5.15.0-94-generic 6.5.0-17-generic 5.15.0-1056-azure 5.15.0-1057-azure 5.15.0-97-generic 6.5.0-1015-azure 6.5.0-18-generic 6.5.0-21-generic |
| 22.04 LTS | 9.57 | 5.15.0-1052-azure 5.15.0-1053-azure 5.15.0-76-generic 5.15.0-89-generic 5.15.0-91-generic |
| 22.04 LTS | 9.56 | 5.15.0-1049-azure 5.15.0-1050-azure 5.15.0-1051-azure 5.15.0-86-generic 5.15.0-87-generic 5.15.0-88-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.
Supported Debian kernel versions for Azure virtual machines
Note
Mobility service versions 9.58 and 9.59 are not released for Azure to Azure Site Recovery.
| Release | Mobility service version | Kernel version |
|---|---|---|
| Debian 7 | 9.62 | No new Debian 7 kernels supported in this release. |
| Debian 7 | 9.61 | No new Debian 7 kernels supported in this release. |
| Debian 7 | [9.60] | No new Debian 7 kernels supported in this release. |
| Debian 7 | 9.57 | No new Debian 7 kernels supported in this release. |
| Debian 7 | 9.56 | No new Debian 7 kernels supported in this release. |
| Debian 8 | 9.62 | No new Debian 8 kernels supported in this release. |
| Debian 8 | 9.61 | No new Debian 8 kernels supported in this release. |
| Debian 8 | [9.60] | No new Debian 8 kernels supported in this release. |
| Debian 8 | 9.57 | No new Debian 8 kernels supported in this release. |
| Debian 8 | 9.56 | No new Debian 8 kernels supported in this release. |
| Debian 9.1 | 9.62 | No new Debian 9.1 kernels supported in this release. |
| Debian 9.1 | 9.61 | No new Debian 9.1 kernels supported in this release. |
| Debian 9.1 | [9.60] | No new Debian 9.1 kernels supported in this release. |
| Debian 9.1 | 9.57 | No new Debian 9.1 kernels supported in this release. |
| Debian 9.1 | 9.56 | No new Debian 9.1 kernels supported in this release. |
| Debian 10 | 9.62 | 4.19.0-27-amd64 4.19.0-27-cloud-amd64 5.10.0-0.deb10.30-amd64 5.10.0-0.deb10.30-cloud-amd64 |
| Debian 10 | 9.61 | 5.10.0-0.deb10.29-amd64 5.10.0-0.deb10.29-cloud-amd64 |
| Debian 10 | [9.60] | 4.19.0-26-amd64 4.19.0-26-cloud-amd64 5.10.0-0.deb10.27-amd64 5.10.0-0.deb10.27-cloud-amd64 5.10.0-0.deb10.28-amd64 5.10.0-0.deb10.28-cloud-amd64 |
| Debian 10 | 9.57 | No new Debian 10 kernels supported in this release. |
| Debian 10 | 9.56 | 5.10.0-0.deb10.26-amd64 5.10.0-0.deb10.26-cloud-amd64 |
| Debian 11 | 9.62 | 5.10.0-30-amd64 5.10.0-30-cloud-amd64 6.1.0-0.deb11.21-amd64 6.1.0-0.deb11.21-cloud-amd64 |
| Debian 11 | 9.61 | 6.1.0-0.deb11.13-amd64 6.1.0-0.deb11.13-cloud-amd64 6.1.0-0.deb11.17-amd64 6.1.0-0.deb11.17-cloud-amd64 6.1.0-0.deb11.18-amd64 6.1.0-0.deb11.18-cloud-amd64 5.10.0-29-amd64 5.10.0-29-cloud-amd64 |
| Debian 11 | 9.60 | 5.10.0-27-amd64 5.10.0-27-cloud-amd64 5.10.0-28-amd64 5.10.0-28-cloud-amd64 |
| Debian 11 | 9.57 | No new Debian 11 kernels supported in this release. |
| Debian 11 | 9.56 | 5.10.0-26-amd64 5.10.0-26-cloud-amd64 |
| Debian 12 | 9.62 | 6.1.0-22-amd64 6.1.0-22-cloud-amd64 |
| Debian 12 | 9.61 | 5.17.0-1-amd64 5.17.0-1-cloud-amd64 6.1.-11-amd64 6.1.0-11-cloud-amd64 6.1.0-12-amd64 6.1.0-12-cloud-amd64 6.1.0-13-amd64 6.1.0-15-amd64 6.1.0-15-cloud-amd64 6.1.0-16-amd64 6.1.0-16-cloud-amd64 6.1.0-17-amd64 6.1.0-17-cloud-amd64 6.1.0-18-amd64 6.1.0-18-cloud-amd64 6.1.0-7-amd64 6.1.0-7-cloud-amd64 6.5.0-0.deb12.4-amd64 6.5.0-0.deb12.4-cloud-amd64 6.1.0-20-amd64 6.1.0-20-cloud-amd64 6.1.0-21-amd64 6.1.0-21-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
Note
Mobility service versions 9.58 and 9.59 are not released for Azure to Azure Site Recovery.
| Release | Mobility service version | Kernel version |
|---|---|---|
| SUSE Linux Enterprise Server 12 (SP1, SP2, SP3, SP4, SP5) | 9.62 | All stock SUSE 12 SP1,SP2,SP3,SP4,SP5 kernels are supported. 4.12.14-16.185-azure:5 4.12.14-16.188-azure:5 |
| SUSE Linux Enterprise Server 12 (SP1, SP2, SP3, SP4, SP5) | 9.61 | All stock SUSE 12 SP1,SP2,SP3,SP4,SP5 kernels are supported. 4.12.14-16.173-azure 4.12.14-16.182-azure:5 |
| SUSE Linux Enterprise Server 12 (SP1, SP2, SP3, SP4, SP5) | 9.60 | All stock SUSE 12 SP1,SP2,SP3,SP4,SP5 kernels are supported. 4.12.14-16.163-azure:5 |
| SUSE Linux Enterprise Server 12 (SP1, SP2, SP3, SP4, SP5) | 9.57 | All stock SUSE 12 SP1,SP2,SP3,SP4,SP5 kernels are supported. 4.12.14-16.155-azure:5 |
| SUSE Linux Enterprise Server 12 (SP1, SP2, SP3, SP4, SP5) | 9.56 | All stock SUSE 12 SP1,SP2,SP3,SP4,SP5 kernels are supported. 4.12.14-16.152-azure:5 |
Supported SUSE Linux Enterprise Server 15 kernel versions for Azure virtual machines
Note
Mobility service versions 9.58 and 9.59 are not released for Azure to Azure Site Recovery.
| Release | Mobility service version | Kernel version |
|---|---|---|
| SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5) | 9.62 | All stock SUSE 12 SP1,SP2,SP3,SP4,SP5 kernels are supported. 5.14.21-150500.33.54-azure:5 5.14.21-150500.33.57-azure:5 |
| SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5) | 9.61 | All stock SUSE 12 SP1,SP2,SP3,SP4,SP5 kernels are supported. 5.14.21-150500.33.37-azure 5.14.21-150500.33.42-azure 5.14.21-150500.33.48-azure:5 5.14.21-150500.33.51-azure:5 |
| SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5) | 9.60 | By default, all stock SUSE 15, SP1, SP2, SP3, SP4, SP5 kernels are supported. 5.14.21-150500.33.29-azure 5.14.21-150500.33.34-azure |
| SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5) | 9.57 | By default, all stock SUSE 15, SP1, SP2, SP3, SP4, SP5 kernels are supported. 5.14.21-150400.14.72-azure:4 5.14.21-150500.33.23-azure:5 5.14.21-150500.33.26-azure:5 |
| SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5) | 9.56 | By default, all stock SUSE 15, SP1, SP2, SP3, SP4, SP5 kernels are supported. 5.14.21-150400.14.69-azure:4 5.14.21-150500.31-azure:5 5.14.21-150500.33.11-azure:5 5.14.21-150500.33.14-azure:5 5.14.21-150500.33.17-azure:5 5.14.21-150500.33.20-azure:5 5.14.21-150500.33.3-azure:5 5.14.21-150500.33.6-azure:5 |
Supported Rocky Linux kernel versions for Azure virtual machines
Note
Mobility service versions 9.58 and 9.59 are not released for Azure to Azure Site Recovery.
| Release | Mobility service version | Red Hat kernel version |
|---|---|---|
| Rocky Linux 9.0 Rocky Linux 9.1 |
9.62 | 5.14.0-70.97.1.el9_0.x86_64 5.14.0-70.101.1.el9_0.x86_64 5.14.0-284.62.1.el9_2.x86_64 5.14.0-284.64.1.el9_2.x86_64 5.14.0-284.66.1.el9_2.x86_64 5.14.0-284.67.1.el9_2.x86_64 5.14.0-284.69.1.el9_2.x86_64 5.14.0-284.71.1.el9_2.x86_64 5.14.0-427.13.1.el9_4.x86_64 5.14.0-427.16.1.el9_4.x86_64 5.14.0-427.18.1.el9_4.x86_64 5.14.0-427.20.1.el9_4.x86_64 5.14.0-427.22.1.el9_4.x86_64 |
| Rocky Linux 9.0 Rocky Linux 9.1 |
9.61 | 5.14.0-70.93.2.el9_0.x86_64 |
| Rocky Linux 9.0 Rocky Linux 9.1 |
9.60 | 5.14.0-70.13.1.el9_0.x86_64 5.14.0-70.17.1.el9_0.x86_64 5.14.0-70.22.1.el9_0.x86_64 5.14.0-70.26.1.el9_0.x86_64 5.14.0-70.30.1.el9_0.x86_64 5.14.0-70.36.1.el9_0.x86_64 5.14.0-70.43.1.el9_0.x86_64 5.14.0-70.49.1.el9_0.x86_64 5.14.0-70.50.2.el9_0.x86_64 5.14.0-70.53.1.el9_0.x86_64 5.14.0-70.58.1.el9_0.x86_64 5.14.0-70.64.1.el9_0.x86_64 5.14.0-70.70.1.el9_0.x86_64 5.14.0-70.75.1.el9_0.x86_64 5.14.0-70.80.1.el9_0.x86_64 5.14.0-70.85.1.el9_0.x86_64 5.14.0-162.6.1.el9_1.x86_64 5.14.0-162.12.1.el9_1.x86_64 5.14.0-162.18.1.el9_1.x86_64 5.14.0-162.22.2.el9_1.x86_64 5.14.0-162.23.1.el9_1.x86_64 |
| Release | Mobility service version | Kernel version |
|---|---|---|
| Rocky Linux | 9.57 | Rocky Linux 8.8 Rocky Linux 8.9 |
| Rocky Linux | 9.56 | Rocky Linux 8.7 Rocky Linux 9.0 |
Important
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 isn't supported.
Replicated machines - compute settings
| Setting | Support | Details |
|---|---|---|
| Size | Any Azure VM size with at least two 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 | |
| Dedicated Hosts | Not 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 Set Flex | Availability scenario - supported. Scalability scenario - not supported. | |
| Azure gallery images - Azure 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 aren't replicated to the failover VM in target region. |
| Extensions | Not supported | Extensions aren't 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 isn't 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 >=4 TB, 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 isn't supported for disks 4 TB and larger. If multiple disks are attached to your VM, each disk that is smaller than 4 TB will support caching. Changing the cache setting of an Azure disk detaches and re-attaches the target disk. If it's 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
Note
Azure Site Recovery supports storage accounts with page blob for unmanaged disk replication.
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 | 4096 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. 1 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 maximum size per storage account (for unmanaged disks) | 35 TB | This is an upper limit for cumulative size of page blobs created in a premium Storage Account |
| 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 doesn't have more than 3000 Azure Site Recovery-protected Disks (Both Data and OS). |
| Standard SSD | Supported | |
| Redundancy | LRS, ZRS, and GRS are 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 | Not Supported | The VM will get protected, but the failed over VM won't have Encryption at host enabled. 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 aren't supported. HSM-protected keys aren't supported. Encryption of individual volumes on a single disk isn't supported. |
| Azure Disk Encryption (ADE) for Linux OS | Supported for VMs with managed disks. | VMs using unmanaged disks aren't supported. HSM-protected keys aren't supported. Encryption of individual volumes on a single disk isn't 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 isn't 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 | Supported. You can use PowerShell or navigate to Advanced Setting > Storage Settings > Disk to Replicate option from the portal. | Temporary disks are excluded by default. |
| Storage Spaces Direct | Supported for crash consistent recovery points. Application consistent recovery points aren't supported. | |
| Scale-out File Server | Supported for crash consistent recovery points. Application consistent recovery points aren't supported. | |
| DRBD | Disks that are part of a DRBD setup aren't supported. | |
| LRS | Supported | |
| GRS | Supported | |
| RA-GRS | Supported | |
| ZRS | Supported | |
| Cool and Hot Storage | Not supported | Virtual machine disks aren't supported on cool and hot storage |
| Azure Storage firewalls for virtual networks | Supported | If you want to 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 | |
| Ultra Disks | Not supported | |
| Secure transfer option | Supported | |
| Write accelerator enabled disks | Not supported | |
| Tags | Supported | User-generated tags are replicated every 24 hours. |
| Soft delete | Not supported | Soft delete isn't supported because once it's enabled on a storage account, it increases cost. Azure Site Recovery performs very frequent creates/deletes of log files while replicating causing costs to increase. |
| iSCSI disks | Not supported | Azure Site Recovery may be used to migrate or failover iSCSI disks into Azure. However, iSCSI disks aren't supported for Azure to Azure replication and failover/failback. |
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 your 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 isn't guaranteed to be the same as the original order. You can rename NICs in the target region based on your organization's naming conventions. |
| Internet Load Balancer | Not supported | You can set up public/internet load balancers in the primary region. However, public/internet load balancers aren't 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 > 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 | 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 by default. To failover Secondary IP Configurations, go to the Network blade and configure them. This is supported only for region replication, zone to zone replication isn't supported. |
| 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 can't 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 isn't 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 Azure services are allowed access to the storage account. |
| Accelerated networking | Supported | Accelerated networking can be enabled on the recovery VM only if it is enabled on the source VM also. 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 doesn't let any outbound activity to be configured inside the Virtual Machine. |
| IPv6 | Not supported | Mixed configurations that include both IPv4 and IPv6 are supported. However, Azure Site Recovery will use any free IPv4 address available, if there are no free IPv4 addresses in the subnet, then the configuration is not supported. |
| Private link access to Site Recovery service | Supported | Learn more |
| Tags | Supported | User-generated tags on NICs are replicated every 24 hours. |
Next steps
- Read networking guidance for replicating Azure VMs.
- Deploy disaster recovery by replicating Azure VMs.