Skip to content

Commit 366187d

Browse files
author
Ankita Dutta
committed
PBI29307506, 31922335, 32178006, 31477685, 31342018, 31087914, 30546856
1 parent b2f20b4 commit 366187d

6 files changed

+35
-9
lines changed

articles/site-recovery/deploy-vmware-azure-replication-appliance-modernized.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -158,6 +158,9 @@ If there are any organizational restrictions, you can manually set up the Site R
158158

159159
By default, an authentication code is generated as highlighted below, in the **Appliance configuration manager** page. Use this code in the authentication tab.
160160

161+
>[!NOTE]
162+
> During Azure Site Recovery modernized appliance deployment, you must use the device code flow for authentication during registration.
163+
161164
- Enter your Microsoft Azure credentials to complete registration.
162165

163166
After successful registration, you can close the tab and move to appliance configuration manager to continue the setup.

articles/site-recovery/how-to-enable-replication-proximity-placement-groups.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: ankitaduttaMSFT
66
ms.topic: how-to
77
ms.service: azure-site-recovery
88
ms.custom: devx-track-azurepowershell
9-
ms.date: 03/21/2025
9+
ms.date: 04/26/2025
1010
---
1111

1212
# Replicate virtual machines running in a proximity placement group to another region
@@ -42,7 +42,9 @@ Site Recovery replicates the data from one Azure region to another region. It br
4242
You can choose to enable replication for a virtual machine through the virtual machine disaster recovery page. Or you can enable replication by going to a pre-created vault, going to the Site Recovery section, and then enabling replication. Let's look at how you can set up Site Recovery virtual machines inside a proximity placement group through both approaches.
4343

4444
> [!NOTE]
45-
> Resource group of the target PPG should be same as that of target virtual machine.
45+
> - Ensure that the target PPG and the target virtual machine are in the same resource group.
46+
>
47+
> - If the VM is also a part of an *Availability Set*, ensure that the availability set, VM, and PPG all reside in the same resource group.
4648
4749
To select a proximity placement group in the DR region while enabling replication through the infrastructure as a service (IaaS) virtual machine DR page:
4850

articles/site-recovery/hyper-v-azure-common-questions.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Common questions for Hyper-V disaster recovery with Azure Site Recovery
33
description: This article summarizes common questions about setting up disaster recovery for on-premises Hyper-V VMs to Azure using the Azure Site Recovery site.
4-
ms.date: 03/27/2025
4+
ms.date: 04/26/2025
55
ms.service: azure-site-recovery
66
ms.topic: overview
77
ms.author: ankitadutta
@@ -78,6 +78,16 @@ Yes. When you create a vault in a region, we ensure that all metadata used by Si
7878
### Does Site Recovery encrypt replication?
7979
Yes, both encryption-in-transit and [encryption in Azure](../storage/common/storage-service-encryption.md) are supported.
8080

81+
### Does backup recovery services agent (MARS) installation on Hyper-V host impact the replication?
82+
83+
84+
Without VMM, the Azure Site Recovery provider and Recovery Services agent are installed on each Hyper-V host.
85+
86+
With VMM, the Recovery Services agent is installed on each Hyper-V host, while the Azure Site Recovery Provider runs on the VMM server.
87+
88+
> [!IMPORTANT]
89+
> Installing the Recovery Services agent designed for Microsoft Azure Backup (MARS) is not supported. Ensure you install the correct version of the Recovery Services agent specifically tailored for Azure Site Recovery.
90+
8191

8292
## Deployment
8393

articles/site-recovery/site-recovery-deployment-planner.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
55
ms.service: azure-site-recovery
66
ms.topic: concept-article
77
ms.author: ankitadutta
8-
ms.date: 03/31/2025
8+
ms.date: 04/26/2025
99
---
1010

