backup-and-restore: add basic introduction#2089
Merged
Merged
Conversation
3pointer
force-pushed
the
br_introduce
branch
from
2315f50 to
efc557d
Compare
overvenus
reviewed
Dec 2, 2019
Co-Authored-By: Neil Shen <overvenus@gmail.com>
Co-Authored-By: Neil Shen <overvenus@gmail.com>
IANTHEREAL
reviewed
Dec 3, 2019
IANTHEREAL
reviewed
Dec 3, 2019
Co-Authored-By: Ian <ArGregoryIan@gmail.com>
Co-Authored-By: Ian <ArGregoryIan@gmail.com>
IANTHEREAL
reviewed
Dec 3, 2019
IANTHEREAL
reviewed
Dec 3, 2019
Co-Authored-By: Ian <ArGregoryIan@gmail.com>
Co-Authored-By: Ian <ArGregoryIan@gmail.com>
3pointer
force-pushed
the
br_introduce
branch
from
cd24c18 to
8949a8a
Compare
zier-one
approved these changes
Dec 3, 2019
|
|
||
| ### 备份原理 | ||
|
|
||
| BR 执行备份时，会先从 PD 获取到 |
Contributor
There was a problem hiding this comment.
Suggested change
| BR 执行备份时，会先从 PD 获取到 | |
| BR 执行备份时，会先从 PD 获取到： |
zier-one
reviewed
Dec 3, 2019
|
|
||
| 然后根据上述信息，在 BR 内部启动一个 TiDB，获取对应 TS 的数据库／表信息。同时过滤掉系统库（`information_schema`，`performance_schema`，`mysql`)； | ||
|
|
||
| 如果是全量备份，会遍历全部库表，并且根据每一张表构建需要备份的 KV Range； |
Contributor
There was a problem hiding this comment.
Suggested change
| 如果是全量备份，会遍历全部库表，并且根据每一张表构建需要备份的 KV Range； | |
| - 如果是全量备份，会遍历全部库表，并且根据每一张表构建需要备份的 KV Range； |
|
|
||
| 如果是全量备份，会遍历全部库表，并且根据每一张表构建需要备份的 KV Range； | ||
|
|
||
| 如果是单表备份，会根据该表构建需要备份的 KV Range。 |
Contributor
There was a problem hiding this comment.
Suggested change
| 如果是单表备份，会根据该表构建需要备份的 KV Range。 | |
| - 如果是单表备份，会根据该表构建需要备份的 KV Range。 |
zier-one
reviewed
Dec 3, 2019
| - 当前的 TS 作为备份快照的时间点。 | ||
| - 当前集群的 TikV 节点信息。 | ||
|
|
||
| 然后根据上述信息，在 BR 内部启动一个 TiDB，获取对应 TS 的数据库／表信息。同时过滤掉系统库（`information_schema`，`performance_schema`，`mysql`)； |
Contributor
There was a problem hiding this comment.
Suggested change
| 然后根据上述信息，在 BR 内部启动一个 TiDB，获取对应 TS 的数据库／表信息。同时过滤掉系统库（`information_schema`，`performance_schema`，`mysql`)； | |
| 然后根据上述信息，在 BR 内部启动一个 TiDB，获取对应 TS 的数据库／表信息。同时过滤掉系统库（`information_schema`，`performance_schema`，`mysql`)。 |
zier-one
reviewed
Dec 3, 2019
|
|
||
| 最后，BR 将需要备份的 KV Range 收集后，构造完整请求分发给集群内的 TiKV 节点。 | ||
|
|
||
| 请求主要结构如下 |
Contributor
There was a problem hiding this comment.
Suggested change
| 请求主要结构如下 | |
| 请求主要结构如下： |
3pointer
force-pushed
the
br_introduce
branch
from
6df2869 to
9ce8fdc
Compare
Member
|
@TomShawn Please take a look at the language, apply changes to v3.1, and update the English version pingcap/docs#1680 accordingly. Thanks! |
TomShawn
added
translation/done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is changed, added or deleted?
add basic introduction for br
What is the related PR or file link(s)?
N/A
N/A
Which version does your change affect?
N/A