Usage Restrictions of BR in TiDB 301 Training Course

Translated
1

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

Original topic: tidb301培训课程中br使用限制

| username: huanglao2002

Usage limitations of BR:

  • When BR restores to the upstream cluster of TiCDC and Drainer, the restored data cannot be synchronized to the downstream by TiCDC and Drainer.
  • Both the backup cluster and the restore cluster use the same collation (new_collations_enable_on_first_bootstrap).
  • Version compatibility (forcefully skipping version check using -check-requirements=false).
  • Certain features being enabled or disabled can cause changes in the KV format.

Can any expert explain limitations 1 and 4? I didn’t understand them.

2
| username: WalterWj | Original post link

  1. It means that the restored cluster with br, neither ticdc nor drainer will record it. So when synchronizing to the replica, it is equivalent to the replica not having this part of the restored data.

  2. It is estimated that the new collation bootstrap parameter is enabled, or some encoding-related configurations will cause the format to change. Theoretically, the configuration of the backup cluster and the restored cluster should be the same.

3
| username: huanglao2002 | Original post link

After the recovery is complete, can ticdc and drainer be enabled to start a new replication?

4
| username: WalterWj | Original post link

Use br to perform a full backup downstream as well. Generally, when initializing data for master-slave synchronization, both upstream and downstream are fully restored, and then incremental backups are done based on the backup time points.

5
| username: huanglao2002 | Original post link

Thank you, I roughly understand. I’ll do an experiment to test it next time.

6
| username: system | Original post link

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