Support matrix for disaster recovery of VMware VMs and physical servers to Azure
Caution
This article references CentOS, a Linux distribution that is End Of Life (EOL) status. Please consider your use and plan accordingly.
This article summarizes supported components and settings for disaster recovery of VMware VMs and physical servers to Azure using Azure Site Recovery.
Note
You can now move your existing replicated items to modernized VMware disaster recovery experience. Learn more.
- Learn more about VMware VM/physical server disaster recovery architecture.
- Follow our tutorials to try out disaster recovery.
Note
Site Recovery doesn't move or store customer data out of the target region, in which disaster recovery has been set up for the source machines. Customers may select a Recovery Services Vault from a different region if they so choose. The Recovery Services Vault contains metadata but no actual customer data.
Deployment scenarios
| Scenario | Details |
|---|---|
| Disaster recovery of VMware VMs | Replication of on-premises VMware VMs to Azure. You can deploy this scenario in the Azure portal or by using PowerShell. |
| Disaster recovery of physical servers | Replication of on-premises Windows/Linux physical servers to Azure. You can deploy this scenario in the Azure portal. |
On-premises virtualization servers
| Server | Requirements | Details |
|---|---|---|
| vCenter Server | Version 8.0 & subsequent updates in this version, Version 7.0, 6.7 or 6.5 | We recommend that you use a vCenter server in your disaster recovery deployment. |
| vSphere hosts | Version 8.0 & subsequent updates in this version, Version 7.0, 6.7 or 6.5 | We recommend that vSphere hosts and vCenter servers are located in the same network as the process server. By default the process server runs on the configuration server. Learn more. |
Azure Site Recovery replication appliance
The replication appliance is an on-premises machine that runs Site Recovery components, including various Site Recovery services that help with discovery of on-premises environment, orchestration of disaster recovery and act as a bridge between on-premises and Azure.
- For VMware VMs, you can create the replication appliance by downloading an OVF template to create a VMware VM.
- For physical servers, you can set up the replication appliance manually by running our PowerShell script.
| Component | Requirements |
|---|---|
| CPU cores | 8 |
| RAM | 16 GB |
| Number of disks | 2 disks Disks include the OS disk and data disk. |
| Operating system | Windows Server 2019 with Desktop experience |
| Operating system locale | English (en-us) |
| Windows Server roles | Don't enable Active Directory Domain Services; Internet Information Services (IIS) or Hyper-V. |
| Group policies | Don't enable these group policies: - Prevent access to the command prompt. - Prevent access to registry editing tools. - Trust logic for file attachments. - Turn on Script Execution. - Learn more |
| IIS | Make sure you: - Don't have a pre-existing default website - Enable anonymous authentication - Enable FastCGI setting - Don't have preexisting website/app listening on port 443 |
| NIC type | VMXNET3 (when deployed as a VMware VM) |
| Fully qualified domain name (FQDN) | Static |
| Ports | 443 used for control channel orchestration 9443 for data transport |
| NAT | Supported |
Note
Operating system has to be installed with English locale. Conversion of locale post installation could result in potential issues.
Replicated machines
Site Recovery supports replication of any workload running on a supported machine.
| Component | Details |
|---|---|
| Machine settings | Machines that replicate to Azure must meet Azure requirements. |
| Machine workload | Site Recovery supports replication of any workload running on a supported machine. Learn more. |
| Machine name | Ensure that the display name of machine doesn't fall into Azure reserved resource names. Logical volume names aren't case-sensitive. Ensure that no two volumes on a device have same name. For example, Volumes with names "voLUME1", "volume1" can't be protected through Azure Site Recovery. |
| Azure Virtual Machines as Physical | Failover of virtual machines with Marketplace image disks is currently not supported. |
Note
Different machine with same BIOS ID are not supported.
For Windows
Note
Ensure that 500MB free space is available on the installation folder in the on-premises and Azure machine.
| Operating system | Details |
|---|---|
| Windows Server 2022 | Supported from Update rollup 59 (version 9.46 of the Mobility service) onwards. |
| Windows Server 2019 | Supported from Update rollup 34 (version 9.22 of the Mobility service) onwards. |
| Windows Server 2016 64-bit | Supported for Server Core, Server with Desktop Experience. |
| Windows Server 2012 R2 / Windows Server 2012 | Supported. |
| Windows Server 2008 R2 with SP1 onwards. | Supported. From version 9.30 of the Mobility service agent, you need servicing stack update (SSU) and SHA-2 update installed on machines running Windows 2008 R2 with SP1 or later. 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 Server 2008 with SP2 or later (64-bit/32-bit) | Supported for migration only. Learn more. From version 9.30 of the Mobility service agent, you need servicing stack update (SSU) and SHA-2 update installed on Windows 2008 SP2 machines. SHA-1 isn't supported from September 2019, and if SHA-2 code signing isn't enabled the agent extension won't install/upgrade as expected. Learn more about SHA-2 upgrade and requirements. |
| Windows 10 | Only 64-bit system is supported. 32-bit system isn't supported. |
| Windows 7 with SP1 64-bit | Supported from Update rollup 36 (version 9.22 of the Mobility service) onwards. From 9.30 of the Mobility service agent, you need servicing stack update (SSU) and SHA-2 update installed on Windows 7 SP1 machines. 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. |
For Linux
Note
Mobility service versions9.56, 9.60, 9.62 and 9.63 are only available for Modernized experience.
Mobility service version 9.58 is not released for VMWare to Azure Site Recovery.
Mobility service versions 9.59 is only available for Classic experience.
| Operating system | Details |
|---|---|
| Linux | Only 64-bit system is supported. 32-bit system isn't supported. Every Linux server should have Linux Integration Services (LIS) components installed. It is required to boot the server in Azure after test failover/failover. If in-built LIS components are missing, ensure to install the components before enabling replication for the machines to boot in Azure. Site Recovery orchestrates failover to run Linux servers in Azure. However Linux vendors might limit support to only distribution versions that haven't reached end-of-life. On Linux distributions, only the stock kernels that are part of the distribution minor version release/update are supported. Upgrading protected machines across major Linux distribution versions isn't supported. To upgrade, disable replication, upgrade the operating system, and then enable replication again. Learn more about support for Linux and open-source technology in Azure. Chained IO isn't supported by Site Recovery. |
| Linux Red Hat Enterprise | 5.2 to 5.11 6.1 to 6.10 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.7, 7.8, 7.9 Beta version, 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.3, 9.4 Few older kernels on servers running Red Hat Enterprise Linux 5.2-5.11 & 6.1-6.10 don't have Linux Integration Services (LIS) components pre-installed. If in-built LIS components are missing, ensure to install the components before enabling replication for the machines to boot in Azure. Notes: - Support for Linux Red Hat Enterprise versions 8.9, 8.10, 9.0, 9.1, 9.2, 9.3 and 9.4 is only available for Modernized experience and isn't available for Classic experience. - RHEL 9.x is supported for the following kernel versions |
| Ubuntu | Ubuntu 14.04* LTS server (review supported kernel versions) Ubuntu 16.04* LTS server (review supported kernel versions) Ubuntu 18.04* LTS server (review supported kernel versions) Ubuntu 20.04* LTS server (review supported kernel versions) Ubuntu 22.04* LTS server (review supported kernel versions) Note: Support for Ubuntu 22.04 is available for Modernized experience only and not available for Classic experience yet. (*includes support for all 14.04.x, 16.04.x, 18.04.x, 20.04.x versions) |
| Debian | Debian 7/Debian 8 (includes support for all 7. x, 8. x versions). Ensure to download latest mobility agent installer on the configuration server. Debian 9 (includes support for 9.1 to 9.13. Debian 9.0 isn't supported.). Ensure to download latest mobility agent installer on the configuration server. Debian 10, Debian 11, Debian 12 (Review supported kernel versions). |
| SUSE Linux | SUSE Linux Enterprise Server 12 SP1, SP2, SP3, SP4, SP5 (review supported kernel versions) SUSE Linux Enterprise Server 15, 15 SP1, SP2, SP3, SP4, SP5 (review supported kernel versions) SUSE Linux Enterprise Server 11 SP3. Ensure to download latest mobility agent installer on the configuration server. SUSE Linux Enterprise Server 11 SP4 Note: Upgrading replicated machines from SUSE Linux Enterprise Server 11 SP3 to SP4 isn't supported. To upgrade, disable replication and re-enable after the upgrade. Support for SUSE Linux Enterprise Server 15 SP5 is available for Modernized experience only. |
| Rocky Linux | See supported versions. |
Note
- Ensure that for Linux versions, Azure Site Recovery doesn't support customized OS images. Only the stock kernels that are part of the distribution minor version release/update are supported.
Supported kernel versions for Red Hat Enterprise Linux for Azure virtual machines
| Release | Mobility service version | Red Hat kernel version |
|---|---|---|
| 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 |
| 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 |
Ubuntu kernel versions
Note
Mobility service versions9.56 9,60, 9.61 and 9.62 are only available for Modernized experience.
Mobility service version 9.58 is not released for VMWare to Azure Site Recovery.
Mobility service versions 9.59 is only available for Classic experience.
| Supported release | Mobility service version | Kernel version |
|---|---|---|
| 14.04 LTS | 9.56, 9.57, 9.59, 9.60, 9.61, 9.62, 9.63 | 3.13.0-24-generic to 3.13.0-170-generic, 3.16.0-25-generic to 3.16.0-77-generic, 3.19.0-18-generic to 3.19.0-80-generic, 4.2.0-18-generic to 4.2.0-42-generic, 4.4.0-21-generic to 4.4.0-148-generic, 4.15.0-1023-azure to 4.15.0-1045-azure |
| 16.04 LTS | 9.56 9.57, 9.59, 9.60, 9.61, 9.62, 9.63 | 4.4.0-21-generic to 4.4.0-210-generic, 4.8.0-34-generic to 4.8.0-58-generic, 4.10.0-14-generic to 4.10.0-42-generic, 4.11.0-13-generic, 4.11.0-14-generic, 4.13.0-16-generic to 4.13.0-45-generic, 4.15.0-13-generic to 4.15.0-142-generic 4.11.0-1009-azure to 4.11.0-1016-azure 4.13.0-1005-azure to 4.13.0-1018-azure 4.15.0-1012-azure to 4.15.0-1113-azure 4.15.0-101-generic to 4.15.0-107-generic |
| 18.04 LTS | 9.63 | 4.15.0-1180-azure 4.15.0-228-generic 5.4.0-1136-azure 5.4.0-193-generic |
| 18.04 LTS | 9.62 | 4.15.0-1178-azure 4.15.0-1179-azure 4.15.0-226-generic 4.15.0-227-generic 5.4.0-1131-azure 5.4.0-1132-azure 5.4.0-1133-azure 5.4.0-1134-azure 5.4.0-1135-azure 5.4.0-186-generic 5.4.0-187-generic 5.4.0-189-generic 5.4.0-190-generic 5.4.0-192-generic |
| 18.04 LTS | 9.61 | Ubuntu 18.04 kernels support added for Modernized experience: 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 Ubuntu 18.04 kernels support added for Classic experience: 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-1174-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 4.15.0-222-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-1123-azure 5.4.0-1124-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-171-generic 5.4.0-172-generic 5.4.0-173-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-1123-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-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.59 | No new Ubuntu 18.04 kernels supported in this release. |
| 20.04 LTS | 9.63 | 5.15.0-1071-azure 5.15.0-119-generic 5.4.0-1136-azure 5.4.0-193-generic |
| 20.04 LTS | 9.62 | 5.15.0-1065-azure 5.15.0-1067-azure 5.15.0-1068-azure 5.15.0-1070-azure 5.15.0-113-generic 5.15.0-116-generic 5.15.0-117-generic 5.15.0-118-generic 5.4.0-1131-azure 5.4.0-1132-azure 5.4.0-1133-azure 5.4.0-1134-azure 5.4.0-1135-azure 5.4.0-186-generic 5.4.0-187-generic 5.4.0-189-generic 5.4.0-190-generic 5.4.0-192-generic |
| 20.04 LTS | 9.61 | Ubuntu 20.04 kernels support added for Modernized experience: 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-1060-azure 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 Ubuntu 20.04 kernels support added for Classic experience: 5.15.0-100-generic 5.15.0-1054-azure 5.15.0-1056-azure 5.15.0-1057-azure 5.15.0-1058-azure 5.15.0-92-generic 5.15.0-94-generic 5.15.0-97-generic 5.4.0-1122-azure 5.4.0-1123-azure 5.4.0-1124-azure 5.4.0-170-generic 5.4.0-171-generic 5.4.0-172-generic 5.4.0-173-generic |
| 20.04 LTS | 9.60 | 5.15.0-1054-azure 5.15.0-92-generic 5.15.0-94-generic 5.4.0-1122-azure 5.4.0-1123-azure 5.4.0-170-generic 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.59 | No new Ubuntu 20.04 kernels supported in this release. |
| 20.04 LTS | 9.57 | 5.15.0-89-generic 5.15.0-91-generic 5.4.0-167-generic 5.4.0-169-generic |
| 22.04 LTS Note: Support for Ubuntu 22.04 is available for Modernized experience only and not available for Classic experience yet. |
9.63 | 5.15.0-1071-azure 5.15.0-119-generic |
| 22.04 LTS Note: Support for Ubuntu 22.04 is available for Modernized experience only and not available for Classic experience yet. |
9.62 | 5.15.0-1066-azure 5.15.0-1067-azure 5.15.0-1068-azure 5.15.0-1070-azure 5.15.0-112-generic 5.15.0-113-generic 5.15.0-116-generic 5.15.0-117-generic 5.15.0-118-generic 6.5.0-1022-azure 6.5.0-1023-azure 6.5.0-1024-azure 6.5.0-1025-azure 6.5.0-41-generic 6.5.0-44-generic 6.5.0-45-generic |
| 22.04 LTS Note: Support for Ubuntu 22.04 is available for Modernized experience only and not available for Classic experience yet. |
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 Note: Support for Ubuntu 22.04 is available for Modernized experience only and not available for Classic experience yet. |
9.60 | 5.19.0-1025-azure 5.19.0-1026-azure 5.19.0-1027-azure 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.5.0-1007-azure 6.5.0-1009-azure 6.5.0-1010-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-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-14-generic 5.15.0-1054-azure 5.15.0-92-generic 5.15.0-94-generic 6.2.0-1019-azure 6.5.0-1011-azure 6.5.0-15-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 Note: Support for Ubuntu 22.04 is available for Modernized experience only and not available for Classic experience yet. |
9.57 | 5.15.0-76-generic 5.15.0-89-generic 5.15.0-91-generic |
Debian kernel versions
Note
Mobility service versions9.56 9,60, 9.61 and 9.62 are only available for Modernized experience.
Mobility service version 9.58 is not released for VMWare to Azure Site Recovery.
Mobility service versions 9.59 is only available for Classic experience.
| Supported release | Mobility service version | Kernel version |
|---|---|---|
| Debian 7 | 9.56, 9.57, 9.59, 9.60, 9.61, 9.62, 9.63 | 3.2.0-4-amd64 to 3.2.0-6-amd64, 3.16.0-0.bpo.4-amd64 |
| Debian 8 | 9.56 9.57, 9.59, 9.60, 9.61, 9.62, 9.63 |
3.16.0-4-amd64 to 3.16.0-11-amd64, 4.9.0-0.bpo.4-amd64 to 4.9.0-0.bpo.12-amd64 |
| Debian 9.1 | 9.63 | No new Debian 9.1 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.59 | No new Debian 9.1 kernels supported in this release. |
| Debian 10 | 9.63 | No new Debian kernels 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 | Debian 10 kernels support added for Modernized experience: 5.10.0-0.deb10.29-amd64 5.10.0-0.deb10.29-cloud-amd64 Debian 10 kernels support added for Classic experience: 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.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.59 | No new Debian 10 kernels supported in this release. |
| Debian 10 | 9.57 | No new Debian 10 kernels supported in this release |
| Debian 11 | 9.63 | No new Debian kernels in this release. |
| Debian 11 | 9.62 | Debian 11 kernels support added for Modernized experience: 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 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 kernels support added for Classic experience: No new Debian 11 kernels supported for Classic version. |
| Debian 11 | 9.61 | Debian 11 kernels support added for Modernized experience: 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 kernels support added for Classic experience: 5.10.0-27-amd64 5.10.0-27-cloud-amd64 5.10.0-28-amd64 5.10.0-28-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 |
| 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.59 | No new Debian 11 kernels supported in this release. |
| Debian 12 Note: Support for Debian 12 is available for Modernized experience only and not available for Classic experience. |
9.63 | 6.1.0-25-amd64 6.1.0-25-cloud-amd64 |
| Debian 12 Note: Support for Debian 12 is available for Modernized experience only and not available for Classic experience. |
9.62 | 6.1.0-15-cloud-amd64 6.1.0-22-amd64 6.1.0-22-cloud-amd64 6.1.0-23-amd64 6.1.0-23-cloud-amd64 |
| Debian 12 Note: Support for Debian 12 is available for Modernized experience only and not available for Classic experience. |
9.61 | 5.17.0-1-amd64 5.17.0-1-cloud-amd64 6.1.0-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 |
SUSE Linux Enterprise Server 12 supported kernel versions
Note
Mobility service versions9.56 9,60, 9.62, and 9.63 are only available for Modernized experience.
Mobility service version 9.58 is not released for VMWare to Azure Site Recovery.
Mobility service versions 9.59 is only available for Classic experience.
| Release | Mobility service version | Kernel version |
|---|---|---|
| SUSE Linux Enterprise Server 12, SP1, SP2, SP3, SP4, SP5 | 9.63 | By default, all stock SUSE 12 SP1, SP2, SP3, SP4, SP5, SP6 kernels are supported. No new kernels in this release. |
| SUSE Linux Enterprise Server 12, SP1, SP2, SP3, SP4, SP5 | 9.62 | By default, all stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels are supported. SUSE 12 Azure kernels support added for Modernized experience: 4.12.14-16.185-azure:5 4.12.14-16.188-azure:5 4.12.14-16.191azure:5 4.12.14-16.194-azure:5 |
| SUSE Linux Enterprise Server 12, SP1, SP2, SP3, SP4, SP5 | 9.61 | By default, all stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels are supported. SUSE 12 Azure kernels support added for Modernized experience: 4.12.14-16.173-azure 4.12.14-16.182-azure:5 SUSE 12 Azure kernels support added for Classic experience: 4.12.14-16.163-azure:5 4.12.14-16.168-azure:5 |
| SUSE Linux Enterprise Server 12, SP1, SP2, SP3, SP4 | 9.60 | By default, all stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels are supported. 4.12.14-16.163-azure:5 4.12.14-16.168-azure |
| SUSE Linux Enterprise Server 12, SP1, SP2, SP3, SP4 | 9.59 | By default, all stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels are supported. No new SUSE 12 kernels supported in this release. |
| SUSE Linux Enterprise Server 12, SP1, SP2, SP3, SP4 | 9.57 | By default, all stock SUSE 12 SP1, SP2, SP3, SP4, SP5 kernels are supported. No new SUSE 12 kernels supported in this release. |
SUSE Linux Enterprise Server 15 supported kernel versions
Note
Mobility service versions9.56 9,60, 9.61, and 9.63 are only available for Modernized experience.
Mobility service version 9.58 is not released for VMWare to Azure Site Recovery.
Mobility service versions 9.59 is only available for Classic experience.
| Release | Mobility service version | Kernel version |
|---|---|---|
| SUSE Linux Enterprise Server 15, SP1, SP2, SP3, SP4, SP5 | 9.63 | By default, all stock SUSE 15 SP1, SP2, SP3, SP4, SP5, SP6 kernels are supported. No new kernels in this release. |
| SUSE Linux Enterprise Server 15, SP1, SP2, SP3, SP4, SP5 | 9.62 | By default, all stock SUSE 15 SP1, SP2, SP3, SP4, SP5 kernels are supported. SUSE 15 Azure kernels support added for Modernized experience: 5.14.21-150500.33.54-azure:5 5.14.21-150500.33.57-azure:5 5.14.21-150500.33.60-azure:5 5.14.21-150500.33.63-azure:5 |
| SUSE Linux Enterprise Server 15, SP1, SP2, SP3, SP4, SP5 | 9.61 | By default, all stock SUSE 15 SP1, SP2, SP3, SP4, SP5 kernels are supported. SUSE 15 Azure kernels support added for Modernized experience: 5.14.21-150500.33.37-azure 5.14.21-150500.33.48-azure:5 5.14.21-150500.33.51-azure:5 SUSE 15 Azure kernels support added for Classic experience: 5.14.21-150500.33.29-azure:5 5.14.21-150500.33.34-azure:5 5.14.21-150500.33.42-azure |
| SUSE Linux Enterprise Server 15, SP1, SP2, SP3, SP4 | 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 | 9.59 | By default, all stock SUSE 15 SP1, SP2, SP3, SP4, SP5 kernels are supported. No new SUSE 15 kernels supported in this release. |
| SUSE Linux Enterprise Server 15, SP1, SP2, SP3, SP4, SP5 Note: SUSE 15 SP5 is only supported for Modernized experience. |
9.57 | By default, all stock SUSE 15, SP1, SP2, SP3, SP4, SP5 kernels are supported. No new SUSE 15 kernels supported in this release. |
Rocky Linux Server supported kernel versions
Important
Support for Rocky Linux is available for Modernized experience only and not available for Classic experience.
| 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 |
Linux file systems/guest storage
| Component | Supported |
|---|---|
| File systems | ext3, ext4, XFS, BTRFS (conditions applicable as per this table) |
| Logical volume management (LVM) provisioning | Thick provision - Yes Thin provision - Yes, it is supported from Update Rollup 61 onwards. It wasn't supported in earlier Mobility service versions. |
| Volume manager | - LVM is supported. - /boot on LVM is supported from Update Rollup 31 (version 9.20 of the Mobility service) onwards. It wasn't supported in earlier Mobility service versions. - Multiple OS disks aren't supported. |
| Paravirtualized storage devices | Devices exported by paravirtualized drivers aren't supported. |
| Multi-queue block IO devices | Not supported. |
| Physical servers with the HP CCISS storage controller | Not supported. |
| Device/Mount point naming convention | Device name or mount point name should be unique. Ensure that no two devices/mount points have case-sensitive names. For example, naming devices for the same VM as device1 and Device1 isn't supported. |
| Directories | If you're running a version of the Mobility service earlier than version 9.20 (released in Update Rollup 31), then these restrictions apply: - These directories (if set up as separate partitions/file-systems) must be on the same OS disk on the source server: /(root), /boot, /usr, /usr/local, /var, /etc. - The /boot directory should be on a disk partition and not be an LVM volume. From version 9.20 onwards, these restrictions don't apply. |
| Boot directory | - Boot disks with GPT partition format are supported. GPT disks are also supported as data disks. Multiple boot disks on a VM aren't supported. - /boot on an LVM volume across more than one disk isn't supported. - A machine without a boot disk can't be replicated. |
| Free space requirements | 2 GB on the /(root) partition 600 MB on the installation folder |
| XFSv5 | XFSv5 features on XFS file systems, such as metadata checksum, are supported (Mobility service version 9.10 onwards). Use the xfs_info utility to check the XFS superblock for the partition. If ftype is set to 1, then XFSv5 features are in use. |
| BTRFS | BTRFS is supported from Update Rollup 34 (version 9.22 of the Mobility service) onwards. BTRFS isn't supported if: - The BTRFS file system subvolume is changed after enabling protection. - The BTRFS file system is spread over multiple disks. - The BTRFS file system supports RAID. |
VM/Disk management
| 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, directly in the VM properties. No need to disable/re-enable replication. If you change the source VM after failover, the changes aren't captures. If you change the disk size on the Azure VM after failover, when you fail back, Site Recovery creates a new VM with the updates. |
| Add disk on replicated VM | Supported. You can manually enable replication on a disk added after a VMware VM has been protected. Learn more. |
| Exclude disk before replicating VM | Supported for VMware machines. Not supported for Physical machines, if using modernized experience. |
Note
- Any change to disk identity isn't supported. For example, if the disk partitioning has been changed from GPT to MBR or vice versa, then this will change the disk identity. In such a scenario, the replication will break and a fresh setup will be required.
- For Linux machines, device name change isn't supported as it has an impact on the disk identity.
- In Modernized, resizing the disk size to reduce it from its original size, isn't supported.
Network
| Component | Supported |
|---|---|
| Host network NIC Teaming | Supported for VMware VMs and physical machine replication. |
| Host network VLAN | Yes. |
| Host network IPv4 | Yes. |
| Host network IPv6 | No. |
| Guest/server network NIC Teaming | No. |
| Guest/server network IPv4 | Yes. |
| Guest/server network IPv6 | No. |
| Guest/server network static IP (Windows) | Yes. |
| Guest/server network static IP (Linux) | Yes. VMs are configured to use DHCP on failback. |
| Guest/server network multiple NICs | Yes. |
| Private link access to Site Recovery service | Yes. Learn more. |
Azure VM network (after failover)
| Component | Supported |
|---|---|
| Azure ExpressRoute | Yes |
| ILB | Yes |
| ELB | Yes |
| Azure Traffic Manager | Yes |
| Multi-NIC | Yes |
| Reserved IP address | Yes |
| IPv4 | Yes |
| Retain source IP address | Yes |
| Azure virtual network service endpoints |
Yes |
| Accelerated networking | No |
Storage
| Component | Supported |
|---|---|
| Dynamic disk | OS disk must be a basic disk. Data disks can be dynamic disks. Data disks can be spanned volumes. |
| Docker disk configuration | No |
| Host NFS | Yes for VMware No for physical servers |
| Host SAN (iSCSI/FC) | Yes |
| Host vSAN | Yes for VMware N/A for physical servers |
| Host multipath (MPIO) | Yes, tested with Microsoft DSM, EMC PowerPath 5.7 SP4, EMC PowerPath DSM for CLARiiON |
| Host Virtual Volumes (VVols) | Yes for VMware N/A for physical servers |
| Guest/server VMDK | Yes |
| Guest/server shared cluster disk | No |
| Guest/server encrypted disk | No |
| FIPS encryption | No |
| Guest/server NFS | No |
| Guest/server iSCSI | For Migration - Yes, but you must setup replication as a Physical machine. For Disaster Recovery - No, iSCSI will failback as an attached disk to the VM |
| Guest/server SMB 3.0 | No |
| Guest/server RDM | Yes N/A for physical servers |
| Guest/server disk > 1 GB | Yes, disk must be larger than 1024 MB Up to 32,767 GB when replicating to managed disk (9.41 version onwards) Up to 4,095 GB when replicating to storage accounts |
| Guest/server disk with 4K logical and 4k physical sector size | No |
| Guest/server disk with 4K logical and 512-bytes physical sector size | No |
| Guest/server volume with striped disk >4 TB | Yes |
| Logical volume management (LVM) | Thick provisioning - Yes Thin provisioning - Yes, it is supported from Update Rollup 61 onwards. It wasn't supported in earlier Mobility service versions. |
| Guest/server - Storage Spaces | No |
| Guest/server - NVMe interface | Yes, for Windows machines. Not supported for Linux machines. |
| Guest/server hot add/remove disk | No |
| Guest/server - exclude disk | Yes |
| Guest/server multipath (MPIO) | No |
| ReFS | Resilient File System is supported with Mobility service version 9.23 or higher |
| Guest/server EFI/UEFI boot | - Supported for all Azure Marketplace UEFI operating systems. - UEFI boot is supported as long as the Secure Boot setting is disabled. Learn more. - Windows 2008 R2 SP1 & Windows 2008 SP2 servers with UEFI isn't supported. |
| RAID disk | Hardware RAID disks aren't supported. Software RAID disks are supported. |
| Storage vMotion | Supported for migration. Not supported for disaster recovery. |
| BIOS | Supported. |
Replication channels
| Type of replication | Supported |
|---|---|
| Offloaded Data Transfers (ODX) | No |
| Offline Seeding | No |
| Azure Data Box | No |
Azure storage
| Component | Supported |
|---|---|
| Locally redundant storage | Yes |
| Geo-redundant storage | Yes |
| Read-access geo-redundant storage | Yes |
| Cool storage | No |
| Hot storage | No |
| Block blobs | No |
| Encryption at host | No |
| Encryption at rest (SSE) | Yes |
| Encryption at rest (CMK) | Yes (via PowerShell Az 3.3.0 module onwards) |
| Double Encryption at rest | Yes (via PowerShell Az 3.3.0 module onwards). Learn more on supported regions for Windows and Linux. |
| Premium storage | Yes |
| Secure transfer option | Yes |
| Import/export service | No |
| Azure Storage firewalls for VNets | Yes. Configured on target storage/cache storage account (used to store replication data). |
| General-purpose v2 storage accounts (hot and cool tiers) | Yes (Transaction costs are substantially higher for V2 compared to V1) |
| Soft delete | Not supported. |
| Disk subscription limits | Up to 3000 protected disks per subscription. Ensure that the target subscription doesn't have more than 3000 Azure Site Recovery-protected Disks (Both Data and OS). |
Azure compute
| Feature | Supported |
|---|---|
| Availability sets | Yes |
| Proximity Placement Groups | Yes |
| Availability zones | No |
| HUB | Yes |
| Managed disks | Yes |
Azure VM requirements
On-premises VMs replicated to Azure must meet the Azure VM requirements summarized in this table. When Site Recovery runs prerequisites check for replication, the check will fail if some of the requirements aren't met.
| Component | Requirements | Details |
|---|---|---|
| Guest operating system | Verify supported operating systems for replicated machines. | Check fails if unsupported. |
| Guest operating system architecture | 64-bit. | Check fails if unsupported. |
| Operating system disk size | Up to 2,048 GB for Generation 1 machines. Up to 4,095 GB for Generation 2 machines. |
Check fails if unsupported. |
| Operating system disk count | 1 boot and system partition on different disks isn't supported |
Check fails if unsupported. |
| Data disk count | 64 or less. | The number of supported disks could be affected if the count of logical volumes is large. In such scenarios, use the below formula to calculate maximum supported count of data disks. If all disks share a logical volume: D < 627790 / (450 + (Count of Logical Volume * 317)) If logical volume shared by disks is varying: D < (627790 - (Count of times Logical Volume is repeated * Count of Logical Volume * 317)) / 450 Here D is the maximum count of data disks that can be protected. |
| Data disk size | Up to 32 TB when replicating to managed disk (9.41 version onwards) Up to 4 TB when replicating to storage account Each premium storage account can host up to 35 TB of data Minimum disk size requirement - at least 1 GB |
Check fails if unsupported. |
| RAM | Site Recovery driver consumes 6% of RAM. | |
| Network adapters | Multiple adapters are supported. | |
| Shared VHD | Not supported. | Check fails if unsupported. |
| FC disk | Not supported. | Check fails if unsupported. |
| BitLocker | Not supported. | BitLocker must be disabled before you enable replication for a machine and should stay disabled while the machine is replicating via Site Recovery. |
| VM name | From 1 to 63 characters. Restricted to letters, numbers, and hyphens. The machine name must start and end with a letter or number. |
Update the value in the machine properties in Site Recovery. |
Resource group limits
To understand the number of virtual machines that can be protected under a single resource group, refer to the article on subscription limits and quotas.
Churn limits
The following table provides the Azure Site Recovery limits.
- These limits are based on our tests, but don't cover all possible app I/O combinations.
- Actual results can vary based on your application I/O mix.
- For best results, we strongly recommend that you run the Deployment Planner tool, and perform extensive application testing using test failovers to get the true performance picture for your app.
| Replication target | Average source disk I/O size | 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 |
| Source data churn | Maximum Limit |
|---|---|
| Peak data churn across all disks on a VM | 54 MB/s |
| Maximum data churn per day supported by a Process Server | 2 TB |
- These are average numbers assuming a 30 percent I/O overlap.
- Site Recovery is capable of handling higher throughput based on overlap ratio, larger write sizes, and actual workload I/O behavior.
- These numbers assume a typical backlog of approximately five minutes. That is, after data is uploaded, it is processed and a recovery point is created within five minutes.
Cache Storage account
This table summarizes support for the cache storage account used by Site Recovery during replication.
| Setting | Support | Details |
|---|---|---|
| General purpose V2 storage accounts | Supported | Site Recovery is transaction-intensive, a general-purpose v1 account may be more cost-effective. |
| 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. |
As average churn on the disks increases, the number of disks that a storage account can support decreases. The below table may be used as a guide for making decisions on number of storage accounts that need to be provisioned.
| Storage account type | Churn = 4 MBps per disk | Churn = 8 MBps per disk |
|---|---|---|
| V1 storage account | 600 disks | 300 disks |
| V2 storage account | 1500 disks | 750 disks |
Please note that the above limits are applicable to VMware and Hyper-V scenarios only.
Vault tasks
| Action | Supported |
|---|---|
| Move vault across resource groups | No |
| Move vault within and across subscriptions | No |
| Move storage, network, Azure VMs across resource groups | No |
| Move storage, network, Azure VMs within and across subscriptions. | No |
Obtain latest components
| Name | Description | Details |
|---|---|---|
| Configuration server | Installed on-premises. Coordinates communications between on-premises VMware servers or physical machines, and Azure. |
- Learn about the configuration server. - Learn about upgrading to the latest version. - Learn about setting up the configuration server. |
| Process server | Installed by default on the configuration server. Receives replication data, optimizes it with caching, compression, and encryption, and sends it to Azure. As your deployment grows, you can add additional process servers to handle larger volumes of replication traffic. |
- Learn about the process server. - Learn about upgrading to the latest version. - Learn about setting up scale-out process servers. |
| Mobility Service | Installed on VMware VM or physical servers you want to replicate. Coordinates replication between on-premises VMware servers/physical servers and Azure. |
- Learn about the Mobility service. - Learn about upgrading to the latest version. |
Next steps
Learn how to prepare Azure for disaster recovery of VMware VMs.