PolarDB:Restore a released cluster

Prerequisites

Before you begin, make sure that:

• The released cluster has at least one available backup set in the recycle bin. If all backup sets have been deleted, the cluster cannot be restored.

• You know which backup set to restore from. The Historical Backups field displays backup times in UTC. Convert accordingly — for example, 2020-05-08 10:00:00 (UTC+8) corresponds to 2020-05-08T02:00:00Z.

Released cluster data is asynchronously archived to level-2 backups at approximately 150 MB/s. For details, see Backup and restoration.

Restore a cluster from the recycle bin

1. Log on to the PolarDB console.

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

3. Select the region of the cluster. In the cluster list, find the cluster and click Restore Data to New Cluster in the Actions column.

4. On the Custom Purchase page, set Creation Method to Restore from Recycle Bin, then configure the following parameters:

   Parameter	Description
   Billing Method	Subscription: upfront payment, suitable for stable, predictable workloads. Pay-as-you-go: charged based on actual usage, suitable for fluctuating workloads. To change billing method after creation, see Change the billing method.
   Region	The region of the released cluster. Cannot be changed after the cluster is created. To minimize latency, deploy the PolarDB cluster and the ECS instance you use to connect to it in the same region.
   Source Version	The database engine version of the released cluster.
   Deleted Clusters	The name of the released cluster.
   Historical Backups	The backup set to restore from. Times are shown in UTC. The backup list displays times in your local system time — make sure to select the correct backup by converting appropriately.
   Database Engine	Inherited from the released cluster. Cannot be changed.
   Database Edition	Standard Edition or Enterprise Edition.
   Specification	General-purpose: shares idle CPU resources with other clusters on the same server, improving cost efficiency. Dedicated: does not share compute resources, improving reliability and stability.
   CPU Architecture	X86: Intel processors with high-performance networking, suited for enterprise workloads requiring stability and performance. YiTian ARM: Alibaba Cloud YiTian 710 processors with 25 Gigabit Ethernet, suited for cost-effective, secure cloud services.
   Primary Zone	The zone where the primary cluster is deployed. Zones are independent geographical locations within a region.
   Network Type	The system automatically selects VPC. To optimize performance and security, use the same Virtual Private Cloud (VPC) for the PolarDB cluster and the ECS instance you connect from. If no existing VPC meets your requirements, use the default VPC and vSwitch: the default VPC uses a 16-bit subnet mask (for example, 192.168.0.0/16), providing up to 65,536 private IP addresses, with one default VPC per region that does not consume your VPC quota; the default vSwitch uses a 20-bit subnet mask (for example, 192.168.0.0/20), providing up to 4,096 private IP addresses, with one default vSwitch per zone that does not consume your vSwitch quota. To create a new VPC, see Create and manage a VPC.
   High Availability Mode	Dual AZ (Enable Hot Standby Storage Cluster): deploys both a primary cluster and a hot standby storage cluster in the same region, each with 3 data replicas (6 total), providing higher SLA reliability. Single AZ (Disable Hot Standby Storage Cluster): retains only the primary cluster with 3 data replicas; storage cost per unit is half that of the dual-AZ setup. For details, see High availability mode.
   Secondary Zone	Required only when High Availability Mode is set to Dual AZ. Select Automatically Allocated to let the system assign a secondary zone.
   Nodes	By default, the cluster includes one primary node and one read-only node. Select 2 nodes (primary + read-only) or 1 node (primary only).
   PolarProxy Type	Standard Enterprise Edition: shared CPU resources, suited for general-purpose clusters, with second-level elastic scaling. Dedicated Enterprise Edition: exclusively occupies allocated CPU resources, suited for dedicated clusters.
   Storage Type	ESSD: high-performance disks with up to 1 million IOPS and ultra-low latency, available in performance levels PL0, PL1, PL2, PL3, and AutoPL. PSL5: legacy PolarDB storage with high performance, reliability, and availability. PSL4: uses Alibaba Cloud smart-SSD technology to compress data at the physical SSD level, reducing storage costs. For a comparison, see How do I choose between PSL4 and PSL5?. > Important Storage type cannot be changed after the cluster is created. To change it, create a new cluster with the desired storage type and migrate your data.
   Storage Billing Method	Pay-as-you-go: serverless approach — storage scales automatically and you are charged for actual usage. Subscription: prepaid storage capacity. Available only when Billing Method is Subscription and Database Edition is Enterprise Edition. If Billing Method is Subscription and Database Edition is Standard Edition, the storage billing method is fixed to Subscription.
   Storage	The prepaid storage capacity. Valid ranges: PSL4/PSL5: 10 GB to 500 TB (10 GB increments); ESSD: 20 GB to 64 TB (10 GB increments). Available only when Storage Billing Method is Subscription. > Note When ESSD storage is full, it enters a read-only state and no additional data can be written.

5. On the right side of the page, verify the configuration summary (including Billing Method, Region, Creation Mode, and Resource Group), then configure:

   Parameter	Description
   Quantity	Number of clusters to create. Up to 50 clusters per order; an Alibaba Cloud account can hold up to 50 clusters in total.
   Duration	Required only when Billing Method is Subscription. Select Enable Auto-Renewal to avoid service interruptions from overdue payments.

6. Review the total cost and expense breakdown, then click Buy Now. On the Payment page, verify your order and click Pay.

Cluster creation takes 10 to 15 minutes. The new cluster appears in the cluster list once its status changes to Running.

While a node is in the Creating state, the cluster is not yet available. The cluster is ready only when its status is Running. Make sure you have selected the correct region, or the cluster will not appear in the list.

API reference