br 恢复的是提示 the config 'new_collation_enabled' not match

【TiDB 使用环境】测试/ Poc
【TiDB 版本】 从tidb 到 Tidb

[tidb@msyql8-ocp tidb]$ 
[tidb@msyql8-ocp tidb]$ tiup br restore full  \
> --pd "192.168.2.82:2379" \
>     --filter 'pingcap.order_line'  \
> --filter 'pingcap.stock'  \
> --filter 'pingcap.customer'  \
> --filter 'pingcap.orders'  \
> --filter 'pingcap.history'  \
> --filter 'pingcap.new_order'  \
> --filter 'pingcap.item'  \
> --filter 'pingcap.district'  \
> --filter 'pingcap.warehouse'  \
> --ratelimit 128  \
> -s "local:///tidb/backup/pingcap" \
>     --log-file /tidb/backup/pingcap/restore_pingcap_1030.log \
> --check-requirements=false
Starting component br: /home/tidb/.tiup/components/br/v7.5.4/br restore full --pd 192.168.2.82:2379 --filter pingcap.order_line --filter pingcap.stock --filter pingcap.customer --filter pingcap.orders --filter pingcap.history --filter pingcap.new_order --filter pingcap.item --filter pingcap.district --filter pingcap.warehouse --ratelimit 128 -s local:///tidb/backup/pingcap --log-file /tidb/backup/pingcap/restore_pingcap_1030.log --check-requirements=false
Detail BR log in /tidb/backup/pingcap/restore_pingcap_1030.log 
[2025/10/30 15:24:23.578 +08:00] [INFO] [collector.go:77] ["Full Restore failed summary"] [total-ranges=0] [ranges-succeed=0] [ranges-failed=0]
Error: the config 'new_collation_enabled' not match, upstream:False, downstream: True: [BR:Common:ErrUnknown]internal error
[tidb@msyql8-ocp tidb]$ 
[tidb@msyql8-ocp tidb]$ 

###上游tidb的 new_collation_enabled = False
###下游采用playground 做的临时环境 ,默认 new_collation_enabled = True ,

根据 备份恢复的FAQ的说法,需要上下游数据库参数值一样才会恢复成功。
现在想着修改下游tidb的参数,如何修改才生效呢, 测试了好多次不成功,

https://docs.pingcap.com/zh/tidb/stable/backup-and-restore-faq/#恢复时为什么会报-new_collation_enabled-不匹配

修改了playground的参数

[tidb@msyql8-ocp ~]$ cat tidb_bootstrap.toml
new_collations_enabled_on_first_bootstrap = false
[tidb@msyql8-ocp ~]$ 

[tidb@msyql8-ocp ~]$ 
[tidb@msyql8-ocp ~]$ tiup --tag downstream playground --host 192.168.2.82 --db 1 --pd 1 --kv 1 --tiflash 0 --ticdc 0  --db.config=/home/tidb/tidb_bootstrap.toml

Note: Version constraint  is resolved to v8.5.2. If you'd like to use other versions:

    Use exact version:      tiup playground v7.1.0
    Use version range:      tiup playground ^5
    Use nightly:            tiup playground nightly

Start pd instance: v8.5.2
Start tikv instance: v8.5.2
Start tidb instance: v8.5.2
Waiting for tidb instances ready
- TiDB: 192.168.2.82:4000 ... Done

🎉 TiDB Playground Cluster is started, enjoy!

Connect TiDB:    mysql --comments --host 192.168.2.82 --port 4000 -u root
TiDB Dashboard:  http://192.168.2.82:2379/dashboard
Grafana:         http://192.168.2.82:3000

[tidb@msyql8-ocp ~]$ ./connect_tidb.sh 
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MySQL connection id is 1742733318
Server version: 8.0.11-TiDB-v8.5.2 TiDB Server (Apache License 2.0) Enterprise Edition, MySQL 8.0 compatible

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MySQL [(none)]> show config where name = 'new_collations_enabled_on_first_bootstrap';
+------+-------------------+-------------------------------------------+-------+
| Type | Instance          | Name                                      | Value |
+------+-------------------+-------------------------------------------+-------+
| tidb | 192.168.2.82:4000 | new_collations_enabled_on_first_bootstrap | false |
+------+-------------------+-------------------------------------------+-------+
1 row in set (0.54 sec)

