Full restoration creates a new PolarDB cluster from all historical data in your original cluster. After you verify the data in the new cluster, you can migrate it back to the original cluster. PolarDB supports two full restoration methods: from a backup set (this topic) and from a point in time.
Usage notes
The new cluster inherits the data and account information of the original cluster. Parameter settings are not restored. Before you restore, record the parameter configuration of your original cluster so you can reapply the settings to the new cluster after restoration.
Restore a cluster from a backup set
Procedure
Log on to the PolarDB console. In the left-side navigation pane, click Clusters. Select a region in the upper-left corner, then click the cluster ID to go to the Basic Information page.
In the left-side navigation pane, choose Settings and Management > Backup and Restoration.
Find the backup set to restore from, then click Restore Data to New Cluster in the Actions column.
Within a region: Find the backup set directly in the list.

Across regions: On the Backup and Restoration page, first select the region where the backup data resides. Then find the backup set and click Restore Data to New Cluster.

Cross-region backup supports restoring data to either the source region or the destination region.
On the Clone Instance page, select a billing method for the new cluster.
Billing method How you are charged Subscription Pay for compute nodes upfront. Storage fees are deducted from your account hourly based on actual usage. Pay-as-you-go Pay after use. Compute node and storage fees are both charged hourly. Use this for short-term workloads—release the cluster when done to reduce costs. Configure the parameters for the new cluster.
Parameter Description Configurable Clone type Select Restore from Backup Set. Yes Region The region to restore data to. If cross-region backup is not enabled, the region is the same as the original cluster. Yes (cross-region backup only) Backup set The backup set to restore from. The Backup Start Time of each set is shown to help you identify the right one. Yes Primary zone The zone where the primary node resides. In regions with two or more zones, PolarDB automatically replicates data to a secondary zone for disaster recovery. Yes Network type Fixed to VPC. No VPC / vSwitch The virtual private cloud (VPC) and vSwitch for the new cluster. Select the same VPC and vSwitch as your original cluster to keep them on the same internal network. Make sure the PolarDB cluster and the Elastic Compute Service (ECS) instance you want to connect to are in the same VPC; otherwise, they cannot communicate over the internal network. Yes Compatibility Automatically set to match the original cluster. No Product edition Automatically set to match the original cluster. No Edition Automatically set to match the original cluster. No Specification type Automatically set to match the original cluster's resource type. No CPU architecture Automatically set to match the original cluster. No Node specification The compute node size. Performance and maximum storage capacity vary by specification. For details, see . Select a specification higher than the original cluster to ensure stable performance. Yes Nodes Default is 2 (one primary node and one read-only node). You can add nodes after creation. A cluster supports one primary node and up to 15 read-only nodes. See . Yes PolarProxy type Fixed to Standard Enterprise. No Enable hot standby cluster When enabled, both the primary cluster and a hot standby storage cluster are deployed in the same region, each with 3 replicas (6 total), delivering higher SLA. When disabled, only the primary cluster is deployed with 3 replicas, and the storage unit price is half that of the enabled option. Yes Storage type Enterprise Edition supports PSL5 and PSL4. PSL5 offers higher performance and availability. PSL4 uses Smart-SSD technology to compress data at the physical disk level, lowering storage costs while maintaining disk performance. Storage type cannot be changed after cluster creation. See Comparison between PSL4 and PSL5. Yes (cannot be changed after creation) Storage billing method Pay-as-you-go: Storage scales dynamically; you pay for actual usage. Subscription: Purchase a fixed storage capacity upfront. See Billing methods for storage. Yes Storage cost Displayed when Storage billing method is Pay-as-you-go. No capacity specification required; charged hourly. Optionally, for more predictable costs. — Storage capacity Available when Billing method is Subscription and Storage billing method is Subscription. Enterprise Edition supports 50 GB to 500 TB in 10 GB increments. Yes (Subscription only) Cluster name 2–128 characters; letters, digits, periods (.), underscores (_), and hyphens (-); must start with a letter. Leave blank to auto-generate a name. You can rename the cluster after creation. Yes Purchase plan Subscription duration. Applies only when Billing method is Subscription. Yes (Subscription only) Number The number of clusters to create. Yes Complete the purchase.
Pay-as-you-go: Read and accept the Terms of Service, then click Buy Now.
Subscription: Read and accept the Terms of Service, click Buy Now, then confirm the order and payment method on the Purchase page and click Subscribe.
Cluster creation takes 10–15 minutes. The new cluster appears on the Clusters page when it is ready.
API reference
| API | Description |
|---|---|
| Creates a PolarDB cluster from a backup set. Set CreationOption to CloneFromPolarDB. |