Skip to content

Commit 7b043dd

Browse files
committed
update replication topic
1 parent 7083a9b commit 7b043dd

File tree

1 file changed

+10
-4
lines changed

1 file changed

+10
-4
lines changed

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

Lines changed: 10 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5,18 +5,24 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: how-to
8-
ms.date: 02/23/2023
8+
ms.date: 12/17/2024
99
ms.author: anfdocs
1010
---
1111
# Create volume replication for Azure NetApp Files
1212

13-
This article shows you how to set up cross-region replication by creating replication peering.
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).
1414

1515
Setting up replication peering enables you to asynchronously replicate data from an Azure NetApp Files volume (source) to another Azure NetApp Files volume (destination). The source volume and the destination volume must be deployed in separate regions. The service level for the destination capacity pool can match that of the source capacity pool, or you can select a different service level.
1616

17-
Azure NetApp Files replication does not currently support multiple subscriptions; all replications must be performed under a single subscription.
17+
## Considerations
18+
19+
* During normal operations, the destination volume in an Azure NetApp Files replication relationship is available for read-only access. The destination volume becomes available for read-write when the replication is stopped. Any subsequent changes to the destination volume need to be synchronized with the source volume by performing a reverse-resync. After the reverse-resync, normal replication can be resumed. For more information, see [Manage disaster recovery using Azure NetApp Files](cross-region-replication-manage-disaster-recovery.md).
20+
* You can establish replication between different subscriptions under the same tenant ID. Replication across tenants isn't supported.
21+
* Replication between capacity pools with different service levels (for example, Premium and Ultra) is supported. You can move volumes to a different capacity pool without interruption to replication.
22+
23+
>[!IMPORTANT]
24+
>Review the [requirements and considerations for cross-region replication](cross-region-replication-requirements-considerations.md) before establishing replication.
1825
19-
Before you begin, ensure that you have reviewed the [requirements and considerations for using cross-region replication](cross-region-replication-requirements-considerations.md).
2026

2127
## Locate the source volume resource ID
2228

0 commit comments

Comments
 (0)