From dbdb6914392697d165bcd21b14ec62ad10fc4c54 Mon Sep 17 00:00:00 2001 From: Cheng Weiwei <65707268+wildpcww@users.noreply.github.com> Date: Fri, 19 Dec 2025 13:33:55 +0800 Subject: [PATCH 01/26] add restore from s3/oss --- .../premium/backup-and-restore-premium.md | 40 +++++++++++++++++-- 1 file changed, 37 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index ba925dda19a4a..798b92fe0dddd 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -154,11 +154,12 @@ To restore a deleted instance from the Recycle Bin, take the following steps: 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 classic backups from a different plan type +### Restore backups from a different plan type -Currently, you can only restore classic backups from a {{{ .dedicated }}} cluster hosted on AWS to a new {{{ .premium }}} instance. -To restore a classic backup generated by a {{{ .dedicated }}} cluster, follow these steps: +Currently, you can only restore backups from a {{{ .dedicated }}} cluster hosted on AWS to a new {{{ .premium }}} instance. + +To restore a backup generated by a {{{ .dedicated }}} cluster, follow these steps: 1. Log in to the [TiDB Cloud console](https://tidbcloud.com), and then navigate to the [**TiDB Instances**](https://tidbcloud.com/tidbs) page. In the upper-right corner, click **...**, and then click **Restore from Another Plan**. @@ -171,6 +172,39 @@ To restore a classic backup generated by a {{{ .dedicated }}} cluster, follow th 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 a Cloud Storage + +TiDB Cloud {{{ .premium }}} supports restoring backups from cloud object storage (such as AWS S3 or Alibaba Cloud OSS) to a new TiDB Cloud instance. This feature is compatible with backups generated from TiDB Cloud {{{ .dedicated }}} clusters or self-managed (on-premises) clusters. + +#### Prerequisites + +Before you begin, ensure the following: + +- **Supported Cloud Providers**: Currently, only backups located in **AWS S3** and **Alibaba Cloud OSS** are supported. +- **Cloud Provider Consistency**: You can only restore to a new instance that uses the same cloud provider as your storage bucket. +- **Credentials**: You have the **Access Key** and **Secret Key** with sufficient permissions to access the backup files. + +#### Steps + +1. Log in to the [TiDB Cloud console](https://tidbcloud.com), and then navigate to the [**TiDB Instances**](https://tidbcloud.com/tidbs) page. In the upper-right corner, click **...** , and then click **Restore from Cloud storage**. + +2. On the **Select Backup Storage Location** page, provide the following information: + - **Cloud Provider**: Select the provider where your backup file is located + - **Backup Files URI**: Enter the URI of the top-level folder that contains your backup files + - **Authentication**: Enter your **Access Key** and **Secret Key** + and then click **Verify Backup and Next**. + +3. If the verification is successful, the **Restore to a New Instance** page appears. Review the backup metadata information displayed at the top of the page: + - If the information is incorrect, click **Previous** at the bottom of the page to return to the storage configuration. + - If the information is correct, follow the same steps as [Restore to a new instance](#restore-to-a-new-instance) to configure and create your new instance. + +Note + - You can only restore backups to an instance within the same cloud provider environment. + - If the region of the new instance differs from the region of the storage bucket, additional **cross-region data transfer fees** may apply. + + ## Limitations Currently, manual backups are not supported for {{{ .premium }}} instances. From 0e7e99e558f9bcf2c9bfba439814bd252d04f4a5 Mon Sep 17 00:00:00 2001 From: Cheng Weiwei <65707268+wildpcww@users.noreply.github.com> Date: Fri, 19 Dec 2025 13:50:58 +0800 Subject: [PATCH 02/26] Update tidb-cloud/premium/backup-and-restore-premium.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- tidb-cloud/premium/backup-and-restore-premium.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index 798b92fe0dddd..7f3ec8915ed59 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -200,9 +200,9 @@ Before you begin, ensure the following: - If the information is incorrect, click **Previous** at the bottom of the page to return to the storage configuration. - If the information is correct, follow the same steps as [Restore to a new instance](#restore-to-a-new-instance) to configure and create your new instance. -Note - - You can only restore backups to an instance within the same cloud provider environment. - - If the region of the new instance differs from the region of the storage bucket, additional **cross-region data transfer fees** may apply. +> **Note:** +> +> If the region of the new instance differs from the region of the storage bucket, additional **cross-region data transfer fees** may apply. ## Limitations From ccf92e71c043dfdaebcf9e591d14c2c3ea8c9d28 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 19 Dec 2025 14:43:58 +0800 Subject: [PATCH 03/26] Apply suggestions from code review Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- tidb-cloud/premium/backup-and-restore-premium.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index 7f3ec8915ed59..c992d91fde7aa 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -174,7 +174,7 @@ To restore a backup generated by a {{{ .dedicated }}} cluster, follow these step -### Restore Backups from a Cloud Storage +### Restore backups from a cloud storage TiDB Cloud {{{ .premium }}} supports restoring backups from cloud object storage (such as AWS S3 or Alibaba Cloud OSS) to a new TiDB Cloud instance. This feature is compatible with backups generated from TiDB Cloud {{{ .dedicated }}} clusters or self-managed (on-premises) clusters. @@ -184,17 +184,16 @@ Before you begin, ensure the following: - **Supported Cloud Providers**: Currently, only backups located in **AWS S3** and **Alibaba Cloud OSS** are supported. - **Cloud Provider Consistency**: You can only restore to a new instance that uses the same cloud provider as your storage bucket. -- **Credentials**: You have the **Access Key** and **Secret Key** with sufficient permissions to access the backup files. +- **Credentials**: You have the access key and secret key with sufficient permissions to access the backup files. #### Steps 1. Log in to the [TiDB Cloud console](https://tidbcloud.com), and then navigate to the [**TiDB Instances**](https://tidbcloud.com/tidbs) page. In the upper-right corner, click **...** , and then click **Restore from Cloud storage**. -2. On the **Select Backup Storage Location** page, provide the following information: - - **Cloud Provider**: Select the provider where your backup file is located - - **Backup Files URI**: Enter the URI of the top-level folder that contains your backup files - - **Authentication**: Enter your **Access Key** and **Secret Key** - and then click **Verify Backup and Next**. +2. On the **Select Backup Storage Location** page, provide the following information, and then click **Verify Backup and Next**: + - **Cloud Provider**: select the provider where your backup file is located + - **Backup Files URI**: enter the URI of the top-level folder that contains your backup files + - **Authentication**: enter your access key and secret key 3. If the verification is successful, the **Restore to a New Instance** page appears. Review the backup metadata information displayed at the top of the page: - If the information is incorrect, click **Previous** at the bottom of the page to return to the storage configuration. From b4d0f9a78be72f0c03061c3ff42e2529b1071ad1 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Fri, 19 Dec 2025 14:47:31 +0800 Subject: [PATCH 04/26] Apply suggestions from code review --- tidb-cloud/premium/backup-and-restore-premium.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index c992d91fde7aa..a9797570db32b 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -172,8 +172,6 @@ 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 a cloud storage TiDB Cloud {{{ .premium }}} supports restoring backups from cloud object storage (such as AWS S3 or Alibaba Cloud OSS) to a new TiDB Cloud instance. This feature is compatible with backups generated from TiDB Cloud {{{ .dedicated }}} clusters or self-managed (on-premises) clusters. @@ -201,8 +199,7 @@ Before you begin, ensure the following: > **Note:** > -> If the region of the new instance differs from the region of the storage bucket, additional **cross-region data transfer fees** may apply. - +> If the instance and the storage bucket are located in different regions, additional cross-region data transfer fees might apply. ## Limitations From 1862cca6d7216f3f79e95acbb4ab4b8ab1b783cc Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 22 Dec 2025 09:51:46 +0800 Subject: [PATCH 05/26] Update backup-and-restore-premium.md --- .../premium/backup-and-restore-premium.md | 23 +++++++++++-------- 1 file changed, 13 insertions(+), 10 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index a9797570db32b..660250c7ad192 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -156,7 +156,6 @@ To restore a deleted instance from the Recycle Bin, take the following steps: ### 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. To restore a backup generated by a {{{ .dedicated }}} cluster, follow these steps: @@ -174,32 +173,36 @@ To restore a backup generated by a {{{ .dedicated }}} cluster, follow these step ### Restore backups from a cloud storage -TiDB Cloud {{{ .premium }}} supports restoring backups from cloud object storage (such as AWS S3 or Alibaba Cloud OSS) to a new TiDB Cloud instance. This feature is compatible with backups generated from TiDB Cloud {{{ .dedicated }}} clusters or self-managed (on-premises) clusters. +{{{ .premium }}} supports restoring backups from cloud object storage (such as AWS S3 or Alibaba Cloud OSS) to a new instance. This feature is compatible with backups generated from {{{ .dedicated }}} clusters or self-managed (on-premises) clusters. + +> **Note:** +> +> If the instance and the storage bucket are located in different regions, additional cross-region data transfer fees might apply. #### Prerequisites Before you begin, ensure the following: -- **Supported Cloud Providers**: Currently, only backups located in **AWS S3** and **Alibaba Cloud OSS** are supported. -- **Cloud Provider Consistency**: You can only restore to a new instance that uses the same cloud provider as your storage bucket. -- **Credentials**: You have the access key and secret key with sufficient permissions to access the backup files. +- Supported cloud providers: currently, only backups located in **AWS S3** and **Alibaba Cloud OSS** are supported. +- Cloud provider consistency: you can only restore to a new instance that uses the same cloud provider as your storage bucket. +- Credentials: You have the access key and secret key with sufficient permissions to access the backup files. #### Steps +To restore backups from a cloud storage, do the following: + 1. Log in to the [TiDB Cloud console](https://tidbcloud.com), and then navigate to the [**TiDB Instances**](https://tidbcloud.com/tidbs) page. In the upper-right corner, click **...** , and then click **Restore from Cloud storage**. 2. On the **Select Backup Storage Location** page, provide the following information, and then click **Verify Backup and Next**: + - **Cloud Provider**: select the provider where your backup file is located - **Backup Files URI**: enter the URI of the top-level folder that contains your backup files - **Authentication**: enter your access key and secret key 3. If the verification is successful, the **Restore to a New Instance** page appears. Review the backup metadata information displayed at the top of the page: - - If the information is incorrect, click **Previous** at the bottom of the page to return to the storage configuration. - - If the information is correct, follow the same steps as [Restore to a new instance](#restore-to-a-new-instance) to configure and create your new instance. -> **Note:** -> -> If the instance and the storage bucket are located in different regions, additional cross-region data transfer fees might apply. + - If the information is correct, follow the same steps as [Restore to a new instance](#restore-to-a-new-instance) to configure and create your new instance. + - If the information is not correct, click **Previous** at the bottom of the page to return to the storage configuration, and then enter the correct information. ## Limitations From a7e98f05d1c018a6e40c16b4d5d75b327f7d89f3 Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 22 Dec 2025 11:05:20 +0800 Subject: [PATCH 06/26] Update backup restore and instance creation steps Clarified and updated instructions for restoring backups from cloud storage, including revised authentication fields and step order. Added details about regional high availability for premium instances and adjusted step numbering for instance creation. --- .../premium/backup-and-restore-premium.md | 18 ++++++++++++------ .../premium/create-tidb-instance-premium.md | 4 +++- 2 files changed, 15 insertions(+), 7 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index 660250c7ad192..c09c363ef2ebf 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -191,19 +191,25 @@ Before you begin, ensure the following: To restore backups from a cloud storage, do the following: -1. Log in to the [TiDB Cloud console](https://tidbcloud.com), and then navigate to the [**TiDB Instances**](https://tidbcloud.com/tidbs) page. In the upper-right corner, click **...** , and then click **Restore from Cloud storage**. +1. Log in to the [TiDB Cloud console](https://tidbcloud.com), and then navigate to the [**TiDB Instances**](https://tidbcloud.com/tidbs) page. In the upper-right corner, click **...** , and then click **Restore from Cloud Storage**. -2. On the **Select Backup Storage Location** page, provide the following information, and then click **Verify Backup and Next**: +2. On the **Select Backup Storage Location** page, provide the following information: - **Cloud Provider**: select the provider where your backup file is located - **Backup Files URI**: enter the URI of the top-level folder that contains your backup files - - **Authentication**: enter your access key and secret key + - **Access Key ID**: enter your access key ID + - **Access Key Secret**: enter your access key secret -3. If the verification is successful, the **Restore to a New Instance** page appears. Review the backup metadata information displayed at the top of the page: +3. Click **Verify Backup and Next**. - - If the information is correct, follow the same steps as [Restore to a new instance](#restore-to-a-new-instance) to configure and create your new instance. - - If the information is not correct, click **Previous** at the bottom of the page to return to the storage configuration, and then enter the correct information. +4. If the verification is successful, the **Restore to a New Instance** page appears. Review the backup metadata information displayed at the top of the page. Follow the same steps as [create a new TiDB instance](/tidb-cloud/premium/create-tidb-instance-premium.md) to restore the backup to a new instance. + + If the information is not correct, click **Previous** at the bottom of the page to return to the storage configuration, and then enter the correct information. + +5. Click **Restore** to restore the backup. ## Limitations Currently, manual backups are not supported for {{{ .premium }}} instances. + +5. Configure your new TiDB instance for restoration. The steps are the same as [creating a new TiDB instance](/tidb-cloud/premium/create-tidb-instance-premium.md). \ No newline at end of file diff --git a/tidb-cloud/premium/create-tidb-instance-premium.md b/tidb-cloud/premium/create-tidb-instance-premium.md index b1b91acefd958..5ffdd6823be2c 100644 --- a/tidb-cloud/premium/create-tidb-instance-premium.md +++ b/tidb-cloud/premium/create-tidb-instance-premium.md @@ -52,7 +52,9 @@ If you have the `Organization Owner` role, you can create a {{{ .premium }}} ins RCUs represent the compute resources provisioned for your workload. TiDB Cloud automatically scales your instance within this range based on demand. -6. Click **Create**. +6. For {{{ .premium }}} instances, only regional high availability is enabled, and it is not configurable. For more information, see [High Availability](/tidb-cloud/serverless-high-availability.md). + +7. Click **Create**. The instance creation process begins. If this is your first instance in the selected region, provisioning typically takes about 30 minutes. If the selected region already has existing instances, the process is faster and usually completes within about 1 minute. From 9dbf2afbb91987484fcab46340986308bcbe7df9 Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 22 Dec 2025 11:08:39 +0800 Subject: [PATCH 07/26] Update backup-and-restore-premium.md --- tidb-cloud/premium/backup-and-restore-premium.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index c09c363ef2ebf..2a90385198b30 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -211,5 +211,3 @@ To restore backups from a cloud storage, do the following: ## Limitations Currently, manual backups are not supported for {{{ .premium }}} instances. - -5. Configure your new TiDB instance for restoration. The steps are the same as [creating a new TiDB instance](/tidb-cloud/premium/create-tidb-instance-premium.md). \ No newline at end of file From 8a789152ce173fb5794c36fde73361a7c5cd6cfa Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 22 Dec 2025 11:11:29 +0800 Subject: [PATCH 08/26] Update backup-and-restore-premium.md --- tidb-cloud/premium/backup-and-restore-premium.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index 2a90385198b30..7779c7c1bca08 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -173,7 +173,7 @@ To restore a backup generated by a {{{ .dedicated }}} cluster, follow these step ### Restore backups from a cloud storage -{{{ .premium }}} supports restoring backups from cloud object storage (such as AWS S3 or Alibaba Cloud OSS) to a new instance. This feature is compatible with backups generated from {{{ .dedicated }}} clusters or self-managed (on-premises) clusters. +{{{ .premium }}} supports restoring backups from a cloud storage (such as AWS S3 or Alibaba Cloud OSS) to a new instance. This feature is compatible with backups generated from {{{ .dedicated }}} clusters or self-managed (on-premises) clusters. > **Note:** > @@ -200,11 +200,11 @@ To restore backups from a cloud storage, do the following: - **Access Key ID**: enter your access key ID - **Access Key Secret**: enter your access key secret -3. Click **Verify Backup and Next**. +3. Click **Verify Backup and Next**. 4. If the verification is successful, the **Restore to a New Instance** page appears. Review the backup metadata information displayed at the top of the page. Follow the same steps as [create a new TiDB instance](/tidb-cloud/premium/create-tidb-instance-premium.md) to restore the backup to a new instance. - If the information is not correct, click **Previous** at the bottom of the page to return to the storage configuration, and then enter the correct information. + If the information is not correct, click **Previous** to return to the previous page, and then enter the correct information. 5. Click **Restore** to restore the backup. From 4abb72f7297704d210e1f3c218285e5510e7721b Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 22 Dec 2025 11:21:36 +0800 Subject: [PATCH 09/26] Update backup-and-restore-premium.md --- tidb-cloud/premium/backup-and-restore-premium.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index 7779c7c1bca08..678385c25ba4c 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -173,7 +173,7 @@ To restore a backup generated by a {{{ .dedicated }}} cluster, follow these step ### Restore backups from a cloud storage -{{{ .premium }}} supports restoring backups from a cloud storage (such as AWS S3 or Alibaba Cloud OSS) to a new instance. This feature is compatible with backups generated from {{{ .dedicated }}} clusters or self-managed (on-premises) clusters. +{{{ .premium }}} supports restoring backups from a cloud storage (such as AWS S3 and Alibaba Cloud Object Storage Service (OSS)) to a new instance. This feature is compatible with backups generated from {{{ .dedicated }}} clusters or self-managed (on-premises) clusters. > **Note:** > @@ -184,8 +184,8 @@ To restore a backup generated by a {{{ .dedicated }}} cluster, follow these step Before you begin, ensure the following: - Supported cloud providers: currently, only backups located in **AWS S3** and **Alibaba Cloud OSS** are supported. -- Cloud provider consistency: you can only restore to a new instance that uses the same cloud provider as your storage bucket. -- Credentials: You have the access key and secret key with sufficient permissions to access the backup files. +- Cloud provider consistency: you can only restore backups to a new instance in the same cloud provider as your storage bucket. +- Credentials: you have the access key and secret key with sufficient permissions to access the backup files. #### Steps @@ -202,7 +202,7 @@ To restore backups from a cloud storage, do the following: 3. Click **Verify Backup and Next**. -4. If the verification is successful, the **Restore to a New Instance** page appears. Review the backup metadata information displayed at the top of the page. Follow the same steps as [create a new TiDB instance](/tidb-cloud/premium/create-tidb-instance-premium.md) to restore the backup to a new instance. +4. If the verification is successful, the **Restore to a New Instance** page appears. Review the backup information displayed at the top of the page. Follow the steps in [Create a {{{ .premium }}} Instance](/tidb-cloud/premium/create-tidb-instance-premium.md) to restore the backup to a new instance. If the information is not correct, click **Previous** to return to the previous page, and then enter the correct information. From fd5fb3ba0f1b83a07e1e7418629e8899fbe99ead Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 22 Dec 2025 11:25:14 +0800 Subject: [PATCH 10/26] Update backup-and-restore-premium.md --- tidb-cloud/premium/backup-and-restore-premium.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index 678385c25ba4c..18c3e79bf5a51 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -171,9 +171,9 @@ 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 a cloud storage +### Restore backups from cloud storage -{{{ .premium }}} supports restoring backups from a cloud storage (such as AWS S3 and Alibaba Cloud Object Storage Service (OSS)) to a new instance. This feature is compatible with backups generated from {{{ .dedicated }}} clusters or self-managed (on-premises) clusters. +{{{ .premium }}} supports restoring backups from cloud storage (such as AWS S3 and Alibaba Cloud Object Storage Service (OSS)) to a new instance. This feature is compatible with backups generated from {{{ .dedicated }}} clusters or self-managed (on-premises) clusters. > **Note:** > @@ -189,7 +189,7 @@ Before you begin, ensure the following: #### Steps -To restore backups from a cloud storage, do the following: +To restore backups from cloud storage, do the following: 1. Log in to the [TiDB Cloud console](https://tidbcloud.com), and then navigate to the [**TiDB Instances**](https://tidbcloud.com/tidbs) page. In the upper-right corner, click **...** , and then click **Restore from Cloud Storage**. From 3adebbb4b6efb76a38c75f6c9e23fd3f80b3ac5f Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 22 Dec 2025 13:17:03 +0800 Subject: [PATCH 11/26] Refactor limitations and prerequisites in restore guide Moved and consolidated limitations for restoring backups to a dedicated section before the steps. Clarified supported cloud providers, manual backup support, and cross-region fees. Updated prerequisites to focus on required credentials. --- .../premium/backup-and-restore-premium.md | 21 +++++++------------ 1 file changed, 7 insertions(+), 14 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index 18c3e79bf5a51..6d58ff46ba503 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -175,20 +175,17 @@ To restore a backup generated by a {{{ .dedicated }}} cluster, follow these step {{{ .premium }}} supports restoring backups from cloud storage (such as AWS S3 and Alibaba Cloud Object Storage Service (OSS)) to a new instance. This feature is compatible with backups generated from {{{ .dedicated }}} clusters or self-managed (on-premises) clusters. -> **Note:** -> -> If the instance and the storage bucket are located in different regions, additional cross-region data transfer fees might apply. - -#### Prerequisites - -Before you begin, ensure the following: +## Limitations -- Supported cloud providers: currently, only backups located in **AWS S3** and **Alibaba Cloud OSS** are supported. -- Cloud provider consistency: you can only restore backups to a new instance in the same cloud provider as your storage bucket. -- Credentials: you have the access key and secret key with sufficient permissions to access the backup files. +- Currently, manual backups are not supported for {{{ .premium }}} instances. +- Currently, only backups located in **AWS S3** and **Alibaba Cloud OSS** are supported. +- You can only restore backups to a new instance in the same cloud provider as your storage bucket. +- If the instance and the storage bucket are located in different regions, additional cross-region data transfer fees might apply. #### Steps +Before getting started, ensure that you have the access key and secret key with sufficient permissions to access the backup files. + To restore backups from cloud storage, do the following: 1. Log in to the [TiDB Cloud console](https://tidbcloud.com), and then navigate to the [**TiDB Instances**](https://tidbcloud.com/tidbs) page. In the upper-right corner, click **...** , and then click **Restore from Cloud Storage**. @@ -207,7 +204,3 @@ To restore backups from cloud storage, do the following: If the information is not correct, click **Previous** to return to the previous page, and then enter the correct information. 5. Click **Restore** to restore the backup. - -## Limitations - -Currently, manual backups are not supported for {{{ .premium }}} instances. From 1248d0238ece62bf429ab8346e3dbc337e2370b9 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Mon, 22 Dec 2025 14:24:06 +0800 Subject: [PATCH 12/26] Apply suggestions from code review Co-authored-by: Grace Cai --- .../premium/backup-and-restore-premium.md | 23 ++++++++++--------- 1 file changed, 12 insertions(+), 11 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index 6d58ff46ba503..ddd29a56ec56d 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -173,18 +173,18 @@ To restore a backup generated by a {{{ .dedicated }}} cluster, follow these step ### Restore backups from cloud storage -{{{ .premium }}} supports restoring backups from cloud storage (such as AWS S3 and Alibaba Cloud Object Storage Service (OSS)) to a new instance. This feature is compatible with backups generated from {{{ .dedicated }}} clusters or self-managed (on-premises) clusters. +{{{ .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. -## Limitations +#### Limitations - Currently, manual backups are not supported for {{{ .premium }}} instances. -- Currently, only backups located in **AWS S3** and **Alibaba Cloud OSS** are supported. -- You can only restore backups to a new instance in the same cloud provider as your storage bucket. +- Currently, only backups located in **Amazon S3** and **Alibaba Cloud OSS** are supported for restore. +- You can restore backups only to a new instance hosted by the same cloud provider as your storage bucket. - If the instance and the storage bucket are located in different regions, additional cross-region data transfer fees might apply. #### Steps -Before getting started, ensure that you have the access key and secret key with sufficient permissions to access the backup files. +Before you begin, ensure that you have an access key and secret key with sufficient permissions to access the backup files. To restore backups from cloud storage, do the following: @@ -192,15 +192,16 @@ To restore backups from cloud storage, do the following: 2. On the **Select Backup Storage Location** page, provide the following information: - - **Cloud Provider**: select the provider where your backup file is located - - **Backup Files URI**: enter the URI of the top-level folder that contains your backup files - - **Access Key ID**: enter your access key ID - - **Access Key Secret**: enter your access key secret + - **Cloud Provider**: select the cloud provider where your backup files are stored. + - **Region**: if your cloud provider is Alibaba Cloud OSS, select a Region. + - **Backup Files URI**: enter the URI of the top-level folder that contains your backup files. + - **Access Key ID**: enter your access key ID. + - **Access Key Secret**: enter your access key secret. 3. Click **Verify Backup and Next**. -4. If the verification is successful, the **Restore to a New Instance** page appears. Review the backup information displayed at the top of the page. Follow the steps in [Create a {{{ .premium }}} Instance](/tidb-cloud/premium/create-tidb-instance-premium.md) to restore the backup to a new instance. +4. If the verification is successful, the **Restore to a New Instance** page appears. Review the backup information displayed at the top of the page, and then follow the steps in [Create a {{{ .premium }}} Instance](/tidb-cloud/premium/create-tidb-instance-premium.md) to restore the backup to a new instance. - If the information is not correct, click **Previous** to return to the previous page, and then enter the correct information. + If the backup information is incorrect, click **Previous** to return to the previous page, and then enter the correct information. 5. Click **Restore** to restore the backup. From 97e95ab88d4100f68cbfb877678b637cfbaff4cd Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 22 Dec 2025 14:27:45 +0800 Subject: [PATCH 13/26] Update serverless-high-availability.md --- tidb-cloud/serverless-high-availability.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/serverless-high-availability.md b/tidb-cloud/serverless-high-availability.md index 60d4823859523..733bc87b257e9 100644 --- a/tidb-cloud/serverless-high-availability.md +++ b/tidb-cloud/serverless-high-availability.md @@ -1,9 +1,9 @@ --- -title: High Availability in {{{ .starter }}} and Essential -summary: Learn about the high availability architecture of {{{ .starter }}} and Essential. Discover Zonal and Regional High Availability options, automated backups, failover processes, and how TiDB ensures data durability and business continuity. +title: High Availability in {{{ .starter }}}, Essential and {{{ .premium }}} +summary: Learn about the high availability architecture of {{{ .starter }}}, Essential and {{{ .premium }}}. Discover Zonal and Regional High Availability options, automated backups, failover processes, and how TiDB ensures data durability and business continuity. --- -# High Availability in {{{ .starter }}} and Essential +# High Availability in {{{ .starter }}}, Essential and {{{ .premium }}} TiDB Cloud is designed with robust mechanisms to maintain high availability and data durability by default, preventing single points of failure and ensuring continuous service even in the face of disruptions. As a fully managed service based on the battle-tested TiDB Open Source product, it inherits TiDB's core high availability (HA) features and augments them with additional cloud-native capabilities. @@ -16,6 +16,7 @@ TiDB Cloud extends these capabilities with zonal high availability and regional > **Note:** > > - For {{{ .starter }}} clusters, only zonal high availability is enabled, and it is not configurable. +> - For {{{ .premium }}} clusters, only regional high availability is enabled, and it is not configurable. > - For {{{ .essential }}} clusters hosted in the AWS Tokyo (ap-northeast-1) region or any Alibaba Cloud region, regional high availability is enabled by default. You can change it to zonal high availability as needed during cluster creation. For {{{ .essential }}} clusters hosted in other regions, only zonal high availability is enabled, and it is not configurable. - **Zonal high availability**: This option places all nodes within a single availability zone, reducing network latency. It ensures high availability without requiring application-level redundancy across zones, making it suitable for applications that prioritize low latency within a single zone. For more information, see [Zonal high availability architecture](#zonal-high-availability-architecture). From c539192b789d5d48a09d931f564a68e7a941ce1a Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 22 Dec 2025 14:31:25 +0800 Subject: [PATCH 14/26] Update high availability references to include Premium Expanded documentation links to reference 'Premium' alongside 'Starter' and 'Essential' in high availability sections for clarity and completeness. --- tidb-cloud/architecture-concepts.md | 2 +- tidb-cloud/key-concepts.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/tidb-cloud/architecture-concepts.md b/tidb-cloud/architecture-concepts.md index e184dc82fd064..8af2d234555ea 100644 --- a/tidb-cloud/architecture-concepts.md +++ b/tidb-cloud/architecture-concepts.md @@ -60,7 +60,7 @@ For applications experiencing growing workloads and needing scalability in real - By default, clusters utilizing the Zonal High Availability option have all components located within the same availability zone, which results in lower network latency. - For applications that require maximum infrastructure isolation and redundancy, the Regional High Availability option distributes nodes across multiple availability zones. -For more information, see [High Availability in {{{ .starter }}} and Essential](/tidb-cloud/serverless-high-availability.md). +For more information, see [High Availability in {{{ .starter }}}, Essential and {{{ .premium }}}](/tidb-cloud/serverless-high-availability.md). ## TiDB Cloud Dedicated diff --git a/tidb-cloud/key-concepts.md b/tidb-cloud/key-concepts.md index e92067db3ca78..268837562a878 100644 --- a/tidb-cloud/key-concepts.md +++ b/tidb-cloud/key-concepts.md @@ -39,7 +39,7 @@ TiDB Cloud Dedicated lets you adjust its compute and storage resources separatel TiDB Cloud ensures high availability in {{{ .starter }}}, {{{ .essential }}}, and TiDB Cloud Dedicated clusters: -- [High Availability in {{{ .starter }}} and Essential](/tidb-cloud/serverless-high-availability.md) +- [High Availability in {{{ .starter }}}, Essential and {{{ .premium }}}](/tidb-cloud/serverless-high-availability.md) - [High Availability in TiDB Cloud Dedicated](/tidb-cloud/high-availability-with-multi-az.md) ## Monitoring From 34d8259aaa527f1f426d57bbccc33b9d1c8dd84b Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 22 Dec 2025 14:53:32 +0800 Subject: [PATCH 15/26] Update serverless-high-availability.md --- tidb-cloud/serverless-high-availability.md | 23 +++++++++++++++++++--- 1 file changed, 20 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/serverless-high-availability.md b/tidb-cloud/serverless-high-availability.md index 733bc87b257e9..2ca85b8a4aad0 100644 --- a/tidb-cloud/serverless-high-availability.md +++ b/tidb-cloud/serverless-high-availability.md @@ -1,24 +1,41 @@ --- -title: High Availability in {{{ .starter }}}, Essential and {{{ .premium }}} -summary: Learn about the high availability architecture of {{{ .starter }}}, Essential and {{{ .premium }}}. Discover Zonal and Regional High Availability options, automated backups, failover processes, and how TiDB ensures data durability and business continuity. +title: High Availability in TiDB Cloud +summary: Learn about the high availability architecture of {{{ .starter }}} and {{{ .essential }}}{{{ .starter }}}, {{{ .essential }}}, and {{{ .premium }}}. Discover Zonal and Regional High Availability options, automated backups, failover processes, and how TiDB ensures data durability and business continuity. --- -# High Availability in {{{ .starter }}}, Essential and {{{ .premium }}} +# High Availability in TiDB Cloud TiDB Cloud is designed with robust mechanisms to maintain high availability and data durability by default, preventing single points of failure and ensuring continuous service even in the face of disruptions. As a fully managed service based on the battle-tested TiDB Open Source product, it inherits TiDB's core high availability (HA) features and augments them with additional cloud-native capabilities. +> **Note:** +> +> This document is only applicable for {{{ .starter }}} and {{{ .essential }}}{{{ .starter }}}, {{{ .essential }}}, and {{{ .premium }}}. + ## Overview TiDB ensures high availability and data durability using the Raft consensus algorithm. This algorithm consistently replicates data changes across multiple nodes, allowing TiDB to handle read and write requests even in the event of node failures or network partitions. This approach provides both high data durability and fault tolerance. TiDB Cloud extends these capabilities with zonal high availability and regional high availability to meet different operational requirements. + + +> **Note:** +> +> - For {{{ .starter }}} clusters, only zonal high availability is enabled, and it is not configurable. +> - For {{{ .essential }}} clusters hosted in the AWS Tokyo (ap-northeast-1) region or any Alibaba Cloud region, regional high availability is enabled by default. You can change it to zonal high availability as needed during cluster creation. For {{{ .essential }}} clusters hosted in other regions, only zonal high availability is enabled, and it is not configurable. + + + + + > **Note:** > > - For {{{ .starter }}} clusters, only zonal high availability is enabled, and it is not configurable. > - For {{{ .premium }}} clusters, only regional high availability is enabled, and it is not configurable. > - For {{{ .essential }}} clusters hosted in the AWS Tokyo (ap-northeast-1) region or any Alibaba Cloud region, regional high availability is enabled by default. You can change it to zonal high availability as needed during cluster creation. For {{{ .essential }}} clusters hosted in other regions, only zonal high availability is enabled, and it is not configurable. + + - **Zonal high availability**: This option places all nodes within a single availability zone, reducing network latency. It ensures high availability without requiring application-level redundancy across zones, making it suitable for applications that prioritize low latency within a single zone. For more information, see [Zonal high availability architecture](#zonal-high-availability-architecture). - **Regional high availability (beta)**: This option distributes nodes across multiple availability zones, offering maximum infrastructure isolation and redundancy. It provides the highest level of availability but requires application-level redundancy across zones. It is recommended to choose this option if you need maximum availability protection against infrastructure failures within a zone. Note that it increases latency and might incur cross-zone data transfer fees. This feature is available in regions with more than three availability zones and can only be enabled during cluster creation. For more information, see [Regional high availability architecture](#regional-high-availability-architecture). From 6ff8e53eba066e24f7dd69e9b7e036f050dd02c7 Mon Sep 17 00:00:00 2001 From: houfaxin Date: Mon, 22 Dec 2025 15:05:45 +0800 Subject: [PATCH 16/26] Update high availability documentation links and notes Standardized references to high availability documentation in TiDB Cloud by updating link text in architecture-concepts.md and key-concepts.md. Added a note in serverless-high-availability.md to direct users to the dedicated high availability documentation for TiDB Cloud Dedicated. --- tidb-cloud/architecture-concepts.md | 2 +- tidb-cloud/key-concepts.md | 2 +- tidb-cloud/serverless-high-availability.md | 3 ++- 3 files changed, 4 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/architecture-concepts.md b/tidb-cloud/architecture-concepts.md index 8af2d234555ea..a6f5976542d6a 100644 --- a/tidb-cloud/architecture-concepts.md +++ b/tidb-cloud/architecture-concepts.md @@ -60,7 +60,7 @@ For applications experiencing growing workloads and needing scalability in real - By default, clusters utilizing the Zonal High Availability option have all components located within the same availability zone, which results in lower network latency. - For applications that require maximum infrastructure isolation and redundancy, the Regional High Availability option distributes nodes across multiple availability zones. -For more information, see [High Availability in {{{ .starter }}}, Essential and {{{ .premium }}}](/tidb-cloud/serverless-high-availability.md). +For more information, see [High Availability in TiDB Cloud](/tidb-cloud/serverless-high-availability.md). ## TiDB Cloud Dedicated diff --git a/tidb-cloud/key-concepts.md b/tidb-cloud/key-concepts.md index 268837562a878..505e12f245014 100644 --- a/tidb-cloud/key-concepts.md +++ b/tidb-cloud/key-concepts.md @@ -39,7 +39,7 @@ TiDB Cloud Dedicated lets you adjust its compute and storage resources separatel TiDB Cloud ensures high availability in {{{ .starter }}}, {{{ .essential }}}, and TiDB Cloud Dedicated clusters: -- [High Availability in {{{ .starter }}}, Essential and {{{ .premium }}}](/tidb-cloud/serverless-high-availability.md) +- [High Availability in TiDB Cloud](/tidb-cloud/serverless-high-availability.md) - [High Availability in TiDB Cloud Dedicated](/tidb-cloud/high-availability-with-multi-az.md) ## Monitoring diff --git a/tidb-cloud/serverless-high-availability.md b/tidb-cloud/serverless-high-availability.md index 2ca85b8a4aad0..a09d12b31748f 100644 --- a/tidb-cloud/serverless-high-availability.md +++ b/tidb-cloud/serverless-high-availability.md @@ -9,7 +9,8 @@ TiDB Cloud is designed with robust mechanisms to maintain high availability and > **Note:** > -> This document is only applicable for {{{ .starter }}} and {{{ .essential }}}{{{ .starter }}}, {{{ .essential }}}, and {{{ .premium }}}. +> - This document is only applicable for {{{ .starter }}} and {{{ .essential }}}{{{ .starter }}}, {{{ .essential }}}, and {{{ .premium }}}. +> - For high availability in TiDB Cloud Dedicated, see [High Availability in TiDB Cloud Dedicated](/tidb-cloud/high-availability-with-multi-az.md). ## Overview From 56a8077002cf26d0ce101d51d59ee24dad779a84 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Mon, 22 Dec 2025 15:47:40 +0800 Subject: [PATCH 17/26] Apply suggestions from code review Co-authored-by: Grace Cai --- tidb-cloud/key-concepts.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tidb-cloud/key-concepts.md b/tidb-cloud/key-concepts.md index 505e12f245014..43b9e74ac201b 100644 --- a/tidb-cloud/key-concepts.md +++ b/tidb-cloud/key-concepts.md @@ -37,10 +37,10 @@ TiDB Cloud Dedicated lets you adjust its compute and storage resources separatel ## High availability -TiDB Cloud ensures high availability in {{{ .starter }}}, {{{ .essential }}}, and TiDB Cloud Dedicated clusters: +TiDB Cloud ensures high availability in all supported plans: -- [High Availability in TiDB Cloud](/tidb-cloud/serverless-high-availability.md) -- [High Availability in TiDB Cloud Dedicated](/tidb-cloud/high-availability-with-multi-az.md) +- For {{{ .starter }}} and {{{ .essential }}}{{{ .starter }}}, {{{ .essential }}}, and {{{ .premium }}}, see [High Availability in TiDB Cloud](/tidb-cloud/serverless-high-availability.md). +- For TiDB Cloud Dedicated, see [High Availability in TiDB Cloud Dedicated](/tidb-cloud/high-availability-with-multi-az.md). ## Monitoring From ba0010549b0d9acb7f1e7eb8ad2f7148a5dd13b7 Mon Sep 17 00:00:00 2001 From: houfaxin Date: Tue, 23 Dec 2025 10:27:00 +0800 Subject: [PATCH 18/26] Update backup-and-restore-premium.md --- tidb-cloud/premium/backup-and-restore-premium.md | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index ddd29a56ec56d..fad03aa08df14 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -175,12 +175,11 @@ To restore a backup generated by a {{{ .dedicated }}} cluster, follow these step {{{ .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. -#### Limitations - -- Currently, manual backups are not supported for {{{ .premium }}} instances. -- Currently, only backups located in **Amazon S3** and **Alibaba Cloud OSS** are supported for restore. -- You can restore backups only to a new instance hosted by the same cloud provider as your storage bucket. -- If the instance and the storage bucket are located in different regions, additional cross-region data transfer fees might apply. +>**Note:** +> +> - Currently, only backups located in **Amazon S3** and **Alibaba Cloud OSS** are supported for restore. +> - You can restore backups only to a new instance hosted by the same cloud provider as your storage bucket. +> - If the instance and the storage bucket are located in different regions, additional cross-region data transfer fees might apply. #### Steps @@ -205,3 +204,7 @@ To restore backups from cloud storage, do the following: If the backup information is incorrect, click **Previous** to return to the previous page, and then enter the correct information. 5. Click **Restore** to restore the backup. + +## Limitations + +Currently, manual backups are not supported for {{{ .premium }}} instances. From 9887ef0cbbd14ec3992a41f638c9b1ef4d42b2de Mon Sep 17 00:00:00 2001 From: houfaxin Date: Tue, 23 Dec 2025 10:27:13 +0800 Subject: [PATCH 19/26] Update backup-and-restore-premium.md --- tidb-cloud/premium/backup-and-restore-premium.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index fad03aa08df14..39d0bfda18601 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -205,6 +205,6 @@ To restore backups from cloud storage, do the following: 5. Click **Restore** to restore the backup. -## Limitations +## Limitation Currently, manual backups are not supported for {{{ .premium }}} instances. From 2d2636de203c80d87cd3938855e06853f79bbb5b Mon Sep 17 00:00:00 2001 From: Cheng Weiwei <65707268+wildpcww@users.noreply.github.com> Date: Wed, 24 Dec 2025 14:09:19 +0800 Subject: [PATCH 20/26] Update backup-and-restore-premium.md --- .../premium/backup-and-restore-premium.md | 61 ++++++++----------- 1 file changed, 26 insertions(+), 35 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index 39d0bfda18601..9b394b771bf70 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -30,49 +30,40 @@ Backup files can originate from the following sources: ## Automatic backups -TiDB Cloud automatically backs up your instance data, letting you restore data from a backup snapshot to minimize data loss in the event of a disaster. +TiDB Cloud Premium offers enhanced automatic backup capabilities, combining high-frequency snapshots with log backups to ensure maximum data reliability for production environments. -### Learn about the backup setting +### Automatic Backup Policy Details +TiDB Cloud Premium instances provide a comprehensive data protection strategy through a multi-layered backup architecture: -Compared with {{{ .starter }}} clusters and {{{ .essential }}} clusters, {{{ .premium }}} offers enhanced backup capabilities, including longer retention and hourly backup support. +- **Point-in-Time Recovery (PITR)** + - Retention: 7 days. + - Restore Detail: Allows restoration to any specific moment within the 7-day retention period. -| Backup setting | {{{ .starter }}} (free) | {{{ .starter }}} (with spending limit > 0) | {{{ .essential }}} | {{{ .premium }}} | -|------------------|--------------------------|---------------------------------------------|--------------------|------------------| -| Backup Cycle | Daily | Daily | Daily | Daily + Hourly | -| Backup Retention | 1 day | 30 days | 30 days | Up to 33 days | -| Backup Time | Fixed time | Configurable | Configurable | Configurable | +- **Hourly Backup Snapshot** + - Retention: 7 days. + - Restore Detail: Regular restoration is available for each hourly snapshot generated within the 7-day window. -- **Backup Cycle** determines how frequently backups are created. +- **Daily Backup Snapshot** + - Retention: 33 days. + - Restore Detail: Restoration is available for daily snapshots (defaulted at 0:00 UTC) for the 33-day retention period. - - Premium instances support both **daily** and **hourly** backups. - - The **default** is **hourly backups**. +### Backup Execution Rules +- **Backup Cycle**: Premium instances support both daily and hourly automatic backups. -- **Backup Retention** is the duration for which backups are retained. Expired backups cannot be restored. +- **Backup Time**: + - Daily Backup: Runs at a fixed time of 0:00 UTC. Backup time management/customization is currently not supported. + - Hourly Backup: Always runs on the hour. - - Premium instances can retain backups for up to **33 days**. +- **Retention Mechanism**: Backups that exceed their retention period (7 days or 33 days) will automatically expire and cannot be restored. -- **Backup Time** is the scheduled start time for backups. - - - For Premium instances, **daily backups** can be configured to start at a preferred time (in 30-minute intervals), while **hourly backups** always run on the hour. - -### Configure the backup settings - -To configure backups for a {{{ .premium }}} instance, perform the following steps: - -1. Navigate to the [**Backup**](#view-the-backup-page) page of your TiDB instance. - -2. Click **Backup Setting**. This will open the **Backup Setting** window, where you can configure automatic backup options. - -3. In **Backup Cycle**, choose between the **Hourly Backup** and **Daily Backup** tabs: - - - **Hourly Backup** (default): - - Runs **on the hour**. - - You can configure **Backup Retention** (1–33 days). - - **Daily Backup**: - - Runs at a configurable time in **30-minute intervals**. - - You can configure both **Backup Retention** (1–33 days) and **Backup Time**. +> **Note**: +> +> **Storage Fees**: Storage costs for automatic backups are calculated based on your backup data volume and retention duration. +> +> **Extending Retention**: If you need to extend the backup retention period, please contact TiDB support team. +> +> **Manual Backup**: Manual backup is currently not supported. -4. Click **Save** to save your settings. ### Delete backup files @@ -205,6 +196,6 @@ To restore backups from cloud storage, do the following: 5. Click **Restore** to restore the backup. -## Limitation +## Limitations Currently, manual backups are not supported for {{{ .premium }}} instances. From 4ac3a13c75c8362f4191048e9a39ddfec9058a9a Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Wed, 24 Dec 2025 14:20:43 +0800 Subject: [PATCH 21/26] Apply suggestions from code review Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- tidb-cloud/key-concepts.md | 2 +- tidb-cloud/premium/backup-and-restore-premium.md | 10 +++++----- tidb-cloud/serverless-high-availability.md | 4 ++-- 3 files changed, 8 insertions(+), 8 deletions(-) diff --git a/tidb-cloud/key-concepts.md b/tidb-cloud/key-concepts.md index 43b9e74ac201b..d4f59f32ab76d 100644 --- a/tidb-cloud/key-concepts.md +++ b/tidb-cloud/key-concepts.md @@ -39,7 +39,7 @@ TiDB Cloud Dedicated lets you adjust its compute and storage resources separatel TiDB Cloud ensures high availability in all supported plans: -- For {{{ .starter }}} and {{{ .essential }}}{{{ .starter }}}, {{{ .essential }}}, and {{{ .premium }}}, see [High Availability in TiDB Cloud](/tidb-cloud/serverless-high-availability.md). +- For {{{ .starter }}} and {{{ .essential }}} {{{ .starter }}}, {{{ .essential }}}, and {{{ .premium }}}, see [High Availability in TiDB Cloud](/tidb-cloud/serverless-high-availability.md). - For TiDB Cloud Dedicated, see [High Availability in TiDB Cloud Dedicated](/tidb-cloud/high-availability-with-multi-az.md). ## Monitoring diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index 9b394b771bf70..5c2c6e369f2f8 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -60,7 +60,7 @@ TiDB Cloud Premium instances provide a comprehensive data protection strategy th > > **Storage Fees**: Storage costs for automatic backups are calculated based on your backup data volume and retention duration. > -> **Extending Retention**: If you need to extend the backup retention period, please contact TiDB support team. +> **Extending Retention**: If you need to extend the backup retention period, contact the TiDB support team. > > **Manual Backup**: Manual backup is currently not supported. @@ -168,7 +168,7 @@ To restore a backup generated by a {{{ .dedicated }}} cluster, follow these step >**Note:** > -> - Currently, only backups located in **Amazon S3** and **Alibaba Cloud OSS** are supported for restore. +> - Currently, only backups located in **Amazon S3** and **Alibaba Cloud OSS** are supported. > - You can restore backups only to a new instance hosted by the same cloud provider as your storage bucket. > - If the instance and the storage bucket are located in different regions, additional cross-region data transfer fees might apply. @@ -176,14 +176,14 @@ To restore a backup generated by a {{{ .dedicated }}} cluster, follow these step Before you begin, ensure that you have an access key and secret key with sufficient permissions to access the backup files. -To restore backups from cloud storage, do the following: +To restore backups from cloud storage, follow these steps: -1. Log in to the [TiDB Cloud console](https://tidbcloud.com), and then navigate to the [**TiDB Instances**](https://tidbcloud.com/tidbs) page. In the upper-right corner, click **...** , and then click **Restore from Cloud Storage**. +1. Log in to the [TiDB Cloud console](https://tidbcloud.com), and then navigate to the [**TiDB Instances**](https://tidbcloud.com/tidbs) page. In the upper-right corner, click **...**, and then click **Restore from Cloud Storage**. 2. On the **Select Backup Storage Location** page, provide the following information: - **Cloud Provider**: select the cloud provider where your backup files are stored. - - **Region**: if your cloud provider is Alibaba Cloud OSS, select a Region. + - **Region**: if your cloud provider is Alibaba Cloud OSS, select a region. - **Backup Files URI**: enter the URI of the top-level folder that contains your backup files. - **Access Key ID**: enter your access key ID. - **Access Key Secret**: enter your access key secret. diff --git a/tidb-cloud/serverless-high-availability.md b/tidb-cloud/serverless-high-availability.md index a09d12b31748f..c66c85f744ba4 100644 --- a/tidb-cloud/serverless-high-availability.md +++ b/tidb-cloud/serverless-high-availability.md @@ -1,6 +1,6 @@ --- title: High Availability in TiDB Cloud -summary: Learn about the high availability architecture of {{{ .starter }}} and {{{ .essential }}}{{{ .starter }}}, {{{ .essential }}}, and {{{ .premium }}}. Discover Zonal and Regional High Availability options, automated backups, failover processes, and how TiDB ensures data durability and business continuity. +summary: Learn about the high availability architecture of {{{ .starter }}} and {{{ .essential }}} {{{ .starter }}}, {{{ .essential }}}, and {{{ .premium }}}. Discover Zonal and Regional High Availability options, automated backups, failover processes, and how TiDB ensures data durability and business continuity. --- # High Availability in TiDB Cloud @@ -9,7 +9,7 @@ TiDB Cloud is designed with robust mechanisms to maintain high availability and > **Note:** > -> - This document is only applicable for {{{ .starter }}} and {{{ .essential }}}{{{ .starter }}}, {{{ .essential }}}, and {{{ .premium }}}. +> - This document is only applicable for {{{ .starter }}} and {{{ .essential }}} {{{ .starter }}}, {{{ .essential }}}, and {{{ .premium }}}. > - For high availability in TiDB Cloud Dedicated, see [High Availability in TiDB Cloud Dedicated](/tidb-cloud/high-availability-with-multi-az.md). ## Overview From abc79650d1f7f2a0dc97ed70c969c58d2c508945 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Wed, 24 Dec 2025 15:31:09 +0800 Subject: [PATCH 22/26] Apply suggestions from code review --- .../premium/backup-and-restore-premium.md | 35 +++++++++---------- 1 file changed, 17 insertions(+), 18 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index d7ebcf8b92f18..8d3623503c95e 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -30,39 +30,38 @@ Backup files can originate from the following sources: ## Automatic backups -TiDB Cloud Premium offers enhanced automatic backup capabilities, combining high-frequency snapshots with log backups to ensure maximum data reliability for production environments. +{{{ .premium }}} offers enhanced automatic backup capabilities, combining high-frequency snapshots with log backups to ensure maximum data reliability for production environments. -### Automatic Backup Policy Details -TiDB Cloud Premium instances provide a comprehensive data protection strategy through a multi-layered backup architecture: +### Automatic backup policies + +{{{ .premium }}} instances provide a comprehensive data protection strategy through a multi-layered backup architecture: - **Point-in-Time Recovery (PITR)** - Retention: 7 days. - Restore Detail: Allows restoration to any specific moment within the 7-day retention period. -- **Hourly Backup Snapshot** +- **Hourly backup snapshot** - Retention: 7 days. - - Restore Detail: Regular restoration is available for each hourly snapshot generated within the 7-day window. + - Restore detail: regular restoration is available for each hourly snapshot generated within the 7-day window. -- **Daily Backup Snapshot** +- **Daily backup snapshot** - Retention: 33 days. - - Restore Detail: Restoration is available for daily snapshots (defaulted at 0:00 UTC) for the 33-day retention period. + - Restore detail: restoration is available for daily snapshots (at 0:00 UTC by default) for the 33-day retention period. + +### Backup execution rules -### Backup Execution Rules -- **Backup Cycle**: Premium instances support both daily and hourly automatic backups. +- **Backup cycle**: {{{ .premium }}} instances support both daily and hourly automatic backups. - **Backup Time**: - - Daily Backup: Runs at a fixed time of 0:00 UTC. Backup time management/customization is currently not supported. - - Hourly Backup: Always runs on the hour. + - Daily backup: runs at a fixed time of 0:00 UTC. Backup time management or customization is currently not supported. + - Hourly backup: always runs on the hour. -- **Retention Mechanism**: Backups that exceed their retention period (7 days or 33 days) will automatically expire and cannot be restored. +- **Retention mechanism**: backups that exceed their retention period (7 days or 33 days) will automatically expire and cannot be restored. -> **Note**: -> -> **Storage Fees**: Storage costs for automatic backups are calculated based on your backup data volume and retention duration. -> -> **Extending Retention**: If you need to extend the backup retention period, contact the TiDB support team. +> **Note:** > -> **Manual Backup**: Manual backup is currently not supported. +> - Storage costs for automatic backups are calculated based on your backup data volume and retention duration. +> - If you need to extend the backup retention period, contact [TiDB Cloud Support](https://docs.pingcap.com/tidbcloud/tidb-cloud-support). ### Delete backup files From 6a31fdc8b6c8f589f88230ddea4b0d6a01e042f5 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Wed, 24 Dec 2025 15:45:48 +0800 Subject: [PATCH 23/26] Update tidb-cloud/premium/backup-and-restore-premium.md --- tidb-cloud/premium/backup-and-restore-premium.md | 1 - 1 file changed, 1 deletion(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index 8d3623503c95e..005155be0a7dc 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -63,7 +63,6 @@ Backup files can originate from the following sources: > - Storage costs for automatic backups are calculated based on your backup data volume and retention duration. > - If you need to extend the backup retention period, contact [TiDB Cloud Support](https://docs.pingcap.com/tidbcloud/tidb-cloud-support). - ### Delete backup files To delete an existing backup file for your {{{ .premium }}} instance, perform the following steps: From 82d7a9cae824823130416f8532e71ac71149d6a9 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Wed, 24 Dec 2025 16:56:16 +0800 Subject: [PATCH 24/26] Apply suggestions from code review --- tidb-cloud/premium/backup-and-restore-premium.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index 005155be0a7dc..6013e1aeeb43c 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -36,11 +36,11 @@ Backup files can originate from the following sources: {{{ .premium }}} instances provide a comprehensive data protection strategy through a multi-layered backup architecture: -- **Point-in-Time Recovery (PITR)** +- Point-in-Time Recovery (PITR) - Retention: 7 days. - - Restore Detail: Allows restoration to any specific moment within the 7-day retention period. + - Restore detail: allows restoration to any specific moment within the 7-day retention period. -- **Hourly backup snapshot** +- Hourly backup snapshot - Retention: 7 days. - Restore detail: regular restoration is available for each hourly snapshot generated within the 7-day window. @@ -50,11 +50,11 @@ Backup files can originate from the following sources: ### Backup execution rules -- **Backup cycle**: {{{ .premium }}} instances support both daily and hourly automatic backups. +- Backup cycle: {{{ .premium }}} instances support both daily and hourly automatic backups. -- **Backup Time**: - - Daily backup: runs at a fixed time of 0:00 UTC. Backup time management or customization is currently not supported. +- Backup time: - Hourly backup: always runs on the hour. + - Daily backup: runs at a fixed time of 0:00 UTC. Currently, backup time management or customization is not supported. - **Retention mechanism**: backups that exceed their retention period (7 days or 33 days) will automatically expire and cannot be restored. From 9fa36ddcc633db14379419ab971c401b960d5d37 Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Wed, 24 Dec 2025 17:24:15 +0800 Subject: [PATCH 25/26] Update tidb-cloud/premium/backup-and-restore-premium.md --- tidb-cloud/premium/backup-and-restore-premium.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index 6013e1aeeb43c..fc8c68f28a5b8 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -44,7 +44,7 @@ Backup files can originate from the following sources: - Retention: 7 days. - Restore detail: regular restoration is available for each hourly snapshot generated within the 7-day window. -- **Daily backup snapshot** +- Daily backup snapshot - Retention: 33 days. - Restore detail: restoration is available for daily snapshots (at 0:00 UTC by default) for the 33-day retention period. From 9b49cab6da3b8c11023e608812bf9e584bf932cd Mon Sep 17 00:00:00 2001 From: xixirangrang Date: Thu, 25 Dec 2025 08:56:00 +0800 Subject: [PATCH 26/26] Apply suggestions from code review --- .../premium/backup-and-restore-premium.md | 25 ++++++++++--------- 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/tidb-cloud/premium/backup-and-restore-premium.md b/tidb-cloud/premium/backup-and-restore-premium.md index fc8c68f28a5b8..947788a3d6d6a 100644 --- a/tidb-cloud/premium/backup-and-restore-premium.md +++ b/tidb-cloud/premium/backup-and-restore-premium.md @@ -30,38 +30,39 @@ Backup files can originate from the following sources: ## Automatic backups -{{{ .premium }}} offers enhanced automatic backup capabilities, combining high-frequency snapshots with log backups to ensure maximum data reliability for production environments. +{{{ .premium }}} offers enhanced automatic backup capabilities, combining high-frequency snapshots with log backups to maximize data reliability for production environments. ### Automatic backup policies {{{ .premium }}} instances provide a comprehensive data protection strategy through a multi-layered backup architecture: - Point-in-Time Recovery (PITR) - - Retention: 7 days. - - Restore detail: allows restoration to any specific moment within the 7-day retention period. + - Retention period: 7 days. + - Restore granularity: supports restoration to any specific moment within the 7-day retention window. - Hourly backup snapshot - - Retention: 7 days. - - Restore detail: regular restoration is available for each hourly snapshot generated within the 7-day window. + - Retention period: 7 days. + - Restore granularity: supports restoration to any specific hourly snapshot generated within the 7-day retention window - Daily backup snapshot - - Retention: 33 days. - - Restore detail: restoration is available for daily snapshots (at 0:00 UTC by default) for the 33-day retention period. + - Retention period: 33 days. + - Restore granularity: supports restoration to any daily snapshot (captured at 0:00 UTC by default) within the 33-day retention window. ### Backup execution rules - Backup cycle: {{{ .premium }}} instances support both daily and hourly automatic backups. -- Backup time: - - Hourly backup: always runs on the hour. - - Daily backup: runs at a fixed time of 0:00 UTC. Currently, backup time management or customization is not supported. +- Backup schedule: + - Hourly backup: always runs at the start of every hour (on the hour). + - Daily backup: executed daily at 0:00 UTC. + - Currently, backup time management or customization is not supported. -- **Retention mechanism**: backups that exceed their retention period (7 days or 33 days) will automatically expire and cannot be restored. +- **Retention mechanism**: backups that exceed their retention period (7 days or 33 days) automatically expire and cannot be restored. > **Note:** > > - Storage costs for automatic backups are calculated based on your backup data volume and retention duration. -> - If you need to extend the backup retention period, contact [TiDB Cloud Support](https://docs.pingcap.com/tidbcloud/tidb-cloud-support). +> - To extend a backup retention period beyond the default limits, contact [TiDB Cloud Support](https://docs.pingcap.com/tidbcloud/tidb-cloud-support). ### Delete backup files