cloud: add info about the Recycle Bin support for Essential

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

@@ -128,6 +128,32 @@ To restore your data to a new {{{ .starter }}} or Essential instance, take the f
 
 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.
+
+    >**Note:**
+    >
+    > If a {{{ .essential }}} instance **has no backup**, the deleted instance is not displayed in the Recycle Bin.
+
+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/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 it. 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 in the future, make sure that you have a backup of it. Otherwise, you cannot restore it.
+
+    - 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, its existing backup files 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 the 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

@@ -116,7 +116,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;">✅</td>
     <td style="text-align:center;">✅</td>
     <td style="text-align:center;">✅</td>
   </tr>

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

@@ -89,6 +89,12 @@ This page lists the release notes of [TiDB Cloud](https://www.pingcap.com/tidb-c
 
 - **TiDB Cloud Essential**
 
+    - Recycle Bin is now available for [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#essential). It stores data from deleted TiDB Cloud resources that have valid backups.
+
+        When a TiDB Cloud Essential instance with existing backups is deleted, its backup files are moved to the Recycle Bin. Backup files created by automatic backups are retained in the Recycle Bin for a specified period. To avoid data loss, restore the data to a new TiDB Cloud Essential instance before the retention period expires. Note that if a TiDB Cloud Essential instance **has no backup**, the deleted instance is not displayed in the Recycle Bin.
+
+        For more information, see [Backup and Restore](/tidb-cloud/backup-and-restore-serverless.md#restore-from-recycle-bin).
+
     - Top RU is now available in public preview for [TiDB Cloud Essential](/tidb-cloud/select-cluster-tier.md#essential) in the following region:
 
         - Alibaba Cloud: `Mexico (na-south-1)`

tidb-cloud/tidb-cloud-glossary.md

@@ -140,7 +140,11 @@ The place where the data of deleted [TiDB Cloud resources](#tidb-cloud-resource)
 
 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 {{{ .premium }}} instances and {{{ .dedicated }}} clusters support the Recycle Bin feature.
+Currently, only the following types of TiDB Cloud resources support the Recycle Bin feature:
+
+- {{{ .essential }}} instances
+- {{{ .premium }}} instances
+- {{{ .dedicated }}} clusters
 
 ### region