serverless BR #19679
Open
serverless BR #19679
+90
−33
Conversation
This file contains 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
ti-chi-bot
bot
added
missing-translation-status
shiyuhang0
force-pushed
the
serverless_br
branch
from
a7af08f to
cfea813
Compare
hfxsd
added
translation/no-need
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
zhangyangyu
reviewed
Dec 13, 2024
zhangyangyu
approved these changes
Dec 13, 2024
|
@zhangyangyu: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: 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. |
sunxiaoguang
approved these changes
Dec 13, 2024
|
@sunxiaoguang: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: 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. |
hfxsd
reviewed
Dec 13, 2024
| @@ -26,7 +26,7 @@ You can delete a cluster at any time by performing the following steps: | |||
|
|
|||
| > **Note:** | |||
| > | |||
| > [TiDB Cloud Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-cloud-serverless) only support [in-place restoring from backups](/tidb-cloud/backup-and-restore-serverless.md#restore) and do not support restoring data after the deletion. If you want to delete a TiDB Cloud Serverless cluster and restore its data in the future, you can use [Dumpling](https://docs.pingcap.com/tidb/stable/dumpling-overview) to export your data as a backup. | |||
| > [TiDB Cloud Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-cloud-serverless) do not support restoring data after the deletion. If you want to delete a TiDB Cloud Serverless cluster and restore its data in the future, you can refer [Export Data from TiDB Cloud Serverless](/tidb-cloud/serverless-export.md) to export your data as a backup. | |||
There was a problem hiding this comment.
Suggested change
| > [TiDB Cloud Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-cloud-serverless) do not support restoring data after the deletion. If you want to delete a TiDB Cloud Serverless cluster and restore its data in the future, you can refer [Export Data from TiDB Cloud Serverless](/tidb-cloud/serverless-export.md) to export your data as a backup. | |
| > [TiDB Cloud Serverless clusters](/tidb-cloud/select-cluster-tier.md#tidb-cloud-serverless) do not support restoring data after the deletion. If you want to delete a TiDB Cloud Serverless cluster and restore its data in the future, refer to [Export Data from TiDB Cloud Serverless](/tidb-cloud/serverless-export.md) to export your data as a backup. |
|
|
||
| ### Learn about the backup setting | ||
|
|
||
| Automatic backups is controlled by the backup setting, which is different for free clusters and scalable clusters: |
There was a problem hiding this comment.
Suggested change
| Automatic backups is controlled by the backup setting, which is different for free clusters and scalable clusters: | |
| Automatic backups is controlled by the backup setting, which is different for free clusters and scalable clusters, as shown in the following table: |
|
|
||
| ## Backup | ||
| | backup setting | free cluster | scalable cluster | |
There was a problem hiding this comment.
Suggested change
| | backup setting | free cluster | scalable cluster | | |
| | Backup setting | Free clusters | Scalable clusters | |
| - Free clusters: the backup retention is 1 day. | ||
| - Scalable clusters: the backup retention is 14 days. | ||
|
|
||
| - **Backup Time** is the time when the backup start to be scheduled. Note that the final backup time may fall behind the configured backup time. |
There was a problem hiding this comment.
Suggested change
| - **Backup Time** is the time when the backup start to be scheduled. Note that the final backup time may fall behind the configured backup time. | |
| - **Backup Time** is the time when the backup starts to be scheduled. Note that the final backup time might fall behind the configured backup time. |
| - **Backup Time** is the time when the backup start to be scheduled. Note that the final backup time may fall behind the configured backup time. | ||
|
|
||
| - Free clusters: the backup time is a randomly fixed time. | ||
| - Scalable clusters: the backup time can be configured to every half an hour. Default to a randomly fixed time. |
There was a problem hiding this comment.
Suggested change
| - Scalable clusters: the backup time can be configured to every half an hour. Default to a randomly fixed time. | |
| - Scalable clusters: you can configure the backup time to every half an hour. The default value is a randomly fixed time. |
| 4. In **Destination**, you can choose to restore in-place or restore to a new cluster. | ||
|
|
||
| <SimpleTab> | ||
| <div label="Restore to a New Cluster"> |
There was a problem hiding this comment.
Suggested change
| <div label="Restore to a New Cluster"> | |
| <div label="Restore to a new cluster"> |
|
|
||
| ## Limitations | ||
|
|
||
| - If any TiFlash replica is enabled, the replica will be unavailable for a while after the restore because data needs to be rebuilt in TiFlash. |
There was a problem hiding this comment.
Suggested change
| - If any TiFlash replica is enabled, the replica will be unavailable for a while after the restore because data needs to be rebuilt in TiFlash. | |
| - If a TiFlash replica is enabled, it will be unavailable for a period after the restore, because data needs to be rebuilt in TiFlash. |
| </div> | ||
| <div label="Restore to a New Cluster"> | ||
|
|
||
| To restore in-place, just click **In-place Restore**. |
There was a problem hiding this comment.
Suggested change
| To restore in-place, just click **In-place Restore**. | |
| To restore in-place, click **In-place Restore**. |
Comment on lines
+128
to
+129
| 4. Set spending limits when your choice is a scalable cluster. | ||
| 5. Set the advanced settings as you need when your choice is a scalable cluster. |
There was a problem hiding this comment.
Suggested change
| 4. Set spending limits when your choice is a scalable cluster. | |
| 5. Set the advanced settings as you need when your choice is a scalable cluster. | |
| 4. Set spending limits when you choose a scalable cluster. | |
| 5. Set the advanced settings as needed when you choose a scalable cluster. |
|
|
||
| - In **Backup Retention**, configure the minimum backup data retention period. | ||
| TiDB Cloud Serverless cluster provides restore functionality to help you recover your data in case of accidental data loss or corruption. |
There was a problem hiding this comment.
Suggested change
| TiDB Cloud Serverless cluster provides restore functionality to help you recover your data in case of accidental data loss or corruption. | |
| TiDB Cloud Serverless clusters offer restore functionality to help recover data in case of accidental loss or corruption. |
hfxsd
reviewed
Dec 13, 2024
| - Manual backup is not yet supported. | ||
| - The cluster will be unavailable during the restore process, and existing connections will be terminated. You can establish new connections once the restore is complete. | ||
| - If any TiFlash replica is enabled, the replica will be unavailable for a while after the restore because data needs to be rebuilt in TiFlash. | ||
| Automatic backups will back up your cluster data automatically, and you can restore your data from the backup snapshot to reduce your loss in extreme disaster situations. |
There was a problem hiding this comment.
Suggested change
| Automatic backups will back up your cluster data automatically, and you can restore your data from the backup snapshot to reduce your loss in extreme disaster situations. | |
| Automatic backups will back up your cluster data regularly, allowing you to restore data from a backup snapshot to minimize data loss in the event of a disaster. |
hfxsd
reviewed
Dec 13, 2024
| @@ -12,46 +12,83 @@ This document describes how to back up and restore your TiDB Cloud Serverless cl | |||
| > | |||
| > To learn how to back up and restore TiDB Cloud Dedicated cluster data, see [Back Up and Restore TiDB Cloud Dedicated Data](/tidb-cloud/backup-and-restore.md). | |||
|
|
|||
| ## Limitations | |||
| ## Automatic Backups | |||
There was a problem hiding this comment.
Suggested change
| ## Automatic Backups | |
| ## Automatic backups |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?