【 TiDB 使用环境】测试
【 TiDB 版本】 7.5.1
【复现路径】
我们在测试环境评估新的集群版本 7.5.1,集群是按照官方文档用Operator 部署在K8S 里的，最近按照官方文档从6.1 版本升级到7.5.1的。
我们使用如下配置来创建BackupSchedule:
apiVersion: pingcap.com/v1alpha1
kind: BackupSchedule
metadata:
name: bas...-schedule-minio2
namespace: tidb-cluster
spec:
backupTemplate:
backoffRetryPolicy:
maxRetryTimes: 2
minRetryDuration: 300s
retryTimeout: 30m
backupMode: snapshot
backupType: full
br:
cluster: ba..i
clusterNamespace: tidb-cluster
calcSizeLevel: all
resources: {}
s3:
bucket: basicai-ops-backup
endpoint: https://minio-endpoint-bxxxx.alidev.bexxxx.com
prefix: tidb/alidev
provider: minio
region: oss-cn-beijing
secretName: tidb-backup-to-minio
volumeBackupInitJobMaxActiveSeconds: 600
maxReservedTime: 84h
schedule: 19 1 * * *
【遇到的问题：问题现象及影响】
当我执行kubectl get backup 时，我们发现新版本的 BackupCR 显示的备份大小不对：
NAME TYPE MODE STATUS BACKUPPATH BACKUPSIZE COMMITTS LOGTRUNCATEUNTIL TIMETAKEN AGE
backup-s3-10181726 full snapshot Complete s3://baXXX-ops-backup/tidb/alidev/backup10181726 1.9 GB 445021209884622860 188d
baXXX-backup-schedule-minio2-2024-04-21t01-19-00 full snapshot Complete s3://baXXX-ops-backup/tidb/alidev/baXXX-pd.tidb-cluster-2379-2024-04-21t01-19-00 394 B 449226302064427009 3m40s 3d5h
baXXX-backup-schedule-minio2-2024-04-22t01-19-00 full snapshot Complete s3://baXXX-ops-backup/tidb/alidev/baXXX-pd.tidb-cluster-2379-2024-04-22t01-19-00 394 B 449248951895588865 1m50s 2d5h
baXXX-backup-schedule-minio2-2024-04-23t01-19-00 full snapshot Complete s3://baXXX-ops-backup/tidb/alidev/baXXX-pd.tidb-cluster-2379-2024-04-23t01-19-00 394 B 449271601936728065 1m54s 29h
baXXX-backup-schedule-minio2-2024-04-24t01-19-00 full snapshot Complete s3://baXXX-ops-backup/tidb/alidev/baXXX-pd.tidb-cluster-2379-2024-04-24t01-19-00 394 B 449294262358769665 2m13s 5h5m
【附件：截图/日志/监控】
