Merge pull request #219343 from b-ahibbard/testing-disaster-recovery

add test disaster recovery topic

Author: v-dirichards

articles/azure-netapp-files/TOC.yml

@@ -303,6 +303,8 @@
         href: cross-region-replication-manage-disaster-recovery.md
       - name: Delete volume replications or volumes
         href: cross-region-replication-delete.md
+      - name: Test disaster recovery
+        href: test-disaster-recovery.md
     - name: Manage availability zones
       items:
       - name: Manage availability zone volume placement

articles/azure-netapp-files/cross-region-replication-introduction.md

@@ -143,3 +143,4 @@ Regular Azure NetApp Files storage capacity charge for Month 2 applies to the de
 * [Volume replication metrics](azure-netapp-files-metrics.md#replication)
 * [Delete volume replications or volumes](cross-region-replication-delete.md)
 * [Troubleshoot cross-region replication](troubleshoot-cross-region-replication.md)
+* [Test disaster recovery for Azure NetApp Files](test-disaster-recovery.md)

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

@@ -23,7 +23,7 @@ This article describes requirements and considerations about [using the volume c
 ## Requirements and considerations 
 
 * Azure NetApp Files replication is only available in certain fixed region pairs. See [Supported region pairs](cross-region-replication-introduction.md#supported-region-pairs). 
-* 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 ADDS 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). 
+* 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. 
 * Azure NetApp Files replication does not currently support multiple subscriptions; all replications must be performed under a single subscription.
@@ -43,3 +43,4 @@ This article describes requirements and considerations about [using the volume c
 * [Volume replication metrics](azure-netapp-files-metrics.md#replication)
 * [Delete volume replications or volumes](cross-region-replication-delete.md)
 * [Troubleshoot cross-region replication](troubleshoot-cross-region-replication.md)
+* [Test disaster recovery for Azure NetApp Files](test-disaster-recovery.md)

articles/azure-netapp-files/snapshots-introduction.md

@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
 ms.workload: storage
 ms.tgt_pltfrm: na
 ms.topic: conceptual
-ms.date: 11/18/2022
+ms.date: 11/22/2022
 ms.author: anfdocs
 ---
 # How Azure NetApp Files snapshots work
@@ -243,3 +243,4 @@ Vaulted snapshot history is managed automatically by the applied snapshot policy
 * [Restore a backup to a new volume](backup-restore-new-volume.md)
 * [Disable backup functionality for a volume](backup-disable.md)
 * [Delete backups of a volume](backup-delete.md)
+* [Test disaster recovery for Azure NetApp Files](test-disaster-recovery.md)

articles/azure-netapp-files/test-disaster-recovery.md

@@ -0,0 +1,62 @@
+---
+title: Test disaster recovery for Azure NetApp Files | Microsoft Docs
+description: Enhance your disaster recovery preparedness with this test plan for cross-region replication.  
+services: azure-netapp-files
+documentationcenter: ''
+author: b-ahibbard
+manager: ''
+editor: ''
+
+ms.assetid:
+ms.service: azure-netapp-files
+ms.workload: storage
+ms.tgt_pltfrm: na
+ms.topic: how-to
+ms.date: 11/30/2022
+ms.author: anfdocs
+---  
+
+# Test disaster recovery for Azure NetApp Files
+
+An effective disaster recovery plan includes testing your disaster recovery configuration. Testing your disaster recovery configuration demonstrates the efficacy of your disaster recovery configuration and that it can achieve the desired recovery point objective (RPO) and recovery time objective (RTO). Testing disaster recovery also ensures that operational runbooks are accurate and that operational staff are trained on the workflow.
+
+This disaster recovery test workflow uses [cross-region replication](cross-region-replication-introduction.md). With cross-region replication, you can test your disaster recovery understanding and preparedness without disrupting the existing replication schedule, posing no risk to RPO or RTO. This test plan also leverages Azure NetApp Files' ability to [create new volumes from the snapshots](snapshots-restore-new-volume.md) in cross-region replication.
+
+## Pre-requisites
+
+* Application consistent snapshots should be created in the volumes hosted in the primary region. Application data hosted in Azure NetApp Files volumes must be in a consistent state prior to the creation of the snapshot. 
+
+    The [Azure Application Consistent Snapshot tool](azacsnap-cmd-ref-configure.md) can be used to create application consistent snapshots. 
+
+    >[!NOTE]
+    >If the data in the snapshot is not consistent, the disaster recovery workflow or test workflow may not work properly.
+
+* Cross-region replication must be set up. The [replication status must be healthy](cross-region-replication-display-health-status.md).
+
+## Steps
+
+Given the uniqueness of each application architecture, there's no specific workflow to test your disaster recovery workflow. The outlined steps are a high-level overview for disaster recovery testing.
+
+1. [Prepare Azure virtual machines (VMs) in the secondary region](cross-region-replication-create-peering.md). You must configure:
+    * The operating system
+    * Application
+    * User accounts
+    * DNS
+    * Any other resources required to run the application in the secondary region
+1. [Create new volumes from the most recent snapshots](snapshots-restore-new-volume.md) replicated to the Azure NetApp Files data protection volumes in the secondary region.
+    >[!NOTE]
+    > Cross-region replication baseline snapshots cannot be used to create volumes.
+1. [Mount the volumes](azure-netapp-files-mount-unmount-volumes-for-virtual-machines.md) to the application VMs from Step 1
+1. Run the application in the secondary region. Test the application's functionality.
+1. Bring down the application in the secondary region.
+1. Unmount the volumes from the application VM in the secondary region. 
+1. Delete the volumes created from the snapshot in step 2. 
+1. Bring down the Azure VM in the secondary region. Clean up any resources configured to support the disaster recovery testing. 
+
+## Next steps
+
+* [How Azure NetApp Files snapshots work](snapshots-introduction.md)
+* [Cross-region replication of Azure NetApp Files volumes](cross-region-replication-introduction.md)
+* [Requirements and considerations for using cross-region replication](cross-region-replication-requirements-considerations.md)
+* [Troubleshoot cross-region replication](troubleshoot-cross-region-replication.md)
+* [What is Azure Application Consistent Snapshot tool](azacsnap-introduction.md)

articles/azure-netapp-files/troubleshoot-cross-region-replication.md

@@ -87,4 +87,4 @@ This article describes error messages and resolutions that can help you troubles
 * [Display health status of replication relationship](cross-region-replication-display-health-status.md)
 * [Manage disaster recovery](cross-region-replication-manage-disaster-recovery.md)
 * [Resize a cross-region replication destination volume](azure-netapp-files-resize-capacity-pools-or-volumes.md#resize-a-cross-region-replication-destination-volume)
-* [Troubleshoot cross-region replication](troubleshoot-cross-region-replication.md)
+* [Test disaster recovery for Azure NetApp Files](test-disaster-recovery.md)