MySQL [(none)]> select *  from mysql.tidb;
+--------------------------+---------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------+
| VARIABLE_NAME            | VARIABLE_VALUE                                                                              | COMMENT                                                                                     |
+--------------------------+---------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------+
| bootstrapped             | True                                                                                        | Bootstrap flag. Do not delete.                                                              |
| tidb_server_version      | 220                                                                                         | Bootstrap version. Do not delete.                                                           |
| system_tz                | Asia/Shanghai                                                                               | TiDB Global System Timezone.                                                                |
| new_collation_enabled    | False                                                                                       | If the new collations are enabled. Do not edit it.                                          |
| ddl_table_version        | 4                                                                                           | DDL Table Version. Do not delete.                                                           |
| tikv_gc_leader_uuid      | 668d0d2f3b40009                                                                             | Current GC worker leader UUID. (DO NOT EDIT)                                                |
| tikv_gc_leader_desc      | host:msyql8-ocp, pid:12889, start at 2025-10-30 16:21:02.876454764 +0800 CST m=+8.134194365 | Host name and pid of current GC leader. (DO NOT EDIT)                                       |
| tikv_gc_leader_lease     | 20251030-16:23:02.926 +0800                                                                 | Current GC worker leader lease. (DO NOT EDIT)                                               |
| tikv_gc_auto_concurrency | true                                                                                        | Let TiDB pick the concurrency automatically. If set false, tikv_gc_concurrency will be used |
| tikv_gc_enable           | true                                                                                        | Current GC enable status                                                                    |
| tikv_gc_run_interval     | 10m0s                                                                                       | GC run interval, at least 10m, in Go format.                                                |
| tikv_gc_life_time        | 10m0s                                                                                       | All versions within life time will not be collected by GC, at least 10m, in Go format.      |
| tikv_gc_last_run_time    | 20251030-16:21:02.929 +0800                                                                 | The time when last GC starts. (DO NOT EDIT)                                                 |
| tikv_gc_safe_point       | 20251030-16:11:02.929 +0800                                                                 | All versions after safe point can be accessed. (DO NOT EDIT)                                |
+--------------------------+---------------------------------------------------------------------------------------------+---------------------------------------------------------------------------------------------+
14 rows in set (0.01 sec)

MySQL [(none)]> 
[tidb@msyql8-ocp ~]$ tiup br restore full  --pd "192.168.2.82:2379"     --filter 'pingcap.order_line'  --filter 'pingcap.stock'  --filter 'pingcap.customer'  --filter 'pingcap.orders'  --filter 'pingcap.history'  --filter 'pingcap.new_order'  --filter 'pingcap.item'  --filter 'pingcap.district'  --filter 'pingcap.warehouse'  --ratelimit 128  -s "local:///tidb/backup/pingcap"     --log-file /tidb/backup/pingcap/restore_pingcap_1030.log --check-requirements=false
Starting component br: /home/tidb/.tiup/components/br/v8.5.2/br restore full --pd 192.168.2.82:2379 --filter pingcap.order_line --filter pingcap.stock --filter pingcap.customer --filter pingcap.orders --filter pingcap.history --filter pingcap.new_order --filter pingcap.item --filter pingcap.district --filter pingcap.warehouse --ratelimit 128 -s local:///tidb/backup/pingcap --log-file /tidb/backup/pingcap/restore_pingcap_1030.log --check-requirements=false
Detail BR log in /tidb/backup/pingcap/restore_pingcap_1030.log 
Full Restore <-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------> 100.00%
[2025/10/30 16:26:46.058 +08:00] [INFO] [collector.go:77] ["Full Restore success summary"] [total-ranges=27] [ranges-succeed=27] [ranges-failed=0] [restore-ranges=15] [total-take=20.192767784s] [RestoreTS=461848651033214977] [total-kv=6285491] [total-kv-size=1.024GB] [average-speed=50.69MB/s] [restore-data-size(after-compressed)=447MB] [Size=447032091] [BackupTS=461846373732712455]
[tidb@msyql8-ocp ~]$ 

测试部署一个单机集群并不比用playground麻烦,建议装个单机版

下游的集群要重建 new_collation_enabled = False 才行

如果源new_collation_enabled是false,目标设置下false就可以

除了架构。我们还需要SQL底层原理

对于开发,我们要写好sql

sql兼容是王道

pingcap.warehouse

单 机版好一些

欢迎提供解决办法

部个虚拟化本地集群吧,更接近生产环境,测起来也方便

就是参数设置的问题,我的贴子上有方法

学习了

多谢分享,这个是什么版本的?