failover note

Author: b-ahibbard

articles/azure-netapp-files/cross-region-replication-create-peering.md

@@ -91,7 +91,7 @@ To authorize the replication, you need to obtain the resource ID of the replicat
 6. In the Authorize field, paste the destination replication volume resource ID that you obtained in Step 3, then select **OK**.
 
     > [!NOTE]
-    > Due to various factors, like the state of the destination storage at a given time, there’s likely a difference between the used space of the source volume and the used space of the destination volume. <!-- ANF-14038 --> 
+    > Due to various factors, such as the state of the destination storage at a given time, there’s likely a difference between the used space of the source volume and the used space of the destination volume. <!-- ANF-14038 --> 
 
 ## Next steps  
 

articles/azure-netapp-files/cross-region-replication-manage-disaster-recovery.md

@@ -6,21 +6,19 @@ author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
 ms.date: 11/09/2022
-ms.author: anfdocs
+ms.author: anfdocs 
 ---
 # Manage disaster recovery using cross-region replication 
 
-An ongoing replication between the source and the destination volumes (see [Create volume replication](cross-region-replication-create-peering.md)) prepares you for a disaster recovery event. 
+An ongoing replication (with [cross-zone](create-cross-zone-replication.md) or [cross-region replication](cross-region-replication-create-peering.md)) between the source and the destination volumes prepares you for a disaster recovery event. 
 
 When such an event occurs, you can [fail over to the destination volume](#fail-over-to-destination-volume), enabling the client to read and write to the destination volume. 
 
 After disaster recovery, you can perform a [resync](#resync-replication) operation to fail back to the source volume. You then [reestablish the source-to-destination replication](#reestablish-source-to-destination-replication) and remount the source volume for the client to access. 
 
-The details are described below. 
-
 ## Fail over to destination volume
 
-Failover is a manual process. When you need to activate the destination volume (for example, when you want to failover to the destination region), you need to break replication peering and then mount the destination volume. . 
+Failover is a manual process. When you need to activate the destination volume (for example, when you want to fail over to the destination region), you need to break replication peering then mount the destination volume.
 
 1. To break replication peering, select the destination volume. Select **Replication** under Storage Service.  
 
@@ -32,9 +30,9 @@ Failover is a manual process. When you need to activate the destination volume (
 
     See [Display health status of replication relationship](cross-region-replication-display-health-status.md). 
 
-3.	Click **Break Peering**.  
+3.	Select **Break Peering**.  
 
-4.	Type **Yes** when prompted and click the **Break** button. 
+4.	Type **Yes** when prompted and then select **Break**.
 
     ![Break replication peering](./media/shared/cross-region-replication-break-replication-peering.png)
 
@@ -53,9 +51,9 @@ After disaster recovery, you can reactivate the source volume by performing a re
 > In case the source volume did not survive the disaster and therefore no common snapshot exists, all data in the destination will be resynchronized to a newly created source volume.
 
 
-1. To reverse resync replication, select the *source* volume. Click **Replication** under Storage Service. Then click **Reverse Resync**.  
+1. To reverse resync replication, select the *source* volume. Select **Replication** under Storage Service. Then select **Reverse Resync**.  
 
-2. Type **Yes** when prompted and click **OK**. 
+2. Type **Yes** when prompted then select **OK**. 
 
     ![Resync replication](./media/cross-region-replication-manage-disaster-recovery/cross-region-replication-resync-replication.png)
 
@@ -70,7 +68,7 @@ After disaster recovery, you can reactivate the source volume by performing a re
 After the resync operation from destination to source is complete, you need to break replication peering again to reestablish source-to-destination replication. You should also remount the source volume so that the client can access it.  
 
 1. Break the replication peering:  
-    a. Select the *destination* volume. Click **Replication** under Storage Service.  
+    a. Select the *destination* volume. Select **Replication** under Storage Service.  
     b. Check the following fields before continuing:   
     * Ensure that Mirror State shows ***Mirrored***.   
     Do not attempt to break replication peering if Mirror State shows *uninitialized*.  
@@ -79,12 +77,12 @@ After the resync operation from destination to source is complete, you need to b
 
         See [Display health status of replication relationship](cross-region-replication-display-health-status.md). 
 
-    c. Click **Break Peering**.   
-    d. Type **Yes** when prompted and click the **Break** button.  
+    c. Select **Break Peering**.   
+    d. Type **Yes** when prompted then select **Break**.  
 
 2. Resync the source volume with the destination volume:  
-    a. Select the *destination* volume. Click **Replication** under Storage Service. Then click **Reverse Resync**.   
-    b. Type **Yes** when prompted and click the **OK** button.
+    a. Select the *destination* volume. Select **Replication** under Storage Service. Then select **Reverse Resync**.   
+    b. Type **Yes** when prompted then select **OK**.
 
 3. Remount the source volume by following the steps in [Mount a volume for Windows or Linux virtual machines](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md).  
     This step enables a client to access the source volume.

articles/azure-netapp-files/cross-region-replication-requirements-considerations.md

@@ -19,6 +19,8 @@ This article describes requirements and considerations about [using the volume c
 * SMB volumes are supported along with NFS volumes. Replication of SMB volumes requires an Active Directory connection in the source and destination NetApp accounts. The destination AD connection must have access to the DNS servers or AD DS Domain Controllers that are reachable from the delegated subnet in the destination region. For more information, see [Requirements for Active Directory connections](create-active-directory-connections.md#requirements-for-active-directory-connections). 
 * The destination account must be in a different region from the source volume region. You can also select an existing NetApp account in a different region.  
 * The replication destination volume is read-only until you [fail over to the destination region](cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume) to enable the destination volume for read and write. 
+    >[!IMPORTANT]
+    >Failover is a manual process. When you need to activate the destination volume (for example, when you want to fail over to the destination region), you need to break replication peering then mount the destination volume. For more information, see [fail over to the destination volume](cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume)
 * Azure NetApp Files replication doesn't currently support multiple subscriptions; all replications must be performed under a single subscription.
 * See [resource limits](azure-netapp-files-resource-limits.md) for the maximum number of cross-region replication destination volumes. You can open a support ticket to [request a limit increase](azure-netapp-files-resource-limits.md#request-limit-increase) in the default quota of replication destination volumes (per subscription in a region).
 * There can be a delay up to five minutes for the interface to reflect a newly added snapshot on the source volume.  

articles/azure-netapp-files/cross-zone-replication-requirements-considerations.md

@@ -21,6 +21,8 @@ This article describes requirements and considerations about [using the volume c
 * You can use cross-zone replication with SMB and NFS volumes. Replication of SMB volumes requires an Active Directory connection in the source and destination NetApp accounts. The destination AD connection must have access to the DNS servers or AD DS Domain Controllers that are reachable from the delegated subnet in the destination zone. For more information, see [Requirements for Active Directory connections](create-active-directory-connections.md#requirements-for-active-directory-connections). 
 * The destination account must be in a different zone from the source volume zone. You can also select an existing NetApp account in a different zone.  
 * The replication destination volume is read-only until you fail over to the destination zone to enable the destination volume for read and write. For more information about the failover process, see [fail over to the destination volume](cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume).
+    >[!IMPORTANT]
+    >Failover is a manual process. When you need to activate the destination volume (for example, when you want to fail over to the destination region), you need to break replication peering then mount the destination volume. For more information, see [fail over to the destination volume](cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume)
 * Azure NetApp Files replication doesn't currently support multiple subscriptions; all replications must be performed under a single subscription.
 * See [resource limits](azure-netapp-files-resource-limits.md) for the maximum number of cross-zone destination volumes. You can open a support ticket to [request a limit increase](azure-netapp-files-resource-limits.md#request-limit-increase) in the default quota of replication destination volumes (per subscription in a region). 
 * There can be a delay up to five minutes for the interface to reflect a newly added snapshot on the source volume.