Skip to content

Commit 2753b91

Browse files
v-regandownerv-regandowner
authored
Merge pull request #298974 from b-ahibbard/crr-troubleshoot
Crr troubleshoot
2 parents 0b0a17b + 0206ba4 commit 2753b91

File tree

1 file changed

+34
-27
lines changed

1 file changed

+34
-27
lines changed

‎articles/azure-netapp-files/troubleshoot-cross-region-replication.md

Lines changed: 34 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
55
author: b-hchen
66
ms.service: azure-netapp-files
77
ms.topic: troubleshooting
8-
ms.date: 08/02/2022
8+
ms.date: 04/28/2025
99
ms.author: anfdocs
1010
---
1111
# Troubleshoot cross-region replication errors
@@ -14,63 +14,70 @@ This article describes error messages and resolutions that can help you troubles
1414

1515
## Errors creating replication
1616

17-
| Error Message | Resolution |
17+
| Error message | Resolution |
1818
|-|-|
19-
| `Volume {0} cannot be used as source because it is already in replication` | You cannot create a replication with a source volume that is already in a data replication relationship. |
20-
| `Peered region '{0}' is not accepted` | You are attempting to create a replication between un-peered regions. |
21-
| `RemoteVolumeResource '{0}' of wrong type '{1}'` | Validate that the remote resource ID is a volume resource ID. |
19+
| `Volume {0} cannot be used as source because it is already in replication` | You cab't create a replication with a source volume that is already in a data replication relationship. |
20+
| `Peered region '{0}' is not accepted` | You can't create replication between unpaired regions. Review [supported regional pairs](cross-region-replication-introduction.md#supported-region-pairs). |
21+
| `RemoteVolumeResource '{0}' of wrong type '{1}'` | Validate that the remote resource ID is a volume resource ID. |
2222

2323
## Errors authorizing volume
2424

25-
| Error Message | Resolution |
25+
| Error message | Resolution |
2626
|-|-|
27-
| `Missing value for 'AuthorizeSourceReplication'` | The `RemoteResourceID` is missing or invalid from the UI or API request (fix error message). |
28-
| `Missing value for 'RemoteVolumeResourceId'` | The `RemoteResourceID` is missing or invalid from the UI or API request. |
29-
| `Data Protection volume not found for RemoteVolumeResourceId: {remoteResourceId}` | Validate if `RemoteResourceID` is correct or exists for the user. |
30-
| `Remote volume '{0}' is not configured for replication` | Destination volume is not a data protection volume. |
31-
| `Remote volume '{0}' does not have source volume '{1}' as RemoteVolumeResourceId` | Data protection volume does not have this source volume in its remote resource ID (wrong source ID was entered). |
32-
| `The destination volume replication creation failed (message: {0})` | This error indicates a server error. Contact Support. |
27+
| `Missing value for 'AuthorizeSourceReplication'` | The `RemoteResourceID` is missing or invalid from the UI or API request (fix error message). |
28+
| `Missing value for 'RemoteVolumeResourceId'` | The `RemoteResourceID` is missing or invalid from the UI or API request. |
29+
| `Data Protection volume not found for RemoteVolumeResourceId: {remoteResourceId}` | Validate if `RemoteResourceID` is correct or exists for the user. |
30+
| `Remote volume '{ }' is not configured for replication` | Destination volume isn't a data protection volume. |
31+
| `Remote volume '{0}' does not have source volume '{1}' as RemoteVolumeResourceId` | Data protection volume doesn't have this source volume in its remote resource ID (wrong source ID was entered). |
32+
| `The destination volume replication creation failed (message: {0})` | This error indicates a server error. Contact Support. |
33+
34+
## Error reinitializing replication
35+
36+
| Error message | Resolution |
37+
|-|-|
38+
| `Replication reinitialization is not possible as it is currently being initialized. The initialization time depends on the amount of data being replicated. If you believe the process is stuck or taking too long, please contact support for assistance.` | Replication is being reinitialized and the initial transfer is in process. Learn more about the [health status](cross-region-replication-display-health-status.md) of the replication relationship. |
39+
3340

3441
## Error breaking replication
3542

36-
| Error Message | Resolution |
43+
| Error message | Resolution |
3744
|-|-|
38-
| `‘Not able to break a volume replication in an uninitialized state.` | Use re-initialize endpoint to get replication in initialized state or delete the replication and try again. |
45+
| `‘Not able to break a volume replication in an uninitialized state.` | Reinitialize the endpoint to return replication to an initialized state or delete the replication and try again. |
3946

