Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

br: remove an unclear usage tip about checksum #10537

Merged
merged 1 commit into from
Jul 18, 2022
Merged

br: remove an unclear usage tip about checksum #10537

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions br/backup-and-restore-overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -100,8 +100,7 @@ BR 内置版本会在执行备份和恢复操作前，对 TiDB 集群版本和
- BR 只支持恢复数据到新集群，会尽可能多的使用恢复集群的资源。不推荐向正在提供服务的生产集群执行恢复，恢复期间会对业务产生不可避免的影响；
- 不推荐多个 BR 备份和恢复任务并行运行。不同的任务并行，不仅会导致备份或恢复的性能降低，影响在线业务；还会因为任务之间缺少协调机制造成任务失败，甚至对集群的状态产生影响；
- 推荐使用支持 S3/GCS/Azure Blob Storage 协议的存储系统保存备份数据；
- 应确保 BR、TiKV 节点和备份存储系统有足够的网络带宽，备份存储系统能提供足够的写入/读取性能，否则，它们有可能成为备份恢复时的性能瓶颈；
- BR 默认会分别在备份、恢复完成后，进行一轮数据校验，将备份数据的 checksum 同集群 [admin checksum table](/sql-statements/sql-statement-admin-checksum-table.md) 的结果比较，来保证正确性。但是 `admin checksum table` 执行耗时久，并且对集群性能影响比较大，可以根据你的情况，选择备份时关闭校验(`--checksum=false`)，只在恢复时开启校验。
- 应确保 BR、TiKV 节点和备份存储系统有足够的网络带宽，备份存储系统能提供足够的写入/读取性能，否则，它们有可能成为备份恢复时的性能瓶颈。

### 探索更多

Expand Down