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-requirements-considerations.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,12 +29,12 @@ This article describes requirements and considerations about [using the volume c
29
29
* Azure NetApp Files replication does not currently support multiple subscriptions; all replications must be performed under a single subscription.
30
30
* 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).
31
31
* There can be a delay up to five minutes for the interface to reflect a newly added snapshot on the source volume.
32
-
* Cascading and fan in/out topologies are not supported.
33
-
* Configuring volume replication for source volumes created from snapshot is not supported at this time.
34
-
* 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 cannot delete snapmirror snapshots until replication relationship and volume is deleted.
35
-
* 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.
36
-
* 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 the replication relationship is broken.
37
-
* You can revert a source or destination volume of a cross-region replication to a snapshot, provided the snapshot is newer than the most recent snapmirror snapshot. Snapshots older than the snapmirror snapshot cannot be used for a volume revert operation. To take advantage of this feature, you must enroll in the public preview. See [Revert a volume using snapshot revert using Azure NetApp Files](snapshots-revert-volume.md) for more information.
32
+
* Cascading and fan in/out topologies aren't supported.
33
+
* Configuring volume replication for source volumes created from snapshot isn't supported at this time.
34
+
* 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.
35
+
* 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.
36
+
* 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.
37
+
* You can revert a source or destination volume of a cross-region replication to a snapshot, provided the snapshot is newer than the most recent SnapMirror snapshot. Snapshots older than the SnapMirror snapshot can't be used for a volume revert operation. To take advantage of this feature, you must enroll in the public preview. For more information, se [Revert a volume using snapshot revert](snapshots-revert-volume.md).
0 commit comments