TiDB 备份时 SST 文件大小为 0

🪐 TiDB 技术问题 备份&数据迁移
1

【 TiDB 使用环境】生产环境
【 TiDB 版本】v6.5.0
【复现路径】做过哪些操作出现的问题
使用 BR 进行备份，备份的文件夹里 sst 文件大小为 0。
这里是使用 S3 挂载本地目录，所有 TiKV 节点都有挂载同样的目录操作。备份和恢复操作的应该都是同一个目录。

image
image2532×366 40.6 KB

大佬指点一下，SST 文件大小为 0 正常吗？

2

br 的操作有什么异常么？

3

br 备份时没报异常，恢复的时候会报错。Cannot read /xxx/xxx/2023-04-19-14-14/1/3536_221_289dc87df641c0306147a6bd6679eeb9cc6aac71f43c90989c87ff7bbf0b4646_1681884920819_default.sst

4

备份时的日志拿下来看看

5

backup-202304191414.log (2.0 MB)
这

6

备份用br的7.0，在6.5的集群上执行的恢复，日志显示不支持

detected the old version of tidb cluster, require: >= 6.6.0, but got 6.5.0"] [errorVerbose="detected the old version of tidb cluster, require: >= 6.6.0, but got 6.5.0\

[2023/04/19 14:21:04.504 +08:00] [WARN] [restore.go:435] ["Keyspace BR is not supported in this cluster, fallback to legacy restore"] [error="detected the old version of tidb cluster, require: >= 6.6.0, but got 6.5.0"] [errorVerbose="detected the old version of tidb cluster, require: >= 6.6.0, but got 6.5.0\ngithub.com/pingcap/tidb/br/pkg/version.CheckVersionForKeyspaceBR\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/version/version.go:177\ngithub.com/pingcap/tidb/br/pkg/version.CheckClusterVersion\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/version/version.go:108\ngithub.com/pingcap/tidb/br/pkg/restore.CheckKeyspaceBREnable\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/restore/client.go:2897\ngithub.com/pingcap/tidb/br/pkg/task.configureRestoreClient\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/task/restore.go:433\ngithub.com/pingcap/tidb/br/pkg/task.runRestore\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/task/restore.go:570\ngithub.com/pingcap/tidb/br/pkg/task.RunRestore\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/pkg/task/restore.go:533\nmain.runRestoreCommand\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/cmd/br/restore.go:63\nmain.newFullRestoreCommand.func1\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/cmd/br/restore.go:148\ngithub.com/spf13/cobra.(*Command).execute\n\t/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:916\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\t/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:1044\ngithub.com/spf13/cobra.(*Command).Execute\n\t/go/pkg/mod/github.com/spf13/cobra@v1.6.1/command.go:968\nmain.main\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/br/br/cmd/br/main.go:57\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:250\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1598"]
7

我刚重装了下 br，换成了 v6.5.0。重新备份再恢复还是 sst 文件问题
backup-202304191653.log (2.1 MB)

8

正常的备份相同名字的 SST 文件是不是只应该有一个。我相同名字的会出现两个 :thinking:

9

相同名字出现两个，那肯定是不正常了。
测一下s3有没有问题

10

此话题已在最后回复的 60 天后被自动关闭。不再允许新回复。