Support matrix for disaster recovery of VMware VMs and physical servers to Azure

This article summarizes supported components and settings for disaster recovery of VMware VMs and physical servers to Azure using Azure Site Recovery.

  • Learn more about VMware VM/physical server disaster recovery architecture.
  • Follow our tutorials to try out disaster recovery.

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 6.7, 6.5, 6.0, or 5.5 We recommend that you use a vCenter server in your disaster recovery deployment.
vSphere hosts Version 6.7, 6.5, 6.0, or 5.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.

Site Recovery configuration server

The configuration server is an on-premises machine that runs Site Recovery components, including the configuration server, process server, and master target server.

  • For VMware VMs you set the configuration server by downloading an OVF template to create a VMware VM.
  • For physical servers, you set up the configuration server machine manually.
Component Requirements
CPU cores 8
RAM 16 GB
Number of disks 3 disks

Disks include the OS disk, process server cache disk, and retention drive for failback.
Disk free space 600 GB of space for the process server cache.
Disk free space 600 GB of space for the retention drive.
Operating system Windows Server 2012 R2, or Windows Server 2016 with Desktop experience
Operating system locale English (en-us)
PowerCLI Not needed for configuration server version 9.14 or later.
Windows Server roles Don't enable Active Directory Domain Services; Internet Information Services (IIS) or Hyper-V.
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 preexisting 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)
IP address type Static
Ports 443 used for control channel orchestration
9443 for data transport

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.
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.x.x (expected release beginning of November 2019) 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.x.x (expected release beginning of November 2019) of the Mobility service agent, you need servicing stack update (SSU) and SHA-2 update installed on Windows 2008 SP2 machines. ISHA-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, Windows 8.1, Windows 8 Supported.
Windows 7 with SP1 64-bit Supported from Update rollup 36 (version 9.22 of the Mobility service) onwards.
From version 9.30.x.x (expected release beginning of November 2019) 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.
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 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.
Linux Red Hat Enterprise 5.2 to 5.11
6.1 to 6.10
7.0 to 7.6

Servers running Red Hat Enterprise Linux 5.2-5.11 & 6.1-6.10 do not have Linux Integration Services (LIS) components pre-installed. Ensure to install the components before enabling replication for the machines to boot in Azure.
Linux: CentOS 5.2 to 5.11
6.1 to 6.10
7.0 to 7.6

Servers running CentOS 5.2-5.11 & 6.1-6.10 do not have Linux Integration Services (LIS) components pre-installed. Ensure to install the components before enabling replication for the machines to boot in Azure.
Ubuntu Ubuntu 14.04 LTS server (review supported kernel versions)

Ubuntu 16.04 LTS server (review supported kernel versions)
Debian Debian 7/Debian 8 (review supported kernel versions)
SUSE Linux SUSE Linux Enterprise Server 12 SP1, SP2, SP3, SP4 (review supported kernel versions)
SUSE Linux Enterprise Server 11 SP3, SUSE Linux Enterprise Server 11 SP4
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.
Oracle Linux 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 6.10, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6

Running the Red Hat compatible kernel or Unbreakable Enterprise Kernel Release 3, 4 & 5 (UEK3, UEK4, UEK5)

Ubuntu kernel versions

Supported release Mobility service version Kernel version
14.04 LTS 9.28 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
14.04 LTS 9.27 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
14.04 LTS 9.26 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
14.04 LTS 9.25 3.13.0-24-generic to 3.13.0-169-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-146-generic,
4.15.0-1023-azure to 4.15.0-1042-azure
16.04 LTS 9.28 4.4.0-21-generic to 4.4.0-159-generic,
4.8.0-34-generic to 4.8.0-58-generic,
4.10.0-14-generic to 4.10.0-42-generic,
4.11.0-13-generic to 4.11.0-14-generic,
4.13.0-16-generic to 4.13.0-45-generic,
4.15.0-13-generic to 4.15.0-58-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-1055-azure
16.04 LTS 9.27 4.4.0-21-generic to 4.4.0-154-generic,
4.8.0-34-generic to 4.8.0-58-generic,
4.10.0-14-generic to 4.10.0-42-generic,
4.11.0-13-generic to 4.11.0-14-generic,
4.13.0-16-generic to 4.13.0-45-generic,
4.15.0-13-generic to 4.15.0-54-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-1050-azure
16.04 LTS 9.26 4.4.0-21-generic to 4.4.0-148-generic,
4.8.0-34-generic to 4.8.0-58-generic,
4.10.0-14-generic to 4.10.0-42-generic,
4.11.0-13-generic to 4.11.0-14-generic,
4.13.0-16-generic to 4.13.0-45-generic,
4.15.0-13-generic to 4.15.0-50-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-1045-azure
16.04 LTS 9.25 4.4.0-21-generic to 4.4.0-146-generic,
4.8.0-34-generic to 4.8.0-58-generic,
4.10.0-14-generic to 4.10.0-42-generic,
4.11.0-13-generic to 4.11.0-14-generic,
4.13.0-16-generic to 4.13.0-45-generic,
4.15.0-13-generic to 4.15.0-48-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-1042-azure

Debian kernel versions

