Experts, please help. What to do if data is deleted?

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 大佬们帮忙。数据被删除了怎么办

| username: tidb狂热爱好者

【TiDB Usage Environment】Production Environment
【TiDB Version】6.1
【Encountered Problem】
ID Role Host Ports OS/Arch Status Data Dir Deploy Dir

172.31.177.213:9093 alertmanager 172.31.177.213 9093/9094 linux/x86_64 Up /data/alertmanager-9093 /tidb-deploy/alertmanager-9093
172.31.177.213:3000 grafana 172.31.177.213 3000 linux/x86_64 Up - /tidb-deploy/grafana-3000
172.31.177.210:2379 pd 172.31.177.210 2379/2380 linux/x86_64 Up|L|UI /data/pd-2379 /tidb-deploy/pd-2379
172.31.177.213:9090 prometheus 172.31.177.213 9090/12020 linux/x86_64 Up /data/prometheus-9090 /tidb-deploy/prometheus-9090
172.31.177.210:4000 tidb 172.31.177.210 4000/10080 linux/x86_64 Down - /tidb-deploy/tidb-4000
172.31.177.212:4000 tidb 172.31.177.212 4000/10080 linux/x86_64 Up - /data/deploy/install/deploy/tidb-4000
172.31.177.212:9000 tiflash 172.31.177.212 9000/8123/3930/20170/20292/8234 linux/x86_64 Up /data/tiflash-9000 /tidb-deploy/tiflash-9000
172.31.177.150:20160 tikv 172.31.177.150 20160/20180 linux/x86_64 Down /data/tikv-20160 /tidb-deploy/tikv-20160
172.31.177.151:20160 tikv 172.31.177.151 20160/20180 linux/x86_64 Down /data/tikv-20160 /tidb-deploy/tikv-20160
172.31.177.152:20160 tikv 172.31.177.152 20160/20180 linux/x86_64 Down /data/tikv-20160 /tidb-deploy/tikv-20160
172.31.177.153:20160 tikv 172.31.177.153 20160/20180 linux/x86_64 Down /data/tikv-20160 /tidb-deploy/tikv-20160
172.31.177.154:20160 tikv 172.31.177.154 20160/20180 linux/x86_64 Down /data/tikv-20160 /tidb-deploy/tikv-20160
172.31.177.210:20160 tikv 172.31.177.210 20160/20180 linux/x86_64 Up /data/tikv-20160 /tidb-deploy/tikv-20160
172.31.177.214:20160 tikv 172.31.177.214 20160/20180 linux/x86_64 Up /data/tikv-20160 /tidb-deploy/tikv-20160
172.31.177.215:20160 tikv 172.31.177.215 20160/20180 linux/x86_64 Up /data/tikv-20160 /tidb-deploy/tikv-20160
172.31.177.216:20160 tikv 172.31.177.216 20160/20180 linux/x86_64 Up /data/tikv-20160 /tidb-deploy/tikv-20160
Total nodes: 16

【Reproduction Path】What operations were performed to cause the problem
【Problem Phenomenon and Impact】
The database is currently unusable. Should we scale down the TiKV nodes first?
【Attachments】

Please provide the version information of each component, such as cdc/tikv, which can be obtained by executing cdc version/tikv-server --version.

2
| username: ddhe9527 | Original post link

If all 5 nodes are deleted, data loss is inevitable. You can refer to the following operational practice to execute unsafe-recover:
https://asktug.com/t/topic/36199

3
| username: cs58_dba | Original post link

Do you perform regular logical or physical backups?

4
| username: kkpeter | Original post link

You must make backups. Doesn’t version 6.0 have an online recovery feature?

5
| username: ablewang_xiaobo | Original post link

It is recommended to first repair the cluster’s status to see if the downed node can be brought back up. If the data has been deleted, it can only be restored through backups.

6
| username: HACK | Original post link

If there is no backup, then the data is probably lost.

7
| username: tidb狂热爱好者 | Original post link

Send this to me to take a look.

8
| username: cs58_dba | Original post link

The image is not available for translation. Please provide the text content directly for translation.

9
| username: tidb狂热爱好者 | Original post link

There are scheduled backups.

10
| username: cs58_dba | Original post link

Generally, a backup is used for cross-machine recovery.

11
| username: system | Original post link

This topic was automatically closed 1 minute after the last reply. No new replies are allowed.