Skip to content

Backupandrestore#23286

Open
wildpcww wants to merge 2 commits into
pingcap:release-8.5from
wildpcww:backupandrestore
Open

Backupandrestore#23286
wildpcww wants to merge 2 commits into
pingcap:release-8.5from
wildpcww:backupandrestore

Conversation

@wildpcww

Copy link
Copy Markdown
Collaborator

First-time contributors' checklist

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

AI agent involvement

  • The changes in this PR were primarily made by an AI agent on behalf of the PR author.

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot

ti-chi-bot Bot commented Jul 15, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lilin90 for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot Bot added contribution This PR is from a community contributor. missing-translation-status This PR does not have translation status info. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jul 15, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the TiDB Cloud backup and restore documentation to incorporate the BYOC (Bring Your Own Cloud) plan type, detailing its backup and restore capabilities. The review feedback highlights minor spacing and formatting inconsistencies around template variables like {{{ .premium }}} and {{{ .byoc }}} that should be corrected for consistency.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.


- [Automatic backups for {{{ .starter }}} and {{{ .essential }}} instances](/tidb-cloud/backup-and-restore-serverless.md#automatic-backups)
- [Automatic backups for {{{ .premium }}} instances](/tidb-cloud/premium/backup-and-restore-premium.md#automatic-backups)
- [Automatic backups for {{{ .premium }}} <CustomContent plan="byoc"> and {{{ .byoc}}} </CustomContent> instances](/tidb-cloud/premium/backup-and-restore-premium.md#automatic-backups)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

There is an extra space after {{{ .premium }}} and a missing space in {{{ .byoc}}}. Let's adjust the spacing for consistency.

Suggested change
- [Automatic backups for {{{ .premium }}} <CustomContent plan="byoc"> and {{{ .byoc}}} </CustomContent> instances](/tidb-cloud/premium/backup-and-restore-premium.md#automatic-backups)
- [Automatic backups for {{{ .premium }}} <CustomContent plan="byoc"> and {{{ .byoc }}} </CustomContent> instances](/tidb-cloud/premium/backup-and-restore-premium.md#automatic-backups)
References
  1. Correct English grammar, spelling, and punctuation mistakes, if any. Use consistent terminology and formatting. (link)

Manual backup enables you to back up your data to a known state as needed, and then restore to that state at any time. You can use a manual backup before high-risk operations such as system upgrades, critical data deletion, or irreversible schema changes.

For more information, see [Perform a manual backup](/tidb-cloud/backup-and-restore.md#perform-a-manual-backup).
{{{ .premium }}} <CustomContent plan="byoc">, {{{ .byoc}}} </CustomContent> and TiDB Cloud Dedicated support manual backups. A manual backup provides a controlled restore point and is retained until you explicitly delete it. Manual backups do not support PITR or partial backups, and each restore operation creates a new instance.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

There is a missing space in {{{ .byoc}}} and a double space after the period in manual backups. A manual backup. Let's correct these spacing issues for better consistency and readability.

Suggested change
{{{ .premium }}} <CustomContent plan="byoc">, {{{ .byoc}}} </CustomContent> and TiDB Cloud Dedicated support manual backups. A manual backup provides a controlled restore point and is retained until you explicitly delete it. Manual backups do not support PITR or partial backups, and each restore operation creates a new instance.
{{{ .premium }}} <CustomContent plan="byoc">, {{{ .byoc }}} </CustomContent> and TiDB Cloud Dedicated support manual backups. A manual backup provides a controlled restore point and is retained until you explicitly delete it. Manual backups do not support PITR or partial backups, and each restore operation creates a new instance.
References
  1. Correct English grammar, spelling, and punctuation mistakes, if any. Use consistent terminology and formatting. (link)


For more information, see the following:

- [Manual backups for {{{ .premium }}} <CustomContent plan="byoc"> and {{{ .byoc}}} </CustomContent> instances](/tidb-cloud/premium/backup-and-restore-premium.md#manual-backups)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

There is a missing space in {{{ .byoc}}}. Let's adjust it to {{{ .byoc }}} for consistency.

Suggested change
- [Manual backups for {{{ .premium }}} <CustomContent plan="byoc"> and {{{ .byoc}}} </CustomContent> instances](/tidb-cloud/premium/backup-and-restore-premium.md#manual-backups)
- [Manual backups for {{{ .premium }}} <CustomContent plan="byoc"> and {{{ .byoc }}} </CustomContent> instances](/tidb-cloud/premium/backup-and-restore-premium.md#manual-backups)
References
  1. Correct English grammar, spelling, and punctuation mistakes, if any. Use consistent terminology and formatting. (link)


TiDB Cloud supports restoring data from backup snapshots or point-in-time recovery to a new cluster or instance. Restore operations help you recover from accidental data loss, data corruption, or application errors.

For {{{ .premium }}} <CustomContent plan="byoc"> and {{{ .byoc}}} </CustomContent> instances, you can restore data to a new instance. You can restore from automatic backups, manual backups, or supported external cloud storage backups. PITR is supported only for automatic backups and is not supported for manual backups.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

low

There is an extra space after {{{ .premium }}} and a missing space in {{{ .byoc}}}. Let's adjust the spacing for consistency.

Suggested change
For {{{ .premium }}} <CustomContent plan="byoc"> and {{{ .byoc}}} </CustomContent> instances, you can restore data to a new instance. You can restore from automatic backups, manual backups, or supported external cloud storage backups. PITR is supported only for automatic backups and is not supported for manual backups.
For {{{ .premium }}} <CustomContent plan="byoc"> and {{{ .byoc }}} </CustomContent> instances, you can restore data to a new instance. You can restore from automatic backups, manual backups, or supported external cloud storage backups. PITR is supported only for automatic backups and is not supported for manual backups.
References
  1. Correct English grammar, spelling, and punctuation mistakes, if any. Use consistent terminology and formatting. (link)

@ti-chi-bot

ti-chi-bot Bot commented Jul 15, 2026

Copy link
Copy Markdown

@wildpcww: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-verify 2f2eec8 link true /test pull-verify

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

contribution This PR is from a community contributor. missing-translation-status This PR does not have translation status info. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant