Skip to content

Commit 2f2eec8

Browse files
committed
Update backup-and-restore-premium.md
1 parent 6b1b458 commit 2f2eec8

1 file changed

Lines changed: 13 additions & 3 deletions

File tree

tidb-cloud/premium/backup-and-restore-premium.md

Lines changed: 13 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,12 @@ aliases: ['/tidbcloud/restore-deleted-tidb-cluster']
88

99
This document describes how to back up and restore your data on {{{ .premium }}} instances. {{{ .premium }}} supports both automatic backups and manual backups, and lets you restore backup data to a new instance as needed.
1010

11+
<CustomContent plan="byoc">
12+
13+
This document also applies to {{{ .byoc }}}. Backup and restore capabilities for {{{ .byoc }}} are currently consistent with {{{ .premium }}}.
14+
15+
</CustomContent>
16+
1117
Backup files can originate from the following sources:
1218

1319
- Active {{{ .premium }}} instances
@@ -162,14 +168,16 @@ To restore a deleted {{{ .premium }}} instance from the Recycle Bin, take the fo
162168
>
163169
> If you are in multiple organizations, use the combo box in the upper-left corner to switch to your target organization first.
164170
165-
2. On the **Recycle Bin** page, click the **Premium** tab to go to the recycle bin of {{{ .premium }}} instances.
171+
2. On the **Recycle Bin** page, click the <CustomContent plan="premium">**Premium**</CustomContent><CustomContent plan="byoc">**BYOC**</CustomContent> tab to go to the recycle bin of <CustomContent plan="premium">{{{ .premium }}}</CustomContent><CustomContent plan="byoc">{{{ .byoc }}}</CustomContent> instances.
166172

167-
3. Locate the {{{ .premium }}} instance you want to restore, and then click the **>** button to expand the available backups of the instance.
173+
3. Locate the <CustomContent plan="premium">{{{ .premium }}}</CustomContent><CustomContent plan="byoc">{{{ .byoc }}}</CustomContent> instance you want to restore, and then click the **>** button to expand the available backups of the instance.
168174

169175
4. In the row of your desired backup, click **...**, and then select **Restore**.
170176

171177
5. On the **Restore** page, follow the same steps as [Restore to a new instance](#restore-to-a-new-instance) to restore the backup to a new instance.
172178

179+
<CustomContent plan="premium">
180+
173181
### Restore backups from a different plan type
174182

175183
Currently, you can only restore backups from a {{{ .dedicated }}} cluster hosted on AWS to a new {{{ .premium }}} instance.
@@ -187,9 +195,11 @@ To restore a backup generated by a {{{ .dedicated }}} cluster, follow these step
187195
188196
3. On the **Restore** page, follow the same steps as [Restore to a new instance](#restore-to-a-new-instance) to restore the backup to a new instance.
189197

198+
</CustomContent>
199+
190200
### Restore backups from cloud storage
191201

192-
{{{ .premium }}} supports restoring backups from cloud storage (such as Amazon S3 and Alibaba Cloud Object Storage Service (OSS)) to a new instance. This feature is compatible with backups generated from {{{ .dedicated }}} clusters or TiDB Self-Managed clusters.
202+
<CustomContent plan="premium">{{{ .premium }}}</CustomContent><CustomContent plan="byoc">{{{ .byoc }}}</CustomContent> supports restoring backups from cloud storage (such as Amazon S3 and Alibaba Cloud Object Storage Service (OSS)) to a new instance. This feature is compatible with backups generated from {{{ .dedicated }}} clusters or TiDB Self-Managed clusters.
193203

194204
>**Note:**
195205
>

0 commit comments

Comments
 (0)