Supported release Mobility service version Kernel version
Debian 7 9.25,9.26, 9.27, 9.28 3.2.0-4-amd64 to 3.2.0-6-amd64, 3.16.0-0.bpo.4-amd64
Debian 8 9.28 3.16.0-4-amd64 to 3.16.0-10-amd64, 4.9.0-0.bpo.4-amd64 to 4.9.0-0.bpo.9-amd64
Debian 8 9.27 3.16.0-4-amd64 to 3.16.0-9-amd64, 4.9.0-0.bpo.4-amd64 to 4.9.0-0.bpo.9-amd64
Debian 8 9.25, 9.26 3.16.0-4-amd64 to 3.16.0-8-amd64, 4.9.0-0.bpo.4-amd64 to 4.9.0-0.bpo.8-amd64

SUSE Linux Enterprise Server 12 supported kernel versions

Release Mobility service version Kernel version
SUSE Linux Enterprise Server 12 (SP1,SP2,SP3,SP4) 9.28 SP1 3.12.49-11-default to 3.12.74-60.64.40-default
SP1(LTSS) 3.12.74-60.64.45-default to 3.12.74-60.64.118-default

SP2 4.4.21-69-default to 4.4.120-92.70-default

SP2(LTSS) 4.4.121-92.73-default to 4.4.121-92.117-default

SP3 4.4.73-5-default to 4.4.180-94.100-default

SP3 4.4.138-4.7-azure to 4.4.180-4.31-azure

SP4 4.12.14-94.41-default to 4.12.14-95.29-default
SP4 4.12.14-6.3-azure to 4.12.14-6.23-azure
SUSE Linux Enterprise Server 12 (SP1,SP2,SP3,SP4) 9.27 SP1 3.12.49-11-default to 3.12.74-60.64.40-default
SP1(LTSS) 3.12.74-60.64.45-default to 3.12.74-60.64.115-default

SP2 4.4.21-69-default to 4.4.120-92.70-default

SP2(LTSS) 4.4.121-92.73-default to 4.4.121-92.114-default

SP3 4.4.73-5-default to 4.4.180-94.97-default

SP3 4.4.138-4.7-azure to 4.4.180-4.31-azure

SP4 4.12.14-94.41-default to 4.12.14-95.19-default
SP4 4.12.14-6.3-azure to 4.12.14-6.15-azure
SUSE Linux Enterprise Server 12 (SP1,SP2,SP3,SP4) 9.26 SP1 3.12.49-11-default to 3.12.74-60.64.40-default
SP1(LTSS) 3.12.74-60.64.45-default to 3.12.74-60.64.110-default

SP2 4.4.21-69-default to 4.4.120-92.70-default

SP2(LTSS) 4.4.121-92.73-default to 4.4.121-92.109-default

SP3 4.4.73-5-default to 4.4.178-94.91-default

SP3 4.4.138-4.7-azure to 4.4.178-4.28-azure

SP4 4.12.14-94.41-default to 4.12.14-95.16-default
SP4 4.12.14-6.3-azure to 4.12.14-6.9-azure
SUSE Linux Enterprise Server 12 (SP1,SP2,SP3,SP4) 9.25 SP1 3.12.49-11-default to 3.12.74-60.64.40-default
SP1(LTSS) 3.12.74-60.64.45-default to 3.12.74-60.64.107-default

SP2 4.4.21-69-default to 4.4.120-92.70-default

SP2(LTSS) 4.4.121-92.73-default to 4.4.121-92.104-default

SP3 4.4.73-5-default to 4.4.176-94.88-default

SP3 4.4.138-4.7-azure to 4.4.176-4.25-azure

SP4 4.12.14-94.41-default to 4.12.14-95.13-default
SP4 4.12.14-6.3-azure to 4.12.14-6.9-azure

Linux file systems/guest storage

Component Supported
File systems ext3, ext4, XFS
Volume manager - LVM is supported.
- /boot on LVM is supported from Update Rollup 31 (version 9.20 of the Mobility service) onwards. It isn'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 mustn't be in GPT partition format. This is an Azure architecture limitation. GPT disks are 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

250 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 Supported.
Add disk on replicated VM Not supported.
Disable replication for the VM, add the disk, and then re-enable replication.

Network

Component Supported
Host network NIC Teaming Supported for VMware VMs.

Not supported for 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.

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
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
Guest/server NFS No
Guest/server iSCSI For Migration - Yes
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 TB Yes, disk must be larger than 1024 MB

Up to 8,192 GB when replicating to managed disks (9.26 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

Logical volume management (LVM)
Yes
Guest/server - Storage Spaces No
Guest/server hot add/remove disk No
Guest/server - exclude disk Yes
Guest/server multipath (MPIO) No
Guest/server GPT partitions Five partitions are supported from Update Rollup 37 (version 9.25 of the Mobility service) onwards. Previously four were supported.
ReFS Resilient File System is supported with Mobility service version 9.23 or higher
Guest/server EFI/UEFI boot - Supported when you're running Mobility service version 9.13 or later.
- Supported when migrating VMware VMs or physical servers running Windows Server 2012 or later to Azure.
- You can only replicate VMs for migration. Failback to on-premises isn't supported.
- Only NTFS is supported
- Secure UEFI boot type is not supported.
- Disk sector size should be 512 bytes per physical sector.

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-rest (SSE) Yes
Premium storage 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)

Azure compute

Feature Supported
Availability sets 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 a 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. Check fails if unsupported.
Operating system disk count 1 Check fails if unsupported.
Data disk count 64 or less. Check fails if unsupported.
Data disk size Up to 8,192 GB when replicating to managed disk (9.26 version onwards)
Up to 4,095 GB when replicating to storage account
Check fails if unsupported.
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.
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
Average data churn per VM 25 MB/s
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.

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.