| title | description | services | documentationcenter | author | manager | editor | ms.assetid | ms.service | ms.workload | ms.tgt_pltfrm | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Display health status of Azure NetApp Files replication relationship | Microsoft Docs |
Describes how to view replication status on the source volume or the destination volume of Azure NetApp Files. |
azure-netapp-files |
b-hchen |
azure-netapp-files |
storage |
na |
how-to |
05/16/2022 |
anfdocs |
You can view replication status on the source volume or the destination volume. You can also set alert rules in Azure Monitor to help you monitor the replication status.
-
From either the source volume or the destination volume, select Replication under Storage Service for either volume.
The following information about replication status and health is displayed:
-
End point type – Identifies whether the volume is the source or destination of replication.
-
Health – Displays the health status of the replication relationship.
-
Mirror state – Shows one of the following values:
- Uninitialized:
This is the initial and default state when a peering relationship is created. The state remains uninitialized until the initialization completes successfully. - Mirrored:
The destination volume has been initialized and is ready to receive mirroring updates. - Broken:
This is the state after you break the peering relationship. The destination volume is‘RW’and snapshots are present.
- Uninitialized:
-
Relationship status – Shows one of the following values:
- Idle:
No transfer operation is in progress and future transfers are not disabled. - Transferring:
A transfer operation is in progress and future transfers are not disabled.
- Idle:
-
Replication schedule – Shows how frequently incremental mirroring updates will be performed when the initialization (baseline copy) is complete.
-
Total progress – Shows the total number of cumulative bytes transferred over the lifetime of the relationship. This amount is the actual bytes transferred, and it might differ from the logical space that the source and destination volumes report.
-
Note
Replication relationship shows health status as unhealthy if previous replication jobs are not complete. This status is a result of large volumes being transferred with a lower transfer window (for example, a ten-minute transfer time for a large volume). In this case, the relationship status shows transferring and health status shows unhealthy.
Follow the following steps to create alert rules in Azure Monitor to help you monitor the status of cross-region replication:
- From Azure Monitor, select Alerts.
- From the Alerts window, select the Create dropdown and select Create new alert rule.
- From the Scope tab of the Create an Alert Rule page, select Select scope. The Select a Resource page appears.
- From the Resource tab, find the Volumes resource type.
- From the Condition tab, select Add condition. From there, find a signal called “is volume replication healthy”.
- There you'll see Condition of the relationship, 1 or 0 and the Configure Signal Logic window is displayed.
- To check if the replication is unhealthy:
- Set Operator to
Less than. - Set Aggregation type to
Average. - Set Threshold value to
1. - Set Unit to
Count.
- Set Operator to
- To check if the replication is healthy:
- Set Operator to
Greater than or equal to. - Set Aggregation type to
Average. - Set Threshold value to
1. - Set Unit to
Count.
- Set Operator to
- Select Review + create. The alert rule is ready for use.
:::image type="content" source="../media/azure-netapp-files/alert-config-signal-logic.png" alt-text="Screenshot of the Azure interface that shows the configure signal logic step with a backdrop of the Create alert rule page." lightbox="../media/azure-netapp-files/alert-config-signal-logic.png":::