PolarDB:Restore a released cluster

Usage notes

• Released clusters in the cluster recycle bin must have at least one backup set. If all backup sets of a cluster have been deleted, you cannot restore the released cluster.

• After a cluster is released, 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 about backup, see Data backup.

• Released clusters in the cluster recycle bin are retained for about 15 days. After 15 days, the recycle bin automatically clears the clusters and the clusters cannot be restored. If you want to use a backup set to restore a released cluster, perform the following steps.

Procedure

1. Log on to the PolarDB console.

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

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

4. Find the cluster that you want to restore, and click Restore Data to New Cluster in the Actions column.

   

5. Set Billing Method to Subscription or Pay-as-you-go.

   • Subscription: When you create a cluster, you must make a payment for the use of the cluster for a specific period of time.

   • Pay-as-you-go: When you create a cluster, you do not need to make a payment first. You are charged for the computing and storage resources that you use.

6. Configure the parameters that are described in the following table.

   Parameter	Description
   Region	The region of the new cluster. You cannot change the region after the new cluster is created. Note Make sure that the new PolarDB cluster and the Elastic Compute Service (ECS) instance to which you want to connect are deployed in the same region. Otherwise, the new PolarDB cluster and the ECS instance can communicate only over the Internet. This degrades the performance of the new cluster.
   Creation Method	Select Restore from Recycle to restore the released cluster in the cluster recycle bin.
   Source Version	The version of the released cluster.
   Deleted Clusters	The ID of the released cluster.
   Backup History	The backup set from which you want to restore the cluster. Note The Backup History drop-down list displays the timestamps of backup sets in UTC. However, the Data Backups tab displays timestamps of backup sets in the same time zone as the system time. Make sure that you choose the correct backup set. For example, if the timestamp of a backup set on the Data Backups tab is 11:19:30 on May 28, 2021 (UTC+08:00), select 2021-05-28T03:19:30Z (UTC) in the Backup History drop-down list.
   Database Engine	By default, the database engine version of the new PolarDB cluster is the same as that of the released cluster. You do not need to configure the parameter.
   Database Edition	By default, the database edition of the new PolarDB cluster is the same as that of the released cluster. You do not need to configure the parameter.
   Edition	By default, the edition of the new PolarDB cluster is the same as that of the released cluster. You do not need to configure the parameter.
   Nodes	If your original cluster is of Cluster Edition (Recommended), the cluster consists of one primary node and one read-only node by default. You can keep the default setting or change it to include only a primary node. If your original cluster is of Multi-master Cluster (Limitless), the system creates two primary nodes with the same specifications by default. In this case, you do not need to configure this parameter.
   Primary Zone	The primary zone where you want to deploy the new cluster. Note In regions that have two or more zones, PolarDB automatically replicates the data to the secondary zone for disaster recovery.
   Enable Hot Standby Storage Cluster	PolarDB provides multiple high availability modes. After you enable the hot standby storage cluster feature for a PolarDB cluster, a hot standby storage cluster is created in the secondary zone of the region in which the PolarDB cluster resides or in a different data center in the same zone. The hot standby storage cluster has independent storage resources. Whether the hot standby storage cluster has independent compute resources varies based on the high availability mode. When the PolarDB cluster in the primary zone fails, the hot standby storage cluster immediately takes over and handles read and write operations and storage tasks. Note For more information about the hot standby storage cluster and related solutions, see High availability modes (hot standby clusters). Rules for changing high availability modes: You cannot directly change the high availability mode of a cluster from Double Zones (Hot Standby Storage Cluster Enabled) or Double Zones (Hot Standby Storage and Compute Clusters Enabled) to Single Zone (Hot Standby Storage Cluster Disabled). For such change of the high availability mode, we recommend that you purchase a new cluster and select the Single Zone (Hot Standby Storage Cluster Disabled) high availability mode for the cluster. Then, migrate the existing cluster to the new cluster by using Data Transmission Service (DTS). For information about how to migrate an existing cluster to a new cluster, see Migrate data between PolarDB for MySQL clusters. You can select the Three Zones high availability mode only when you purchase a new cluster. You cannot change the high availability mode of a cluster from Three Zones to other high availability modes and vice versa. You can manually change the high availability mode of a cluster from Single Zone (Hot Standby Storage Cluster Disabled) to a different high availability mode. For more information, see High availability modes (hot standby clusters).
   Specification	The specifications of the new cluster. You can select the general-purpose or dedicated specification for a PolarDB cluster of Cluster Edition. Dedicated: The computing resources of a host such as CPU cores that are allocated to each PolarDB cluster are exclusive to the cluster. This improves performance stability. General-purpose: Idle computing resources such as CPUs are shared among clusters on the same host for cost-effectiveness. For more information about the differences between the specifications, see Comparison between general-purpose and dedicated compute nodes.
   Filter	The node specification of the new cluster. The maximum storage capacity and performance of a cluster vary based on the node specification. For more information, see Compute node specifications of PolarDB for MySQL Enterprise Edition. Note We recommend that you select a node specification that is higher than the node specification of the original cluster. This ensures that the new cluster runs as expected.
   PolarProxy Type	The type of PolarProxy in the new cluster. PolarDB provides two PolarProxy types: Standard Enterprise Edition and Dedicated Enterprise Edition. Standard Enterprise Edition applicable to general-purpose clusters. PolarProxy of this type uses shared CPU resources and provides intelligent, second-level elastic scaling based on business workloads. Dedicated Enterprise Edition: applicable to dedicated clusters. PolarProxy of this type occupies all allocated CPU resources and provides better stability. Note PolarProxy is available free of charge but may be charged in the future.
   Storage Type	The storage type of the new cluster. PolarDB provides two storage types: PSL5 and PSL4. PSL5: the storage type supported by the historical versions of PolarDB. PSL5 is the default storage type for PolarDB clusters purchased before June 7, 2022. PSL5 provides higher performance, reliability, and availability. PSL4: a new storage type for PolarDB. It uses the Smart-SSD technology developed in-house by Alibaba Cloud to compress and decompress data that is stored on SSDs. PSL4 can minimize the storage costs of data while maintaining a high disk performance. Note You cannot change the storage type of existing clusters. To use PSL4, we recommend that you purchase a new cluster, set the storage type to PSL4, and then migrate data to the new cluster.
   Storage Engine	The storage engine of the new cluster. PolarDB provides two engine types: InnoDB and InnoDB & X-Engine. InnoDB: InnoDB storage engine. InnoDB & X-Engine: deploys both InnoDB and X-Engine. After you select this option, set the ratio of X-Engine Memory Usage. For more information, see Overview.
   Storage Billing Method	The storage billing method of the new cluster. PolarDB supports the Pay-as-you-go and Subscription storage billing methods. Pay-as-you-go: The storage capacity dynamically scales as the data volume increases or decreases. You do not need to specify the storage capacity when creating a cluster, and you are charged for the storage used. For more information, see Pay-as-you-go. Subscription: You need to purchase a specific amount of storage capacity when you create the cluster. For more information, see Subscription. Note If the Billing Method parameter is set to Subscription, the Storage Billing Method parameter can be set to Pay-as-you-go or Subscription. If the Billing Method parameter is set to Pay-as-you-go, you cannot change the default value of this parameter, which is Pay-as-you-go.
   Storage Capacity	The amount of storage capacity that you want to purchase for the new cluster. The storage capacity of a PolarDB cluster ranges from 50 GB to 500 TB, in 10 GB increments. Note This parameter is valid only if Storage Billing Method is set to Subscription.
   Storage Cost	You do not need to specify the required storage capacity when you purchase the PolarDB cluster. You are charged for storage usage on an hourly basis. In addition, you can purchase storage plans based on your business requirements. For more information, see Purchase a storage plan.
   Cluster Name	The method that is used to generate a name for the new cluster. You can select Auto-generate or Custom. If you select Auto-generated, the system automatically generates a cluster name after the new cluster is created. You can modify the automatically generated cluster name. If you select Custom, you need to enter a cluster name. The name must meet the following requirements: The name cannot start with http:// or https://. The name must be 2 to 256 characters in length. The name must start with a letter and can contain digits, periods (.), underscores (_), and hyphens (-).
   Resource Group	The resource group to which the new cluster belongs. For more information, see Create a resource group. Note A resource group is a group of resources that belong to an Alibaba Cloud account. Resource groups allow you to manage resources in a centralized manner. A resource can belong to only one resource group. For more information, see Classify resources into resource groups and grant permissions on the resource groups.
   Network Type	The network type of the new cluster. This parameter is fixed to VPC. You do not need to configure this parameter.
   VPC	The VPC and vSwitch to which the new cluster belongs. We recommend that you select the same VPC and vSwitch that are connected to the original cluster. Note Make sure that the PolarDB cluster is created in the same virtual private cloud (VPC) as the ECS instance to which you want to connect. Otherwise, the cluster and the ECS instance cannot communicate over the internal network to achieve optimal performance.
   vSwitch
   Parameter Template	The parameter template that you want to use. Select a custom or default system parameter template. Note In the parameter template drop-down list, all custom and default system parameter templates available in the current region are displayed. For more information about parameter templates, see Apply a parameter template.
   Time Zone	The time zone of the new cluster. The default value is UTC +08:00.
   Table Name Case Sensitivity	Specifies whether the table names of the cluster are case-sensitive. The default value is Not Case-sensitive (Default). If the databases in your instance have case-sensitive names, we recommend that you select Case-sensitive. Note The value of this parameter cannot be changed after the cluster is created. Exercise caution when you select the value.
   Enable Binary Logging	Specifies whether to enable the binary logging feature. For more information, see Enable binary logging.
   Release Cluster	The backup retention policy that is used when the original cluster is deleted or released. The default value is Retain Last Automatic Backup (Automatic Backup before Release) (Default). Retain Last Automatic Backup (Automatic Backup before Release) (Default): The system retains the last backup when you release the cluster. Retain All Backups: The system retains all backups when you release the cluster. Delete All Backups (Cannot be restored): The system retains no backups when you release the cluster. Note You may be charged for the retained backups. You can delete the backups to reduce costs. For more information, see Billing rules of backup storage that exceeds the free quota.
   Duration	The subscription duration of the new cluster. Note This parameter is valid only if Billing Method is set to Subscription.
   Quantity	The number of clusters that you want to purchase.

7. Complete the rest of the steps based on the billing method of the cluster.

   • Pay-as-you-go

     1. Click Confirm Order.

     2. On the Confirm Order page, confirm your order information. Read and select the terms of service, and then click Buy Now.

   • Subscription

     1. Click Buy Now.

     2. On the Confirm Order page, confirm your order information. Read and select the terms of service, and then click Buy Now.

     3. On the Purchase page, confirm the order and the payment method, and then click Subscribe.

   After you complete the payment, wait 10 to 15 minutes. Then, you can view the newly created cluster on the Clusters page.

   Note

   The amount of time required to restore data to a new cluster depends on the size of the backup set. It takes more time for the system to restore data from a larger backup set. After the cluster is created, you can return to the PolarDB console and view the new cluster on the Clusters page.

Related API operations