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-zone-replication-requirements-considerations.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ ms.service: azure-netapp-files
12
12
ms.workload: storage
13
13
ms.tgt_pltfrm: na
14
14
ms.topic: conceptual
15
-
ms.date: 12/16/2022
15
+
ms.date: 02/23/2023
16
16
ms.author: anfdocs
17
17
---
18
18
# Requirements and considerations for using cross-zone replication
@@ -22,22 +22,22 @@ This article describes requirements and considerations about [using the volume c
22
22
## Requirements and considerations
23
23
24
24
* The cross-zone replication feature uses the [availability zone volume placement feature](use-availability-zones.md) of Azure NetApp Files.
25
-
* You can only use cross-zone replication in regions where the availability zone volume placement is supported. [!INCLUDE [Azure NetApp Files cross-zone-replication supported regions](includes/cross-zone-regions.md)]
25
+
* You can only use cross-zone replication in regions that support the availability zone volume placement. [!INCLUDE [Azure NetApp Files cross-zone-replication supported regions](includes/cross-zone-regions.md)]
26
26
* To establish cross-zone replication, you must create the source volume in an availability zone.
27
27
* You can’t use cross-zone replication and cross-region replication together on the same source volume.
28
28
* You can use cross-zone replication with SMB and 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 zone. For more information, see [Requirements for Active Directory connections](create-active-directory-connections.md#requirements-for-active-directory-connections).
29
29
* The destination account must be in a different zone from the source volume zone. You can also select an existing NetApp account in a different zone.
30
-
* The replication destination volume is read-only until you fail over to the destination zone to enable the destination volume for read and write. For more information about the failover process, refer to[fail over to the destination volume](cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume).
30
+
* The replication destination volume is read-only until you fail over to the destination zone to enable the destination volume for read and write. For more information about the failover process, see[fail over to the destination volume](cross-region-replication-manage-disaster-recovery.md#fail-over-to-destination-volume).
31
31
* Azure NetApp Files replication doesn't currently support multiple subscriptions; all replications must be performed under a single subscription.
32
32
* See [resource limits](azure-netapp-files-resource-limits.md) for the maximum number of cross-zone 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).
33
33
* There can be a delay up to five minutes for the interface to reflect a newly added snapshot on the source volume.
34
-
*Cascading and fan in/out topologies aren't supported.
35
-
*Configuring volume replication for source volumes created from snapshot isn't supported at this time.
34
+
*Cross-zone replication does not support cascading and fan in/out topologies.
35
+
*At this time, you can't configure volume replication for source volumes created from snapshot with cross-zone replication.
36
36
* After you set up cross-zone 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 cannot delete SnapMirror snapshots until you delete the replication relationship and volume.
37
37
* You cannot 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.
38
-
* 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 cannot delete manual snapshots for the destination volume until you break the replication relationship.
39
-
* You can't revert a source or destination volume of cross-zone replication to a snapshot. The snapshot revert functionality is greyed out for volumes in a replication relationship.
40
-
*[Large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) (larger than 100 TiB) are not currently supported with cross-zone replication.
38
+
* You can delete manual snapshots on the source volume of a replication relationship when the replication relationship is active or broken, and also after you've deleted replication relationship. You cannot delete manual snapshots for the destination volume until you break the replication relationship.
39
+
* You can't revert a source or destination volume of cross-zone replication to a snapshot. The snapshot revert functionality is unavailable out for volumes in a replication relationship.
40
+
*You can't currently use cross-zone replication with [large volumes](azure-netapp-files-understand-storage-hierarchy.md#large-volumes) (larger than 100 TiB).
0 commit comments