tidb-kubernetes: add backup and restore usage docs#1945
Closed
TomShawn wants to merge 4 commits into
Closed
Conversation
TomShawn
added
size/large
TomShawn
changed the title
TomShawn
added
translation/from-docs-cn
TomShawn
added
status/PTAL
TomShawn
changed the title
Contributor
Author
|
@yikeke @onlymellb @tennix PTAL, thanks! |
2 tasks
tennix
reviewed
Mar 12, 2020
|
|
||
| ### Ad-hoc backup process | ||
|
|
||
| Create the `Backup` CR and back up data to GSC: |
Member
There was a problem hiding this comment.
Suggested change
| Create the `Backup` CR and back up data to GSC: | |
| Create the `Backup` CR and back up data to GCS: |
tennix
reviewed
Mar 12, 2020
| kubectl get bk -n test1 -owide | ||
| ``` | ||
|
|
||
| More `Backup` CRs are as described follows: |
Member
There was a problem hiding this comment.
Suggested change
| More `Backup` CRs are as described follows: | |
| More `Backup` CRs configurations are as described follows: |
tennix
reviewed
Mar 12, 2020
| * `.spec.from.host`: the address of the TiDB cluster to be backed up. | ||
| * `.spec.from.port`: the port of the TiDB cluster to be backed up. | ||
| * `.spec.from.user`: the accessing user of the TiDB cluster to be backed up. | ||
| * `.spec.from.tidbSecretName`: the secrete of the credential needed by the TiDB cluster to be backed up. |
Member
There was a problem hiding this comment.
Suggested change
| * `.spec.from.tidbSecretName`: the secrete of the credential needed by the TiDB cluster to be backed up. | |
| * `.spec.from.tidbSecretName`: the secret of the credential needed by the TiDB cluster to be backed up. |
Contributor
Author
|
All changes in this PR are migrated to pingcap/docs-tidb-operator#1, so this PR is closed. |
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
3 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? (Required)
Add documents for the CRD-based backup and restoration method for TiDB Operator 1.1 or later.
Which TiDB version(s) do your changes apply to? (Required)
If you select two or more versions from above, to trigger the bot to cherry-pick this PR to your desired release version branch(es), you must add corresponding labels such as needs-cherry-pick-3.1, needs-cherry-pick-3.0, and needs-cherry-pick-2.1.
What is the related PR or file link(s)?