Requirements and considerations for using cross-region replication

Note the following requirements and considerations about using the volume cross-region replication functionality of Azure NetApp Files:

Requirements and considerations

  • The cross-region replication feature is currently in preview. You need to submit a waitlist request for accessing the feature through the Azure NetApp Files cross-region replication waitlist submission page. Wait for an official confirmation email from the Azure NetApp Files team before using the cross-region replication feature.
  • Azure NetApp Files replication is only available in certain fixed region pairs. See Supported region pairs.
  • SMB volumes are supported along with 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 ADDS Domain Controllers that are reachable from the delegated subnet in the destination region. For more information, see Requirements for Active Directory connections.
  • The destination account must be in a different region from the source volume region. You can also select an existing NetApp account in a different region.
  • The replication destination volume is read-only until you fail over to the destination region to enable the destination volume for read and write.
  • Azure NetApp Files replication does not currently support multiple subscriptions; all replications must be performed under a single subscription.
  • You can set up a maximum of five volumes for replication within a single subscription per region. You can open a support ticket to request for an increase in the default quota of five replication destination volumes (per subscription in a region).
  • There can be a delay up to five minutes for the interface to reflect a newly added snapshot on the source volume.
  • Cascading and fan in/out topologies are not supported.
  • Configuring volume replication for source volumes created from snapshot is not supported at this time.
  • 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.
  • 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.
  • You cannot revert a source or destination volume of cross-region replication to a snapshot. The snapshot revert functionality is greyed out for volumes in a replication relationship.

Next steps