You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-netapp-files/troubleshoot-cross-region-replication.md
+24-17Lines changed: 24 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ services: azure-netapp-files
5
5
author: b-hchen
6
6
ms.service: azure-netapp-files
7
7
ms.topic: troubleshooting
8
-
ms.date: 08/02/2022
8
+
ms.date: 04/28/2025
9
9
ms.author: anfdocs
10
10
---
11
11
# Troubleshoot cross-region replication errors
@@ -16,20 +16,27 @@ This article describes error messages and resolutions that can help you troubles
16
16
17
17
| Error Message | Resolution |
18
18
|-|-|
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 cannot 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 un-paired 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. |
22
22
23
23
## Errors authorizing volume
24
24
25
25
| Error Message | Resolution |
26
26
|-|-|
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
+
33
40
34
41
## Error breaking replication
35
42
@@ -41,8 +48,8 @@ This article describes error messages and resolutions that can help you troubles
41
48
42
49
| Error Message | Resolution |
43
50
|-|-|
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 is uninitialized and idle (failed initialization). |
52
+
|`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. |
46
53
| 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
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). |
48
55
@@ -53,24 +60,24 @@ This article describes error messages and resolutions that can help you troubles
53
60
|`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. |
54
61
| `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.
55
62
56
-
## Errors resyncing volume
63
+
## Error resyncing volume
57
64
58
65
| Error Message | Resolution |
59
66
|-|-|
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 volume replication is in state "broken”. |
61
68
62
69
## Errors deleting snapshot
63
70
64
71
| Error Message | Resolution |
65
72
|-|-|
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`| Deletion of replication baseline snapshots is not allowed. |
68
75
69
76
## Errors resizing volumes
70
77
71
78
| Error Message | Resolution |
72
79
|-|-|
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 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. |
0 commit comments