Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit a5e3182

Browse files
committedNov 5, 2020
image names
1 parent 42c3e86 commit a5e3182

File tree

6 files changed

+5
-5
lines changed

6 files changed

+5
-5
lines changed
 

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -24,15 +24,15 @@ You may occasionally see replication cycles failing for a VM. These failures can
2424
Use the following steps to monitor the replication status for your virtual machines:
2525

2626
1. Go to the Servers page in Azure Migrate on the Azure portal.
27-
![Image 1](./media/troubleshoot-changed-block-tracking-replication/slide-0.png)
27+
![Image 1](./media/troubleshoot-changed-block-tracking-replication/image0.png)
2828
1. Navigate to the "Replicating machines" page by clicking on "Replicating servers" in the Server Migration tile.
29-
![Image 2](./media/troubleshoot-changed-block-tracking-replication/slide-2.png)
29+
![Image 2](./media/troubleshoot-changed-block-tracking-replication/image1.png)
3030
1. You'll see a list of replicating servers along with additional information such as status, health, last sync time, etc. The health column indicates the current replication health of the VM. A 'Critical' or 'Warning' value in the health column typically indicates that the previous replication cycle for the VM failed. To get more details, right-click on the VM, and select "Error Details." The Error Details page contains information on the error and additional details on how to troubleshoot. You'll also see a "Recent Events" link that can be used to navigate to the events page for the VM.
31-
![Image 3](./media/troubleshoot-changed-block-tracking-replication/slide-3.png)
31+
![Image 3](./media/troubleshoot-changed-block-tracking-replication/image2.png)
3232
1. Click "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.
33-
![Image 4](./media/troubleshoot-changed-block-tracking-replication/slide-4.png)
33+
![Image 4](./media/troubleshoot-changed-block-tracking-replication/image3.png)
3434
1. Click on the event to understand the possible causes of the error and recommended remediation steps. Use the information provided to troubleshoot and remediate the error.
35-
![Image 5](./media/troubleshoot-changed-block-tracking-replication/slide-5.png)
35+
![Image 5](./media/troubleshoot-changed-block-tracking-replication/image4.png)
3636

3737
## Common Replication Errors
3838

0 commit comments

Comments
 (0)
Please sign in to comment.