From 6b1b45889b707b722b92203a76b6b55c6ff16679 Mon Sep 17 00:00:00 2001 From: Cheng Weiwei <65707268+wildpcww@users.noreply.github.com> Date: Wed, 15 Jul 2026 17:46:55 +0800 Subject: [PATCH 1/6] Update backup-and-restore-concepts.md --- tidb-cloud/backup-and-restore-concepts.md | 25 ++++++++++++++++++++--- 1 file changed, 22 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/backup-and-restore-concepts.md b/tidb-cloud/backup-and-restore-concepts.md index 46d7af4e44ffa..a18cfc4356885 100644 --- a/tidb-cloud/backup-and-restore-concepts.md +++ b/tidb-cloud/backup-and-restore-concepts.md @@ -7,6 +7,12 @@ summary: Learn about backup & restore concepts for TiDB Cloud. TiDB Cloud Backup & Restore features are designed to safeguard your data and ensure business continuity by enabling you to back up and recover data. + + +For TiDB Cloud BYOC, you can manage backup and restore operations through the TiDB Cloud console, while the data plane runs in your own cloud account. This allows you to use managed backup and restore workflows while keeping the BYOC data plane within your cloud environment. + + + ## Automatic backup In TiDB Cloud, snapshot backups are taken automatically by default and stored according to your backup retention policy. @@ -14,14 +20,20 @@ In TiDB Cloud, snapshot backups are taken automatically by default and stored ac For more information, see the following: - [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 }}} and {{{ .byoc}}} instances](/tidb-cloud/premium/backup-and-restore-premium.md#automatic-backups) - [Automatic backups for TiDB Cloud Dedicated clusters](/tidb-cloud/backup-and-restore.md#turn-on-auto-backup) ## Manual backup -Manual backup is a feature of TiDB Cloud Dedicated that enables you to back up your data to a known state as needed, and then restore to that state at any time. +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 }}} , {{{ .byoc}}} 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. + + +For more information, see the following: + +- [Manual backups for {{{ .premium }}} and {{{ .byoc}}} instances](/tidb-cloud/premium/backup-and-restore-premium.md#manual-backups) +- [Perform a manual backup for TiDB Cloud Dedicated clusters](/tidb-cloud/backup-and-restore.md#perform-a-manual-backup) ## Dual region backup @@ -42,3 +54,10 @@ If you want to perform Point-in-time Restore, note the following: - For {{{ .starter }}} instances, Point-in-time Restore is not available. - For {{{ .essential }}} instances, you can restore to any time within the last 30 days. For more information, see [Restore mode](/tidb-cloud/backup-and-restore-serverless.md#restore-mode). - For TiDB Cloud Dedicated clusters, you need to [enable PITR](/tidb-cloud/backup-and-restore.md#turn-on-point-in-time-restore) in advance. + +## Restore + +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 }}} and {{{ .byoc}}} 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. + From 2f2eec83b6b825340c0263e1dab52c548b879367 Mon Sep 17 00:00:00 2001 From: Cheng Weiwei <65707268+wildpcww@users.noreply.github.com> Date: Wed, 15 Jul 2026 18:07:29 +0800 Subject: [PATCH 2/6] Update backup-and-restore-premium.md --- tidb-cloud/premium/backup-and-restore-premium.md | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index 007510d05f9e6..088314a18a203 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -8,6 +8,12 @@ aliases: ['/tidbcloud/restore-deleted-tidb-cluster'] This document describes how to back up and restore your data on {{{ .premium }}} instances. {{{ .premium }}} supports both automatic backups and manual backups, and lets you restore backup data to a new instance as needed. + + +This document also applies to {{{ .byoc }}}. Backup and restore capabilities for {{{ .byoc }}} are currently consistent with {{{ .premium }}}. + + + Backup files can originate from the following sources: - Active {{{ .premium }}} instances @@ -162,14 +168,16 @@ To restore a deleted {{{ .premium }}} instance from the Recycle Bin, take the fo > > If you are in multiple organizations, use the combo box in the upper-left corner to switch to your target organization first. -2. On the **Recycle Bin** page, click the **Premium** tab to go to the recycle bin of {{{ .premium }}} instances. +2. On the **Recycle Bin** page, click the **Premium****BYOC** tab to go to the recycle bin of {{{ .premium }}}{{{ .byoc }}} instances. -3. Locate the {{{ .premium }}} instance you want to restore, and then click the **>** button to expand the available backups of the instance. +3. Locate the {{{ .premium }}}{{{ .byoc }}} instance you want to restore, and then click the **>** button to expand the available backups of the instance. 4. In the row of your desired backup, click **...**, and then select **Restore**. 5. On the **Restore** page, follow the same steps as [Restore to a new instance](#restore-to-a-new-instance) to restore the backup to a new instance. + + ### Restore backups from a different plan type Currently, you can only restore backups from a {{{ .dedicated }}} cluster hosted on AWS to a new {{{ .premium }}} instance. @@ -187,9 +195,11 @@ To restore a backup generated by a {{{ .dedicated }}} cluster, follow these step 3. On the **Restore** page, follow the same steps as [Restore to a new instance](#restore-to-a-new-instance) to restore the backup to a new instance. + + ### Restore backups from cloud storage -{{{ .premium }}} supports restoring backups from cloud storage (such as Amazon S3 and Alibaba Cloud Object Storage Service (OSS)) to a new instance. This feature is compatible with backups generated from {{{ .dedicated }}} clusters or TiDB Self-Managed clusters. +{{{ .premium }}}{{{ .byoc }}} supports restoring backups from cloud storage (such as Amazon S3 and Alibaba Cloud Object Storage Service (OSS)) to a new instance. This feature is compatible with backups generated from {{{ .dedicated }}} clusters or TiDB Self-Managed clusters. >**Note:** > From 20ce4be0a4fc7bc4f66e6dfb77994a9c763a0bec Mon Sep 17 00:00:00 2001 From: lilin90 Date: Tue, 21 Jul 2026 17:22:01 +0800 Subject: [PATCH 3/6] Update capitalization for style --- tidb-cloud/byoc/byoc-prepare-environment-aws.md | 2 +- tidb-cloud/byoc/byoc-service-initialization.md | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/tidb-cloud/byoc/byoc-prepare-environment-aws.md b/tidb-cloud/byoc/byoc-prepare-environment-aws.md index 98a22c4f46208..e06f1100bf16e 100644 --- a/tidb-cloud/byoc/byoc-prepare-environment-aws.md +++ b/tidb-cloud/byoc/byoc-prepare-environment-aws.md @@ -11,7 +11,7 @@ Before initiating the BYOC deployment, prepare the required infrastructure compo Unique identifier for your organization within TiDB Cloud. -1. Log in to the [TiDB Cloud Console](https://tidbcloud.com/). +1. Log in to the [TiDB Cloud console](https://tidbcloud.com/). If you do not have a TiDB Cloud account, click [here](https://tidbcloud.com/free-trial) to sign up. You can sign up with an email and password to manage TiDB Cloud credentials, or use single sign-on (SSO) via Google, GitHub, or Microsoft accounts. diff --git a/tidb-cloud/byoc/byoc-service-initialization.md b/tidb-cloud/byoc/byoc-service-initialization.md index be162c50ca39b..00ed79fdd0ba7 100644 --- a/tidb-cloud/byoc/byoc-service-initialization.md +++ b/tidb-cloud/byoc/byoc-service-initialization.md @@ -11,9 +11,9 @@ Following the successful deployment of your BYOC infrastructure, the next phase ### Create a new TiDB Instance -You can now provision TiDB instances directly via the TiDB Cloud Console. +You can now provision TiDB instances directly via the TiDB Cloud console. -1. Initiate instance creation. Log in to the [TiDB Cloud Console](https://tidbcloud.com/) and follow the standard workflow to create a new instance. +1. Initiate instance creation. Log in to the [TiDB Cloud console](https://tidbcloud.com/) and follow the standard workflow to create a new instance. @@ -36,7 +36,7 @@ After successfully preparing your backup file in Amazon S3, you can proceed to r 2. **Execute the Restore Process.** - Once the access keys are configured, you can initiate the restore job from the TiDB Cloud Console. + Once the access keys are configured, you can initiate the restore job from the TiDB Cloud console. For step-by-step restoration procedures, refer to [Restore backups from cloud storage](/tidb-cloud/premium/backup-and-restore-premium.md#restore-backups-from-cloud-storage). From 7dd57bb5668c59b8489a8590c2870832f65176e2 Mon Sep 17 00:00:00 2001 From: Lilian Lee Date: Tue, 21 Jul 2026 17:28:08 +0800 Subject: [PATCH 4/6] Apply suggestions from code review Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- tidb-cloud/backup-and-restore-concepts.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/backup-and-restore-concepts.md b/tidb-cloud/backup-and-restore-concepts.md index a18cfc4356885..fda6925b863c7 100644 --- a/tidb-cloud/backup-and-restore-concepts.md +++ b/tidb-cloud/backup-and-restore-concepts.md @@ -20,7 +20,7 @@ In TiDB Cloud, snapshot backups are taken automatically by default and stored ac For more information, see the following: - [Automatic backups for {{{ .starter }}} and {{{ .essential }}} instances](/tidb-cloud/backup-and-restore-serverless.md#automatic-backups) -- [Automatic backups for {{{ .premium }}} and {{{ .byoc}}} instances](/tidb-cloud/premium/backup-and-restore-premium.md#automatic-backups) +- [Automatic backups for {{{ .premium }}} and {{{ .byoc }}} instances](/tidb-cloud/premium/backup-and-restore-premium.md#automatic-backups) - [Automatic backups for TiDB Cloud Dedicated clusters](/tidb-cloud/backup-and-restore.md#turn-on-auto-backup) ## Manual backup From f34fdf122c1ffbdef4f1a2c444d3f4ead8703675 Mon Sep 17 00:00:00 2001 From: Lilian Lee Date: Tue, 21 Jul 2026 17:37:12 +0800 Subject: [PATCH 5/6] Refine wording and format --- tidb-cloud/backup-and-restore-concepts.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/tidb-cloud/backup-and-restore-concepts.md b/tidb-cloud/backup-and-restore-concepts.md index fda6925b863c7..7c04fdc5fd15b 100644 --- a/tidb-cloud/backup-and-restore-concepts.md +++ b/tidb-cloud/backup-and-restore-concepts.md @@ -9,7 +9,7 @@ TiDB Cloud Backup & Restore features are designed to safeguard your data and ens -For TiDB Cloud BYOC, you can manage backup and restore operations through the TiDB Cloud console, while the data plane runs in your own cloud account. This allows you to use managed backup and restore workflows while keeping the BYOC data plane within your cloud environment. +With TiDB Cloud BYOC, you can manage backup and restore operations through the TiDB Cloud console, while the data plane runs in your own cloud account. This provides a managed backup and restore experience while keeping your data plane in your cloud environment. @@ -20,19 +20,18 @@ In TiDB Cloud, snapshot backups are taken automatically by default and stored ac For more information, see the following: - [Automatic backups for {{{ .starter }}} and {{{ .essential }}} instances](/tidb-cloud/backup-and-restore-serverless.md#automatic-backups) -- [Automatic backups for {{{ .premium }}} and {{{ .byoc }}} instances](/tidb-cloud/premium/backup-and-restore-premium.md#automatic-backups) +- [Automatic backups for {{{ .premium }}} and {{{ .byoc }}} instances](/tidb-cloud/premium/backup-and-restore-premium.md#automatic-backups) - [Automatic backups for TiDB Cloud Dedicated clusters](/tidb-cloud/backup-and-restore.md#turn-on-auto-backup) ## Manual backup 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. -{{{ .premium }}} , {{{ .byoc}}} 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 }}}, {{{ .byoc }}}, 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. For more information, see the following: -- [Manual backups for {{{ .premium }}} and {{{ .byoc}}} instances](/tidb-cloud/premium/backup-and-restore-premium.md#manual-backups) +- [Manual backups for {{{ .premium }}} and {{{ .byoc }}} instances](/tidb-cloud/premium/backup-and-restore-premium.md#manual-backups) - [Perform a manual backup for TiDB Cloud Dedicated clusters](/tidb-cloud/backup-and-restore.md#perform-a-manual-backup) ## Dual region backup @@ -59,5 +58,5 @@ If you want to perform Point-in-time Restore, note the following: 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 }}} and {{{ .byoc}}} 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 }}} and {{{ .byoc }}} 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. From 3dac83f27e661cdeb150c0810e13d5af3cebd24e Mon Sep 17 00:00:00 2001 From: lilin90 Date: Tue, 21 Jul 2026 17:40:26 +0800 Subject: [PATCH 6/6] Remove an extra blank line --- tidb-cloud/backup-and-restore-concepts.md | 1 - 1 file changed, 1 deletion(-) diff --git a/tidb-cloud/backup-and-restore-concepts.md b/tidb-cloud/backup-and-restore-concepts.md index 7c04fdc5fd15b..299059ac5166c 100644 --- a/tidb-cloud/backup-and-restore-concepts.md +++ b/tidb-cloud/backup-and-restore-concepts.md @@ -59,4 +59,3 @@ If you want to perform Point-in-time Restore, note the following: 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 }}} and {{{ .byoc }}} 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. -