4047
## Errors deleting replication
4148

42-
| Error Message | Resolution |
49+
| Error message | Resolution |
4350
|-|-|
44-
| `Replication cannot be deleted, mirror state needs to be in status: Broken before deleting` | Validate that either replication has been broken or it is uninitialized and idle (failed initialization). |
45-
| `Cannot delete source replication` | Deleting the replication from the source side is not allowed. Make sure that you are deleting the replication from the destination side. |
51+
| `Replication cannot be deleted, mirror state needs to be in status: Broken before deleting` | Validate that either replication has been broken or it's uninitialized and idle (failed initialization). |
52+
| `Cannot delete source replication` | Deleting the replication from the source side is not allowed. Make sure that you're deleting the replication from the destination side. |
4653
| Deleting replication in uninitialized state and transferring relationship status: <br> `Replication cannot be deleted while relationship status is transferring.` | Wait until replication is idle and try again. |
47-
| `Replication cannot be deleted while in Mirrored state` | Break the replication relationship before proceeding. See [Delete volume replications or volumes](cross-region-replication-delete.md). |
54+
| `Replication cannot be deleted while in Mirrored state` | Break the replication relationship before proceeding. See [Delete volume replications or volumes](cross-region-replication-delete.md). |
4855

4956
## Errors deleting volume
5057

51-
| Error Message | Resolution |
58+
| Error message | Resolution |
5259
|-|-|
5360
| `Volume is a member of an active volume replication relationship` | Delete replication before deleting the volume. See [Delete replications](cross-region-replication-delete.md). This operation requires that you break the peering before deleting the replication for the volume. |
5461
| `Volume with replication cannot be deleted` | Delete replication before deleting the volume. See [Delete replications](cross-region-replication-delete.md). This operation requires that you break the peering before deleting the replication for the volume.
5562

56-
## Errors resyncing volume
63+
## Error resyncing volume
5764

58-
| Error Message | Resolution |
65+
| Error message | Resolution |
5966
|-|-|
60-
| `Volume Replication is in invalid status: (Mirrored|Uninitialized) for operation: 'ResyncReplication'` | Validate that volume replication is in state "broken”. |
67+
| `Volume replication is in invalid status: (Mirrored|Uninitialized) for operation: 'ResyncReplication'` | Confirm the volume's replication state is "broken." |
6168

6269
## Errors deleting snapshot
6370

64-
| Error Message | Resolution |
71+
| Error message | Resolution |
6572
|-|-|
66-
| `Snapshot cannot be deleted, parent volume is a Data Protection volume with a replication object` | Validate that you have broken the volume's replication if you want to delete this snapshot. |
67-
| `Cannot delete volume replication generated snapshot` | Deletion of replication baseline snapshots is not allowed. |
73+
| `Snapshot cannot be deleted, parent volume is a data protection volume with a replication object` | Validate that you've broken the volume's replication if you want to delete this snapshot. |
74+
| `Cannot delete volume replication generated snapshot` | Deleting replication baseline snapshots isn't allowed. |
6875

6976
## Errors resizing volumes
7077

71-
| Error Message | Resolution |
78+
| Error message | Resolution |
7279
|-|-|
73-
| Attempt to resize a source volume is failing with the error `"PoolSizeTooSmall","message":"Pool size too small for total volume size."` | Ensure that you have enough headroom in the capacity pools for both the source and the destination volumes of cross-region replication. When you resize the source volume, the destination volume is automatically resized. But if the capacity pool hosting the destination volume doesn’t have enough headroom, the resizing of both the source and the destination volumes will fail. See [Resize a cross-region replication destination volume](azure-netapp-files-resize-capacity-pools-or-volumes.md#resize-a-cross-region-replication-destination-volume) for details. |
80+
| Attempt to resize a source volume is failing with the error `"PoolSizeTooSmall","message":"Pool size too small for total volume size."` | Ensure you have enough space available in the capacity pools for both the source and the destination volumes of cross-region replication. When you resize the source volume, the destination volume is automatically resized. If the capacity pool hosting the destination volume doesn’t have enough available space, resizing both the source and the destination volumes will fail. See [Resize a cross-region replication destination volume](azure-netapp-files-resize-capacity-pools-or-volumes.md#resize-a-cross-region-replication-destination-volume) for details. |
7481

7582
## Next steps
7683

0 commit comments

Comments
 (0)