Can TiDB Backup Data to Another Database in Real-Time Before Deletion?

Translated
1

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

Original topic: TiDB能否将数据库要删除的数据实时备份到另一个数据库

| username: Azzerare

【TiDB Usage Environment】Production Environment
【TiDB Version】6.5.1
【Encountered Problem: Problem Phenomenon and Impact】Previously, the database used triggers to back up deleted data to another database. Now TiDB does not support triggers, and there is too much logic involved, making it impractical to implement with code. TICDC seems to only support incremental synchronization. Is there any good implementation method?

2
| username: redgame | Original post link

No solution…

3
| username: zhanggame1 | Original post link

Without using triggers and without changing the business logic, if the data volume is not large, you can add a trigger to synchronize to MySQL.

4
| username: yiduoyunQ | Original post link

TiCDC to Kafka, consumer consumes delete events.

5
| username: zhanggame1 | Original post link

What about the deleted data? Where can I find it?

6
| username: YuchongXU | Original post link

CDC, data synchronization software

7
| username: DBRE | Original post link

Try pt-archiver.

8
| username: xingzhenxiang | Original post link

pt-archiver can achieve this function, but if the data volume is too large, you need to test whether it meets the requirements.

9
| username: system | Original post link

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