Skip to content

Commit

Permalink
Fix heading indentation (#2658) (#2683)
Browse files Browse the repository at this point in the history
  • Loading branch information
ti-chi-bot authored Jan 20, 2025
1 parent eb064bf commit 8404605
Show file tree
Hide file tree
Showing 4 changed files with 5 additions and 5 deletions.
4 changes: 2 additions & 2 deletions en/restore-from-aws-s3-using-br.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ Before restoring backup data on a S3-compatible storage to TiDB using BR, take t
kubectl create secret generic restore-demo2-tidb-secret --from-literal=password=${password} --namespace=test2
```

## Step 2: Restore the backup data to a TiDB cluster
### Step 2: Restore the backup data to a TiDB cluster

Depending on which method you choose to grant permissions to the remote storage when preparing the restore environment, you can restore the data by doing one of the following:

Expand Down Expand Up @@ -311,4 +311,4 @@ The detailed steps are as follows:
## Troubleshooting
If you encounter any problem during the restore process, refer to [Common Deployment Failures](deploy-failures.md).
If you encounter any problem during the restore process, refer to [Common Deployment Failures](deploy-failures.md).
2 changes: 1 addition & 1 deletion en/restore-from-gcs-using-br.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ Before restoring backup data on GCS to TiDB using BR, take the following steps t
kubectl create secret generic restore-demo2-tidb-secret --from-literal=user=root --from-literal=password=<password> --namespace=test2
```

## Step 2: Restore the backup data to a TiDB cluster
### Step 2: Restore the backup data to a TiDB cluster

1. Create the `Restore` custom resource (CR) to restore the specified data to your cluster:

Expand Down
2 changes: 1 addition & 1 deletion zh/restore-from-aws-s3-using-br.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ PITR 全称为 Point-in-time recovery,该功能可以让你在新集群上恢
kubectl create secret generic restore-demo2-tidb-secret --from-literal=password=${password} --namespace=test2
```

## 第 2 步:将指定备份数据恢复到 TiDB 集群
### 第 2 步:将指定备份数据恢复到 TiDB 集群

根据上一步选择的远程存储访问授权方式,你需要使用下面对应的方法将备份数据恢复到 TiDB:

Expand Down
2 changes: 1 addition & 1 deletion zh/restore-from-gcs-using-br.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,7 +62,7 @@ PITR 全称为 Point-in-time recovery,该功能可以让你在新集群上恢
kubectl create secret generic restore-demo2-tidb-secret --from-literal=user=root --from-literal=password=<password> --namespace=test2
```

## 第 2 步:将指定备份数据恢复到 TiDB 集群
### 第 2 步:将指定备份数据恢复到 TiDB 集群

1. 创建 restore custom resource (CR),将指定的备份数据恢复至 TiDB 集群:

Expand Down

0 comments on commit 8404605

Please sign in to comment.