【BR】Backing up tables with global indexes will miss the global indexes, resulting in inconsistent checksum #57469
Description
Bug Report
Backing up tables with global indexes will miss the global indexes, resulting in inconsistent checksum.
[2024/11/18 17:10:01.936 +08:00] [WARN] [backup.go:311] ["setting `--ratelimit` and `--concurrency` at the same time, ignoring `--concurrency`: `--ratelimit` forces sequential (i.e. concurrency = 1) backup"] [ratelimit=268.4MB/s] [concurrency-specified=4]
Database Backup <----------------------------------------------------------------------------------------------------------------------> 100.00%
Checksum <-----------------------------------------------------------------------------------------------------------------------------> 100.00%
[2024/11/18 17:10:06.026 +08:00] [INFO] [collector.go:77] ["Database Backup failed summary"] [total-ranges=6] [ranges-succeed=6] [ranges-failed=0] [backup-checksum=46.146682ms] [backup-fast-checksum=9.151047ms] [backup-total-regions=42] [backup-total-ranges=42]
Error: [BR:Backup:ErrBackupChecksumMismatch]backup checksum mismatch
1. Minimal reproduce step (Required)
- create table with global index
- insert 1 row into table
- backup full/db table
2. What did you expect to see? (Required)
checksum successfully
3. What did you see instead (Required)
[2024/11/18 17:10:06.026 +08:00] [INFO] [collector.go:77] ["Database Backup failed summary"] [total-ranges=6] [ranges-succeed=6] [ranges-failed=0] [backup-checksum=46.146682ms] [backup-fast-checksum=9.151047ms] [backup-total-regions=42] [backup-total-ranges=42]
Error: [BR:Backup:ErrBackupChecksumMismatch]backup checksum mismatch
4. What is your TiDB version? (Required)
cluster :v8.4.0
br :v8.4.0
command
tiup br:v8.4.0 backup db --db="xxxx" --pd "pd-peer:2379" --storage "s3://xxxx/xxxx" --send-credentials-to-tikv=true --s3.endpoint=http://xxx.xxx.xxx:xxx/ --ratelimit 256 --log-file /tiup/backuptable.log