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/azure-to-azure-common-questions.md
+7-1Lines changed: 7 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Common questions about Azure virtual machine disaster recovery with Azure
3
3
description: This article answers common questions about Azure virtual machine disaster recovery when you use Azure Site Recovery.
4
4
ms.author: ankitadutta
5
5
author: ankitaduttaMSFT
6
-
ms.date: 03/13/2025
6
+
ms.date: 05/11/2025
7
7
ms.topic: faq
8
8
ms.service: azure-site-recovery
9
9
@@ -137,6 +137,12 @@ The Azure portal displays *logical Zones*. In the datacenter, actual physical zo
137
137
138
138
In case the source and target zones are the same, you can't view zone for target configuration while enabling zonal replication.
139
139
140
+
### Can I choose a different name for my recovery services vault automation instead of using the existing one?
141
+
142
+
When you replicate a new VM and specify a new Automation Account name, the vault updates to use this new Automation Account at the vault level. This updated name appears in the vault under **Recovery Services Vault** > **Site Recovery Infrastructure** > **Extension Update Settings**.
143
+
144
+
Azure Site Recovery uses this new Automation Account to manage the site recovery extension on all replicated VMs.
@@ -56,7 +56,7 @@ A recovery services vault is an entity that contains the replication information
56
56
used to trigger Site Recovery operations. For more information, see
57
57
[Create a Recovery Services vault](./azure-to-azure-tutorial-enable-replication.md#create-a-recovery-services-vault).
58
58
59
-
## Enable the managed identity for the vault.
59
+
## Enable the managed identity for the vault
60
60
61
61
A [managed identity](../active-directory/managed-identities-azure-resources/overview.md) allow the
62
62
vault to gain access to the customer's storage accounts. Site Recovery needs to access the source
@@ -67,6 +67,9 @@ Managed identity access is essential when you're using private links service for
67
67
68
68
:::image type="content" source="./media/azure-to-azure-how-to-enable-replication-private-endpoints/enable-managed-identity-in-vault.png" alt-text="Shows the Azure portal and the Recovery Services page.":::
69
69
70
+
> [!NOTE]
71
+
> System assigned and User assigned managed identity is supported for Recovery Services vault.
72
+
70
73
1. Change the **Status** to _On_ and select **Save**.
71
74
72
75
1. An **Object ID** is generated indicating that the vault is now registered with Azure Active
Copy file name to clipboardExpand all lines: articles/site-recovery/azure-to-azure-support-matrix.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Support matrix for Azure VM disaster recovery with Azure Site Recovery
3
3
description: Summarizes support for Azure VMs disaster recovery to a secondary region with Azure Site Recovery.
4
4
ms.topic: concept-article
5
-
ms.date: 04/07/2025
5
+
ms.date: 05/11/2025
6
6
ms.service: azure-site-recovery
7
7
author: ankitaduttaMSFT
8
8
ms.author: ankitadutta
@@ -139,6 +139,8 @@ Rocky Linux | [See supported versions](#supported-rocky-linux-kernel-versions-fo
139
139
140
140
> [!NOTE]
141
141
> For Linux versions, Azure Site Recovery doesn't support custom OS kernels. Only the stock kernels that are part of the distribution minor version release/update are supported.
142
+
>
143
+
> VMs created on ARM64 CPU architecture aren't supported by Azure Site Recovery.
142
144
143
145
> [!NOTE]
144
146
> To support latest Linux kernels within 15 days of release, Azure Site Recovery rolls out hot fix patch on top of latest mobility agent version. This fix is rolled out in between two major version releases. To update to latest version of mobility agent (including hot fix patch), follow steps mentioned in [this article](service-updates-how-to.md#azure-vm-disaster-recovery-to-azure). This patch is currently rolled out for mobility agents used in Azure to Azure DR scenario.
@@ -447,6 +449,7 @@ Internal Load balancer | Supported | Associate the preconfigured load balancer u
447
449
Public IP address | Supported | Associate an existing public IP address with the NIC. Or, create a public IP address and associate it with the NIC using an Azure Automation script in a recovery plan.
448
450
NSG on NIC | Supported | Associate the NSG with the NIC using an Azure Automation script in a recovery plan.
449
451
NSG on subnet | Supported | Associate the NSG with the subnet using an Azure Automation script in a recovery plan.
452
+
ASG | Unsupported | Azure Site Recovery doesn't support ASGs.
450
453
Reserved (static) IP address | Supported | If the NIC on the source VM has a static IP address, and the target subnet has the same IP address available, it's assigned to the failed over VM.<br/><br/> If the target subnet doesn't have the same IP address available, one of the available IP addresses in the subnet is reserved for the VM.<br/><br/> You can also specify a fixed IP address and subnet in **Replicated items** > **Settings** > **Network** > **Network interfaces**.
451
454
Dynamic IP address | Supported | If the NIC on the source has dynamic IP addressing, the NIC on the failed over VM is also dynamic by default.<br/><br/> You can modify this to a fixed IP address if required.
452
455
Multiple IP addresses | Supported | When you fail over a VM that has a NIC with multiple IP addresses, only the primary IP address of the NIC in the source region is kept by default. To failover Secondary IP Configurations, go to the **Network** blade and configure them. <br> This is supported only for region replication, zone to zone replication isn't supported.
Copy file name to clipboardExpand all lines: articles/site-recovery/hybrid-how-to-enable-replication-private-endpoints.md
+2-10Lines changed: 2 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
5
5
ms.author: ankitadutta
6
6
ms.service: azure-site-recovery
7
7
ms.topic: how-to
8
-
ms.date: 12/19/2024
8
+
ms.date: 05/11/2025
9
9
ms.custom: subject-rbac-steps, engagement-fy23
10
10
---
11
11
# Replicate on-premises machines by using private endpoints
@@ -17,15 +17,6 @@ a recovery vault is supported in all Azure Commercial & Government regions.
17
17
>[!Note]
18
18
>Automatic upgrades are not supported for Private Endpoints. [Learn more](upgrade-mobility-service-modernized.md).
19
19
20
-
In this tutorial, you learn how to:
21
-
22
-
> [!div class="checklist"]
23
-
> * Create an Azure Backup Recovery Services vault to protect your machines.
24
-
> * Enable a managed identity for the vault. Grant the permissions required to access the storage accounts to enable replication of traffic from on-premises to Azure target locations. Managed identity access for storage is required for Private Link access to the vault.
25
-
> * Make DNS changes that are required for private endpoints.
26
-
> * Create and approve private endpoints for a vault inside a virtual network.
27
-
> * Create private endpoints for the storage accounts. You can continue to allow public or firewalled access for storage as needed. Creating a private endpoint to access storage isn't required for Azure Site Recovery.
28
-
29
20
30
21
The following diagram shows the replication workflow for hybrid disaster
31
22
recovery with private endpoints. You can't create private endpoints in your on-premises network. To use private links, you need to create an Azure virtual network (called a *bypass network* in this article), establish private connectivity between on-premises and the bypass network, and
@@ -39,6 +30,7 @@ then create private endpoints in the bypass network. You can choose any form of
39
30
40
31
- Private links are supported in Site Recovery 9.35 and later.
41
32
- You can create private endpoints only for new Recovery Services vaults that don't have any items registered to them. Therefore, you must create private endpoints before any items are added to the vault. See [Azure Private Link pricing](https://azure.microsoft.com/pricing/details/private-link/) for pricing information.
33
+
- Private endpoint for Recovery Services only supports dynamic IP addresses. Static IP addresses are not supported.
42
34
- When you create a private endpoint for a vault, the vault is locked down. It can be accessed only from networks that have private endpoints.
43
35
- Microsoft Entra ID doesn't currently support private endpoints. So you need to allow outbound access from the secured Azure virtual network to IPs and fully qualified domain names that are required for Microsoft Entra ID to work in a region. As applicable, you can also use network security group tag "Microsoft Entra ID" and Azure Firewall tags to allow access to Microsoft Entra ID.
44
36
- Five IP addresses are required in the bypass network where you create your private endpoint. When you create a private endpoint for the vault, Site Recovery creates five private links for access to its microservices.
0 commit comments