Skip to content

Commit cdb7036

Browse files
Merge pull request #314704 from Dhananjayanr98/patch-47
Update troubleshoot-changed-block-tracking-replication.md
2 parents d784a2c + 3a5de73 commit cdb7036

1 file changed

Lines changed: 5 additions & 17 deletions

File tree

articles/migrate/troubleshoot-changed-block-tracking-replication.md

Lines changed: 5 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -28,25 +28,13 @@ You might occasionally see replication cycles failing for a VM. These failures c
2828

2929
Use the following steps to monitor the replication status for your virtual machines:
3030

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.
3434

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.
3636

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.":::
37+
5038

5139
## Common Replication Errors
5240

0 commit comments

Comments
 (0)