EEE 2312 tasks

Author: Ankita Dutta

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-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
 ---
@@ -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/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?