PolarDB:Restore a released cluster

Usage notes

• Each cluster in the cluster recycle bin must retain at least one backup set. If all backup sets of a cluster are deleted, the cluster cannot be restored.

• After you release a cluster, if you choose to retain backups, the relevant data backups are saved in the cluster recycle bin. For more information, see Cluster recycle bin.

• Make sure that your account balance is sufficient to avoid restoration failures due to overdue payments.

Procedure

1. Log in to the PolarDB console，In the navigation pane on the left, click Clusters. Select the Region where the cluster is deployed, and then find the target cluster。

2. In the Actions column, click Restore Data to New Cluster.

3. On the purchase page that appears, configure the following parameters. You can configure the other parameters based on your business requirements. For details, see Custom Purchase.

   Parameter	Description
   Creation Method	Select Restore from Recycle Bin to restore a deleted PolarDB cluster based on the backup sets retained in the cluster recycle bin. Note If the original PolarDB cluster had X-Engine (high-compression engine) enabled and contained the corresponding database and table data, you must select InnoDB & X-Engine under Storage Engine. Otherwise, the new PolarDB cluster cannot access data in the high-compression engine.
   Original Version	Select the edition of the deleted cluster.
   Deleted Clusters	Select the ID of the deleted cluster.
   Backup History	Select the backup to restore. Note The backup times shown in Backup History are in UTC. The backup times on the Data Backups tab have been converted to your local time zone. Make sure that the selected backup is correct. For example, if you are in the UTC+8 time zone (Beijing time) and the backup list in the console shows a backup creation time of 2021-05-28 11:19:30 (Beijing time), select 2021-05-28T03:19:30Z (UTC) from the backup history list.
   Database Engine	The database engine version of the PolarDB cluster. By default, it is the same as the edition of the deleted cluster and cannot be changed.

4. After you complete the purchase, the system requires 10 to 15 minutes to create the cluster. You can then view the new cluster in the cluster list of the PolarDB console.

   Note

   • While the status of the nodes in the cluster is Creating, the cluster may still be under creation and is unavailable. The cluster can be used only when the cluster status is Running.

   • Make sure that you have selected the correct region in the upper-left corner of the page. Otherwise, you cannot view the cluster that you created.

FAQ

• When I restore a cluster from the cluster recycle bin, the errorThe restore function has been disabled due to arrears. is reported. What do I do?

  If your Alibaba Cloud account has an overdue payment, the system disables the backup restoration feature for PolarDB clusters. After you top up your account, the system automatically re-enables this feature.

  If the error persists when you restore a cluster, manually call ReactivateDBClusterBackup to re-enable the backup restoration feature for the cluster.

  Note

  • If your Alibaba Cloud account remains overdue for more than 14 days, the system automatically releases the backup sets in the cluster recycle bin. The data is no longer retained and cannot be recovered.

  • You can run this API operation directly in OpenAPI Explorer without the need to manually calculate the signature.

• When I restore a cluster from the cluster recycle bin, the errorSpecified StorageType is not valid is reported. What do I do?

  When you restore a cluster from the cluster recycle bin, make sure that the restored cluster is consistent with the original cluster in terms of product edition, series, and CPU architecture. Common causes of this error include:

  • Incorrect product edition: For example, the original cluster is Enterprise Edition but the restored cluster is Standard Edition.

  • Incorrect CPU architecture: For example, the original cluster uses Yitian ARM but the restored cluster uses x86.

  • Incorrect storage type: For example, the original cluster uses PSL4/PSL5 but the restored cluster uses ESSD.

Related API