|
| 1 | +--- |
| 2 | +title: Re-establish deleted volume replication relationships in Azure NetApp Files |
| 3 | +description: You can re-establish the replication relationship between volumes. |
| 4 | +services: azure-netapp-files |
| 5 | +author: b-ahibbard |
| 6 | +ms.author: anfdocs |
| 7 | +ms.service: azure-netapp-files |
| 8 | +ms.workload: storage |
| 9 | +ms.topic: how-to |
| 10 | +ms.date: 02/21/2023 |
| 11 | +--- |
| 12 | +# Re-establish deleted volume replication relationships in Azure NetApp Files |
| 13 | + |
| 14 | +Azure NetApp Files allows you to re-establish a replication relationship between two volumes in case you had previously deleted it. You can only re-establish the relationship from the destination volume. |
| 15 | + |
| 16 | +If the destination volume remains operational and no snapshots were deleted, the replication re-establish operation uses the last common snapshot. The operation incrementally synchronizes the destination volume based on the last known good snapshot. A baseline snapshot isn't required. |
| 17 | + |
| 18 | +## Considerations |
| 19 | + |
| 20 | +* You can only re-establish relationships when there's an existing snapshot generated either [manually](azure-netapp-files-manage-snapshots.md) or by a [snapshot policy](snapshots-manage-policy.md). |
| 21 | + |
| 22 | +## Register the feature |
| 23 | + |
| 24 | +The re-establish deleted volume replication relationships capability is currently in preview. If you're using this feature for the first time, you need to register the feature first. |
| 25 | + |
| 26 | +1. Register the feature by running the following commands: |
| 27 | + |
| 28 | + ```azurepowershell-interactive |
| 29 | + Register-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFReestablishReplication |
| 30 | + ``` |
| 31 | +
|
| 32 | +2. Check the status of the feature registration: |
| 33 | +
|
| 34 | + > [!NOTE] |
| 35 | + > The **RegistrationState** may be in the `Registering` state for up to 60 minutes before changing to `Registered`. Wait until the status is `Registered` before continuing. |
| 36 | +
|
| 37 | + ```azurepowershell-interactive |
| 38 | + Get-AzProviderFeature -ProviderNamespace Microsoft.NetApp -FeatureName ANFReestablishReplication |
| 39 | + ``` |
| 40 | +You can also use [Azure CLI commands](/cli/azure/feature) `az feature register` and `az feature show` to register the feature and display the registration status. |
| 41 | +
|
| 42 | +## Re-establish the relationship |
| 43 | +
|
| 44 | +1. From the **Volumes** menu under **Storage service**, select the volume that was formerly the _destination_ volume in the replication relationship you want to restore. Then select the **Replication** tab. |
| 45 | +1. In the **Replication** tab, select the **Re-establish** button. |
| 46 | + :::image type="content" source="./media/reestablish-deleted-volume-relationships/reestablish-button.png" alt-text="Screenshot of volume menu that depicts no existing volume relationships. A red box surrounds the re-establish button." lightbox="./media/reestablish-deleted-volume-relationships/reestablish-button.png"::: |
| 47 | +1. A dropdown list appears with a selection of all volumes that formerly had either a source or destination replication relationship with the selected volume. From the dropdown menu, select the volume you want to reestablish a relationship with. Select **OK** to reestablish the relationship. |
| 48 | + :::image type="content" source="./media/reestablish-deleted-volume-relationships/reestablish-confirm.png" alt-text="Screenshot of a dropdown menu with available volume relationships to restore." lightbox="./media/reestablish-deleted-volume-relationships/reestablish-confirm.png"::: |
| 49 | +
|
| 50 | +## Next steps |
| 51 | +
|
| 52 | +* [Cross-region replication](cross-region-replication-introduction.md) |
| 53 | +* [Requirements and considerations for using cross-region replication](cross-region-replication-requirements-considerations.md) |
| 54 | +* [Display health status of replication relationship](cross-region-replication-display-health-status.md) |
| 55 | +* [Troubleshoot cross-region-replication](troubleshoot-cross-region-replication.md) |
0 commit comments