|
| 1 | +--- |
| 2 | +title: Relocate Azure NetApp Files volume to another region |
| 3 | +description: Learn how to relocate an Azure NetApp Files volume to another region |
| 4 | +author: anaharris-ms |
| 5 | +ms.author: anaharris |
| 6 | +ms.reviewer: anaharris |
| 7 | +ms.date: 08/14/2024 |
| 8 | +ms.service: azure-automation |
| 9 | +ms.topic: how-to |
| 10 | +ms.custom: |
| 11 | + - subject-relocation |
| 12 | +--- |
| 13 | + |
| 14 | +# Relocate Azure NetApp Files volume to another region |
| 15 | + |
| 16 | +This article covers guidance for relocating [Azure NetApp Files](../azure-netapp-files/azure-netapp-files-introduction.md) volumes to another region. |
| 17 | + |
| 18 | +[!INCLUDE [relocate-reasons](./includes/service-relocation-reason-include.md)] |
| 19 | + |
| 20 | + |
| 21 | +## Prerequisites |
| 22 | + |
| 23 | +Before you begin the relocation planning stage, first review the following prerequisites: |
| 24 | + |
| 25 | +- The target NetApp account instance should already be created. |
| 26 | + |
| 27 | +- Source and target regions must be paired regions. To see if they're paired, see [Supported cross-region replication pairs](../azure-netapp-files/cross-region-replication-introduction.md?#supported-region-pairs). |
| 28 | + |
| 29 | +- Understand all dependent resources. Some of the resources could be: |
| 30 | + - Microsoft Entra ID |
| 31 | + - [Virtual Network](./relocation-virtual-network.md) |
| 32 | + - Azure DNS |
| 33 | + - [Storage services](./relocation-storage-account.md) |
| 34 | + - [Capacity pools](../azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md) |
| 35 | + |
| 36 | + |
| 37 | +## Prepare |
| 38 | + |
| 39 | +Before you begin the relocation process, make sure to complete the following preparations: |
| 40 | + |
| 41 | +- The target Microsoft Entra ID connection must have access to the DNS servers, AD DS Domain Controllers, or Microsoft Entra Domain Services Domain Controllers that are reachable from the delegated subnet in the target region. |
| 42 | + |
| 43 | +- The network configurations (including separate subnets if needed and IP ranges) should already be planned and prepared |
| 44 | + |
| 45 | +- Turn off replication procedures to disaster recovery region. If you've established a disaster recovery (DR) solution using replication to a DR region, turn off replication to the DR site before initiating relocation procedures. |
| 46 | + |
| 47 | +- Understand the following considerations in regards to replication: |
| 48 | + |
| 49 | + - SMB, NFS, and dual-protocol volumes are supported. Replication of SMB volumes requires a Microsoft Entra ID connection in the source and target NetApp accounts. |
| 50 | + |
| 51 | + - The replication destination volume is read-only until the entire move is complete. |
| 52 | + |
| 53 | + - Azure NetApp Files replication doesn't currently support multiple subscriptions. All replications must be performed under a single subscription. |
| 54 | + |
| 55 | + - There are resource limits for the maximum number of cross-region replication destination volumes. For more information, see [Resource limits for Azure NetApp Files](../azure-netapp-files/azure-netapp-files-resource-limits.md). |
| 56 | + |
| 57 | +## Redeploy |
| 58 | + |
| 59 | +**To redeploy your NetApp resources:** |
| 60 | + |
| 61 | +1. [Create the target NetApp account](../azure-netapp-files/azure-netapp-files-create-netapp-account.md). |
| 62 | + |
| 63 | +1. [Create the target capacity pool](../azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md). |
| 64 | + |
| 65 | +1. [Delegate a subnet in the target region](../azure-netapp-files/azure-netapp-files-delegate-subnet.md). Azure NetApp Files creates a system route to the delegated subnet. Peering and endpoints can be used to connect to the target as needed. |
| 66 | + |
| 67 | +1. Create a data replication volume by following the directions in [Create volume replication for Azure NetApp Files](../azure-netapp-files/cross-region-replication-create-peering.md). |
| 68 | + |
| 69 | +1. [Verify that the health status](../azure-netapp-files/cross-region-replication-display-health-status.md) of replication is healthy. |
| 70 | + |
| 71 | + |
| 72 | +## Cleanup |
| 73 | + |
| 74 | +Once the replication is complete, you can then safely delete the replication peering the source volume. |
| 75 | + |
| 76 | +To learn how to clean up a replication, see [Delete volume replications or volumes](/azure/azure-netapp-files/cross-region-replication-delete). |
| 77 | + |
| 78 | + |
| 79 | +## Related content |
| 80 | + |
| 81 | + |
| 82 | +- [Cross-region replication of Azure NetApp Files volumes](../azure-netapp-files/cross-region-replication-introduction.md) |
| 83 | + |
| 84 | +To learn more about moving resources between regions and disaster recovery in Azure, refer to: |
| 85 | + |
| 86 | +- [Requirements for Active Directory Connections](/azure/azure-netapp-files/create-active-directory-connections#requirements-for-active-directory-connections) |
| 87 | + |
| 88 | +- [Guidelines for Azure NetApp Files network planning](/azure/azure-netapp-files/azure-netapp-files-network-topologies) |
| 89 | + |
| 90 | +- [Fail over to the destination region](/azure/azure-netapp-files/cross-region-replication-manage-disaster-recovery#fail-over-to-destination-volume) |
| 91 | + |
| 92 | +- [Move resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md) |
| 93 | + |
| 94 | +- [Move Azure VMs to another region](../site-recovery/azure-to-azure-tutorial-migrate.md) |
0 commit comments