Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article summarizes support and prerequisites for disaster recovery (DR) of Azure virtual machines (VMs) from one Azure region to another by using Azure Site Recovery.
Deployment method support
| Deployment | Support |
|---|---|
| Azure portal | Supported. |
| Azure PowerShell | Supported. For more information, see how to set up DR for Azure VMs by using Azure PowerShell. |
| REST API | Supported. |
| Azure CLI | Not currently supported. |
Resource move or migrate support
| Resource action | Details |
|---|---|
| Move vaults across resource groups. | Not supported. |
| Move compute, storage, or network resources across resource groups. | Not supported. For example, you move a VM or associated components, such as storage or a network, after the VM is replicating. Then you need to disable and re-enable replication for the VM. |
| Replicate Azure VMs from one subscription to another for DR. | 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 Host. | Not supported. |
| Azure Virtual Desktop infrastructure VMs. | Supported if all the Azure-to-Azure replication prerequisites are fulfilled. (Zone-to-zone replication for individual servers is also 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 (GPv2) storage accounts (hot and cool tiers) | Supported | We recommend using GPv2 because GPv1 doesn't support zone-redundant storage (ZRS). |
| Premium storage | Supported | Use Premium block blob storage accounts to get high-churn support. For more information, see Azure VM disaster recovery: High-churn support. |
| Region | Same region as VM | Cache storage account should be in the same region as the VM being protected. |
| Subscription | Can be different from source VMs | Cache storage account must be in the same subscription as the source VMs. To use cache storage from the target subscription, use Azure PowerShell. |
| Azure Storage firewalls for virtual networks | Supported | If you use a firewall-enabled cache storage account or a target storage account, ensure that you allow trusted Microsoft services. Ensure that you allow access to at least one subnet of the source virtual network. If you use user-assigned managed identity (UAMI) created on an Azure Recovery Services vault, don't restrict virtual network access to your storage accounts that are used for Site Recovery. Allow access from all networks if you use vault UAMI. |
| Soft delete | Not supported | Soft delete isn't supported because after soft delete is enabled on a cache storage account, it increases cost. Site Recovery performs frequent creates/deletes of log files. Replicating causes costs to increase. |
| Encryption at rest | Supported | You can configure storage account encryption with customer-managed keys (CMKs). |
| Managed identity | Not supported | The cached storage account must allow shared key access and shared access signatures signed by the shared key. Recent changes in Azure Policy disable key authentication because of security concerns. For Site Recovery, you need to enable it again. |
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. Use the preceding table as a guide for making decisions on the number of storage accounts that must be provisioned.
The cache limits are specific to Azure-to-Azure and zone-to-zone DR scenarios.
When you enable replication via the VM workflow for cross-subscriptions, the portal lists only the cache storage account from the source subscription. It doesn't list any storage account created in the target subscription. To set up this scenario, use Azure PowerShell.
Replicated machine operating systems
Site Recovery supports replication of Azure VMs running the operating systems listed in this section. For example, an already-replicating machine's operating system is later upgraded (or downgraded) to a different major version of the operating system, as in Red Hat Enterprise Linux (RHEL) 8 to RHEL 9. Then you must disable replication, uninstall the mobility agent, and re-enable replication after the upgrade.
Windows
| Operating system | Details |
|---|---|
| Windows Server 2025 | Supported. |
| 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 as of September 2019. If SHA-2 code signing isn't enabled, the agent extension won't install/upgrade as expected. For more information, see SHA-2 code signing support requirement for Windows. |
| Windows 11 (x64) | Supported (from the mobility agent version 9.56 and later). |
| Windows 10 (x64) | Supported. |
| Windows 7 (x64) with SP1 and later | From version 9.30 of the Mobility service extension for Azure VMs, you need to install a Windows SSU and SHA-2 update on machines running Windows 7 with SP1. SHA-1 isn't supported as of September 2019. If SHA-2 code signing isn't enabled, the agent extension won't install/upgrade as expected. For more information, see SHA-2 code signing support requirement for Windows. |
Linux
Mobility service versions 9.58 and 9.59 aren't 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 later), 8.5 (4.18.0-348.5.1.el8_5.x86_64 or later), 8.6 (4.18.0-348.5.1.el8_5.x86_64 or later), 8.7, 8.8, 8.9, 8.10, 9.0, 9.1, 9.2, 9.3, 9.4, 9.5, 9.6, 10.0 RHEL 9.x, 10.x is supported for the following kernel versions. |
| 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 versions. 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 cloud-init configuration). To re-enable password-based sign-in on the VM, reset 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 versions. 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 cloud-init configuration). To re-enable password-based sign-in on the VM, reset 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 versions. |
| Ubuntu 22.04 LTS server | Includes support for all 22.04.x versions. Supported kernel versions. |
| 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, SP6, SP7. (Supported kernel versions.) |
| SUSE Linux Enterprise Server 11 | SP3. Upgrade of replicating machines from SP3 to SP4 isn't supported. If a replicated machine was upgraded, disable replication and re-enable replication after the upgrade. |
| SUSE Linux Enterprise Server 11 | SP4. |
Rocky Linux | See supported versions.
For Linux versions, Site Recovery doesn't support custom OS kernels. Only the stock kernels that are part of the distribution minor version release/update are supported.
Site Recovery doesn't support VMs created on ARM64 CPU architecture.
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 VMs
Enabling replication when you create a VM deployment workflow isn't supported for VMs with OS RHEL 9 and later.
| Release | Mobility service version | Red Hat kernel version |
|---|---|---|
| RHEL 10.0 | 9.66 | 6.12.0-55.9.1 and later |
| RHEL 9.0 RHEL 9.1 RHEL 9.2 RHEL 9.3 RHEL 9.4 RHEL 9.5 RHEL 9.6 |
9.65 | 5.14.0-503.11.1 and later 5.14.0-570.12.1 and later |
| RHEL 9.0 RHEL 9.1 RHEL 9.2 RHEL 9.3 RHEL 9.4 RHEL 9.5 |
9.64 | 5.14.0-503.11.1 and later |
| RHEL 9.0 RHEL 9.1 RHEL 9.2 RHEL 9.3 RHEL 9.4 |
9.63 | 5.14.0-284.73.1.el9_2.x86_64 5.14.0-284.75.1.el9_2.x86_64 5.14.0-284.77.1.el9_2.x86_64 5.14.0-284.79.1.el9_2.x86_64 5.14.0-284.80.1.el9_2.x86_64 5.14.0-284.82.1.el9_2.x86_64 5.14.0-284.84.1.el9_2.x86_64 5.14.0-284.85.1.el9_2.x86_64 5.14.0-284.86.1.el9_2.x86_64 5.14.0-427.24.1.el9_4.x86_64 5.14.0-427.26.1.el9_4.x86_64 5.14.0-427.28.1.el9_4.x86_64 5.14.0-427.31.1.el9_4.x86_64 5.14.0-427.33.1.el9_4.x86_64 5.14.0-427.35.1.el9_4.x86_64 5.14.0-427.37.1.el9_4.x86_64 5.14.0-427.13.1.el9_4.x86_64 and later |
| 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 5.14.0-427.13.1.el9_4.x86_64 and later |
| 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 VMs
Mobility service versions 9.58 and 9.59 aren't released for Azure to Azure Site Recovery.
| Release | Mobility service version | Kernel version |
|---|---|---|
| 14.04 LTS | 9.66 | No new 14.04 LTS kernels supported in this release. |
| 14.04 LTS | 9.65 | No new 14.04 LTS kernels supported in this release. |
| 14.04 LTS | 9.64 | No new 14.04 LTS kernels supported in this release. |
| 14.04 LTS | 9.63 | No new 14.04 LTS kernels supported in this release. |
| 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. |
| 16.04 LTS | 9.66 | No new 16.04 LTS kernels supported in this release. |
| 16.04 LTS | 9.65 | No new 16.04 LTS kernels supported in this release. |
| 16.04 LTS | 9.64 | No new 16.04 LTS kernels supported in this release. |
| 16.04 LTS | 9.63 | No new 16.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. |
| 18.04 LTS | 9.66 | 4.15.0-1188-azure 4.15.0-1189-azure 4.15.0-1190-azure 4.15.0-1191-azure 4.15.0-1192-azure 4.15.0-237-generic 4.15.0-238-generic 4.15.0-239-generic 4.15.0-240-generic 4.15.0-241-generic 5.4.0-1150-azure 5.4.0-1151-azure 5.4.0-1152-azure 5.4.0-1153-azure 5.4.0-215-generic 5.4.0-216-generic 5.4.0-218-generic 5.4.0-219-generic 5.4.0-220-generic 5.4.0-221-generic |
| 18.04 LTS | 9.65 | 4.15.0-1186-azure 4.15.0-1187-azure 4.15.0-235-generic 4.15.0-236-generic 5.4.0-1147-azure 5.4.0-1148-azure 5.4.0-1149-azure 5.4.0-211-generic 5.4.0-212-generic 5.4.0-214-generic |
| 18.04 LTS | 9.64 | 4.15.0-1185-azure 4.15.0-233-generic 4.15.0-234-generic 5.4.0-1142-azure 5.4.0-1143-azure 5.4.0-1145-azure 5.4.0-208-generic 4.15.0-1181-azure 4.15.0-1182-azure 4.15.0-1183-azure 4.15.0-1184-azure 4.15.0-229-generic 4.15.0-230-generic 4.15.0-231-generic 4.15.0-232-generic 5.4.0-1137-azure 5.4.0-1138-azure 5.4.0-1139-azure 5.4.0-1140-azure 5.4.0-195-generic 5.4.0-196-generic 5.4.0-198-generic 5.4.0-200-generic 5.4.0-202-generic 5.4.0-204-generic |
| 18.04 LTS | 9.63 | 5.4.0-1135-azure 5.4.0-192-generic 4.15.0-1180-azure 4.15.0-228-generic 5.4.0-1136-azure 5.4.0-193-generic 5.4.0-1137-azure 5.4.0-1138-azure 5.4.0-195-generic 5.4.0-196-generic 4.15.0-1181-azure 4.15.0-229-generic 4.15.0-1182-azure 4.15.0-230-generic 5.4.0-1139-azure 5.4.0-198-generic |
| 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 4.15.0-1178-azure 5.4.0-1132-azure 5.4.0-1133-azure 5.4.0-1134-azure 5.4.0-190-generic 5.4.0-189-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 |
| 20.04 LTS | 9.66 | 5.15.0-1088-azure 5.15.0-1089-azure 5.15.0-1091-azure 5.15.0-1094-azure 5.15.0-1095-azure 5.15.0-139-generic 5.15.0-142-generic 5.15.0-143-generic 5.15.0-144-generic 5.15.0-145-generic 5.15.0-151-generic 5.15.0-152-generic 5.15.0-153-generic 5.4.0-1150-azure 5.4.0-1151-azure 5.4.0-1152-azure 5.4.0-1153-azure 5.4.0-215-generic 5.4.0-216-generic 5.4.0-218-generic 5.4.0-219-generic 5.4.0-220-generic 5.4.0-221-generic |
| 20.04 LTS | 9.65 | 5.15.0-1082-azure 5.15.0-1086-azure 5.15.0-1087-azure 5.15.0-136-generic 5.15.0-138-generic 5.4.0-1147-azure 5.4.0-1148-azure 5.4.0-1149-azure 5.4.0-211-generic 5.4.0-212-generic 5.4.0-214-generic |
| 20.04 LTS | 9.64 | 5.15.0-1079-azure 5.15.0-1081-azure 5.15.0-131-generic 5.15.0-134-generic 5.4.0-1143-azure 5.4.0-1145-azure 5.4.0-205-generic 5.4.0-208-generic 5.15.0-1072-azure 5.15.0-1073-azure 5.15.0-1074-azure 5.15.0-1075-azure 5.15.0-1078-azure 5.15.0-121-generic 5.15.0-122-generic 5.15.0-124-generic 5.15.0-125-generic 5.15.0-126-generic 5.15.0-127-generic 5.15.0-130-generic 5.4.0-1137-azure 5.4.0-1138-azure 5.4.0-1139-azure 5.4.0-1140-azure 5.4.0-1142-azure 5.4.0-195-generic 5.4.0-196-generic 5.4.0-198-generic 5.4.0-200-generic 5.4.0-202-generic 5.4.0-204-generic |
| 20.04 LTS | 9.63 | 5.15.0-1070-azure 5.4.0-1135-azure 5.4.0-192-generic 5.15.0-1071-azure 5.15.0-118-generic 5.15.0-119-generic 5.4.0-1136-azure 5.4.0-193-generic 5.15.0-1072-azure 5.15.0-1073-azure 5.15.0-121-generic 5.15.0-122-generic 5.4.0-1137-azure 5.4.0-1138-azure 5.4.0-195-generic 5.4.0-196-generic |
| 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 5.15.0-1068-azure 5.15.0-116-generic 5.15.0-117-generic 5.4.0-1133-azure 5.4.0-1134-azure 5.4.0-189-generic 5.4.0-190-generic 5.15.0-1074-azure 5.15.0-124-generic 5.4.0-1139-azure 5.4.0-198-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 |
| 22.04 LTS | 9.66 | 5.15.0-1088-azure 5.15.0-1089-azure 5.15.0-1090-azure 5.15.0-1091-azure 5.15.0-1092-azure 5.15.0-1094-azure 5.15.0-1095-azure 5.15.0-139-generic 5.15.0-140-generic 5.15.0-141-generic 5.15.0-142-generic 5.15.0-143-generic 5.15.0-144-generic 5.15.0-151-generic 5.15.0-152-generic 5.15.0-153-generic 6.8.0-1028-azure 6.8.0-1029-azure 6.8.0-1030-azure 6.8.0-1031-azure 6.8.0-1034-azure 6.8.0-58-generic 6.8.0-59-generic 6.8.0-60-generic 6.8.0-64-generic 6.8.0-65-generic 6.8.0-78-generic 6.8.0-79-generic 6.8.0-83-generic |
| 22.04 LTS | 9.65 | 5.15.0-1082-azure 5.15.0-1084-azure 5.15.0-1086-azure 5.15.0-1087-azure 5.15.0-135-generic 5.15.0-136-generic 5.15.0-138-generic 6.8.0-1025-azure 6.8.0-1026-azure 6.8.0-1027-azure 6.8.0-57-generic |
| 22.04 LTS | 9.64 | 5.15.0-1079-azure 5.15.0-1081-azure 5.15.0-131-generic 5.15.0-133-generic 5.15.0-134-generic 6.8.0-1021-azure 6.8.0-52-generic 5.15.0-1072-azure 5.15.0-1073-azure 5.15.0-1074-azure 5.15.0-1075-azure 5.15.0-1078-azure 5.15.0-121-generic 5.15.0-122-generic 5.15.0-124-generic 5.15.0-125-generic 5.15.0-126-generic 5.15.0-127-generic 5.15.0-130-generic 6.8.0-1008-azure 6.8.0-1009-azure 6.8.0-1010-azure 6.8.0-1012-azure 6.8.0-1013-azure 6.8.0-1014-azure 6.8.0-1015-azure 6.8.0-1017-azure 6.8.0-1018-azure 6.8.0-1020-azure 6.8.0-38-generic 6.8.0-39-generic 6.8.0-40-generic 6.8.0-45-generic 6.8.0-47-generic 6.8.0-48-generic 6.8.0-49-generic 6.8.0-50-generic 6.8.0-51-generic |
| 22.04 LTS | 9.63 | 5.15.0-1070-azure 5.15.0-118-generic 5.15.0-1071-azure 5.15.0-119-generic 5.15.0-1072-azure 5.15.0-1073-azure 5.15.0-121-generic 5.15.0-122-generic 5.15.0-1074-azure 5.15.0-124-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 5.15.0-1068-azure 5.15.0-116-generic 5.15.0-117-generic 6.5.0-1024-azure 6.5.0-1025-azure 6.5.0-44-generic 6.5.0-45-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 |
| 24.04 LTS | 9.66 | 6.11.0-1008-azure 6.11.0-1012-azure 6.11.0-1013-azure 6.11.0-1014-azure 6.11.0-1015-azure 6.11.0-1017-azure 6.11.0-1018-azure 6.11.0-17-generic 6.11.0-19-generic 6.11.0-21-generic 6.11.0-24-generic 6.11.0-25-generic 6.11.0-26-generic 6.11.0-28-generic 6.11.0-29-generic 6.8.0-1028-azure 6.8.0-1029-azure 6.8.0-1030-azure 6.8.0-1031-azure 6.8.0-1034-azure 6.8.0-59-generic 6.8.0-60-generic 6.8.0-62-generic 6.8.0-63-generic 6.8.0-64-generic 6.8.0-71-generic 6.8.0-78-generic 6.8.0-79-generic 6.8.0-83-generic |
| 24.04 LTS | 9.65 | 6.8.0-1025-azure 6.8.0-1026-azure 6.8.0-1027-azure 6.8.0-56-generic 6.8.0-57-generic 6.8.0-58-generic |
| 24.04 LTS | 9.64 | 6.8.0-1021-azure 6.8.0-52-generic 6.8.0-53-generic 6.8.0-54-generic 6.8.0-55-generic 6.8.0-1007-azure 6.8.0-1008-azure 6.8.0-1009-azure 6.8.0-1010-azure 6.8.0-1012-azure 6.8.0-1013-azure 6.8.0-1014-azure 6.8.0-1015-azure 6.8.0-1016-azure 6.8.0-1017-azure 6.8.0-1018-azure 6.8.0-1020-azure 6.8.0-31-generic 6.8.0-35-generic 6.8.0-36-generic 6.8.0-38-generic 6.8.0-39-generic 6.8.0-40-generic 6.8.0-41-generic 6.8.0-44-generic 6.8.0-45-generic 6.8.0-47-generic 6.8.0-48-generic 6.8.0-49-generic 6.8.0-50-generic 6.8.0-51-generic |
Supported Debian kernel versions for Azure VMs
Mobility service versions 9.58 and 9.59 aren't released for Azure to Azure Site Recovery.
| Release | Mobility service version | Kernel version |
|---|---|---|
| Debian 7 | 9.66 | No new Debian 7 kernels supported in this release. |
| Debian 7 | 9.65 | No new Debian 7 kernels supported in this release. |
| Debian 7 | 9.64 | No new Debian 7 kernels supported in this release. |
| Debian 7 | 9.63 | No new Debian 7 kernels supported in this release. |
| 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 8 | 9.66 | No new Debian 8 kernels supported in this release. |
| Debian 8 | 9.65 | No new Debian 8 kernels supported in this release. |
| Debian 8 | 9.64 | No new Debian 8 kernels supported in this release. |
| Debian 8 | 9.63 | No new Debian 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 9 | 9.66 | No new Debian 9 kernels supported in this release. |
| Debian 9 | 9.65 | No new Debian 9 kernels supported in this release. |
| Debian 9 | 9.64 | No new Debian 9 kernels supported in this release. |
| Debian 9.1 | 9.62 | No new Debian 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 10 | 9.66 | No new Debian 10 kernels supported in this release. |
| Debian 10 | 9.65 | No new Debian 10 kernels supported in this release. |
| Debian 10 | 9.64 | No new Debian 10 kernels supported in this release. |
| Debian 10 | 9.63 | No new Debian 10 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 11 | 9.66 | 5.10.0-35-amd64 5.10.0-35-cloud-amd64 6.1.0-0.deb11.35-amd64 6.1.0-0.deb11.35-cloud-amd64 6.1.0-0.deb11.37-amd64 6.1.0-0.deb11.37-cloud-amd64 6.1.0-0.deb11.38-amd64 6.1.0-0.deb11.38-cloud-amd64 6.1.0-0.deb11.39-amd64 6.1.0-0.deb11.39-cloud-amd64 |
| Debian 11 | 9.65 | 6.1.0-0.deb11.32-amd64 6.1.0-0.deb11.32-cloud-amd64 |
| Debian 11 | 9.64 | 5.10.0-34-amd64 5.10.0-34-cloud-amd64 6.1.0-0.deb11.31-amd64 6.1.0-0.deb11.31-cloud-amd64 5.10.0-33-amd64 5.10.0-33-cloud-amd64 6.1.0-0.deb11.25-amd64 6.1.0-0.deb11.25-cloud-amd64 6.1.0-0.deb11.26-amd64 6.1.0-0.deb11.26-cloud-amd64 6.1.0-0.deb11.28-amd64 6.1.0-0.deb11.28-cloud-amd64 |
| Debian 11 | 9.63 | 5.10.0-26-amd64 5.10.0-26-cloud-amd64 5.10.0-31-amd64 5.10.0-31-cloud-amd64 5.10.0-32-amd64 5.10.0-32-cloud-amd64 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 6.1.0-0.deb11.21-amd64 6.1.0-0.deb11.21-cloud-amd64 6.1.0-0.deb11.22-amd64 6.1.0-0.deb11.22-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 12 | 9.66 | 6.1.0-34-amd64 6.1.0-34-cloud-amd64 6.1.0-35-amd64 6.1.0-35-cloud-amd64 6.1.0-37-amd64 6.1.0-37-cloud-amd64 6.1.0-38-amd64 6.1.0-38-cloud-amd64 6.1.0-39-amd64 6.1.0-39-cloud-amd64 |
| Debian 12 | 9.65 | 6.1.0-32-amd64 6.1.0-32-cloud-amd64 6.1.0-33-amd64 6.1.0-33-cloud-amd64 |
| Debian 12 | 9.64 | 6.1.0-29-amd64 6.1.0-29-cloud-amd64 6.1.0-30-amd64 6.1.0-30-cloud-amd64 6.1.0-31-amd64 6.1.0-31-cloud-amd64 6.1.0-15-cloud-amd64 6.1.0-26-amd64 6.1.0-26-cloud-amd64 6.1.0-27-amd64 6.1.0-27-cloud-amd64 6.1.0-28-amd64 6.1.0-28-cloud-amd64 |
| Debian 12 | 9.63 | 6.1.0-25-amd64 6.1.0-25-cloud-amd64 6.1.0-26-amd64 6.1.0-26-cloud-amd64 |
| Debian 12 | 9.62 | 6.1.0-22-amd64 6.1.0-22-cloud-amd64 6.1.0-23-amd64 6.1.0-23-cloud-amd64 6.5.0-0.deb12.4-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 |
Supported SUSE Linux Enterprise Server 12 kernel versions for Azure VMs
Mobility service versions 9.58 and 9.59 aren't released for Azure to Azure Site Recovery.
| Release | Mobility service version | Kernel version |
|---|---|---|
| SUSE Linux Enterprise Server 12 (SP1, SP2, SP3, SP4, SP5) | 9.66 | New SUSE 12 kernels aren't supported in this release. |
| SUSE Linux Enterprise Server 12 (SP1, SP2, SP3, SP4, SP5) | 9.65 | All stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels are supported. 4.12.14-16.197-azure:5 4.12.14-16.200-azure:5 |
| SUSE Linux Enterprise Server 12 (SP1, SP2, SP3, SP4, SP5) | 9.64 | All stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels are supported. 4.12.14-16.197-azure:5 4.12.14-16.200-azure:5 |
| SUSE Linux Enterprise Server 12 (SP1, SP2, SP3, SP4, SP5) | 9.63 | All stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels are supported. 4.12.14-16.194-azure:5 4.12.14-16.197-azure:5 4.12.14-16.200-azure:5 |
| 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 4.12.14-16.191-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 |
Supported SUSE Linux Enterprise Server 15 kernel versions for Azure VMs
Mobility service versions 9.58 and 9.59 aren't released for Azure to Azure Site Recovery.
| Release | Mobility service version | Kernel version |
|---|---|---|
| SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5, SP6, SP7) | 9.66 | All stock SUSE 15 SP1, SP2, SP3, SP4, SP5, SP6, SP7 kernels are supported. 6.4.0-150600.8.37-azure:6 6.4.0-150600.8.40-azure:6 6.4.0-150600.8.43-azure:6 6.4.0-150600.8.48-azure:6 6.4.0-150700.18-azure:7 6.4.0-150700.20.11-azure:7 6.4.0-150700.20.3-azure:7 6.4.0-150700.20.6-azure:7 |
| SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5, SP6) | 9.65 | All stock SUSE 15 SP1, SP2, SP3, SP4, SP5, SP6 kernels are supported. 6.4.0-150600.8.23-azure:6 6.4.0-150600.8.26-azure:6 6.4.0-150600.8.31-azure:6 6.4.0-150600.8.34-azure:6 |
| SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5, SP6) | 9.64 | All stock SUSE 15 SP1, SP2, SP3, SP4, SP5, SP6 kernels are supported. 5.14.21-150500.33.66-azure:5 5.14.21-150500.33.69-azure:5 5.14.21-150500.33.72-azure:5 5.14.21-150500.33.75-azure:5 6.4.0-150600.6-azure:6 6.4.0-150600.8.11-azure:6 6.4.0-150600.8.14-azure:6 6.4.0-150600.8.17-azure:6 6.4.0-150600.8.20-azure:6 6.4.0-150600.8.5-azure:6 6.4.0-150600.8.8-azure:6 |
| SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5, SP6) | 9.63 | All stock SUSE 15 SP1, SP2, SP3, SP4, SP5, SP6 kernels are supported. 5.14.21-150500.33.63-azure:5 5.14.21-150500.33.66-azure:5 6.4.0-150600.6-azure:6 6.4.0-150600.8.11-azure:6 6.4.0-150600.8.5-azure:6 6.4.0-150600.8.8-azure:6 6.4.0-150600.8.14-azure:6 5.14.21-150500.33.69-azure:5 |
| SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5) | 9.62 | All stock SUSE 15 SP1, SP2, SP3, SP4, SP5 kernels are supported. 5.14.21-150500.33.54-azure:5 5.14.21-150500.33.57-azure:5 5.14.21-150500.33.60-azure:5 |
| SUSE Linux Enterprise Server 15 (SP1, SP2, SP3, SP4, SP5) | 9.61 | All stock SUSE 15 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 |
Supported Rocky Linux kernel versions for Azure VMs
Mobility service versions 9.58 and 9.59 aren't released for Azure to Azure Site Recovery.
| Release | Mobility service version | Red Hat kernel version |
|---|---|---|
| Rocky Linux 10.0 Rocky linux 9.6 |
9.66 | 6.12.0-55.9.1 and later 5.14.0-570.12.1 and later |
| Rocky Linux 9.0 Rocky Linux 9.1 Rocky Linux 9.2 Rocky Linux 9.3 Rocky Linux 9.4 Rocky Linux 9.5 |
9.65 | 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.64 | 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.63 | 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.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 |
Replicated machines: Linux file system/guest storage
- File systems: ext3, ext4, XFS, and BTRFS
- Volume manager: LVM2
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 VM sizes. |
| RAM | 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. | |
| Azure Dedicated Host | 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: Non-Microsoft published | Supported. | Supported if the VM runs on a supported operating system. |
| Custom images: Non-Microsoft published | Supported. | The VM is supported if it runs on a supported operating system. During test failover and failover, Azure creates a VM with an Azure Marketplace image. Ensure that no custom Azure policy blocks this operation. |
| VMs migrated by using Site Recovery | Supported. | If a VMware VM or physical machine was migrated to Azure by using Site Recovery, you need to uninstall the older version of the Mobility service running on the machine and restart the machine before you replicate it to another Azure region. |
| Azure role-based access control (RBAC) policies | Not supported. | Azure RBAC policies on VMs aren't replicated to the failover VM in the target region. |
| Extensions | Not supported. | Extensions aren't replicated to the failover VM in the target region. It needs to be installed manually after failover. |
| Proximity placement groups (PPGs) | Supported. | VMs located inside PPGs by using Site Recovery. |
| Tags | Supported. | User-generated tags applied on source VMs are carried over to target VMs post-test failover or failover. Tags on the VMs replicate once every 24 hours for as long as the VMs are present in the target region. |
Replicated machines: Disk actions
| Action | Details |
|---|---|
| Resize a disk on a replicated VM. | Resizing up on the source VM is supported. Resizing down on the source VM isn't supported. Perform resizing 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, Site Recovery doesn't capture the changes. Failback is to the original VM size. If you resize to 4 TB or larger, see the Azure guidance on disk caching in Azure Premium storage: Design for high performance. |
| 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's smaller than 4 TB supports caching. Changing the cache setting of an Azure disk detaches and reattaches the target disk. If it's the operating system disk, the VM is restarted. Before you change the disk cache setting, stop all applications or services that this disruption might affect. Not following the recommendations could lead to data corruption. |
Replicated machines: Storage
Note
Site Recovery supports storage accounts with page blobs for unmanaged disk replication.
Unmanaged disks were deprecated on September 30, 2022, and are slated to fully retire by March 31, 2026. Managed disks now offer the full capabilities of unmanaged disks, along with other advancements.
The following table summarizes support for the Azure VM OS disk, data disk, and temporary disk:
- To avoid any performance issues, observe the VM disk limits and targets for managed disks.
- If you deploy with the default settings, Site Recovery automatically creates disks and storage accounts based on the source settings.
- If you customize, ensure that you follow the guidelines.
| Component | Support | Details |
|---|---|---|
| Disk renaming | Supported. | |
| OS disk maximum size | 4,095 GiB. | 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 about temporary disks. |
| Data disk maximum size | 32 TiB for managed disks. 4 TiB for unmanaged disks. |
|
| Data disk minimum size | No restriction for unmanaged disks. 1 GiB 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 TiB. | This size is the upper limit for cumulative size of page blobs created in a Premium storage account. |
| Data disks 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 can't catch up. 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 that you have the same storage configuration in the target region. |
| Managed disk: Standard | Supported in Azure regions in which Site Recovery is supported. | |
| Managed disk: Premium | Supported in Azure regions in which Site Recovery is supported. | |
| Disk subscription limits | Up to 3,000 protected disks per subscription. | Ensure that the source or target subscription doesn't have more than 3,000 Site Recovery-protected disks (both data and OS). |
| Standard SSD | Supported. | |
| Redundancy | Locally redundant storage (LRS), ZRS, and geo-redundant storage (GRS) are supported. | |
| Cool and hot storage | Not supported. | VM disks aren't supported on cool or hot storage. |
| Storage Spaces | Supported. | |
| NVMe storage interface | Not supported. | |
| Encryption at host | Not supported. | The VM is protected, but the failed-over VM doesn't have encryption at host enabled. For more information, see Enable end-to-end encryption by using encryption at host. |
| Encryption at rest (SSE) | Supported. | SSE is the default setting on storage accounts. |
| Double encryption at rest | Supported. | Learn more about supported regions for Windows and Linux. |
| FIPS encryption | Not supported. | |
| Shared access signature key rotation | Supported. | If the shared access signature key for storage accounts is rotated, you must 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. Use hot add to add only one disk at a time to an Azure VM. Parallel addition of multiple disks isn't supported. |
| Hot remove disk | Not supported. | If you remove a data disk on the VM, you need to disable replication and enable replication again for the VM. |
| Exclude disk | Supported. Use Azure PowerShell or go to the 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. | |
| Distributed replicated block device (DRBD) | Disks that are part of a DRBD setup aren't supported. | |
| LRS | Supported. | |
| GRS | Supported. | |
| Read-access GRS | Supported. | |
| Cool and hot storage | Not supported. | VM disks aren't supported on cool or 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 (hot and cool tiers) | Supported. | Transaction costs increase substantially compared to general-purpose V1 storage accounts. |
| Generation 2 (UEFI boot) | Supported. | |
| NVMe disks | Not supported. | |
| Managed shared disk | Supported. | Premium SSDv2 and Ultra disks aren't supported. |
| Managed Premium SSD v2 disk | Supported. | Because block blob storage accounts aren't supported in China North and China East regions, Site Recovery for Premium SSD v2 disks can't be supported. |
| Ultra disks | Supported. | Because block blob storage accounts aren't supported in China North and China East regions, Site Recovery for Ultra disks can't be supported. |
| Secure transfer option | Supported. | |
| Write accelerator enabled disks | Not supported. | |
| Tags | Supported. | User-generated tags replicate every 24 hours. |
| Soft delete | Not supported. | Soft delete isn't supported because after soft delete is enabled on a storage account, it increases cost. Site Recovery performs frequent creations and deletions of log files. Replicating causes costs to increase. |
| iSCSI disks | Not supported. | You can use Site Recovery to migrate or fail over iSCSI disks into Azure. However, iSCSI disks aren't supported for Azure-to-Azure replication and failover/failback. |
| Storage Replica | Not supported. |
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 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-VM data churn.
- The current limit for per-VM data churn is 54 MBps regardless of size.
| Replica disk type | Average source disk I/O | Average source disk data churn | Total source disk data churn per day |
|---|---|---|---|
| Standard storage | 8 KB | 2 MBps | 168 GB per disk |
| Premium SSD with disk size 128 GiB or more | 8 KB | 2 MBps | 168 GB per disk |
| Premium SSD with disk size 128 GiB or more | 16 KB | 4 MBps | 336 GB per disk |
| Premium SSD with disk size 128 GiB or more | 32 KB or greater | 8 MBps | 672 GB per disk |
| Premium SSD with disk size 512 GiB or more | 8 KB | 5 MBps | 421 GB per disk |
| Premium SSD with disk size 512 GiB or more | 16 KB or greater | 20 MBps | 1,684 GB per disk |
High-churn support is now available in Site Recovery where churn limit per VM increased up to 100 MBps. For more information, see Azure VM disaster recovery: High-churn support.
Replicated machines: Networking
| Setting | Support | Details |
|---|---|---|
| Network interface card (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 affect 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. Site Recovery doesn't support public/internet load balancers in the DR region. |
| Internal load balancer | Supported | Associate the preconfigured load balancer by using an Azure Automation script in a recovery plan. |
| Public IP address | Supported | Associate an existing public IP address with the NIC. You can also create a public IP address and associate it with the NIC by using an Azure Automation script in a recovery plan. |
| Network security group (NSG) on NIC | Supported | Associate the NSG with the NIC by using an Azure Automation script in a recovery plan. |
| NSG on subnet | Supported | Associate the NSG with the subnet by using an Azure Automation script in a recovery plan. |
| Application security group (ASG) | Unsupported | Site Recovery doesn't support ASGs. |
| 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, the NIC is 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 to a fixed IP address if necessary. |
| 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 fail over secondary IP configurations, go to the Network pane and configure them. Supported only for region replication. Zone-to-zone replication isn't supported. |
| Azure Traffic Manager | Supported | You can preconfigure Traffic Manager so that traffic is regularly routed to the endpoint in the source region. You can also route traffic to the endpoint in the target region if there was failover. |
| Azure DNS | Supported | |
| Custom DNS | Supported | |
| Unauthenticated proxy | Supported | Learn more about networking in Azure VM disaster recovery. |
| Authenticated proxy | Not supported | If the VM is using an authenticated proxy for outbound connectivity, it can't be replicated by using Site Recovery. |
| VPN site-to-site connection to on-premises (with or without Azure ExpressRoute) | Supported | Ensure that the user-defined routes and NSGs are configured in such a way that the Site Recovery traffic isn't routed to on-premises. Learn more about networking in Azure VM disaster recovery. |
| Network-to-network connection | Supported | Learn more about networking in Azure VM disaster recovery. |
| Virtual network service endpoints | Supported | If you restrict the virtual network access to storage accounts, ensure that the trusted Microsoft services are allowed access to the storage account. |
| Accelerated networking | Supported | You can enable accelerated networking on the recovery VM only if you enable it on the source VM also. Learn more about accelerated networking with Azure VM disaster recovery. |
| Palo Alto Network Appliance | Not supported | With non-Microsoft appliances, the provider inside the VM often imposes restrictions. Site Recovery needs agents, extensions, and outbound connectivity to be available. The appliance doesn't allow any outbound activity to be configured inside the VM. |
| IPv6 | Not supported | Mixed configurations that include both IPv4 and IPv6 are supported. Site Recovery uses any free IPv4 address that's available. If there are no free IPv4 addresses in the subnet, the configuration isn't supported. |
| Private link access to Site Recovery | Supported | Learn more about how to replicate machines with private endpoints. |
| Tags | Supported | User-generated tags on NICs replicate every 24 hours. |
Related content
- Read networking guidance for replicating Azure VMs.
- Deploy disaster recovery by replicating Azure VMs.