How to Recover DM Synchronized Data When the Upstream Server Crashes?

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: DM同步数据，当上游服务器出现宕机，如何恢复？

| username: AllinTiDB

【TiDB Usage Environment】Production
【TiDB Version】6.1.0
【Encountered Problem】DM synchronization task: the upstream MySQL data source experienced a crash event, causing DM synchronization to pause and unable to recover!!!

EFC8A0C5-9E65-43d7-A381-33BD653E4320
EFC8A0C5-9E65-43d7-A381-33BD653E43201380×656 47.4 KB

2
| username: db_user | Original post link

How long was the downtime?

  1. If the downtime was long and there are no binary backups, then resynchronization is needed.

  2. If the downtime was short and the upstream binary logs are not found but there are binary log backups, you can pull the backups into the dm-worker’s relay-log and then synchronize.

3
| username: AllinTiDB | Original post link

It has been resolved by restoring the position using the binlog meta modification method.

4
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.