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
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Support for disaster recovery of Hyper-V VMs to Azure with Azure Site Rec
3
3
description: Summarizes the supported components and requirements for Hyper-V VM disaster recovery to Azure with Azure Site Recovery
4
4
ms.service: azure-site-recovery
5
5
ms.topic: concept-article
6
-
ms.date: 10/28/2024
6
+
ms.date: 12/19/2024
7
7
author: ankitaduttaMSFT
8
8
ms.author: ankitadutta
9
9
---
@@ -20,7 +20,7 @@ This article summarizes the supported components and settings for disaster recov
20
20
21
21
**Scenario** | **Details**
22
22
--- | ---
23
-
Hyper-V with Virtual Machine Manager <br> <br>| 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.<br/><br/> You can deploy this scenario in the Azure portal or by using PowerShell.<br/><br/> 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-vmm-disaster-recovery.md).
23
+
Hyper-V with Virtual Machine Manager <br> <br>| 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.<br/><br/> You can deploy this scenario in the Azure portal or by using PowerShell.<br/><br/> 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-vmm-azure-tutorial.md).
24
24
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.<br/><br/> You can deploy this scenario in the Azure portal or by using PowerShell.
25
25
26
26
> [!NOTE]
@@ -44,7 +44,7 @@ The following table summarizes VM support. Site Recovery supports any workloads
44
44
**Component** | **Details**
45
45
--- | ---
46
46
VM configuration | VMs that replicate to Azure must meet [Azure requirements](#azure-vm-requirements).
47
-
Guest operating system | Any guest OS [supported for Azure](../cloud-services/cloud-services-guestos-update-matrix.md#family-5-releases)..<br/><br/> Windows Server 2016 Nano Server isn't supported.
47
+
Guest operating system | Any guest OS [supported for Azure](https://learn.microsoft.com/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc794868%28v=ws.10%29#supported-guest-operating-systems). <br/><br/> Windows Server 2016 Nano Server isn't supported.
48
48
49
49
50
50
## VM/Disk management
@@ -200,4 +200,5 @@ Azure Site Recovery provider | Coordinates communications between on-premises se
200
200
Microsoft Azure Recovery Services agent | Coordinates replication between Hyper-V VMs and Azure<br/><br/> Installed on on-premises Hyper-V servers (with or without Virtual Machine Manager) | Latest agent available from the portal
201
201
202
202
## Next steps
203
-
Learn how to [prepare Azure](tutorial-prepare-azure.md) for disaster recovery of on-premises Hyper-V VMs.
203
+
204
+
Learn how to [prepare Azure](tutorial-prepare-azure-for-hyperv.md) for disaster recovery of on-premises Hyper-V VMs.
Copy file name to clipboardExpand all lines: articles/site-recovery/vmware-azure-enable-replication.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,14 @@
1
1
---
2
-
title: Enable VMware VMs for disaster recovery using Azure Site Recovery
3
-
description: This article describes how to enable VMware VM replication for disaster recovery using the Azure Site Recovery service
2
+
title: Enable VMware VMs (Modernized) for disaster recovery using Azure Site Recovery
3
+
description: This article describes how to enable VMware VM replication for disaster recovery using the Azure Site Recovery service.
4
4
author: ankitaduttaMSFT
5
5
ms.service: azure-site-recovery
6
6
ms.topic: how-to
7
7
ms.author: ankitadutta
8
-
ms.date: 09/24/2024
8
+
ms.date: 12/19/2024
9
9
---
10
10
11
-
# Enable replication to Azure for VMware VMs
11
+
# Enable replication to Azure for VMware VMs - Modernized
12
12
13
13
This article describes how to enable replication of on-premises VMware virtual machines (VM) to Azure.
14
14
@@ -56,7 +56,7 @@ To enable replication, follow these steps:
56
56
1. In the **Source** page > **Source**, select the configuration server.
57
57
1. For **Machine type**, select **Virtual Machines** or **Physical Machines**.
58
58
1. In **vCenter/vSphere Hypervisor**, select the vCenter server that manages the vSphere host, or select the host. This setting isn't relevant if you're replicating physical computers.
59
-
1. Select the process server. If there are no additional process servers created, the inbuilt process server of configuration server will be available in the dropdown menu. The health status of each process server is indicated as per recommended limits and other parameters. Choose a healthy process server. A [critical](vmware-physical-azure-monitor-process-server.md#process-server-alerts)process server can't be chosen. You can either [troubleshoot and resolve](vmware-physical-azure-troubleshoot-process-server.md) the errors **or** set up a [scale-out process server](vmware-azure-set-up-process-server-scale.md).
59
+
1. Select the process server. If there are no additional process servers created, the inbuilt process server of configuration server will be available in the dropdown menu. The health status of each process server is indicated as per recommended limits and other parameters. Choose a healthy process server. A [critical](vmware-physical-azure-monitor-process-server.md#process-server-alerts)appliance can't be chosen. You can either [troubleshoot and resolve](vmware-physical-azure-troubleshoot-process-server.md) the errors **or** set up a [scale-out process server](vmware-azure-set-up-process-server-scale.md).
0 commit comments