Skip to content

Latest commit

 

History

History
74 lines (55 loc) · 4.79 KB

File metadata and controls

74 lines (55 loc) · 4.79 KB
title Manage cross-zone-region replication for Azure NetApp Files
description Describes how to manage disaster recovery by using Azure NetApp Files cross-zone-region replication.
services azure-netapp-files
author b-ahibbard
ms.service azure-netapp-files
ms.topic how-to
ms.date 12/09/2025
ms.author anfdocs

Manage cross-zone-region replication for Azure NetApp Files

Azure NetApp Files supports volume cross-zone and cross-region replication on the same source volume.

Requirements

  • Cross-zone-region replication supports creating two replication relationships for a source volume: cross-zone replication, cross-region replication, or a combination.
  • Cross-zone-region replication volumes must abide by the same requirements and considerations as individual cross-region and cross-zone replication volumes.
  • You must break and delete 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.
  • Fan-out deployments are supported for two destination volumes: one source (read/write) volume and two destination volumes.

Note

Data protection is limited to two volumes.

Configure replication

  1. On the source volume:

  2. 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.

  3. Create the cross-zone replication destination volume.

  4. Create the cross-region replication destination volume.

  5. Authorize data replication from the source volume.

  6. In the source volume’s menu, select Replication. Confirm there are two volumes listed under Destination volumes.

Note

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.

:::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":::

Next steps