You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/cross-region-replication-create-peering.md
+6-3
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,16 @@
1
1
---
2
-
title: Create volume replication for Azure NetApp Files | Microsoft Docs
2
+
title: Create volume replication for Azure NetApp Files
3
3
description: Describes how to create volume replication peering for Azure NetApp Files to set up cross-region replication.
4
4
services: azure-netapp-files
5
5
author: b-hchen
6
6
ms.service: azure-netapp-files
7
7
ms.topic: how-to
8
-
ms.date: 05/08/2025
8
+
ms.date: 05/12/2025
9
9
ms.author: anfdocs
10
10
---
11
11
# Create volume replication for Azure NetApp Files
12
12
13
-
Azure NetApp Files supports [cross-region](cross-region-replication-introduction.md) and [cross-zonereplication](cross-zone-replication-introduction.md).
13
+
Azure NetApp Files enables you to replicate a volume for data protection and resiliency. You can replicate volumes across [regions](cross-region-replication-introduction.md), [zones in the same region](cross-zone-replication-introduction.md), or a [combination](cross-zone-region-replication.md).
14
14
15
15
Setting up replication peering enables you to asynchronously replicate data from an Azure NetApp Files volume (source) to another Azure NetApp Files volume (destination). You can create volume replication between regions (the source and destination volumes reside in different regions, this is known as cross-region replication), or within a region where the replication is established to a different zone in the same region (this is known as cross-zone replication).
16
16
@@ -123,8 +123,11 @@ To authorize the replication, you need to obtain the resource ID of the replicat
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/cross-region-replication-display-health-status.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Display health status of Azure NetApp Files replication relationship | Microsoft Docs
2
+
title: Display health status of Azure NetApp Files replication relationship
3
3
description: Describes how to view replication status on the source volume or the destination volume of Azure NetApp Files.
4
4
services: azure-netapp-files
5
5
author: b-hchen
@@ -8,7 +8,7 @@ ms.topic: how-to
8
8
ms.date: 03/03/2025
9
9
ms.author: anfdocs
10
10
---
11
-
# Display health and monitor status of replication relationship
11
+
# Display health and monitor status of replication relationship in Azure NetApp Files
12
12
13
13
You can view replication status on the source volume or the destination volume. You can also set alert rules in Azure Monitor to help you monitor the replication status.
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/cross-region-replication-introduction.md
+2-58
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Cross-region replication of Azure NetApp Files volumes | Microsoft Docs
2
+
title: Cross-region replication of Azure NetApp Files volumes
3
3
description: Describes what Azure NetApp Files cross-region replication does, supported region pairs, service-level objectives, data durability, and cost model.
4
4
services: azure-netapp-files
5
5
author: b-hchen
@@ -15,63 +15,7 @@ The Azure NetApp Files replication functionality provides data protection throug
Azure NetApp Files volume replication is supported between various [Azure regional pairs](../reliability/cross-region-replication-azure.md#azure-paired-regions) and non-standard pairs. Azure NetApp Files volume replication is currently available between the following regions. You can replicate Azure NetApp Files volumes from Regional Pair A to Regional Pair B, and vice versa.
19
-
20
-
### Azure regional pairs
21
-
22
-
| Geography | Regional Pair A | Regional Pair B |
23
-
|:--- |:--- |:--- |
24
-
| Australia | Australia Central | Australia Central 2 |
25
-
| Australia | Australia East | Australia Southeast |
26
-
| Asia-Pacific | East Asia | Southeast Asia |
27
-
| Brazil | Brazil South | Brazil Southeast |
28
-
| Brazil/North America | Brazil South | South Central US |
29
-
| Canada | Canada Central | Canada East |
30
-
| Europe | North Europe | West Europe |
31
-
| Germany | Germany West Central | Germany North |
32
-
| India | Central India |South India |
33
-
| Japan | Japan East | Japan West |
34
-
| Korea | Korea Central | Korea South |
35
-
| North America | Central US | West US 3 |
36
-
| North America | East US | West US |
37
-
| North America | East US 2 | Central US |
38
-
| North America | North Central US | South Central US|
39
-
| North America | West US 3 | East US |
40
-
| Norway | Norway East | Norway West |
41
-
| Switzerland | Switzerland North | Switzerland West |
42
-
| UK | UK South | UK West |
43
-
| United Arab Emirates | UAE North | UAE Central |
44
-
| US Government | US Gov Arizona | US Gov Texas |
45
-
| US Government | US Gov Virginia | US Gov Texas |
46
-
47
-
### Azure regional non-standard pairs
48
-
49
-
| Geography | Regional Pair A | Regional Pair B |
50
-
|:--- |:--- |:--- |
51
-
| Australia/Southeast Asia | Australia East | Southeast Asia |
52
-
| Israel/Sweden | Israel Central | Sweden Central |
53
-
| Qatar/Europe | Qatar Central | West Europe |
54
-
| France/Europe | France Central | West Europe |
55
-
| Germany/UK | Germany West Central | UK South |
56
-
| Germany/Europe | Germany West Central | West Europe |
57
-
| Germany/France | Germany West Central | France Central |
58
-
| Italy/Sweden | Italy North | Sweden Central |
59
-
| Sweden/Germany | Sweden Central | Germany West Central |
60
-
| Spain/Sweden | Spain Central | Sweden Central |
61
-
| North America | East US | East US 2 |
62
-
| North America | East US | North Central US |
63
-
| North America | East US 2| West US 2 |
64
-
| North America | East US 2 | West US 3 |
65
-
| North America | North Central US | East US 2|
66
-
| North America | South Central US | East US |
67
-
| North America | South Central US | East US 2 |
68
-
| North America | South Central US | Central US |
69
-
| North America | West US 2 | East US |
70
-
| North America | West US 2 | West US 3 |
71
-
| Sweden/Europe | Sweden Central | North Europe |
72
-
| Sweden/Europe | Sweden Central | West Europe |
73
-
| UK/Europe | UK South | North Europe |
74
-
| US Government | US Gov Arizona | US Gov Virginia |
18
+
[!INCLUDE [Supported region pairs](includes/region-pairs.md)]
75
19
76
20
>[!NOTE]
77
21
>There may be a discrepancy in the size and number of snapshots between source and destination. This discrepancy is expected. Snapshot policies and replication schedules will influence the number of snapshots. Snapshot policies and replication schedules, combined with the amount of data changed between snapshots, will influence the size of snapshots. To learn more about snapshots, refer to [How Azure NetApp Files snapshots work](snapshots-introduction.md).
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/cross-region-replication-manage-disaster-recovery.md
+8-3
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
5
5
author: b-hchen
6
6
ms.service: azure-netapp-files
7
7
ms.topic: how-to
8
-
ms.date: 04/14/2025
8
+
ms.date: 05/12/2025
9
9
ms.author: anfdocs
10
10
---
11
11
# Manage disaster recovery using Azure NetApp Files
@@ -51,10 +51,15 @@ After disaster recovery, you can reactivate the source volume by performing a re
51
51
>
52
52
> ***The reverse resync operation overwrites any newer data (than the most common snapshot) in the source volume with the updated destination volume data. The UI warns you about the potential for data loss. You will be prompted to confirm the resync action before the operation starts.***
53
53
>
54
-
> 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.
54
+
> In case the source volume didn't survive the disaster and therefore no common snapshot exists, all data in the destination will be resynchronized to a newly created source volume.
55
+
56
+
>[!NOTE]
57
+
>To perform a reverse resync with [cross-zone-region replication](cross-zone-region-replication.md), you must break the secondary relationship then perform the reverse resync as described.
58
+
>
59
+
> To restore the cross-zone-region replication, delete the secondary DP volume then [reconfigure replication](cross-zone-region-replication-configure.md).
55
60
56
61
57
-
1. To reverse resync replication, select the *source* volume. Select **Replication** under Storage Service. Then select **Reverse Resync**.
62
+
1. To perform a reverse resync, select the *source* volume. Select **Replication** under Storage Service. Then select **Reverse Resync**.
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/cross-region-replication-requirements-considerations.md
+5-4
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,15 @@
1
1
---
2
-
title: Requirements and considerations for Azure NetApp Files cross-region replication | Microsoft Docs
2
+
title: Requirements and considerations for Azure NetApp Files cross-region replication
3
3
description: Describes the requirements and considerations for using the volume cross-region replication functionality of Azure NetApp Files.
4
4
services: azure-netapp-files
5
5
author: b-hchen
6
6
ms.service: azure-netapp-files
7
7
ms.topic: concept-article
8
-
ms.date: 05/08/2025
8
+
ms.date: 05/12/2025
9
9
ms.author: anfdocs
10
10
---
11
11
12
-
# Requirements and considerations for using cross-region replication
12
+
# Requirements and considerations for Azure NetApp Files cross-region replication
13
13
14
14
This article describes requirements and considerations about [using the volume cross-region replication](cross-region-replication-create-peering.md) functionality of Azure NetApp Files.
15
15
@@ -26,7 +26,7 @@ This article describes requirements and considerations about [using the volume c
26
26
* Azure NetApp Files replication is supported within a subscription and between subscriptions under the same tenant. You must [register this feature](cross-region-replication-create-peering.md#register-for-cross-subscription-replication) before using it for the first time.
27
27
* 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).
28
28
* There can be a delay up to five minutes for the interface to reflect a newly added snapshot on the source volume.
29
-
* Cascading and fan in/out topologies aren't supported.
29
+
* Cascading and fan-in topologies aren't supported. For support of fan-out deployments, see [configure cross-zone-region replication](cross-zone-region-replication-configure.md#requirements).
30
30
* After you set up cross-region replication, the replication process creates *SnapMirror snapshots* to provide references between the source volume and the destination volume. SnapMirror snapshots are cycled automatically when a new one is created for every incremental transfer. You can't delete SnapMirror snapshots until replication relationship and volume is deleted.
31
31
* You can't mount a dual-protocol volume until you [authorize replication from the source volume](cross-region-replication-create-peering.md#authorize-replication-from-the-source-volume) and the initial [transfer](cross-region-replication-display-health-status.md#display-replication-status) happens.
32
32
* You can delete manual snapshots on the source volume of a replication relationship when the replication relationship is active or broken, and also after the replication relationship is deleted. You can't delete manual snapshots for the destination volume until the replication relationship is broken.
@@ -38,6 +38,7 @@ This article describes requirements and considerations about [using the volume c
38
38
* If the volume's size exceeds 95% utilization, there's a risk that replication to the destination volume can fail depending on the rate of data changes.
title: Manage cross-zone-region replication for Azure NetApp Files
3
+
description: Describes how to manage disaster recovery by using Azure NetApp Files cross-zone-region replication.
4
+
services: azure-netapp-files
5
+
author: b-ahibbard
6
+
ms.service: azure-netapp-files
7
+
ms.topic: how-to
8
+
ms.date: 05/12/2025
9
+
ms.author: anfdocs
10
+
---
11
+
# Manage cross-zone-region replication for Azure NetApp Files (preview)
12
+
13
+
Azure NetApp Files supports volume cross-zone and cross-region replication on the same source volume.
14
+
15
+
## Requirements
16
+
17
+
- Cross-zone-region replication supports creating two replication relationships for a source volume: cross-zone replication, cross-region replication, or a combination.
18
+
- Cross-zone-region replication volumes must abide by the same requirements and considerations as individual [cross-zone replication](cross-zone-replication-requirements-considerations.md) and [cross-region replication](cross-region-replication-requirements-considerations.md) volumes.
19
+
- You must break the secondary relationship before you can perform a reverse resync operation with cross-zone-region replication. For more information, see [Resync volumes after disaster recovery](cross-region-replication-manage-disaster-recovery.md#resync-replication).
20
+
- Azure NetApp Files replication is supported within a subscription and between subscriptions under the same tenant.
21
+
- Fan-out deployments are supported for two destination volumes: one source (read/write) volume and two destination volumes.
22
+
23
+
>[!NOTE]
24
+
>Data protection is limited to two volumes.
25
+
26
+
## Register for cross-zone-region replication
27
+
28
+
Cross-zone-region replication for Azure NetApp Files is currently in preview. You need to register the feature before using it for the first time. Feature registration may take up to 60 minutes to complete.
> The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is `Registered` before continuing.
You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status.
45
+
46
+
## Configure replication
47
+
48
+
1. On the source volume:
49
+
- **If you're using an existing volume without an availability zone:** [populate it with an availability zone](manage-availability-zone-volume-placement.md#populate-an-existing-volume-with-availability-zone-information).
50
+
- **If you're creating a new volume:** [create it with an availability zone](manage-availability-zone-volume-placement.md#create-a-volume-with-an-availability-zone).
51
+
52
+
1. Under Properties, take note of the source volume’s resource ID. The source volume's resource ID is required to complete the next two steps.
53
+
1. [Create the cross-zone replication destination volume](create-cross-zone-replication.md#create-the-data-replication-volume-in-another-availability-zone-of-the-same-region).
54
+
1. [Create the cross-region replication destination volume](cross-region-replication-create-peering.md#create-the-data-replication-volume-the-destination-volume).
55
+
1. [Authorize data replication from the source volume](cross-region-replication-create-peering.md#authorize-replication-from-the-source-volume).
56
+
1. In the source volume’s menu, select **Replication**. Confirm there are two volumes listed under **Destination volumes**.
57
+
58
+
>[!NOTE]
59
+
>With cross-zone-region replication, you can create a combination of a cross-zone and a cross-region replication relationship, two cross-region replication relationships, or two cross-zone replication relationships. The cross-zone relationship can be within the same zone.
60
+
61
+
:::image type="content" source="./media/cross-zone-region-replication-configure/complete-configuration.png" alt-text="Screenshot of successful configuration." lightbox="./media/cross-zone-region-replication-configure/complete-configuration.png":::
0 commit comments