Skip to content

Commit 8193792

Browse files
committed
spacing
1 parent 7d1362a commit 8193792

File tree

1 file changed

+16
-16
lines changed

1 file changed

+16
-16
lines changed

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

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -14,20 +14,20 @@ 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
|-|-|
1919
| `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. |
2020
| `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). |
2121
| `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 '{ }' is not configured for replication` | Destination volume isn't a data protection volume. |
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. |
3131
| `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). |
3232
| `The destination volume replication creation failed (message: {0})` | This error indicates a server error. Contact Support. |
3333

@@ -40,42 +40,42 @@ This article describes error messages and resolutions that can help you troubles
4040

4141
## Error breaking replication
4242

43-
| Error Message | Resolution |
43+
| Error message | Resolution |
4444
|-|-|
4545
| `‘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. |
4646

4747
## Errors deleting replication
4848

49-
| Error Message | Resolution |
49+
| Error message | Resolution |
5050
|-|-|
5151
| `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. |
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. |
5353
| 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. |
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). |
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). |
5555

5656
## Errors deleting volume
5757

58-
| Error Message | Resolution |
58+
| Error message | Resolution |
5959
|-|-|
6060
| `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. |
6161
| `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.
6262

6363
## Error resyncing volume
6464

65-
| Error Message | Resolution |
65+
| Error message | Resolution |
6666
|-|-|
6767
| `Volume Replication is in invalid status: (Mirrored|Uninitialized) for operation: 'ResyncReplication'` | Confirm volume replication is in state "broken”. |
6868

6969
## Errors deleting snapshot
7070

71-
| Error Message | Resolution |
71+
| Error message | Resolution |
7272
|-|-|
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. |
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. |
7575

7676
## Errors resizing volumes
7777

78-
| Error Message | Resolution |
78+
| Error message | Resolution |
7979
|-|-|
8080
| 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. |
8181

0 commit comments

Comments
 (0)