new doc

Author: Ankita Dutta

articles/site-recovery/tutorial-replicate-vms-edge-zone-to-azure-region.md

@@ -4,7 +4,7 @@ description: This article describes how to replicate, failover, and failback Azu
 author: ankitaduttaMSFT
 ms.service: azure-site-recovery
 ms.topic: tutorial
-ms.date: 12/11/2024
+ms.date: 12/18/2024
 ms.author: ankitadutta
 
 ---
@@ -13,6 +13,9 @@ ms.author: ankitadutta
 
 This article describes how to replicate, failover, and failback Azure virtual machines (VMs) running on an Azure Extended Zone to its parent Azure region.
 
+> [!IMPORTANT]
+> The Azure Site Recovery functionality for Extended Zones is in preview state.
+
 ## Disaster recovery in Azure Extended Zone 
 
 Site Recovery ensures business continuity by keeping workloads running during outages by continuously replicating the workload from a primary to a secondary location. The ASR functionality for Extended Zones is in preview. 

articles/site-recovery/tutorial-replicate-vms-extended-zones-to-another-zone.md

@@ -1,28 +1,29 @@
 ---
-title: Set up disaster recovery to another Public MEC using PowerShell
-description: This article describes how to replicate, failover, and failback Azure virtual machines (VMs) running an Azure Public MEC (in preview for ASR functionality) to another Public MEC connected to the same parent region.
+title: Set up disaster recovery to another Extended Zones using PowerShell
+description: This article describes how to replicate, failover, and failback Azure virtual machines (VMs) running an Azure Extended Zone (in preview for ASR functionality) to another Extended Zone connected to the same parent region.
 author: ankitaduttaMSFT
 ms.service: azure-site-recovery
 ms.topic: tutorial
-ms.date: 12/14/2022
+ms.date: 12/18/2024
 ms.author: ankitadutta
 ---
 
-# Replicate virtual machines running in an Azure Public MEC to another Azure Public MEC in the same region 
+# Replicate virtual machines running in an Azure Extended Zones to another Azure Extended Zones in the same region 
 
 > [!IMPORTANT]
-> The Azure Site Recovery functionality for Public MEC is in preview state.
-This article describes how to replicate, failover, and failback Azure virtual machines (VMs) running an Azure Public MEC to another Azure Public MEC connected to the same parent region. 
+> The Azure Site Recovery functionality for Extended Zones is in preview state.
 
-Azure Public MECs are fully managed solution deployed close to your data center and includes hardware, services, and support. 
+This article describes how to replicate, failover, and failback Azure virtual machines (VMs) running an Azure Extended Zones to another Azure Extended Zones connected to the same parent region. 
 
-## Disaster recovery in Azure Public MEC 
+Azure Extended Zones are fully managed solution deployed close to your data center and includes hardware, services, and support. 
+
+## Disaster recovery in Azure Extended Zones 
 
 Site Recovery ensures business continuity by keeping workloads running during outages by continuously replicating the workload from primary to secondary location. The ASR functionality for MEC is in preview. 
 
-Here the primary location is an Azure Public MEC and secondary location is another Azure Public MEC connected to the same parent region. 
+Here the primary location is an Azure Extended Zones and secondary location is another Azure Extended Zones connected to the same parent region. 
 
-## Set up disaster recovery for VMs in an Azure Public MEC using PowerShell
+## Set up disaster recovery for VMs in an Azure Extended Zones using PowerShell
 
 ### Prerequisites
 
@@ -32,34 +33,43 @@ Here the primary location is an Azure Public MEC and secondary location is anoth
     ```
     Get-InstalledModule -Name Az
     ```