1111
# About the Azure Site Recovery Deployment Planner for VMware to Azure
@@ -63,7 +63,10 @@ The tool provides the following details:
6363
| Supported configuration|vCenter Server, ESXi| Hyper-V cluster, Hyper-V host|NA|Hyper-V cluster, Hyper-V host|NA |
6464
| Number of servers that can be profiled per running instance of Site Recovery Deployment Planner |Single (VMs belonging to one vCenter Server or one ESXi server can be profiled at a time)|Multiple (VMs across multiple hosts or host clusters can be profiled at a time)| NA |Multiple (VMs across multiple hosts or host clusters can be profiled at a time)| NA |
6565

66-
*The tool is primarily for the Hyper-V to Azure disaster recovery scenario. For Hyper-V to secondary site disaster recovery, it can be used only to understand source-side recommendations like required network bandwidth, required free storage space on each of the source Hyper-V servers, and initial replication batching numbers and batch definitions. Ignore the Azure recommendations and costs from the report. Also, the Get Throughput operation is not applicable for the Hyper-V-to-secondary-site disaster recovery scenario.
66+
The tool supports Hyper-V to Azure disaster recovery scenarios. For Hyper-V to secondary site disaster recovery, use the tool only to obtain source-side recommendations, such as required network bandwidth, required free storage space on each source Hyper-V server, and initial replication batch sizes and definitions. Ignore Azure recommendations and costs in the report. The Get Throughput operation doesn't apply to the Hyper-V to secondary site disaster recovery scenario.
67+
68+
> [!NOTE]
69+
> The Azure Site Recovery Deployment Planner doesn't support OfferID MS-AZR-0017P.
6770
6871
## Prerequisites
6972

articles/site-recovery/vmware-azure-set-up-replication-tutorial-modernized.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Set up VMware VM disaster recovery to Azure with Azure Site Recovery - Mo
33
description: Learn how to set up disaster recovery to Azure for on-premises VMware VMs with Azure Site Recovery - Modernized.
44
ms.service: azure-site-recovery
55
ms.topic: tutorial
6-
ms.date: 04/03/2025
6+
ms.date: 04/26/2025
77
ms.custom: MVC
88
ms.author: ankitadutta
99
author: ankitaduttaMSFT
@@ -44,7 +44,7 @@ To create and register the Azure Site Recovery replication appliance, you need a
4444

4545
- Contributor or Owner permissions on the Azure subscription.
4646
- Permissions to register Microsoft Entra apps.
47-
- Owner or Contributor and User Access Administrator permissions on the Azure subscription to create a Key Vault, used during agentless VMware migration.
47+
4848

4949
If you just created a free Azure account, you're the owner of your subscription. If you're not the subscription owner, work with the owner for the required permissions.
5050

articles/site-recovery/vmware-azure-set-up-source.md

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
55
ms.service: azure-site-recovery
66
ms.topic: how-to
77
ms.author: ankitadutta
8-
ms.date: 07/08/2024
8+
ms.date: 04/26/2025
99

1010
---
1111

@@ -79,7 +79,7 @@ Exclude following folders from Antivirus software
7979

8080
### If Antivirus Software is active on the Linux Master Target
8181

82-
Exclude following folders from Antivirus software
82+
Exclude following folders from Antivirus software:
8383

8484
1. /usr/local/ASR
8585
2. /usr/local/InMage
@@ -89,6 +89,14 @@ Exclude following folders from Antivirus software
8989
6. /var/log/ASRsetuptelemetry
9090
7. /var/log/ASRsetuptelemetry_uploaded
9191

92+
Exclude the following registries from Antivirus software:
93+
94+
1. HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SV Systems
95+
1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Azure Site Recovery\Registration
96+
1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Azure Site Recovery\ProxySettings
97+
1. HKEY_LOCAL_MACHINE\SOFTWARE\InMage Systems
98+
1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure Backup\Config\InMageMT
99+
92100

93101
## Next steps
94102
[Set up your target environment](./vmware-azure-set-up-target.md)

0 commit comments

Comments
 (0)