PolarDB:Restore a released cluster

Usage notes

• A cluster in the cluster recycle bin must have at least one backup set to be restorable. If you delete all backup sets of a cluster, you cannot restore it.

• 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.

• Ensure that your account has a sufficient balance to prevent restoration failures that are caused by overdue payments.

Procedure

1. Log on to the PolarDB console.

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

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

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

   

5. On the purchase page, set the following parameters and configure any other parameters as needed. For more information, see Custom Purchase.

   Parameter	Description
   Creation Method	Select Restore From Recycle Bin to restore the deleted PolarDB cluster using its backup set retained in the cluster recycle bin. Note If the original PolarDB cluster has X-Engine enabled and contains database or table data stored in X-Engine, set Storage Engine to InnoDB & X-Engine. Otherwise, the new PolarDB cluster cannot access data stored in X-Engine.
   Source Version	Select the version of the deleted cluster.
   Deleted Clusters	Select the ID of the deleted cluster.
   Backup History	Select the backup to restore. Note The Backup History list displays backup times in UTC. The Data Backups tab displays backup times converted to your local time zone. Ensure you select the correct backup. For example, if your current time zone is UTC+8 (Beijing Time) and the backup creation time shown in the console’s backup list is May 28, 2021 11:19:30 (Beijing Time), select 2021-05-28T03:19:30Z (UTC) in the Backup History list.
   Database Engine	The database engine version of the PolarDB cluster. By default, it matches the version of the deleted cluster and cannot be changed.

6. After you complete the purchase, wait 10 to 15 minutes for the system to create the cluster. Then, you can view the new cluster in the cluster list of the PolarDB console.

   Note

   • If the status of the cluster nodes is Creating, the cluster is being created and is unavailable. The cluster is ready to use only when its status changes to Running.

   • Ensure you select the correct region in the top-left corner of the console. Otherwise, you cannot find your cluster.

FAQ

• When I try to restore a cluster from the cluster recycle bin, the following error is reported:The restore function has been disabled due to arrears. What should I do?

  If your Alibaba Cloud account has an overdue payment, the backup and restoration feature for PolarDB clusters is disabled. After you add funds to your account, this feature is automatically re-enabled.

  If errors still occur during cluster restoration, you can manually call ReactivateDBClusterBackup to re-enable backup restoration for the cluster.

  Note

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

  • You can call this API operation in OpenAPI Explorer without having to manually calculate the signature.

• When I try to restore a cluster from the cluster recycle bin, the following error is reported:Specified StorageType is not valid What should I do?

  When you restore a cluster from the cluster recycle bin, make sure that the product edition, series, and CPU architecture of the new cluster are the same as those of the original cluster. This error can be caused by the following reasons:

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

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

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

Related API operations