PolarDB:Restore a released cluster

Prerequisites

Before you begin, ensure that you have:

• At least one backup set in the recycle bin for the cluster you want to restore. If all backup sets are deleted, the cluster cannot be restored.

• A sufficient account balance. Overdue payments disable the backup and restoration feature.

Limitations

• Backup archiving: After you release a cluster, all level-1 backups in the cluster recycle bin are asynchronously archived to level-2 backups at a rate of approximately 150 MB/s. For more information, see Backup and recovery.

• X-Engine data: If the original cluster has X-Engine enabled and contains X-Engine data, set Storage Engine to InnoDB & X-Engine on the new cluster. Otherwise, the new cluster cannot access the X-Engine data.

• Cluster configuration matching: The new cluster's product edition, series, and CPU architecture must match those of the original cluster. A mismatch causes a Specified StorageType is not valid error. For details, see FAQ.

Restore a cluster from the recycle bin

1. Log on to the PolarDB console.

2. In the left navigation pane, click Cluster Recycle Bin.

3. In the upper-left corner, select the region where the cluster was deployed.

4. Find the cluster and click Restore Data to New Cluster in the Actions column.

   

5. On the purchase page, set the following parameters. For other parameters, see Custom Purchase.

   Parameter	Description
   Creation Method	Select Restore From Recycle Bin.
   Source Version	Select the version of the released cluster.
   Deleted Clusters	Select the ID of the released cluster.
   Backup History	Select the backup set to restore. The list displays backup times in UTC. The Data Backups tab displays times in your local time zone — make sure you select the matching UTC time. For example, if your local time zone is UTC+8 and the Data Backups tab shows May 28, 2021 11:19:30 (UTC+8), select 2021-05-28T03:19:30Z in the Backup History list.
   Database Engine	Automatically set to the version of the released cluster. Cannot be changed.

6. Complete the purchase. The system creates the new cluster within 10–15 minutes. After creation, the cluster appears in the cluster list of the PolarDB console.

   The cluster is unavailable while its status is Creating. It is ready to use when the status changes to Running. Make sure the correct region is selected in the console; otherwise, the cluster will not appear in the list.

FAQ

The restore function has been disabled due to arrears. What should I do?

Overdue payments on your Alibaba Cloud account disable the backup and restoration feature. Add funds to your account — the feature is automatically re-enabled.

If the error persists after adding funds, call ReactivateDBClusterBackup to manually re-enable backup restoration. You can call this operation directly in OpenAPI Explorer without calculating a signature.

If your account remains in arrears for more than 14 days, the system automatically deletes all backup sets in the cluster recycle bin. Deleted data cannot be recovered.

"Specified StorageType is not valid" error. What should I do?

The new cluster's configuration must match the original cluster. This error is caused by one of the following mismatches:

• Product edition: For example, you selected Standard Edition for the new cluster, but the original cluster is Enterprise Edition.

• CPU architecture: For example, you selected X86 for the new cluster, but the original cluster uses Yitian ARM.

• Storage class: For example, you selected enterprise SSD for the new cluster, but the original cluster uses PSL4/PSL5.

Match the product edition, series, and CPU architecture of the original cluster and try again.

API reference