How to Set Up Full Backup with BR and Incremental Sync with Drainer in TiDB 4.0.7

Translated
1

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

Original topic: br全量+drainer同步增量就行了是如何搭建的 4.0.7

| username: TiDBer_oHSwKxOH

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed that caused the issue
[Encountered Issues: Problem Symptoms and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots / Logs / Monitoring]
Experts, can I just use br for full backup and drainer for incremental synchronization?

2
| username: MrSylar | Original post link

Need to elaborate on what the problem is.

3
| username: xfworld | Original post link

You can choose snapshot backups for the full backup, and use binlog for the incremental part.

However, it is recommended to upgrade to 6.1.x or 6.5.x and use TiCDC to handle the incremental data capture.

4
| username: tidb菜鸟一只 | Original post link

After a full backup with BR, you can obtain a globally consistent timestamp:

COMMIT_TS=`br validate decode --field="end-version" -s local:///home/tidb/backupdata | tail -n1`

Drainer can start syncing from the specified timestamp in the configuration file:

initial-commit-ts = COMMIT_TS
5
| username: redgame | Original post link

BR full backup is used to back up the data from the source database to the target TiDB cluster, while Drainer is used to synchronize incremental changes from the source database to the target TiDB cluster in real-time.