en: reorg the disaster recovery part (pingcap#467)

Co-authored-by: DanielZhangQD <[email protected]>
zhenjiaogao · Jun 23, 2020 · fbc92a8 · fbc92a8
1 parent 301d21d
commit fbc92a8
Show file tree

Hide file tree

Showing 3 changed files with 36 additions and 13 deletions.
diff --git a/en/TOC.md b/en/TOC.md
@@ -51,8 +51,10 @@
   - [Maintain a Kubernetes Node](maintain-a-kubernetes-node.md)
   - [Collect TiDB Logs](collect-tidb-logs.md)
   - [Enable Automatic Failover](use-auto-failover.md)
-  - [Recover the PD Cluster](pd-recover.md)
   - [Destroy a TiDB Cluster](destroy-a-tidb-cluster.md)
++ Disaster Recovery
+  - [Recover PD Cluster](pd-recover.md)
+  - [Recover Deleted Cluster](recover-deleted-cluster.md)
 - [Import Data](restore-data-using-tidb-lightning.md)
 - [Troubleshoot](troubleshoot.md)
 - [FAQs](faq.md)

diff --git a/en/recover-deleted-cluster.md b/en/recover-deleted-cluster.md
@@ -0,0 +1,33 @@
+---
+title: Recover the Deleted Cluster
+summary: Learn how to recover a TiDB cluster that has been deleted mistakenly.
+category: how-to
+---
+
+# Recover the Deleted Cluster
+
+This document describes how to recover a TiDB cluster that has been deleted mistakenly.
+
+## Recover the cluster managed by TidbCluster
+
+TiDB Operator uses PV (Persistent Volume) and PVC (Persistent Volume Claim) to store persistent data. If you accidentally delete a cluster using `kubectl delete tc`, the PV/PVC objects and data are still retained to ensure data safety.
+
+To recover the deleted cluster, use the `kubectl create` command to create a cluster that has the same name and configuration as the deleted one. In the new cluster, the retained PV/PVC and data are reused.
+
+{{< copyable "shell-regular" >}}
+
+```shell
+kubectl -n ${namespace} create -f tidb-cluster.yaml
+```
+
+## Recover the cluster managed by Helm
+
+TiDB Operator uses PV (Persistent Volume) and PVC (Persistent Volume Claim) to store persistent data. If you accidentally delete a cluster using `helm delete`, the PV/PVC objects and data are still retained to ensure data safety.
+
+To recover the cluster at this time, use the `helm install` command to create a cluster that has the same name and configuration as the deleted one. In the new cluster, the retained PV/PVC and data are reused.
+
+{{< copyable "shell-regular" >}}
+
+```shell
+helm install pingcap/tidb-cluster -n ${release_name} --namespace=${namespace} --version=${chart_version} -f values.yaml
+```
diff --git a/en/troubleshoot.md b/en/troubleshoot.md
@@ -52,18 +52,6 @@ To use the diagnostic mode for troubleshooting:
 
     After the Pod is rebuilt, it automatically returns to the normal mode.
 
-## Recover the cluster after accidental deletion
-
-TiDB Operator uses PV (Persistent Volume) and PVC (Persistent Volume Claim) to store persistent data. If you accidentally delete a cluster using `helm delete`, the PV/PVC objects and data are still retained to ensure data safety.
-
-To restore the cluster at this time, use the `helm install` command to create a cluster with the same name. The retained PV/PVC and data are reused.
-
-{{< copyable "shell-regular" >}}
-
-```shell
-helm install pingcap/tidb-cluster -n ${release_name} --namespace=${namespace} --version=${version} -f values.yaml
-```
-
 ## Pod is not created normally
 
 After creating a cluster using `helm install`, if the Pod is not created, you can diagnose it using the following commands: