Merge pull request #292323 from ankitaduttaMSFT/eeeasr

EEE 2312 tasks

Author: prmerger-automator[bot]

articles/site-recovery/azure-to-azure-architecture.md

@@ -3,19 +3,16 @@ title: Azure to Azure disaster recovery architecture in Azure Site Recovery
 description: Overview of the architecture used when you set up disaster recovery between Azure regions for Azure VMs, using the Azure Site Recovery service.
 ms.service: azure-site-recovery
 ms.topic: concept-article
-ms.date: 02/29/2024
+ms.date: 12/23/2024
 ms.author: ankitadutta
 author: ankitaduttaMSFT
 ---
 
-
 # Azure to Azure disaster recovery architecture
 
-
 This article describes the architecture, components, and processes used when you deploy disaster recovery for Azure virtual machines (VMs)  using the [Azure Site Recovery](site-recovery-overview.md) service. With disaster recovery setup, Azure VMs continuously replicate to a different target region. If an outage occurs, you can fail over VMs to the secondary region, and access them from there. When everything's running normally again, you can fail back and continue working in the primary location.
 
 
-
 ## Architectural components
 
 The components involved in disaster recovery for Azure VMs are summarized in the following table.

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

@@ -3,7 +3,7 @@ title: Common questions about Azure virtual machine disaster recovery with Azure
 description: This article answers common questions about Azure virtual machine disaster recovery when you use Azure Site Recovery.
 ms.author: ankitadutta
 author: ankitaduttaMSFT
-ms.date: 11/25/2024
+ms.date: 12/23/2024
 ms.topic: faq
 ms.service: azure-site-recovery
 
@@ -295,6 +295,12 @@ You can start failover. Site Recovery doesn't need connectivity from the primary
 
 Site Recovery has an RTO SLA of [one hours](https://azure.microsoft.com/support/legal/sla/site-recovery/v1_2/). Most of the time, Site Recovery fails over virtual machines within minutes. To calculate the RTO, review the failover job, which shows the time it took to bring up a virtual machine.
 
+### Are the extensions replicated to failover VM in target region? 
+
+Extensions aren't replicated to the failover VM in the target region, so we need to install them manually after failover.
+
+**For SQL VM zonal replication:** In the case of a SQL VM, it'll not be shown if we don't have the corresponding IaaS SQL Extension installed. After installing the `SqlIaasExtension`, the `SQL virtual machine` is created automatically. [Learn more](https://learn.microsoft.com/azure/azure-sql/virtual-machines/windows/sql-agent-extension-manually-register-single-vm?view=azuresql&tabs=azure-powershell#register-with-extension).
+
 ## Recovery plans
 
 ### What's a recovery plan?
@@ -352,6 +358,12 @@ While Site Recovery makes a best effort to ensure that capacity is available in
 
 Yes, you can purchase [reserved Azure virtual machines](https://azure.microsoft.com/pricing/reserved-vm-instances/) in the disaster recovery region, and Site Recovery failover operations use them. No additional configuration is needed.
 
+### Where do we see the VM mapping to the reservation group when we enable capacity reservation for our VMs in ASR on the target region?
+
+When we enable capacity reservation for our VMs in Azure Site Recovery on the target region, the VM maps to the reservation group during replication. Since the target VM is not created until a test failover or actual failover is performed, we see the mapping under *Recovery Services Vault* > **Compute** > **Capacity Reservation** settings.
+
+The VM associated option under the capacity reservation group populates only when the target VMs are created during a test failover or actual failover. [Learn more](https://learn.microsoft.com/azure/virtual-machines/capacity-reservation-overview#capacity-reservation-lifecycle).
+
 ## Security
 
 ### Is replication data sent to the Site Recovery service?

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

@@ -5,15 +5,12 @@ author: ankitaduttaMSFT
 ms.author: ankitadutta
 ms.service: azure-site-recovery
 ms.topic: how-to
-ms.date: 09/03/2024
+ms.date: 12/23/2024
 ms.custom: references_regions, subject-rbac-steps, engagement-fy23
 ---
 # Replicate machines with private endpoints
 
-Azure Site Recovery allows you to use
-[Azure Private Link](../private-link/private-endpoint-overview.md) private endpoints for replicating
-your machines from inside an isolated virtual network. Private endpoint access to
-a recovery vault is supported in all Azure Commercial & Government regions.
+Azure Site Recovery allows you to use [Azure Private Link](../private-link/private-endpoint-overview.md) private endpoints for replicating your machines from inside an isolated virtual network. Private endpoint access to a recovery vault is supported in all Azure Commercial & Government regions.
 
 This article provides instructions for you to perform the following steps:
 
@@ -27,7 +24,7 @@ This article provides instructions for you to perform the following steps:
   access for storage as needed. Creation of a private endpoint for accessing storage isn't mandatory
   for Azure Site Recovery.
 
-Below is a reference architecture on how the replication workflow changes with private endpoints.
+Following is a reference architecture on how the replication workflow changes with private endpoints.
 
 :::image type="content" source="./media/azure-to-azure-how-to-enable-replication-private-endpoints/architecture.png" alt-text="Reference architecture for Site Recovery with private endpoints.":::
 
@@ -44,7 +41,7 @@ Below is a reference architecture on how the replication workflow changes with p
   outbound access from the secured network. You can also use network security group tag "Azure
   Active Directory" and Azure Firewall tags for allowing access to Microsoft Entra ID, as
   applicable.
-- **At least seven IP addresses are required** in the subnets of both your source machines and your
+- **At least nine IP addresses are required** in the subnets of both your source machines and your
   recovery machines. When you create a private endpoint for the vault, Site Recovery creates five
   private links for access to its microservices. Further, when you enable the replication, it adds
   two additional private links for the source and target region pairing.

articles/site-recovery/azure-to-azure-how-to-enable-zone-to-zone-disaster-recovery.md

@@ -2,10 +2,9 @@
 title: Enable zone-to-zone disaster recovery for Azure virtual machines
 description: This article describes when and how to use zone-to-zone disaster recovery for Azure virtual machines.
 author: ankitaduttaMSFT
-manager: aravindang
 ms.service: azure-site-recovery
 ms.topic: tutorial
-ms.date: 10/28/2024
+ms.date: 12/23/2024
 ms.author: ankitadutta
 ms.custom: references_regions
 ---
@@ -44,7 +43,7 @@ Learn more about [Azure regions with availability zones](../reliability/availabi
 > [!NOTE]
 > Zone-to-zone disaster recovery isn't supported for VMs that have managed disks via zone-redundant storage (ZRS).
 >
->Regions that don't support Azure availability zones also don't support Azure Site Recovery zone-to-zone replication. For Azure Site Recovery zone-to-zone replication to work, the region must support availability zones.
+> Regions that don't support Azure availability zones also don't support Azure Site Recovery zone-to-zone replication. For Azure Site Recovery zone-to-zone replication to work, the region must support availability zones.
 
 ## Using availability zones for disaster recovery
 
@@ -119,7 +118,7 @@ Pricing for zone-to-zone disaster recovery is identical to the pricing for Azure
 The egress charges in zone-to-zone disaster recovery are lower than the egress charges in region-to-region disaster recovery. For information about data transfer charges between availability zones, see the [bandwidth pricing page](https://azure.microsoft.com/pricing/details/bandwidth/).
 
 **What is the SLA for RTO and RPO?**
-The service-level agreement (SLA) for recovery time objective (RTO) is the same as the SLA for Site Recovery overall. We promise an RTO of up to two hours. There's no defined SLA for RPO.
+The service-level agreement (SLA) for recovery time objective (RTO) is the same as the SLA for Site Recovery overall. We promise an RTO of up to one hour. There's no defined SLA for RPO. 
 
 **Is capacity guaranteed in the secondary zone?**
 The Site Recovery team and the Azure capacity management team plan for sufficient infrastructure capacity. When you start a failover, the teams also help ensure that VM instances protected by Site Recovery deploy to the target zone. For more FAQs on capacity, check the [common questions about Azure-to-Azure disaster recovery](./azure-to-azure-common-questions.md#capacity).

articles/site-recovery/azure-to-azure-how-to-reprotect.md

@@ -104,11 +104,7 @@ Let's take the example from the following screenshot, where Enable Replication f
 
    :::image type="content" source="./media/site-recovery-how-to-reprotect-azure-to-azure/estimated-reprotection.png" alt-text="Screenshot displays example duration of reprotection of a virtual machine on the Azure portal." lightbox="./media/site-recovery-how-to-reprotect-azure-to-azure/estimated-reprotection.png":::
 
-The above is a simple illustration of how to estimate the reprotection time. 
-
-When the virtual machine is re-protected from disaster recovery region to primary region (that is, after failing over from the primary region to disaster recovery region), the target virtual machine (original source virtual machine), and associated NIC(s) are deleted.
-
-However, when the virtual machine is re-protected again from the primary region to disaster recovery region after failback, we do not delete the virtual machine and associated NIC(s) in the disaster recovery region that were created during the earlier failover.
+The above is a simple illustration of how to estimate the reprotection time. When customer failover to target region and reprotect, the source virtual machine and associated resources are **not deleted**. When customer *failback* to primary region and reprotect, the VM (in the target / disaster recovery region) and associated resources are then deleted. 
 
 ## Next steps
 

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

@@ -210,16 +210,29 @@ Site Recovery generates crash-consistent recovery points every 5 minutes.
 
 ### Can I change an already replicating machine from one to another Recovery Services vault?
 
-Switching Recovery Services vaults, when the replication is already ongoing, isn't supported. To do so, replication needs to be disabled and enabled again. Additionally, the mobility service agent, installed on the source machine, will need to be unconfigured so that it can be configured to a new vault. Use the below commands to perform the unregistration - 
+Switching Recovery Services vaults, when the replication is already ongoing, isn't supported. To do so, replication needs to be disabled and enabled again. Additionally, the mobility service agent, installed on the source machine, must be un-configured so that it can be configured to a new vault. Use the following commands to perform the unregistration:
 
-For Windows machines - 
+*For Windows machines:*
 
 `C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\UnifiedAgentConfigurator.exe /Unconfigure true`
 
-For Linux machines - 
+*For Linux machines:*
 
 `/usr/local/ASR/Vx/bin/UnifiedAgentConfigurator.sh -q -U true -c CSPrime`
 
+### Can I change an already replicating machine from one region to another region? 
+
+Switching region, when the replication is already ongoing isn't supported. To do so, replication needs to be disabled and enabled again. Additionally, to avoid reboot there is no need to uninstall the mobility agent, mobility agent installed on the source machine, must be un-configured using the commands mentioned. Use the following commands to perform the unregistration:
+
+*For Windows machines:*
+
+`C:\Program Files (x86)\Microsoft Azure Site Recovery\agent\UnifiedAgentConfigurator.exe /Unconfigure true`
+
+*For Linux machines:*
+
+`/usr/local/ASR/Vx/bin/UnifiedAgentConfigurator.sh -q -U true -c CSPrime`
+
+
 ## Component upgrade
 
 ### My version of the Mobility services agent or configuration server is old, and my upgrade failed. What do I do?