Skip to content

Commit 46af051

Browse files
authored
Revert "docs: add dual region backup" (#15011)
1 parent f6a17eb commit 46af051

File tree

5 files changed

+70
-145
lines changed

5 files changed

+70
-145
lines changed

tidb-cloud/backup-and-restore.md

Lines changed: 63 additions & 132 deletions
Original file line numberDiff line numberDiff line change
@@ -6,153 +6,81 @@ aliases: ['/tidbcloud/restore-deleted-tidb-cluster']
66

77
# Back Up and Restore TiDB Dedicated Data
88

9-
This document describes how to back up and restore your TiDB Dedicated cluster data on TiDB Cloud. TiDB Dedicated supports automatic backup and manual backup. You can also restore backup data to a new cluster or restore a deleted cluster from the recycle bin.
9+
This document describes how to back up and restore your TiDB Dedicated cluster data on TiDB Cloud.
1010

11-
> **Tip**
11+
> **Tip:**
1212
>
1313
> To learn how to back up and restore TiDB Serverless cluster data, see [Back Up and Restore TiDB Serverless Data](/tidb-cloud/backup-and-restore-serverless.md).
1414
1515
## Limitations
1616

1717
- TiDB Cloud does not support restoring tables in the `mysql` schema, including user permissions and system variables.
18-
- If you turn on and off Point-in-time Restore multiple times, you can only choose a time point within the recoverable range after the most recent Point-in-time Restore is enabled. The earlier recoverable range is not accessible.
19-
- DO NOT modify the switches of **Point-in-time Restore** and **Dual Region Backup** at the same time.
18+
- If you turn on and off PITR (Point-in-time Recovery) multiple times, you can only choose a time point within the recoverable range after the most recent PITR is enabled. The earlier recoverable range is not accessible.
2019

2120
## Backup
2221

23-
### Turn on auto backup
22+
TiDB Dedicated supports automatic backup and manual backup.
2423

25-
TiDB Dedicated supports both [snapshot backup](https://docs.pingcap.com/tidb/stable/br-snapshot-guide) and [log backup](https://docs.pingcap.com/tidb/stable/br-pitr-guide). Snapshot backup enables you to restore data to the backup point. By default, snapshot backups are taken automatically and stored according to your backup retention policy. You can disable auto backup at any time.
24+
Automatic backups are scheduled for your TiDB Dedicated clusters according to the backup setting, which can reduce your loss in extreme disaster situations. You can also pick a backup snapshot and restore it into a new TiDB Dedicated cluster at any time.
2625

27-
#### Turn on Point-in-time Restore
26+
### Automatic backup
2827

29-
> **Note**
30-
>
31-
> The Point-in-time Restore feature is supported for TiDB Dedicated clusters that are v6.4.0 or later.
32-
33-
This feature supports restoring data of any point in time to a new cluster. You can use it to:
34-
35-
- Reduce RPO in disaster recovery.
36-
- Resolve cases of data write errors by restoring point-in-time that is before the error event.
37-
- Audit the historical data of the business.
38-
39-
It is strongly recommended to turn on this feature. The cost is the same as snapshot backup. For more information, refer to [Data Backup Cost](https://www.pingcap.com/tidb-dedicated-pricing-details#backup-storage-cost).
40-
41-
To turn on this feature, perform the following steps:
42-
43-
1. Navigate to the **Backup** page of a TiDB Dedicated cluster.
44-
45-
2. Click **Backup Settings**.
46-
47-
3. Toggle the **Auto Backup** switch to **On**.
48-
49-
4. Toggle the **Point-in-time Restore** switch to **On**.
50-
51-
> **Warning**
52-
>
53-
> Point-in-Time Restore only takes effect after the next backup task is completed. To make it take effect earlier, you can [manually perform a backup](#perform-a-manual-backup) after enabling it.
54-
55-
5. Click **Confirm** to preview the configuration changes.
56-
57-
6. Click **Confirm** again to save changes.
58-
59-
#### Configure backup schedule
60-
61-
TiDB Dedicated supports daily and weekly backup schedules. By default, the backup schedule is set to daily. You can choose a specific time of the day or week to start snapshot backup.
62-
63-
To configure the backup schedule, perform the following steps:
28+
By the automatic backup, you can back up the TiDB Dedicated cluster data every day at the backup time you have set. To set the backup time, perform the following steps:
6429

6530
1. Navigate to the **Backup** page of a TiDB Dedicated cluster.
6631

67-
2. Click **Backup Settings**.
32+
2. Click **Backup Settings**. The setting window displays.
6833

69-
3. Toggle the **Auto Backup** switch to **On**.
34+
3. In the setting window, configure the automatic backup:
7035

71-
4. Configure the backup schedule as follows:
36+
- Toggle the **Auto Backup** switch to **On**.
7237

73-
- In **Backup Scheduler**, select either the **Daily** or **Weekly** checkbox. If you select **Weekly**, you need to specify the days of the week for the backup.
74-
75-
> **Warning**
76-
>
77-
> - When weekly backup is enabled, the Point-in-time Restore feature is enabled by default and cannot be disabled.
78-
> - If you change the backup scheduler from weekly to daily, the Point-in-time Restore feature remains its original setting. You can manually disable it if needed.
38+
- In **Backup Cycle**, select either the **Daily** or **Weekly** checkbox. If you select **Weekly**, you need to specify the days of the week for the backup.
7939

8040
- In **Backup Time**, schedule a start time for the daily or weekly cluster backup.
8141

82-
If you do not specify a preferred backup time, TiDB Cloud assigns a default backup time, which is 2:00 AM in the time zone of the region where the cluster is located.
42+
It is recommended to schedule automatic backup at a low workload period. If you do not specify a preferred backup time, TiDB Cloud assigns a default backup time, which is 2:00 AM in the time zone of the region where the cluster is located.
8343

84-
> **Note**
85-
>
86-
> - Backup jobs are automatically delayed when data import jobs are in progress. **DO NOT** run manual backups during data import or cluster scaling.
44+
- In **Backup Retention**, configure the minimum backup data retention period.
8745

88-
- In **Backup Retention**, configure the minimum backup data retention period. The default period is 7 days. To minimize the impact on business, it is recommended to schedule automatic backup during periods of low workloads.
46+
- Turn on or off the PITR (**Point-in-time Recovery**) feature.
8947

90-
> **Note**
48+
> **Note:**
9149
>
92-
> - After you delete a cluster, the automatic backup files will be retained for a specified period, as set in backup retention. You need to delete the backup files accordingly.
93-
> - After you delete a cluster, the existing manual backup files will be retained until you manually delete them, or your account is closed.
94-
95-
### Turn on dual region backup (beta)
96-
97-
> **Note:**
98-
>
99-
> The dual region backup feature is currently in beta.
100-
101-
TiDB Dedicated supports dual region backup by replicating backups from your cluster region to another different region. After you enable this feature, all backups are automatically replicated to the specified region. This provides cross-region data protection and disaster recovery capabilities. It is estimated that approximately 99% of the data can be replicated to the secondary region within an hour.
102-
103-
Dual region backup costs include both backup storage usage and cross-region data transfer fees. For more information, refer to [Data Backup Cost](https://www.pingcap.com/tidb-dedicated-pricing-details#backup-storage-cost).
104-
105-
To turn on dual region backup, perform the following steps:
106-
107-
1. Navigate to the **Backup** page of a TiDB Dedicated cluster.
50+
> - The PITR feature is enabled by default and cannot be disabled when you enable weekly backup.
51+
> - If you change the backup cycle from weekly to daily, the PITR feature remains enabled. You can manually disable it if needed.
10852
109-
2. Click **Backup Settings**.
53+
PITR supports restoring data of any point in time to a new cluster. You can use it to:
11054

111-
3. Toggle the **Dual Region Backup** switch to **On**.
55+
- Reduce RPO in disaster recovery.
56+
- Resolve cases of data write errors by restoring point-in-time that is before the error event.
57+
- Audit the historical data of the business.
11258

113-
4. From the **Dual Region** drop-down list, select a region to store the backup files.
59+
If you have one of the preceding needs and want to use the PITR feature, make sure that your TiDB Dedicated cluster version is at least v6.4.0.
11460

115-
5. Click **Confirm** to preview the configuration changes.
61+
- In **Backup Storage Region**, select the regions where you want to store your backup data.
11662

117-
6. Click **Confirm** again to save changes.
63+
TiDB Cloud stores your backup data in the current region of your cluster by default. This behavior cannot be changed. In addition, you can add another remote region, and TiDB Cloud will copy all new backup data to the remote region, which facilitates data safety and faster recovery. After adding a remote region as a backup data storage, you cannot remove the region.
11864

119-
### Turn off auto backup
65+
4. Click **Confirm** to preview the configuration change.
12066

121-
> **Note**
122-
>
123-
> Turning off auto backup will also turn off point-in-time restore by default.
124-
125-
To turn off auto backup, perform the following steps:
126-
127-
1. Navigate to the **Backup** page of a TiDB Dedicated cluster.
67+
If you turn on PITR, you can select the **Perform a backup immediately and use it as recovery starting point in PITR.** checkbox. Otherwise, PITR will not be available until the next backup is completed.
12868

129-
2. Click **Backup Settings**.
69+
5. Click **Confirm**.
13070

131-
3. Toggle the **Auto Backup** switch to **Off**.
71+
### Backup storage region support
13272

133-
4. Click **Confirm** to preview the configuration changes.
73+
Currently, you cannot select an arbitrary remote region for backup data storage. The regions already supported are as follows:
13474

135-
5. Click **Confirm** again to save changes.
75+
| Cloud provider | Cluster region | Remote region support |
76+
|----------------|-----------------------------|--------------------------|
77+
| Google Cloud | Tokyo (asia-northeast1) | Osaka (asia-northeast2) |
13678

137-
### Turn off dual region backup (beta)
138-
139-
> **Tip**
79+
> **Note:**
14080
>
141-
> Disabling dual region backup does not immediately delete the backups in the secondary region. These backups will be cleaned up later according to the backup retention schedule. To remove them immediately, you can manually [delete the backups](#delete-backups).
142-
143-
To turn off dual region backup, perform the following steps:
81+
> If you select multiple backup storage regions, you will be charged for multiple backup storage and inter-region backup data replication out from the cluster region to each destination region. The cost is on a per-region basis and varies with the backup regions selected. For more information, see [Data Backup Cost](https://www.pingcap.com/tidb-cloud-pricing-details/#backup-storage-cost).
14482
145-
1. Navigate to the **Backup** page of a TiDB Dedicated cluster.
146-
147-
2. Click **Backup Settings**.
148-
149-
3. Toggle the **Dual Region Backup** switch to **Off**.
150-
151-
4. Click **Confirm** to preview the configuration changes.
152-
153-
5. Click **Confirm** again to save changes.
154-
155-
### Perform a manual backup
83+
### Manual backup
15684

15785
Manual backups are user-initiated backups that enable you to back up your data to a known state as needed, and then restore to that state at any time.
15886

@@ -166,26 +94,35 @@ To apply a manual backup to your TiDB Dedicated cluster, perform the following s
16694

16795
4. Click **Confirm**. Then your cluster data is backed up.
16896

169-
### Delete backups
170-
171-
#### Delete backup files
97+
### Delete backup files
17298

17399
To delete an existing backup file, perform the following steps:
174100

175101
1. Navigate to the **Backup** tab of a cluster.
176102

177103
2. Click **Delete** for the backup file that you want to delete.
178104

179-
#### Delete a running backup job
105+
### Delete a running backup job
180106

181107
To delete a running backup job, it is similar as [**Delete backup files**](#delete-backup-files).
182108

183109
1. Navigate to the **Backup** tab of a cluster.
184110

185111
2. Click **Delete** for the backup file that is in the **Pending** or **Running** state.
186112

113+
### Best practices for backup
114+
115+
- It is recommended that you perform backup operations at cluster idle time to minimize the impact on business.
116+
- Do not run the manual backup while importing data, or during cluster scaling.
117+
- After you delete a cluster, the existing manual backup files will be retained until you manually delete them, or your account is closed. Automatic backup files will be retained for a specified period (you can configure the retention period in **Backup Settings**) from the date of cluster deletion. You need to delete the backup files accordingly.
118+
187119
## Restore
188120

121+
TiDB Dedicated provides two types of data restoration:
122+
123+
- Restore backup data to a new cluster
124+
- Restore a deleted cluster from the recycle bin
125+
189126
### Restore data to a new cluster
190127

191128
To restore your TiDB Dedicated cluster data from a backup to a new cluster, take the following steps:
@@ -194,54 +131,44 @@ To restore your TiDB Dedicated cluster data from a backup to a new cluster, take
194131

195132
2. Click **Restore**. The setting window displays.
196133

197-
3. In **Restore Mode**, choose **Restore From Region**, indicating the region of backup stores.
198-
199-
> **Note**
200-
>
201-
> - The default value of the **Restore From Region** is the same as the backup cluster.
202-
203-
4. In **Restore Mode**, choose to restore data of any point in time or a selected backup to a new cluster.
134+
3. In **Restore Mode**, you can choose to restore data of any point in time or a selected backup to a new cluster.
204135

205136
<SimpleTab>
206137
<div label="Select Time Point">
207138

208-
To restore data of any point in time within the backup retention to a new cluster, make sure that **Point-in-time Restore** in **Backup Settings** is on and then take the following steps:
139+
To restore data of any point in time within the backup retention to a new cluster, make sure that **PITR** in **Backup Settings** is on and then take the following steps:
209140

210-
- Click **Select Time Point**.
211-
- Select **Date** and **Time** you want to restore to.
141+
1. Click **Select Time Point**.
142+
2. Select **Date** and **Time** you want to restore to.
212143

213144
</div>
214145

215146
<div label="Select Backup Name">
216147

217148
To restore a selected backup to the new cluster, take the following steps:
218149

219-
- Click **Select Backup Name**.
220-
- Select a backup you want to restore to.
150+
1. Click **Select Backup Name**.
151+
2. Select a backup you want to restore to.
221152

222153
</div>
223154
</SimpleTab>
224155

225-
5. In **Restore to Region**, select the same region as the **Backup Storage Region** configured in the **Backup Settings**.
156+
4. In **Restore to Region**, select the same region as the **Backup Storage Region** configured in the **Backup Settings**.
226157

227-
6. In the **Restore** window, you can also make the following changes if necessary:
158+
5. In the **Restore** window, you can also make the following changes if necessary:
228159

229160
- Set the cluster name.
230161
- Update the port number of the cluster.
231162
- Increase node number, vCPU and RAM, and storage for the cluster.
232163

233-
7. Click **Restore**.
164+
6. Click **Restore**.
234165

235166
The cluster restore process starts and the **Security Settings** dialog box is displayed.
236167

237-
8. In the **Security Settings** dialog box, set the root password and allowed IP addresses to connect to your cluster, and then click **Apply**.
168+
7. In the **Security Settings** dialog box, set the root password and allowed IP addresses to connect to your cluster, and then click **Apply**.
238169

239170
### Restore a deleted cluster
240171

241-
> **Note:**
242-
>
243-
> You cannot restore a deleted cluster to any point in time. You can only select an automatic or manual backup to restore.
244-
245172
To restore a deleted cluster from recycle bin, take the following steps:
246173

247174
1. Log in to the [TiDB Cloud console](https://tidbcloud.com).
@@ -257,4 +184,8 @@ To restore a deleted cluster from recycle bin, take the following steps:
257184

258185
The cluster restore process starts and the **Security Settings** dialog box is displayed.
259186

260-
7. In the **Security Settings** dialog box, set the root password and allowed IP addresses to connect to your cluster, and then click **Apply**.
187+
7. In the **Security Settings** dialog box, set the root password and allowed IP addresses to connect to your cluster, and then click **Apply**.
188+
189+
> **Note:**
190+
>
191+
> You cannot restore a deleted cluster to any point in time. You can only select an automatic or manual backup to restore.

tidb-cloud/pause-or-resume-tidb-cluster.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ When a cluster is paused, note the following:
3434
- Node Storage Cost
3535
- Data Backup Cost
3636

37-
- TiDB Cloud stops [automatic backup](/tidb-cloud/backup-and-restore.md#turn-on-auto-backup) of the cluster.
37+
- TiDB Cloud stops [automatic backup](/tidb-cloud/backup-and-restore.md#automatic-backup) of the cluster.
3838

3939
To pause a cluster, take the following steps:
4040

@@ -61,7 +61,7 @@ After a paused cluster is resumed, note the following:
6161

6262
- TiDB Cloud resumes collecting the monitoring information of the cluster, and you can read data from or write data to the cluster.
6363
- TiDB Cloud resumes charging both compute and storage costs.
64-
- TiDB Cloud resumes [automatic backup](/tidb-cloud/backup-and-restore.md#turn-on-auto-backup) of the cluster.
64+
- TiDB Cloud resumes [automatic backup](/tidb-cloud/backup-and-restore.md#automatic-backup) of the cluster.
6565

6666
To resume a paused cluster, take the following steps:
6767

tidb-cloud/tidb-cloud-faq.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ TiDB is highly compatible with MySQL. You can migrate data from any MySQL-compat
104104

105105
### Does TiDB Cloud support incremental backups?
106106

107-
No. If you need to restore data to any point in time within the cluster's backup retention, you can use PITR (Point-in-time Recovery). For more information, see [Use PITR in a TiDB Dedicated cluster](/tidb-cloud/backup-and-restore.md#turn-on-auto-backup) or [Use PITR in a TiDB Serverless cluster](/tidb-cloud/backup-and-restore-serverless.md#restore).
107+
No. If you need to restore data to any point in time within the cluster's backup retention, you can use PITR (Point-in-time Recovery). For more information, see [Use PITR in a TiDB Dedicated cluster](/tidb-cloud/backup-and-restore.md#automatic-backup) or [Use PITR in a TiDB Serverless cluster](/tidb-cloud/backup-and-restore-serverless.md#restore).
108108

109109
## HTAP FAQs
110110

0 commit comments

Comments
 (0)