Incomplete Data Recovery in DM

Translated
1

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

Original topic: DM恢复数据不全

| username: TiDBer_ryXbUL9o

【TiDB Usage Environment】Production
【TiDB Version】v6.1
【Encountered Problem】Source database MySQL 5.7, binlog logs are saved for 10 days. When using DM for recovery, it was found that only part of the data was restored.

2
| username: xiaohetao | Original post link

Is there an error log?

3
| username: Tank001 | Original post link

Do you have logs?

4
| username: buchuitoudegou | Original post link

Could you also send the task configuration? As I understand it, using DM for recovery is a full import rather than an incremental import, right?

5
| username: Hacker007 | Original post link

You read the binlog, which indicates incremental data. You need to confirm whether the offset is at the position of the last consumption. For your situation, it might be better to either recover or delete and reconstruct a full task.