cloud: update steps to access Recycle Bin (#22610)

Author: qiancai

tidb-cloud/backup-and-restore-serverless.md

@@ -85,7 +85,7 @@ The restore process typically completes within a few minutes. If the restore tak
 
 If the data is corrupted after a canceled restore and cannot be recovered, contact [TiDB Cloud Support](/tidb-cloud/tidb-cloud-support.md) for assistance.
 
-### Perform the restore
+### Restore to a new {{{ .starter }}} or Essential instance {#restore-to-a-new-instance}
 
 > **Note:**
 >
@@ -119,15 +119,37 @@ To restore your data to a new {{{ .starter }}} or Essential instance, take the f
     </SimpleTab>
 
 4. Enter a name for the new instance.
-5. Choose a plan for the new instance and update the capacity as needed.
+5. Update the capacity as needed.
 
-    - If you choose a {{{ .starter }}} instance and need more resources than the [free quota](/tidb-cloud/select-cluster-tier.md#usage-quota), set a monthly spending limit.
-    - If you choose a {{{ .essential }}} instance, set the minimum RCU and maximum RCU, and then configure advanced settings as needed.
+    - For a {{{ .starter }}} instance, if you need more resources than the [free quota](/tidb-cloud/select-cluster-tier.md#usage-quota), set a monthly spending limit.
+    - For a {{{ .essential }}} instance, set the minimum RCU and maximum RCU, and then configure advanced settings as needed.
 
 6. Click **Restore** to begin the restore process.
 
 Once the restore process begins, the {{{ .starter }}} or Essential instance status changes to **Restoring**. The {{{ .starter }}} or Essential instance will remain unavailable until the restore is complete and the status changes to **Available**.
 
+### Restore from Recycle Bin
+
+> **Note:**
+>
+> {{{ .starter }}} does not support restoring from Recycle Bin.
+
+To restore a deleted {{{ .essential }}} instance from the Recycle Bin, take the following steps:
+
+1. In the [TiDB Cloud console](https://tidbcloud.com), navigate to the [**My TiDB**](https://tidbcloud.com/tidbs) page of your organization, click **...** in the upper-right corner, and then click **Recycle Bin**.
+
+    >**Tip:**
+    >
+    > 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 **Essential** tab to go to the recycle bin of {{{ .essential }}} instances.
+
+3. Locate the {{{ .essential }}} 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.
+
 ## Limitations
 
 - If a TiFlash replica is enabled, it will be unavailable for a period after the restore, because the data needs to be rebuilt in TiFlash.

tidb-cloud/backup-and-restore.md

@@ -323,12 +323,17 @@ To restore your TiDB Cloud Dedicated cluster data from a backup to a new cluster
 >
 > You cannot restore a deleted cluster to any point in time. You can only select an automatic or manual backup to restore.
 
-To restore a deleted cluster from recycle bin, take the following steps:
+To restore a deleted TiDB Cloud Dedicated cluster from the Recycle Bin, take the following steps:
 
-1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target project using the combo box in the upper-left corner.
-2. In the left navigation pane, click **Project Settings** > **Recycle Bin**.
-3. On the **Recycle Bin** page, locate the cluster you want to restore, click **...** in the **Action** column, and then click **Backups**.
-4. On the **Backups** page, locate your desired backup time, click **...** in the **Action** column, and then click **Restore**.
+1. In the [TiDB Cloud console](https://tidbcloud.com), navigate to the [**My TiDB**](https://tidbcloud.com/tidbs) page of your organization, click **...** in the upper-right corner, and then click **Recycle Bin**.
+
+    >**Tip:**
+    >
+    > 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 **Dedicated** tab to go to the recycle bin of TiDB Cloud Dedicated clusters.
+3. Locate the cluster you want to restore, and then click the **>** button to expand the available backups of the cluster.
+4. In the row of your desired backup, click **...**, and then select **Restore**.
 5. On the **Restore** page, specify a name for the new cluster, and then make the following changes if necessary:
 
     - Update the port number of the cluster.

tidb-cloud/delete-tidb-cluster.md

@@ -26,15 +26,18 @@ You can delete a TiDB Cloud resource at any time by performing the following ste
     - If you have at least one manual or automatic backup, you can see the number of backups and the charging policy for backups. Click **Continue** and enter `<organization name>/<project name>/<resource name>`.
     - If you do not have any backups, just enter `<organization name>/<project name>/<resource name>`.
 
-    If you want to restore a deleted {{{ .dedicated }}} cluster sometime in the future, make sure that you have a backup of the cluster. Otherwise, you cannot restore it anymore. For more information about how to back up TiDB Cloud Dedicated clusters, see [Back Up and Restore TiDB Cloud Dedicated Data](/tidb-cloud/backup-and-restore.md).
+    If you want to restore a deleted {{{ .essential }}} instance or {{{ .dedicated }}} cluster sometime in the future, make sure that you have a backup of it. Otherwise, you cannot restore it anymore.
+
+    - For more information about how to back up {{{ .essential }}} instances, see [Back Up and Restore {{{ .essential }}} Data](/tidb-cloud/backup-and-restore-serverless.md).
+    - For more information about how to back up TiDB Cloud Dedicated clusters, see [Back Up and Restore TiDB Cloud Dedicated Data](/tidb-cloud/backup-and-restore.md).
 
     > **Note:**
     >
-    > [{{{ .starter }}}](/tidb-cloud/select-cluster-tier.md#starter) and [{{{ .essential }}}](/tidb-cloud/select-cluster-tier.md#essential) instances do not support restoring data after the deletion. If you want to delete a {{{ .starter }}} or {{{ .essential }}} instance and restore its data in the future, see [Export Data from {{{ .starter }}} or Essential](/tidb-cloud/serverless-export.md) to export your data as a backup.
+    > [{{{ .starter }}}](/tidb-cloud/select-cluster-tier.md#starter) instances do not support restoring data after the deletion. If you want to delete a {{{ .starter }}} instance and restore its data in the future, see [Export Data from {{{ .starter }}}](/tidb-cloud/serverless-export.md) to export your data as a backup.
 
 5. Click **I understand, delete it**.
 
-    Once a backed up TiDB Cloud Dedicated cluster is deleted, the existing backup files of the cluster are moved to the recycle bin.
+    Once a backed up {{{ .essential }}} instance or TiDB Cloud Dedicated cluster is deleted, the existing backup files of it are moved to the Recycle Bin.
 
     - Automatic backups will expire and be automatically deleted once the retention period ends, except for the latest one. The default retention period is 7 days if you don't modify it. The latest automatic backup will not be deleted unless you explicitly delete it.
     - Manual backups will be kept in the Recycle Bin until manually deleted.
@@ -43,4 +46,7 @@ You can delete a TiDB Cloud resource at any time by performing the following ste
     >
     > Please be aware that backups will continue to incur charges until deleted.
 
-    If you want to restore a TiDB Cloud Dedicated cluster from recycle bin, see [Restore a deleted cluster](/tidb-cloud/backup-and-restore.md#restore-a-deleted-cluster).
+    If you want to restore data from Recycle Bin, see the following documents:
+
+    - [Restore a deleted {{{ .essential }}} instance](/tidb-cloud/backup-and-restore-serverless.md#restore-from-recycle-bin).
+    - [Restore a deleted TiDB Cloud Dedicated cluster](/tidb-cloud/backup-and-restore.md#restore-a-deleted-cluster).

tidb-cloud/features.md

@@ -103,7 +103,7 @@ This document lists the feature support status for different TiDB Cloud plans, i
   <tr>
     <td>Backup file recycle bin</td>
     <td style="text-align:center; font-size: 14px;">❌</td>
-    <td style="text-align:center; font-size: 14px;">❌</td>
+    <td style="text-align:center; font-size: 14px;">✅</td>
     <td style="text-align:center;">✅</td>
   </tr>
   <tr>

tidb-cloud/premium/backup-and-restore-premium.md

@@ -85,9 +85,9 @@ TiDB Cloud supports snapshot restore and point-in-time restore for your instance
 
 TiDB Cloud supports restoring data to a new instance.
 
-### Restore to a new instance
+### Restore to a new {{{ .premium }}} instance {#restore-to-a-new-instance}
 
-To restore your data to a new instance, take the following steps:
+To restore your data to a new {{{ .premium }}} instance, take the following steps:
 
 1. Navigate to the [**Backup**](#view-the-backup-page) page of your instance.
 
@@ -128,16 +128,21 @@ To restore your data to a new instance, take the following steps:
 
 ### Restore from Recycle Bin
 
-To restore a deleted instance from the Recycle Bin, take the following steps:
+To restore a deleted {{{ .premium }}} instance from the Recycle Bin, take the following steps:
 
-1. Log in to the [TiDB Cloud console](https://tidbcloud.com), and then navigate to the [**My TiDB**](https://tidbcloud.com/tidbs) page. In the top-right corner, click **Recycle Bin**.
+1. In the [TiDB Cloud console](https://tidbcloud.com), navigate to the [**My TiDB**](https://tidbcloud.com/tidbs) page of your organization, click **...** in the upper-right corner, and then click **Recycle Bin**.
 
-2. On the **Recycle Bin** page, locate the {{{ .premium }}} instance you want to restore:
+    >**Tip:**
+    >
+    > If you are in multiple organizations, use the combo box in the upper-left corner to switch to your target organization first.
 
-    - Click the **>** button to expand instance details.
-    - Find the desired backup, click **...** in the **Action** column, and then select **Restore**.
+2. On the **Recycle Bin** page, click the **Premium** tab to go to the recycle bin of {{{ .premium }}} instances.
 
-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.
+3. Locate the {{{ .premium }}} 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
 

tidb-cloud/releases/release-notes-2025.md

@@ -198,7 +198,7 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c
 
     - [TiDB Cloud Starter](/tidb-cloud/select-cluster-tier.md#starter) removes the in-place restore feature, which means you can no longer restore a backup directly to the same cluster. This change helps prevent accidental overwrites of active production data and potential data loss.
 
-        To restore your data, you can [restore the backup to a new cluster](/tidb-cloud/backup-and-restore-serverless.md#perform-the-restore). After validating the restored data, switch your application to the new cluster. Previously restored data in existing clusters remains intact, and no action is required unless you perform a new restore.
+        To restore your data, you can [restore the backup to a new cluster](/tidb-cloud/backup-and-restore-serverless.md#restore-to-a-new-instance). After validating the restored data, switch your application to the new cluster. Previously restored data in existing clusters remains intact, and no action is required unless you perform a new restore.
 
         For safer restore and migration workflows with more control and flexibility, consider using [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#essential).
 

tidb-cloud/tidb-cloud-glossary.md

@@ -119,9 +119,15 @@ Project members are users who are invited to join one or more projects of the or
 
 ### Recycle Bin
 
-The place where the data of deleted {{{ .dedicated }}} clusters and {{{ .premium }}} instances with valid backups is stored.
+The place where the data of deleted TiDB Cloud resources with valid backups is stored.
 
-Once a backed-up {{{ .dedicated }}} cluster or {{{ .premium }}} instance is deleted, the existing backup files of the cluster or instance are moved to the recycle bin. For backup files from automatic backups, the recycle bin will retain them for a specified period. You can configure the backup retention in **Backup Setting**, and the default is 7 days. For backup files from manual backups, there is no expiration date. To avoid data loss, remember to restore the data to a new {{{ .dedicated }}} cluster or {{{ .premium }}} instance in time. Note that if a {{{ .dedicated }}} cluster or {{{ .premium }}} instance **has no backup**, the deleted cluster or instance will not be displayed here.
+Once a backed-up TiDB Cloud resource is deleted, the existing backup files of it are moved to the Recycle Bin. For backup files from automatic backups, the Recycle Bin will retain them for a specified period. You can configure the backup retention in **Backup Setting**, and the default is 7 days. For backup files from manual backups, there is no expiration date. To avoid data loss, remember to restore the data to a new TiDB Cloud resource in time. Note that if a TiDB Cloud resource **has no backup**, the deleted resource will not be displayed in the Recycle Bin.
+
+Currently, only the following types of TiDB Cloud resources support the Recycle Bin feature:
+
+- {{{ .essential }}} instances
+- {{{ .premium }}} instances
+- {{{ .dedicated }}} clusters
 
 ### region