TiDB Cloud Docs: Add documentation for new Recovery Group feature

TOC-tidb-cloud.md

@@ -253,6 +253,11 @@
   - [To Kafka Sink](/tidb-cloud/changefeed-sink-to-apache-kafka.md)
   - [To TiDB Cloud Sink](/tidb-cloud/changefeed-sink-to-tidb-cloud.md)
   - [To Cloud Storage](/tidb-cloud/changefeed-sink-to-cloud-storage.md)
+- Disaster Recovery
+  - [Recovery Group Overview](/tidb-cloud/recovery-group-overview.md)
+  - [Get Started](/tidb-cloud/recovery-group-get-started.md)
+  - [Failover and Reprotect Databases](/tidb-cloud/recovery-group-failover.md)
+  - [Delete Recovery Group](/tidb-cloud/recovery-group-delete.md)
 - Security
   - Identity Access Control
     - [Password Authentication](/tidb-cloud/tidb-cloud-password-authentication.md)
@@ -283,6 +288,7 @@
   - [Billing from AWS or GCP Marketplace](/tidb-cloud/tidb-cloud-billing.md#billing-from-aws-marketplace-or-google-cloud-marketplace)
   - [Billing for Changefeed](/tidb-cloud/tidb-cloud-billing-ticdc-rcu.md)
   - [Billing for Data Migration](/tidb-cloud/tidb-cloud-billing-dm.md)
+  - [Billing for Recovery Groups](/tidb-cloud/tidb-cloud-billing-recovery-group.md)
 - API
 - API
   - [API Overview](/tidb-cloud/api-overview.md)

tidb-cloud/recovery-group-delete.md

@@ -0,0 +1,28 @@
+---
+title: Delete Recovery Group
+summary: Learn how to delete a Recovery Group when it is no longer needed
+---
+
+# Delete Recovery Group
+
+When a Recovery Group is no longer needed it may be deleted.
+
+## Delete a Recovery Group
+
+When a recovery group is no longer needed to manage the replication of a set of databases it may be deleted form the system.
+
+1. In the TiDB Cloud console, click **Project Settings** in the left navigation pane.
+
+2. On the project settings navigation pane, click **Recovery Group**.
+
+3. On the recovery group page, click the name of the recovery group that you wish to delete.
+
+4. Click the action menu for the recovery group, and click **Delete**. The failover dialog will open.
+
+    > **Warning**
+    >
+    > - Deleting a Recovery Group also removes any of the associated replication relationship that were associated with that Recovery Group. 
+    > - The databases associated with the Recovery Group are no longer protected against disaster.
+
+5. Confirm that you understand the impacting of the deletion by typing the name of the recovery group and clicking **I understand, delete it** to delete the recovery group.
+

tidb-cloud/recovery-group-failover.md

@@ -0,0 +1,72 @@
+---
+title: Failover and Reprotect Databases
+summary: Learn how to use a Recovery Group to Failover and Reprotect databases between TiDB Cloud clusters
+---
+
+# Failover and Reprotect Databases
+
+Databases that are part of a replication group are replicated from one cluster to another (typucally in a different region of the cloud service provider).
+
+The **Failover** action promotes the replicated copy of the databases at the secondary region to be the new primary copy. Ensuring ongoing availability in the event of a regional outage.
+
+When the regional outage has concluded, the ability to reverse the replication from the recovery region back to the original region is done using the **Reprotect** action. This ensures that the databases are protected against future disasters impacting their new region, and prepares them for migration back to the original region if desired.
+
+## Prerequisites
+
+Prior to performing a failover, the Recovery Group should have been created and be successfully replicating to the secondary cluster. See [Get Started with Recovery Groups](/tidb-cloud/recovery-group-get-started.md)
+
+![Protected Recovery Group](/media/tidb-cloud/recovery-group/recovery-group-protected.png)
+
+## Failover Databases using Recovery Group
+
+In the event of a disaster the recovery group is used to fail over databases to the secondary cluster.
+
+1. In the TiDB Cloud console, click **Project Settings** in the left navigation pane.
+
+2. On the project settings navigation pane, click **Recovery Group**.
+
+3. On the recovery group page, click the name of the recovery group that you wish to failover.
+
+4. Click the action menu for the recovery group, and click **Failover**. The failover dialog will open.
+
+    > **Warning**
+    >
+    > Performing a failover will sever the existing replication relationship.
+
+5. Select the secondary TiDB Cloud cluster that will be promoted to the primary copy. Ensure that the selected cluster is in a healthy state.
+
+6. Confirm that you understand the potentially disruptive nature of a failover by typing **Failover** into the confirmation entry and clicking **I understand, Failover Group** to begin the failover.
+
+    ![Fail Over Recovery Group](/media/tidb-cloud/recovery-group/recovery-group-failover.png)
+
+## Reprotect Databases using Recovery Group
+
+After a failover completes, the replica databases on the secondary cluster are now the primary copy. However, these databases are unprotected against future disasters as the replication relationship is stopped by the failover process.
+
+If the cluster that was impacted by the disaster is able to be brought online again, a replication relationship from the recovery region back to the original region can be established. This is performed using the **Reprotect** action.
+
+![Unprotected Recovery Group](/media/tidb-cloud/recovery-group/recovery-group-unprotected.png)
+
+1. In the TiDB Cloud console, click **Project Settings** in the left navigation pane.
+
+2. On the project settings navigation pane, click **Recovery Group**.
+
+3. On the recovery group page, click the name of the recovery group that you wish to reprotect.
+
+    > **Note**
+    >
+    > The **Recovery Group Detail** page provides information about the recovery group including current status and replication topology.
+
+4. Click the action menu for the recovery group, and click **Reprotect**. The reprotect dialog will open.
+
+5. Confirm the reprotect operation by clicking **I understand, Failover Group** to begin the reprotect operation.
+
+    ![Reprotect Recovery Group](/media/tidb-cloud/recovery-group/recovery-group-reprotected.png)
+
+## What's next
+
+After creating the recovery group you may want to familiarize yourself with the failover and reprotect operations. These operations are used to (1) **Failover** the primary cluster for the replicated databases from one cluster to the other, and then to later (2) reestablish replication in the opposite direction to **Reprotect** the failed over databases.
+
+- [Failover Databases](/tidb-cloud/recovery-group-failover.md)
+- [Reprotect Databases](/tidb-cloud/recovery-group-reprotect.md)
+

tidb-cloud/recovery-group-get-started.md

@@ -0,0 +1,70 @@
+---
+title: Get Started with Recovery Groups
+summary: Learn how to create a Recovery Group in TiDB Cloud and view its details
+---
+
+# Get Started with Recovery Groups
+
+This document describes how to create a Recovery Group to protect your databases running on TiDB Cloud Dedicated Clusters using the TiDB Cloud user interface. It also shows how to view details of the recovery group.
+
+## Prerequisites
+
+Recovery Groups replicate your databases to another cluster to protect your databases from a regional disaster. To create a recovery group you will need to have two TiDB Cloud Dedicated Clusters, one where the databases are primarily located, and a second cluster that will be used for the replicated copy of the databases. If you have not done so already, follow the steps in [Create a TiDB Dedicated Cluster](/tidb-cloud/create-tidb-cluster.md) to create the necessary clusters.
+
+> **Note**
+>
+> TiDB Cloud Recovery Groups are currently supported with TiDB Cloud Dedicated Cluster deployed on AWS
+
+## Create a new Recovery Group
+
+To create a Recovery Group, perform the following steps:
+
+1. In the TiDB Cloud console, click **Project Settings** in the left navigation pane.
+
+2. On the project settings navigation pane, click **Recovery Group**.
+
+3. On the recovery group page, click **Create Recovery Group**. A dialog is displayed.
+
+4. In the Create Recovery Group Dialog enter a name for the recovery group.
+
+    > **Note**
+    >
+    > Currently only one resiliency level is supported.
+
+5. Select the TiDB Cloud cluster that will be the primary cluster for this group.
+
+6. Select the TiDB Cloud cluster that will be the seondary cluster that databases will be replicated to for this group.
+
+7. Select which databases you wish to replicate as part of this recovery group.
+
+    > **Note**
+    >
+    > When assigning databases to the group you can select specific databases to the recovery group, or select all databases on the primary cluster (current and future).
+    > If you **Assign all databases (current and future)** then any future databases added to the cluster will be automatically included in this recovery group and replicated to the secondary cluster.
+    > If you **Assign specific databases** then you will select the specific databases on the primary cluster that you want to replicate to the secondary cluster. If any databases are added to the primary cluster in the future, then these will not be automatically replicated as part of this recovery group.
+
+8. Review the summary information and click **Create** to begin protecting the databases as part of a new Recovery Group.
+
+## View Recovery Group Details
+
+After creating a Recovery Group, view the **Recovery Group Detail** page to view status information about the group:
+
+1. In the TiDB Cloud console, click **Project Settings** in the left navigation pane.
+
+2. On the project settings navigation pane, click **Recovery Group**.
+
+3. On the recovery group page, click the name of the recovery group that you wish to view.
+
+    > **Note**
+    >
+    > The **Recovery Group Detail** page provides information about the recovery group including the configuration details provided when it was created, and its current status.
+    > The page also provides metrics on the throughput of the recovery groups replication, and the replication latency experienced.
+
+4. The status of the Recovery Group will read as **Available** when the replication relationship is fully established and functioning.
+
+## What's next
+
+After creating the recovery group you may want to familiarize yourself with the failover and reprotect operations. These operations are used to (1) **Failover** the primary cluster for the replicated databases from one cluster to the other, and then to later (2) reestablish replication in the opposite direction to **Reprotect** the failed over databases.
+
+- [Failover and Reprotect Databases](/tidb-cloud/recovery-group-failover.md)
+

tidb-cloud/recovery-group-overview.md

@@ -0,0 +1,35 @@
+---
+title: Recovery Group Overview (Beta)
+summary: Learn how to protect your databases against disasters by using TiDB Cloud Recovery Groups.
+---
+
+# Recovery Group Overview (Beta)
+
+TiDB Cloud Recovery Groups allow you to replicate your databases between TiDB Cloud Dedicated clusters for protection against regional disasters. Recovery Groups allow you to orchestrate the failover of databases from one cluster to another. After failover to the secondary cluster, if the original cluster becomes available again, you can re-establish replication in the reverse direction to reprotect the databases.
+
+## Architecture
+
+A Recovery Group consists of a set of replicated databases that can be failed over together between two TiDB Dedicated Clusters. Each Recovery Group is assigned a primary cluster, databases on this primary cluster are associated with the group and are then replicated to the secondary cluster.
+
+![Recovery Group](/media/tidb-cloud/recovery-group/recovery-group-overview.png)
+
+- Recovery Group: a group of databases that are replicated between two clusters
+- Primary Cluster: the cluster where the database is actively written by the application
+- Secondary Cluster: the cluster where replicas of the database are located
+
+You can also describe the basic working principles here, or integrate the principles into the component introduction above.
+
+## Key features/Limitations
+
+- Recovery Groups support TiDB Cloud Dedicated Clusters that are deployed on AWS.
+- Recovery Groups are established between two clusters.
+- Bi-directional replication of a database is not supported with recovery groups.
+
+> **Warning**
+>
+> This feature is a beta feature and not recommended for product environments.
+
+## What's next
+
+- To get started with recovery groups, see [Create Database Recovery Group](/tidb-cloud/recovery-group-get-started.md).
+- To learn how to use a recovery group, see [Failover Databases](/tidb-cloud/recovery-group-failover.md) and [Reprotect Databases](/tidb-cloud/recovery-group-reprotect.md)

tidb-cloud/tidb-cloud-billing-recovery-group.md

@@ -0,0 +1,12 @@
+---
+title: Recovery Group Billing
+summary: Learn about billing for recovery groups in TiDB Cloud.
+---
+
+# Recovery Group Billing
+
+TiDB Cloud bills for Recovery Groups based on the deployed size of the TiKV cluster that is the primary cluster in the Recovery Group. When you [create a recovery group](/tidb-cloud/changefeed-overview.md#create-a-changefeed) for a cluster, you can select the primary cluster that the recovery group will be associated with. The larger the TiKV configuration, the higher the cost for Recovery Group protection.
+
+## Price
+
+To learn about the supported regions and the price of TiDB Cloud for each Recovery Group, see [Recovery Group Cost](https://www.pingcap.com/tidb-cloud-pricing-details/#recovery-group-cost).