Skip to content

Commit 08114cc

Browse files
authored
Merge pull request #296268 from ankitaduttaMSFT/eee
PBI27385183, 24720622, 24660876
2 parents 3e2d964 + 35ad7fa commit 08114cc

File tree

3 files changed

+14
-9
lines changed

3 files changed

+14
-9
lines changed

articles/site-recovery/azure-to-azure-common-questions.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Common questions about Azure virtual machine disaster recovery with Azure
33
description: This article answers common questions about Azure virtual machine disaster recovery when you use Azure Site Recovery.
44
ms.author: ankitadutta
55
author: ankitaduttaMSFT
6-
ms.date: 12/23/2024
6+
ms.date: 03/13/2025
77
ms.topic: faq
88
ms.service: azure-site-recovery
99

@@ -130,6 +130,12 @@ For example, if the apps have three tiers (application/database/web) in differen
130130

131131
No, this is unsupported. If you accidentally move storage accounts to a different resource group and delete the original resource group, then you can create a new resource group with the same name as the old resource group, and then move the storage account to this resource group.
132132

133+
### How can I view a particular zone for target configuration while enabling zonal replication?
134+
135+
The Azure portal displays *logical Zones*. In the datacenter, actual physical zones are mapped to these logical zones, and the mappings vary by subscription. For example, Subscription A's Zone 1 may map to Physical Zone 1, while Subscription B's Zone 1 may map to Physical Zone 2. Therefore, you see different mapped zones for different subscriptions in the same region. In Site Recovery, the source and target zones must have different physical zones.
136+
137+
In case the source and target zones are the same, you can't view zone for target configuration while enabling zonal replication.
138+
133139
## Replication policy
134140

135141
### What is a replication policy?

articles/site-recovery/azure-to-azure-how-to-enable-replication-private-endpoints.md

Lines changed: 5 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: ankitaduttaMSFT
55
ms.author: ankitadutta
66
ms.service: azure-site-recovery
77
ms.topic: how-to
8-
ms.date: 12/23/2024
8+
ms.date: 03/13/2025
99
ms.custom: references_regions, subject-rbac-steps, engagement-fy23
1010
---
1111
# Replicate machines with private endpoints
@@ -186,11 +186,10 @@ following requirements apply:
186186

187187
> [!NOTE]
188188
> If private endpoints are not enabled on storage account, protection would still be successful. However, replication traffic would transit to Azure Site Recovery public endpoints. To ensure replication traffic flows via private links, storage account must be enabled with private endpoints.
189-
190-
> [!NOTE]
191-
> Private endpoint for storage can only be created on a **General Purpose v2** storage accounts. For
192-
> pricing information, see
193-
> [Standard page blob prices](https://azure.microsoft.com/pricing/details/storage/page-blobs/).
189+
>
190+
> Private endpoint for storage can only be created on a **General Purpose v2** storage accounts. For pricing information, see [Standard page blob prices](https://azure.microsoft.com/pricing/details/storage/page-blobs/).
191+
>
192+
> For Cache Storage Account, assigning a Private Endpoint (PE) to the cache storage account and adding a static IP functions correctly if the source machine maintains a network line of sight. This doesn't apply to Site Recovery.
194193
195194
Follow the
196195
[guidance for creation of private storage](../private-link/tutorial-private-endpoint-storage-portal.md#create-storage-account-with-a-private-endpoint)

articles/site-recovery/vmware-azure-architecture-modernized.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: VMware VM disaster recovery architecture in Azure Site Recovery - Moderni
33
description: This article provides an overview of components and architecture used when setting up disaster recovery of on-premises VMware VMs to Azure with Azure Site Recovery - Modernized
44
ms.service: azure-site-recovery
55
ms.topic: concept-article
6-
ms.date: 12/04/2023
6+
ms.date: 03/13/2025
77
ms.author: ankitadutta
88
author: ankitaduttaMSFT
99
---
@@ -37,7 +37,7 @@ The following table and graphic provide a high-level view of the components used
3737
For Site Recovery to work as expected, you need to modify outbound network connectivity to allow your environment to replicate.
3838

3939
> [!NOTE]
40-
> Site Recovery doesn't support using an authentication proxy to control network connectivity.
40+
> Site Recovery modernized architecture supports using an authentication proxy to control network connectivity.
4141
4242
### Outbound connectivity for URLs
4343

0 commit comments

Comments
 (0)