Support matrix for disaster recovery of on-premises Hyper-V VMs to Azure
This article summarizes the supported components and settings for disaster recovery of on-premises Hyper-V VMs to Azure by using Azure Site Recovery.
Supported scenarios
| Scenario | Details |
|---|---|
| Hyper-V with Virtual Machine Manager | You can perform disaster recovery to Azure for VMs running on Hyper-V hosts that are managed in the System Center Virtual Machine Manager fabric. You can deploy this scenario in the Azure portal or by using PowerShell. When Hyper-V hosts are managed by Virtual Machine Manager, you also can perform disaster recovery to a secondary on-premises site. To learn more about this scenario, read this tutorial. |
| Hyper-V without Virtual Machine Manager | You can perform disaster recovery to Azure for VMs running on Hyper-V hosts that aren't managed by Virtual Machine Manager. You can deploy this scenario in the Azure portal or by using PowerShell. |
On-premises servers
| Server | Requirements | Details |
|---|---|---|
| Hyper-V (running without Virtual Machine Manager) | Windows Server 2019, Windows Server 2016 (including server core installation), Windows Server 2012 R2 with latest updates | If you have already configured Windows Server 2012 R2 with/or SCVMM 2012 R2 with Azure Site Recovery and plan to upgrade the OS, please follow the guidance documentation. |
| Hyper-V (running with Virtual Machine Manager) | Virtual Machine Manager 2019, Virtual Machine Manager 2016, Virtual Machine Manager 2012 R2 | If Virtual Machine Manager is used, Windows Server 2019 hosts should be managed in Virtual Machine Manager 2019. Similarly, Windows Server 2016 hosts should be managed in Virtual Machine Manager 2016. |
Replicated VMs
The following table summarizes VM support. Site Recovery supports any workloads running on a supported operating system.
| Component | Details |
|---|---|
| VM configuration | VMs that replicate to Azure must meet Azure requirements. |
| Guest operating system | Any guest OS supported for Azure.. Windows Server 2016 Nano Server isn't supported. |
VM/Disk management
| Action | Details |
|---|---|
| Resize disk on replicated Hyper-V VM | Not supported. Disable replication, make the change, and then reenable replication for the VM. |
| Add disk on replicated Hyper-V VM | Not supported. Disable replication, make the change, and then reenable replication for the VM. |
Hyper-V network configuration
| Component | Hyper-V with Virtual Machine Manager | Hyper-V without Virtual Machine Manager |
|---|---|---|
| Host network: NIC Teaming | Yes | Yes |
| Host network: VLAN | Yes | Yes |
| Host network: IPv4 | Yes | Yes |
| Host network: IPv6 | No | No |
| Guest VM network: NIC Teaming | No | No |
| Guest VM network: IPv4 | Yes | Yes |
| Guest VM network: IPv6 | No | Yes |
| Guest VM network: Static IP (Windows) | Yes | Yes |
| Guest VM network: Static IP (Linux) | No | No |
| Guest VM network: Multi-NIC | Yes | Yes |
Azure VM network configuration (after failover)
| Component | Hyper-V with Virtual Machine Manager | Hyper-V without Virtual Machine Manager |
|---|---|---|
| Azure ExpressRoute | Yes | Yes |
| ILB | Yes | Yes |
| ELB | Yes | Yes |
| Azure Traffic Manager | Yes | Yes |
| Multi-NIC | Yes | Yes |
| Reserved IP | Yes | Yes |
| IPv4 | Yes | Yes |
| Retain source IP address | Yes | Yes |
| Azure Virtual Network service endpoints (without Azure Storage firewalls) |
Yes | Yes |
| Accelerated Networking | No | No |
Hyper-V host storage
| Storage | Hyper-V with Virtual Machine Manager | Hyper-V without Virtual Machine Manager |
|---|---|---|
| NFS | NA | NA |
| SMB 3.0 | Yes | Yes |
| SAN (ISCSI) | Yes | Yes |
| Multi-path (MPIO). Tested with: Microsoft DSM, EMC PowerPath 5.7 SP4 EMC PowerPath DSM for CLARiiON |
Yes | Yes |
Hyper-V VM guest storage
| Storage | Hyper-V with Virtual Machine Manager | Hyper-V without Virtual Machine Manager |
|---|---|---|
| VMDK | NA | NA |
| VHD/VHDX | Yes | Yes |
| Generation 2 VM | Yes | Yes |
| EFI/UEFI | Yes | Yes |
| Shared cluster disk | No | No |
| Encrypted disk | No | No |
| NFS | NA | NA |
| SMB 3.0 | No | No |
| RDM | NA | NA |
| Disk >1 TB | Yes, up to 4,095 GB | Yes, up to 4,095 GB |
| Disk: 4K logical and physical sector | Not supported: Gen 1/Gen 2 | Not supported: Gen 1/Gen 2 |
| Disk: 4K logical and 512 bytes physical sector | Yes | Yes |
| Logical volume management (LVM). LVM is supported on data disks only. Azure provides only a single OS disk. | Yes | Yes |
| Volume with striped disk >1 TB | Yes | Yes |
| Storage Spaces | No | No |
| Hot add/remove disk | No | No |
| Exclude disk | Yes | Yes |
| Multi-path (MPIO) | Yes | Yes |
Azure Storage
| Component | Hyper-V with Virtual Machine Manager | Hyper-V without Virtual Machine Manager |
|---|---|---|
| Locally redundant storage | Yes | Yes |
| Geo-redundant storage | Yes | Yes |
| Read-access geo-redundant storage | Yes | Yes |
| Cool storage | No | No |
| Hot storage | No | No |
| Block blobs | No | No |
| Encryption at rest (SSE) | Yes | Yes |
| Premium storage | Yes | Yes |
| Import/export service | No | No |
| Azure Storage firewalls for virtual networks configured on target storage/cache storage account (used to store replication data) | No | No |
Azure compute features
| Feature | Hyper-V with Virtual Machine Manager | Hyper-V without Virtual Machine Manager |
|---|---|---|
| Availability sets | Yes | Yes |
| HUB | Yes | Yes |
| Managed disks | Yes, for failover. Failback of managed disks isn't supported. |
Yes, for failover. Failback of managed disks isn't supported. |
Azure VM requirements
On-premises VMs that you replicate to Azure must meet the Azure VM requirements summarized in this table.
| Component | Requirements | Details |
|---|---|---|
| Guest operating system | Site Recovery supports all operating systems that are supported by Azure. | Prerequisites check fails if unsupported. |
| Guest operating system architecture | 32-bit (Windows Server 2008)/64-bit | Prerequisites check fails if unsupported. |
| Operating system disk size | Up to 2,048 GB for generation 1 VMs. Up to 300 GB for generation 2 VMs. |
Prerequisites check fails if unsupported. |
| Operating system disk count | 1 | Prerequisites check fails if unsupported. |
| Data disk count | 16 or less | Prerequisites check fails if unsupported. |
| Data disk VHD size | Up to 4,095 GB | Prerequisites check fails if unsupported. |
| Network adapters | Multiple adapters are supported | |
| Shared VHD | Not supported | Prerequisites check fails if unsupported. |
| FC disk | Not supported | Prerequisites check fails if unsupported. |
| Hard disk format | VHD VHDX |
Site Recovery automatically converts VHDX to VHD when you fail over to Azure. When you fail back to on-premises, the virtual machines continue to use the VHDX format. |
| BitLocker | Not supported | BitLocker must be disabled before you enable replication for a VM. |
| VM name | Between 1 and 63 characters. Restricted to letters, numbers, and hyphens. The VM name must start and end with a letter or number. | Update the value in the VM properties in Site Recovery. |
| VM type | Generation 1 Generation 2--Windows |
Generation 2 VMs with an OS disk type of basic (which includes one or two data volumes formatted as VHDX) and less than 300 GB of disk space are supported. Linux Generation 2 VMs aren't supported. Learn more. |
Recovery Services vault actions
| Action | Hyper-V with VMM | Hyper-V without VMM |
|---|---|---|
| Move vault across resource groups Within and across subscriptions |
No | No |
| Move storage, network, Azure VMs across resource groups Within and across subscriptions |
No | No |
Note
When replicating Hyper-VMs from on-premises to Azure, you can replicate to only one AD tenant from one specific environment - Hyper-V site or Hyper-V with VMM as applicable.
Provider and agent
To make sure your deployment is compatible with settings in this article, make sure you're running the latest provider and agent versions.
| Name | Description | Details |
|---|---|---|
| Azure Site Recovery provider | Coordinates communications between on-premises servers and Azure Hyper-V with Virtual Machine Manager: Installed on Virtual Machine Manager servers Hyper-V without Virtual Machine Manager: Installed on Hyper-V hosts |
Latest version: 5.1.2700.1 (available from the Azure portal) Latest features and fixes |
| Microsoft Azure Recovery Services agent | Coordinates replication between Hyper-V VMs and Azure Installed on on-premises Hyper-V servers (with or without Virtual Machine Manager) |
Latest agent available from the portal |
Next steps
Learn how to prepare Azure for disaster recovery of on-premises Hyper-V VMs.
Feedback
Loading feedback...