Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.
Original topic: 从5.4.1 使用br导入数据库6.5.0 报错如下
[TiDB Usage Environment] Test/PoC
[TiDB Version] 6.5.0
Encountered an error related to new features when using BR to export data from 5.4.1 to 6.5.0. Are there any solutions for this?
[Attachment: Screenshot/Log/Monitoring]
New_collation information from the upstream database 5.4.1
Error screenshot from the downstream database 6.5.0
Backup and restore seem to have version requirements, right?
Do not operate across versions.
Option 1:
Upgrade the existing cluster to version 6.0 or above, then import it into the new 6.5.0 cluster.
Option 2:
Create a new 5.x version cluster, import using BR, and then upgrade the cluster to 6.5.0.
We can only use Solution 2. The new_collations_enabled_on_first_bootstrap parameter in the lower version is consistent with the new version, but it doesn’t work after trying.
The default value of tidb_gc_life_time
is 10m, which means that the data deleted within 10 minutes can be restored. If you want to restore the data deleted within 10 minutes, you can set tidb_gc_life_time
to a larger value, such as 24h.
Both clusters have enabled collation support.
If the collations feature was not enabled in version 5.4.1 of the database, will it be automatically enabled after upgrading to 6.5.0? One of my clusters on site did not have it enabled. 
Upgrading from 5.4.1 to 6.5.0, exporting data with BR, and restoring to 6.5.0. The new_collations_enabled_on_first_bootstrap
warning is gone, but a new issue has appeared.
Post this question in a new thread for consultation, and also paste the error message into the new topic.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.