+
 - Ensure the Linux distro version and kernel is supported by Azure Site Recovery. For more information, see the [support matrix](./azure-to-azure-support-matrix.md#linux).
 - Ensure the primary VM has a public IP. To validate, go to the VM NIC and check if public IP is attached to the NIC. Ensure that recovery VM has a public IP when you switch to protection direction. 
+
     >[!Note]
     >Azure Site Recovery doesn’t re-create the public IP, so it's important to check the availability of the public IP and that it is attached to the NIC before you switch to protection direction from recovery to primary. 
-## Replicate Virtual machines running in an Azure Public MEC to another Azure Public MEC 
-To replicate VMs running in a Public MEC to another Azure Public MEC, follow these steps:
+
+## Replicate Virtual machines running in an Azure Extended Zones to another Azure Extended Zones 
+
+To replicate VMs running in a Extended Zones to another Azure Extended Zones, follow these steps:
+
 > [!NOTE] 
-> For this example, the primary location is an Azure Public MEC, and the secondary/recovery location is another Azure Public MEC connected to the same region. 
+> For this example, the primary location is an Azure Extended Zones, and the secondary/recovery location is another Azure Extended Zones connected to the same region. 
+
 1. Sign-in to your Azure account.
     ```
     Connect-AzAccount
     ```
+
 1. Select Right subscription. 
     ```
     $subscription = Get-AzSubscription -SubscriptionName "<SubscriptionName>"
     Set-AzContext $subscription.Id
     $targetEdgeZoneName = “microsoftrrdclab3” 
     ```
+
 1. Get the details of the virtual machine that you plan to replicate.
     ```
     $VM = Get-AzVM -ResourceGroupName "<ResourceGroupName>" -Name "<VMName>" 
     
     $sourceEdgeZoneName = $VM.ExtendedLocation.Name
     Write-Output $VM
     ```
+
 1. Create a resource group for the recovery services vault in the secondary Azure region.
     ```
-    New-AzResourceGroup -Name "edgezonerecoveryrg" -Location "<EdgeZoneRegion>"
+    New-AzResourceGroup -Name "edgezonerecoveryrg" -Location "<AzureRegion>"
     ```
     
 1. Create a new Recovery services vault in the secondary region.
@@ -69,13 +79,16 @@ To replicate VMs running in a Public MEC to another Azure Public MEC, follow the
     ResourceGroupName "edgezonerecovery" -Location "\<EdgeZoneRegion\>"
     Write-Output $vault
     ```
+
 1. Set the vault context.
     ```
     Set-AzRecoveryServicesAsrVaultContext -Vault $vault 
     ```
+
+
 1. Create Primary Site Recovery fabric.
     ```
-    $TempASRJob = New-AzRecoveryServicesAsrFabric -Azure -Location “<EdgeZoneRegion>” -
+    $TempASRJob = New-AzRecoveryServicesAsrFabric -Azure -Location “<AzureRegion>” -
     Name "EdgeZoneFabric"
     ```
     
@@ -154,6 +167,7 @@ To replicate VMs running in a Public MEC to another Azure Public MEC, follow the
     ```
     
     1. Track Job status to check for completion.
+    
         ```
         while (($TempASRJob.State -eq "InProgress") -or ($TempASRJob.State -eq 
         "NotStarted")){
@@ -170,7 +184,9 @@ To replicate VMs running in a Public MEC to another Azure Public MEC, follow the
         $EdgeZoneToAzurePCMapping = Get-AzRecoveryServicesAsrProtectionContainerMapping -
         ProtectionContainer $PrimaryProtectionContainer -Name "PrimaryToRecovery"
         ```
+
     1. Create a protection container mapping for failback, between the recovery and primary protection containers with the Replication policy.
+
         ```
         $TempASRJob = New-AzRecoveryServicesAsrProtectionContainerMapping -Name 
         "RecoveryToPrimary" -Policy $ReplicationPolicy -PrimaryProtectionContainer 
@@ -179,13 +195,13 @@ To replicate VMs running in a Public MEC to another Azure Public MEC, follow the
         ```
     
        1. Track Job status to check for completion.
-            ```
-            while (($TempASRJob.State -eq "InProgress") -or ($TempASRJob.State -eq 
-            "NotStarted")){
+             ```
+             while (($TempASRJob.State -eq "InProgress") -or ($TempASRJob.State -eq 
+             "NotStarted")){
              sleep 10;
              $TempASRJob = Get-AzRecoveryServicesAsrJob -Job $TempASRJob
-            }
-            ```
+             }
+             ```
     
        1. On successful completion, the job state must be **Succeeded**.
     
@@ -194,35 +210,41 @@ To replicate VMs running in a Public MEC to another Azure Public MEC, follow the
             $AzureToEdgeZonePCMapping = Get-AzRecoveryServicesAsrProtectionContainerMapping -
             ProtectionContainer $RecoveryProtectionContainer -Name "RecoveryToPrimary"
             ```
+
 1. Create a cache storage account for replication logs in the primary region. The cache storage account is created in the primary region.
-    You can use **Local cache** (cache in the Public MEC) or **Remote cache** (cache in Azure). 
+    You can use **Local cache** (cache in the Extended Zone) or **Remote cache** (cache in Azure). 
     
     In this example, remote cache is used but there is no difference between them in terms of PowerShell commands. ARM ID of the cache storage account we provide to `New-AzRecoveryServicesAsrAzureToAzureDiskReplicationConfig` is the only difference.
+
     ```
     $CacheStorageAccount = New-AzStorageAccount -Name "cachestorage" -ResourceGroupName 
-    "<primary ResourceGroupName>" -Location '<EdgeZoneRegion>' -SkuName Standard_LRS -
+    "<primary ResourceGroupName>" -Location '<AzureRegion>' -SkuName Standard_LRS -
     Kind Storage
     ```
+
     ```
     $CacheStorageAccount = New-AzStorageAccount -Name "cachestorage" -ResourceGroupName 
-    "<primary ResourceGroupName>" -Location '<EdgeZoneRegion>' -SkuName Standard_LRS -
+    "<primary ResourceGroupName>" -Location '<AzureRegion>' -SkuName Standard_LRS -
     Kind Storage
     ```
+
 1. Ensure to create a virtual network in the target location. Create a Recovery Network in the recovery region.
     
     ```
     $recoveryVnet = New-AzVirtualNetwork -Name "recoveryvnet" -ResourceGroupName 
-    "recoveryrg" -Location '<EdgeZoneRegion>' -AddressPrefix "10.0.0.0/16" -EdgeZone $targetEdgeZoneName 
+    "recoveryrg" -Location '<AzureRegion>' -AddressPrefix "10.0.0.0/16" -EdgeZone $targetEdgeZoneName 
     Add-AzVirtualNetworkSubnetConfig -Name "defaultsubnetconf" -VirtualNetwork 
     $recoveryVnet -AddressPrefix "10.0.0.0/24" | Set-AzVirtualNetwork
     $recoveryNetwork = $recoveryVnet.Id
     ```
-1. Use the following PowerShell cmdlet to replicate an Azure Public MECs Azure virtual machine with managed disks. This step may take around 20 minutes to complete.
+
+1. Use the following PowerShell cmdlet to replicate an Azure Extended Zones Azure virtual machine with managed disks. This step may take around 20 minutes to complete.
     1. Get the resource group that the virtual machine must be created in when it's failed 
     over.
+
         ```
         $RecoveryRG = Get-AzResourceGroup -Name "edgezonerecoveryrg" -Location "
-        <EdgeZoneRegion>"
+        <AzureRegion>"
         ```
     
     1. Get VM and display contents.
@@ -246,11 +268,12 @@ To replicate VMs running in a Public MEC to another Azure Public MEC, follow the
         RecoveryReplicaDiskAccountType $RecoveryReplicaDiskAccountType `
          -RecoveryTargetDiskAccountType $RecoveryOSDiskAccountType
         ```
+
     1. Data disk
-        1. If VM has data disk, use the following command to create disk configuration. If not,
-    you can skip this section. From `$datadiskId` to `$DataDisk1ReplicationConfig $datadiskId = $vm.StorageProfile.OSDisk.ManagedDisk.Id`.
+        1. If VM has data disk, use the following command to create disk configuration. If not, you can skip this section. From `$datadiskId` to `$DataDisk1ReplicationConfig $datadiskId = $vm.StorageProfile.OSDisk.ManagedDisk.Id`.
     
-            Alternatively,
+            Alternatively, use:
+
             ```
             $RecoveryReplicaDiskAccountType = "Premium_LRS"
             $RecoveryTargetDiskAccountType = "Premium_LRS"
@@ -286,15 +309,11 @@ To replicate VMs running in a Public MEC to another Azure Public MEC, follow the
         ```
         Write-Output $TempASRJob.State
         ```
+
     1. After the operation to start replication succeeds, virtual machine data is replicated to the recovery region.
     
     Initially, when the replication process starts, it creates a copy of the replicating disks of the virtual machine in the recovery region. This phase is called the initial replication phase. This step takes around 20 minutes. See the status of the replication in the Vault blade under **Replicated items**.     
     
-    :::image type="Replicated items" source="./media/tutorial-replicate-vms-edge-zone-to-another-zone/replicated-items.png" alt-text="Screenshot of replicated items.":::
-    When the replication is completed, the Vault replication items will show as below:
-    
-    :::image type="Vault replication" source="./media/tutorial-replicate-vms-edge-zone-to-another-zone/vault-replication.png" alt-text="Screenshot of Vault replication.":::
-    
     Now the virtual machine is protected, and you can perform a test failover operation. The replication state of the replicated item that represents the virtual machine goes to the protected state after initial replication completes.
     
     Monitor the replication state and replication health for the virtual machine by getting details of the replication protected item that corresponds to it:
@@ -308,13 +327,12 @@ To replicate VMs running in a Public MEC to another Azure Public MEC, follow the
     
     If you see **Protected** in the *ProtectionState*, you are ready to proceed to test failover. 
     
-    :::image type="Protection state" source="./media/tutorial-replicate-vms-edge-zone-to-another-zone/protection-state.png" alt-text="Screenshot of Protection state.":::
 1. Perform, validate, and clean up a test failover. You can skip the Test failover. However, we recommend executing test failover to ensure that your secondary region comes up as expected. 
     1. Create a separate network for test failover (not connected to my DR network).
     
         ```
         $TFOVnet = New-AzVirtualNetwork -Name "TFOvnet" -ResourceGroupName "edgezonerecoveryrg" 
-        -Location '<EdgeZoneRegion>' -AddressPrefix "10.3.0.0/26"
+        -Location '<AzureRegion>' -AddressPrefix "10.3.0.0/26"
     
         Add-AzVirtualNetworkSubnetConfig -Name "default" -VirtualNetwork $TFOVnet -AddressPrefix 
         "10.3.0.0/26" | Set-AzVirtualNetwork
@@ -343,26 +361,34 @@ To replicate VMs running in a Public MEC to another Azure Public MEC, follow the
         ```
     
     1. Wait for the test failover to complete.
+    
         ```
         Get-AzRecoveryServicesAsrJob -Job $TFOJob
         ```
+
     >[!NOTE]
     >To check the progress, go to the portal, select the vault and then select the Site Recovery Jobs.
+
     After the test failover job completes successfully, you can connect to the test failed over virtual machine and validate the test failover. Once testing is complete on the test failed over virtual machine, clean up the test copy by starting the cleanup test failover operation. This operation deletes the test copy of the virtual machine that was created by the test failover.
     Verify that all the target settings are right in the test failover VM including location, network setting, no data corruption, and no data is lost in the target VM. Now you can delete the test failover and start the failover.
+
     ```
     $Job_TFOCleanup = Start-AzRecoveryServicesAsrTestFailoverCleanupJob -
     ReplicationProtectedItem $ReplicationProtectedItem 
     Get-AzRecoveryServicesAsrJob -Job $Job_TFOCleanup | Select State
     ```
+
 1. Next step would be to fail over the virtual machine. This step will create the VM using the replicated disks in recovery region.
+
     ```
     $ReplicationProtectedItem = Get-AzRecoveryServicesAsrReplicationProtectedItem -
     FriendlyName "<VMName>" -ProtectionContainer $PrimaryProtectionContainer
     $RecoveryPoints = Get-AzRecoveryServicesAsrRecoveryPoint -ReplicationProtectedItem 
     $ReplicationProtectedItem 
     ```
+
     The list of recovery points returned may not be sorted chronologically. You need to sort these first to find the oldest or the latest recovery points for the virtual machine.
+
     ```
      "{0} {1}" -f $RecoveryPoints[0].RecoveryPointType, $RecoveryPoints[-
     1].RecoveryPointTime
@@ -381,11 +407,14 @@ To replicate VMs running in a Public MEC to another Azure Public MEC, follow the
         "NotStarted")) 
         $Job_Failover.State
         ```
+
 1. When the failover job is successful, you can commit the failover.
+
     ```
      $CommitFailoverJob = Start-AzRecoveryServicesAsrCommitFailoverJob -
     ReplicationProtectedItem $ReplicationProtectedItem 
      ```
+
     1. Wait until commit failover job is finished.
     
         ```
@@ -396,6 +425,7 @@ To replicate VMs running in a Public MEC to another Azure Public MEC, follow the
         }
          Get-AzRecoveryServicesAsrJob -Job $CommitFailoverJOb
         ```
+
 1. After a failover, when you're ready to go back to the original region, start reverse replication for the replication protected item using the `Update-AzRecoveryServicesAsrProtectionDirection` cmdlet. 
     1. Create Cache storage account for replication logs in the recovery region.
     
@@ -405,7 +435,7 @@ To replicate VMs running in a Public MEC to another Azure Public MEC, follow the
         Standard_LRS -Kind Storage
         ```
     
-    1. Use the recovery protection container, the new cache storage account in Azure Public MECs region, and the source region VM resource group. 
+    1. Use the recovery protection container, the new cache storage account in Azure Extended Zoness region, and the source region VM resource group. 
     
         ```
         $ReplicationProtectedItem = Get-AzRecoveryServicesAsrReplicationProtectedItem -
@@ -418,14 +448,23 @@ To replicate VMs running in a Public MEC to another Azure Public MEC, follow the
          -LogStorageAccountId $EdgeZoneCacheStorageAccount.Id `
          -RecoveryResourceGroupID $sourceVMResourcegroupId
         ```
+    
     This step takes ~20 minutes and the status will move from **In progress** to **Successful**. 
-    :::image type="Protected items list" source="media/tutorial-replicate-vms-edge-zone-to-another-zone/protected-items-inline.png" alt-text="Screenshot of Protected items list." lightbox="media/tutorial-replicate-vms-edge-zone-to-another-zone/protected-items-expanded.png":::
+    
 1. Disable replication.
+
     ```
     Remove-AzRecoveryServicesAsrReplicationProtectedItem -ReplicationProtectedItem 
     $ReplicationProtectedItem
     ```
+
 1. Clean the environment. This step is optional and can be used to remove the resource group. 
+
     ```
     Remove-AzResourceGroup -Name $Name -Force
-    ```
+    ```
+
+## Next steps
+
+- View the [Azure Site Recovery PowerShell reference](https://learn.microsoft.com/powershell/module/az.recoveryservices/?view=azps-13.0.0) to learn how you can create recovery plans, perform failovers, and failbacks with PowerShell.
+- Learn how to [Set up  disaster recovery for Azure VMs using the Azure PowerShell](../azure-to-azure-powershell.md).