Skip to content

Commit 2659580

Browse files
committed
edit
1 parent 2262dcb commit 2659580

File tree

3 files changed

+90
-0
lines changed

3 files changed

+90
-0
lines changed

articles/operational-excellence/TOC.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -88,6 +88,8 @@
8888
href: relocation-automation.md
8989
- name: Azure IoT Hub
9090
href: ../iot-hub/iot-hub-how-to-clone.md?toc=/azure/operational-excellence/toc.json
91+
- name: Azure NetApp Files
92+
href: relocation-net-app.md
9193
- name: Power BI
9294
href: /power-bi/admin/service-admin-region-move?toc=/azure/operational-excellence/toc.json
9395

articles/operational-excellence/overview-relocation.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -85,6 +85,7 @@ The following tables provide links to each Azure service relocation document. Th
8585
| --- | --- | --- | ---|
8686
[Azure Automation](./relocation-automation.md)| ✅ | ✅| ❌ |
8787
[Azure IoT Hub](/azure/iot-hub/iot-hub-how-to-clone?toc=/azure/operational-excellence/toc.json)| ✅ | ✅| ❌ |
88+
[Azure NetApps Files](./relocation-net-app.md)| ✅ | ✅| ❌ |
8889
[Power BI](/power-bi/admin/service-admin-region-move?toc=/azure/operational-excellence/toc.json)| ✅ |❌ | ❌ |
8990

9091

Lines changed: 87 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,87 @@
1+
---
2+
title: Relocate Azure Net App Files to another region
3+
description: Learn how to relocate an Azure Net App Files to a 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 Net App Files to another region
15+
16+
This article cover guidance for relocating [Azure Net App Files](../azure-netapp-files/azure-netapp-files-introduction.md) resources 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 are paired, see [Azure paired regions](../reliability/cross-region-replication-azure.md#azure-paired-regions).
28+
29+
- Understand all dependent resources. Some of the resources could be the following:
30+
- Azure 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+
38+
## Downtime
39+
40+
41+
42+
## Prepare
43+
44+
45+
- The target Microsoft Entra ID connection must have access to the DNS servers or Microsoft Entra Domain Services Domain Controllers that are reachable from the delegated subnet in the target region.
46+
47+
- The network configurations (including separate subnets if needed and IP ranges) should already be planned and prepared
48+
49+
- 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.
50+
51+
- Understand the following considerations in regards to replication:
52+
53+
- SMB volumes are supported along with NFS volumes. Replication of SMB volumes requires an Microsoft Entra ID connection in the source and target NetApp accounts.
54+
55+
- The replication destination volume is read-only until the entire move is complete.
56+
57+
- Azure NetApp Files replication doesn't currently support multiple subscriptions. All replications must be performed under a single subscription.
58+
59+
- There can be 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)
60+
61+
## Redeploy
62+
63+
**To redeploy your NetApp resources:**
64+
65+
1. [Create the target NetApp account](../azure-netapp-files/azure-netapp-files-create-netapp-account.md).
66+
67+
1. (Optional) [Create the target capacity pool](../azure-netapp-files/azure-netapp-files-set-up-capacity-pool.md).
68+
69+
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.
70+
71+
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).
72+
73+
1. [Verify that the health status](../azure-netapp-files/cross-region-replication-display-health-status.md) of replication is healthy.
74+
75+
76+
## Cleanup
77+
78+
Once the replication is complete, the replication peering, the source volume and replication can be deleted.
79+
80+
## Related content
81+
82+
83+
- [Cross-region replication of Azure NetApp Files volumes](../azure-netapp-files/cross-region-replication-introduction.md)
84+
To learn more about moving resources between regions and disaster recovery in Azure, refer to:
85+
86+
- [Move resources to a new resource group or subscription](../azure-resource-manager/management/move-resource-group-and-subscription.md)
87+
- [Move Azure VMs to another region](../site-recovery/azure-to-azure-tutorial-migrate.md)

0 commit comments

Comments
 (0)