Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

br: change the compatibility table #12529

Merged
merged 3 commits into from
Feb 20, 2023
Merged

br: change the compatibility table #12529

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a0cfa53
br: change the compatibility table
shichun-0415 Feb 16, 2023
40f29e4
Update backup-and-restore-overview.md
shichun-0415 Feb 16, 2023
a4779e1
sync from chinese
shichun-0415 Feb 16, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 8 additions & 9 deletions br/backup-and-restore-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -121,15 +121,14 @@ Backup and restore might go wrong when some TiDB features are enabled or disable

Before performing backup and restore, BR compares and checks the TiDB cluster version with its own. If there is a major-version mismatch, BR prompts a reminder to exit. To forcibly skip the version check, you can set `--check-requirements=false`. Note that skipping the version check might introduce incompatibility.

| Backup version (vertical) \ Restore version (horizontal) | Restore to TiDB v6.0 | Restore to TiDB v6.1 | Restore to TiDB v6.2 | Restore to TiDB v6.3 | Restore to TiDB v6.4 | Restore to TiDB v6.5 |
| ---- | ---- | ---- | ---- | ---- | ---- | ---- |
| TiDB v6.0 snapshot backup | Compatible | Compatible | Compatible | Compatible | Compatible | Compatible |
| TiDB v6.1 snapshot backup | Compatible (A known issue [#36379](https://github.com/pingcap/tidb/issues/36379): if backup data contains an empty schema, BR might report an error.) | Compatible | Compatible | Compatible | Compatible | Compatible |
| TiDB v6.2 snapshot backup | Compatible (A known issue [#36379](https://github.com/pingcap/tidb/issues/36379): if backup data contains an empty schema, BR might report an error.) | Compatible | Compatible | Compatible | Compatible | Compatible |
| TiDB v6.3 snapshot backup | Compatible (A known issue [#36379](https://github.com/pingcap/tidb/issues/36379): if backup data contains an empty schema, BR might report an error.) | Compatible | Compatible | Compatible | Compatible | Compatible |
| TiDB v6.3 log backup | N/A | N/A | Incompatible | Compatible | Compatible | Compatible |
| TiDB v6.4 log backup | N/A | N/A | Incompatible | Compatible | Compatible | Compatible |
| TiDB v6.5 log backup | N/A | N/A | Incompatible | Compatible | Compatible | Compatible |
> **Note:**
>
> When performing backup and restore, it is recommended that the BR and TiDB cluster are of the same version.

| Backup version (vertical) \ Restore version (horizontal) | Restore to TiDB v6.0 | Restore to TiDB v6.1 | Restore to TiDB v6.2 | Restore to TiDB v6.3, v6.4, or v6.5 | Restore to TiDB v6.6 |
| ---- | ---- | ---- | ---- | ---- | ---- |
| TiDB v6.0, v6.1, v6.2, v6.3, v6.4, or v6.5 snapshot backup | Compatible (known issue [#36379](https://github.com/pingcap/tidb/issues/36379): if backup data contains an empty schema, BR might report an error.) | Compatible | Compatible | Compatible | Compatible (BR must be v6.6 or later) |
| TiDB v6.3, v6.4, v6.5, or v6.6 log backup| Incompatible | Incompatible | Incompatible | Compatible | Compatible |

## See also

Expand Down