You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/site-recovery/hyper-v-azure-support-matrix.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: rayne-wiselman
5
5
manager: carmonm
6
6
ms.service: site-recovery
7
7
ms.topic: conceptual
8
-
ms.date: 1/10/2020
8
+
ms.date: 1/27/2020
9
9
ms.author: raynew
10
10
---
11
11
@@ -29,7 +29,7 @@ Hyper-V without Virtual Machine Manager | You can perform disaster recovery to A
29
29
**Server** | **Requirements** | **Details**
30
30
--- | --- | ---
31
31
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.](upgrade-2012R2-to-2016.md)
32
-
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.<br/><br/>
32
+
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.<br/><br/> Note: Failback to alternate location is not supported for Windows Server 2019 hosts.
33
33
34
34
35
35
## Replicated VMs
@@ -47,8 +47,8 @@ Guest operating system | Any guest OS [supported for Azure](https://docs.microso
47
47
48
48
**Action** | **Details**
49
49
--- | ---
50
-
Resize disk on replicated Hyper-V VM | Not supported. Disable replication, make the change, and then reenable replication for the VM.
51
-
Add disk on replicated Hyper-V VM | Not supported. Disable replication, make the change, and then reenable replication for the VM.
50
+
Resize disk on replicated Hyper-V VM | Not supported. Disable replication, make the change, and then re-enable replication for the VM.
51
+
Add disk on replicated Hyper-V VM | Not supported. Disable replication, make the change, and then re-enable replication for the VM.
52
52
53
53
## Hyper-V network configuration
54
54
@@ -107,7 +107,7 @@ SMB 3.0 | No | No
107
107
RDM | NA | NA
108
108
Disk >1 TB | Yes, up to 4,095 GB | Yes, up to 4,095 GB
109
109
Disk: 4K logical and physical sector | Not supported: Gen 1/Gen 2 | Not supported: Gen 1/Gen 2
Logical volume management (LVM). LVM is supported on data disks only. Azure provides only a single OS disk. | Yes | Yes
112
112
Volume with striped disk >1 TB | Yes | Yes
113
113
Storage Spaces | No | No
@@ -128,9 +128,9 @@ Block blobs | No | No
128
128
Encryption at rest (SSE)| Yes | Yes
129
129
Encryption at rest (CMK) <br></br> (Only for failover to managed disks)| Yes (via PowerShell Az 3.3.0 module onwards) | Yes (via PowerShell Az 3.3.0 module onwards)
130
130
Premium storage | Yes | Yes
131
-
Import/export service | No | No
132
-
Azure storage accounts with firewall enabled | Yes. For target storage and cache. | Yes. For target storage and cache.
133
-
Modify storage account | No. The target Azure storage account can't be modified after enabling replication. To modify, disable and then reenable disaster recovery. | No
131
+
Import/Export service | No | No
132
+
Azure Storage accounts with firewall enabled | Yes. For target storage and cache. | Yes. For target storage and cache.
133
+
Modify storage account | No. The target Azure Storage account can't be modified after enabling replication. To modify, disable and then re-enable disaster recovery. | No
0 commit comments