Restore a released PolarDB for PostgreSQL (Compatible with Oracle) cluster from the Cluster Recycle Bin. The restored cluster is created as a new cluster — the original cluster is not recovered in place.
Prerequisites
Before you begin, make sure that:
The released cluster has at least one available backup set in the Cluster 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, while the backup list uses local system time. For example, if the backup list shows
2020-05-08 10:00:00 (UTC+8), the corresponding historical backup time is2020-05-08T02:00:00Z
Usage notes
Released cluster data is asynchronously archived to level-2 backups at approximately 150 MB/s. For more information, see Backup and restoration.
After restoration, the cluster is available only when its status changes to Running. While the cluster is in the Creating state, it is not yet fully established and cannot be used. Cluster creation takes approximately 10 to 15 minutes after purchase.
Restore a cluster from the recycle bin
Log on to the PolarDB console.
In the left-side navigation pane, click Cluster Recycle Bin.
Select the region of the cluster to restore. In the cluster list, find the cluster and click Restore Data to New Cluster in the Actions column.

On the Custom Purchase page, configure the cluster parameters. The following tables describe the key parameters.
Basic settings
Parameter Description Billing method Select Subscription (upfront payment) or Pay-as-you-go (postpaid, charged by actual usage). Subscription suits predictable, long-running workloads; Pay-as-you-go suits variable or short-term workloads. To change the billing method later, see Converting billing types. Region The region of the released cluster. The region cannot be changed after the cluster is created. For optimal performance and security, deploy the PolarDB cluster and the ECS instance in the same region. You can deploy the PolarDB cluster and the ECS instance in the same zone or across different zones. Deploying them in the same zone can reduce network latency and improve access speed. Creation method Select Restore from Recycle Bin. Source version The version of the released cluster. Deleted clusters The name of the released cluster. Historical backups The backup set to restore from. Backup times are displayed in UTC. Database engine The database engine version of the released cluster. Cannot be changed. Database edition The edition of the released cluster. Cannot be changed. CPU architecture The CPU architecture of the released cluster. Cannot be changed. Edition Automatically set to Cluster Edition (Recommended). No manual configuration required. Specification Automatically set to Dedicated. No manual configuration required. Zone and network
Parameter Description Primary zone The zone where the cluster is deployed. Zones are independent geographical locations within a region — all zones in a region provide the same performance level. Network type Automatically set to VPC (virtual private cloud). No manual configuration required. Select a VPC and vSwitch. For optimal performance and security, use the same VPC as the ECS instance that connects to the cluster. If you have an existing VPC that meets your network requirements, select it. Otherwise, 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, and does not consume the 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, and does not consume the vSwitch quota. Each region has only one default VPC, and each zone has only one default vSwitch. If the default VPC and vSwitch do not meet your requirements, see Create and manage a VPC.High availability mode Select one of the following modes: Dual AZ (Enable Hot Standby Storage Cluster) deploys both the primary cluster and a hot standby storage cluster within the same region, with 3 data replicas each (6 replicas total), providing higher Service-Level Agreement (SLA) reliability. Single AZ (Disable Hot Standby Storage Cluster) retains only the primary cluster with 3 data replicas, at half the storage cost per unit but with lower SLA reliability. For details, see High availability mode. Secondary zone Required only if High availability mode is set to Dual AZ (Enable Hot Standby Storage Cluster). Select Automatically Allocated to let the system assign a secondary zone. Compute and storage
Parameter Description Nodes By default, the cluster has one primary node and one read-only node. Select two nodes (primary + read-only) or one node (primary only). PolarProxy type Automatically set to Dedicated Enterprise Edition, which matches dedicated cluster specifications and exclusively occupies all allocated CPU resources for improved stability. Storage type Select PSL5 (the storage type supported in PolarDB historical versions; higher performance, reliability, and availability) or PSL4 (uses Alibaba Cloud smart-SSD technology to compress data at the physical SSD level, reducing storage cost per unit capacity). The storage type cannot be changed after the cluster is created. For a comparison, see . Storage billing method Pay-as-you-go: storage scales automatically as data grows, and you are charged based on actual usage. Subscription: prepay for a fixed storage capacity. Available only if Billing method is set to Subscription. Storage The storage capacity to purchase, from 10 GB to 500 TB in increments of 10 GB. Available only if both Billing method and Storage billing method are set to Subscription. On the right side of the page, confirm that Billing method, Region, Creation mode, and Resource group meet your requirements, then configure the following:
Parameter Description Quantity The number of clusters to purchase, up to 50 at a time. An Alibaba Cloud account can purchase up to 50 clusters in total. Duration Required only if Billing method is Subscription. Enable Auto-renewal to prevent service interruptions from overdue payments. Review the total cost and the breakdown (compute specifications, storage, and network), then click Buy Now. On the Payment page, verify the order details, select a payment method, and click Pay.
The cluster appears in the cluster list after purchase. Wait until the cluster status changes to Running (approximately 10 to 15 minutes) before using it.
Make sure you are in the correct region; otherwise, the cluster is not displayed in the list.
API reference
| Operation | Description |
|---|---|
| Creates a PolarDB cluster. |