1 Answer
- Newest
- Most votes
- Most comments
0
Thank you for your question.
You should be able to perform planned database changes, update the binlog path, and resume the database migration task without specifying a start point. However, ensure that the binary logs are available to AWS DMS for processing change data capture (CDC).
Detailed steps on how to change binlog path are outlined as follows:
- Stop the DMS migration task after you have confirmed that the source and target latency are in sync, whenever possible.
- Check current log-bin path and naming format.
show variables like '%log_bin%';
- Change the log-bin path in my.cnf file as below log_bin = new_path/naming_format.
- Shutdown your mysql server.
- Move your bin log files from previous location to new location.
- Star you mysql server.
- From here you will be able to resume DMS migration task.
Moving forward, if you wish to initiate a DMS migration task from a specific point, you can consider using a checkpoint or a CDC start point as a CDC starting point by creating a CDC-only task. For a detailed, step-by-step guide on this concept, please see: https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Task.CDC.html#CHAP_Task.CDC.StartPoint.Checkpoint
Relevant content
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- Why is no data migrated from my Amazon S3 source endpoint even though my AWS DMS task is successful?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago