TiDB BR Backup

Translated
1

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

Original topic: TIDB BR备份

| username: MSGJC

After backing up with TIDB’s BR, can you specify the data table to be restored to a temporary table instead of directly overwriting the original table?

2
| username: hey-hoho | Original post link

It can only be restored to a table with the same name. It is best to create a new database for the restoration.

3
| username: MSGJC | Original post link

Is it possible to restore to another TiDB cluster?

4
| username: 长安是只喵 | Original post link

Support restoring to another TiDB cluster.

5
| username: hey-hoho | Original post link

Yes, it is possible.

6
| username: cs58_dba | Original post link

Limitations of Using BR

  1. When BR restores to the upstream cluster of TiCDC/Drainer, the restored data cannot be synchronized to the downstream by TiCDC/Drainer.
  2. The backup cluster and the restore cluster use the same collation (new_collations_enabled_on_first_bootstrap).
  3. Version compatibility (use -check-requirements=false to forcibly skip version checks).
  4. Certain features, when enabled or disabled, can cause changes in the KV format.
7
| username: MSGJC | Original post link

How to specify the TiDB cluster to restore, should the new cluster’s PD address be specified in --pd, or?

8
| username: hey-hoho | Original post link

–pd specifies the pd of the new cluster

9
| username: system | Original post link

This topic will be automatically closed 60 days after the last reply. No new replies are allowed.