Stuck with AWS DMS migration task? We can help you.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.

Today, let us see how our Support Techs resolve this AWS error.

AWS DMS migration task is stuck

AWS DMS tasks are rarely stuck, they can sometimes be slow to progress.

Today, let us see the steps followed by our Support Techs to check if the data from your DMS task migrate from source to target.

Check the status of your AWS DMS task

Use the following steps below to check the status of your DMS task.

1.Firstly, log in to the AWS DMS console.
2.From the navigation pane, choose the Database migration tasks.
3.Then, review the status of your task. The status should be as follows:

• During the full load phase, your task status should be Running.
• During change data capture (CDC) phase or ongoing replication phase of a CDC-only task, your task status should be Replication ongoing.
• Then during a full load and CDC, your task status should be Load complete, replication ongoing.

Monitor Amazon CloudWatch logs

Check the migration task by monitoring the Amazon CloudWatch logs.

1.Firstly, log in to the AWS DMS console.
2.From the navigation pane, choose Database migration tasks, and then select your task.
3.Choose View CloudWatch logs. This redirects you to the AWS CloudWatch console, where you can monitor the logs for your task.

Refresh the table statistics of your DMS task

1.Firstly, log in to the AWS DMS console.
2.From the navigation pane, choose Database migration tasks, and then select your task.
3.Finally, choose Table statistics.

During a full load, you can see an increase in the Full Load rows value and a change in the Load state value.

During ongoing replication (CDC), you can see an increase in DMLs (Inserts, Updates, and Deletes) and DDLs.

Monitor CloudWatch metrics for rows unloading and applying

1. Firstly, log in to the AWS DMS console.
2. From the navigation pane, choose Database migration tasks, and then choose your task.
3. Choose CloudWatch metrics. This action re-directs you to the CloudWatch Console.

During the full load phase of the DMS task, monitor the following metrics using CloudWatch:

1. Choose Full load from the dropdown list in the CloudWatch console.
2. Monitor the FullLoadThroughputRowsSource metric. This metric gives a detailed picture of the rate at which AWS DMS can unload source data into the replication instance during the full load phase.
3. Monitor the FullLoadThroughputRowsTarget. This metric shows the rate at which the rows are leaving the replication instance to commit to the target.

During the CDC phase, monitor the following metrics using CloudWatch:

1. Choose CDC from the drop down list in the CloudWatch console.
2. Monitor the CDCThroughputRowsSource metric. This metric gives a detailed picture of the rate at which changes are captured from the source and moved to the replication instance during the CDC phase.
3. Then, monitor the CDCThroughputRowsTarget. This metric shows the rate at which the changes are moved from the replication instance to the target.
4. Monitor the CDCLatencySource metric. This metric shows the latency between source and replication instance in seconds.
5. Monitor the CDCLatencyTarget metric. This metric shows the latency between replication instance and target in seconds.

[Need help with the process? We’d be happy to assist you]

Conclusion

To conclude, here we saw how our Support Techs resolve when AWS DMS migration task is stuck.