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/migrate/troubleshoot-changed-block-tracking-replication.md
+5-17Lines changed: 5 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,25 +28,13 @@ You might occasionally see replication cycles failing for a VM. These failures c
28
28
29
29
Use the following steps to monitor the replication status for your virtual machines:
30
30
31
-
1. Go to the **Servers, databases and web apps** page in Azure Migrate on the Azure portal.
32
-
33
-
:::image type="content" source="./media/troubleshoot-changed-block-tracking-replication/Overview.png" alt-text="Screenshot of the Get started screen of Azure Migrate.":::
31
+
1. Go to the **Execute>Migrations** page in Azure Migrate on the Azure portal.
32
+
33
+
2. You'll see a list of servers in execution stage along with information about stage, status. The **Execution stage** column indicates the current migration stage of the VM (Preparation, Testing & Completion). The **Execution status** column shows the current status of the VM (In progress, In error, Action pending & Completed). [Learn more](end-to-end-portal-experience-server-migrations.md#track-migrations) about Execution stage and Execution status.
34
34
35
-
1. In the **Migration and modernization**tile, under **Replications**, select the number next to **Azure VM**.
35
+
3. In **Execution status**column, click on any VM with **In error** status to open the detailed migration job pane. Then, click on the error link to view the detailed error message and related remediation guidance for the same.
36
36
37
-
:::image type="content" source="./media/troubleshoot-changed-block-tracking-replication/replicating-servers.png" alt-text="Screenshot of the Migration and Modernization screen.":::
38
-
39
-
1. You'll see a list of replicating servers along with additional information such as status, health, last sync time, etc. The **Replication health** column indicates the current replication health of the VM. A *Critical* or *Warning* value typically indicates that the previous replication cycle for the VM failed. To get more details, right-click on the VM, and select **Health error Details**. The **Error Details** page contains information on the error and additional details on how to troubleshoot.
40
-
41
-
:::image type="content" source="./media/troubleshoot-changed-block-tracking-replication/health-error-details.png" alt-text="Screenshot of Health error details option in the Replication machines screen.":::
42
-
43
-
1. Select **Recent Events** to see the previous replication cycle failures for the VM. In the events page, look for the most recent event of type *Replication cycle failed* or *Replication cycle failed* for disk" for the VM.
44
-
45
-
:::image type="content" source="./media/troubleshoot-changed-block-tracking-replication/recent-events.png" alt-text="Screenshot of Recent Events option.":::
46
-
47
-
1. Select the event to understand the possible causes of the error and recommended remediation steps. Use the information provided to troubleshoot and remediate the error.
48
-
49
-
:::image type="content" source="./media/troubleshoot-changed-block-tracking-replication/error-details.png" alt-text="Screenshot of error message in the Error details screen.":::
0 commit comments