Full restoration restores the entire dataset of a PolarDB cluster to a new cluster. After you verify the data in the new cluster, you can also migrate the restored data to the source cluster. You can restore data from a backup set or to a specific point in time. This topic describes how to restore the entire dataset of a cluster from a backup set.
Precautions
The restored cluster contains the data and account information of the source cluster but does not include its parameter settings.
Procedure
-
Log on to the PolarDB console. In the left-side navigation pane, click Clusters. Select the region where the target cluster is located, and then click the cluster ID to open the cluster details page.
-
In the left-side navigation pane, choose .
-
Restore data to a new cluster.
-
To restore to the same region:
Find the target backup set and click Restore Data to New Cluster in the Actions column.
-
To restore to a different region:
-
On the Backup and Restoration page, select the region where the data that you want to restore is located.
-
Find the target backup set and click Restore Data to New Cluster in the Actions column.
-
-
-
On the Clone Instance page, select a billing method for the new cluster.
-
Subscription: You pay for compute nodes when you create the cluster. Storage space is billed hourly based on the actual amount of data stored.
-
Pay-As-You-Go: You are billed hourly for both compute nodes and storage resources based on actual usage, with no upfront fees. If you need the cluster only for a short period, select Pay-As-You-Go to save costs, as you can release it when no longer needed.
-
-
Configure the following parameters.
Parameter
Description
Operation type
Select Restore from Backup Set.
Region
Select the destination region for the new cluster.
Note-
If cross-region backup is enabled, you can restore data to the source region or the destination backup region.
-
If cross-region backup is disabled, the destination region is the same as the source region by default and cannot be changed.
Backup Set
Select the backup set that you want to restore.
NoteThe Backup Start Time of each backup set is displayed. You can use this information to identify the correct backup set.
Primary Zone
Select the primary Primary Zone for the cluster.
NoteIn regions that have two or more zones, PolarDB automatically replicates data to a secondary zone for disaster recovery.
Network Type
This parameter is fixed to VPC and cannot be changed.
VPC
Select the VPC and VSwitch for the cluster. We recommend that you use the same VPC and VSwitch as the source cluster.
NoteTo ensure optimal performance, make sure that the PolarDB cluster and the ECS instances that need to connect to the cluster are created in the same VPC. Otherwise, they cannot communicate with each other over the internal network.
VSwitch
Compatibility
By default, the Compatibility is the same as that of the original cluster, and no selection is required.
Service Edition
By default, this parameter is the same as the Service Edition of the source cluster and cannot be changed.
Edition
By default, this parameter is the same as the Edition of the source cluster and cannot be changed.
Specification Edition
By default, this is the same as the Specification Edition of the original cluster, and you do not need to select it.
CPU Architecture
By default, this parameter is the same as the CPU Architecture of the source cluster and cannot be changed.
Node Specifications
Select a Node Specifications. Different specifications have different maximum storage capacities and performance. For more information, see Compute node specifications.
NoteTo ensure that the restored cluster runs as expected, we recommend that you select a Node Specifications that is higher than the specification of the source cluster.
Nodes
The default value is 2.
NoteBy default, a new cluster is created with one primary node and one read-only node. After the cluster is created, you can add nodes to scale it up to 1 primary node and 15 read-only nodes. For more information, see Add or remove nodes.
PolarProxy type
This parameter is fixed to Enterprise Dedicated Edition and cannot be changed.
Enable hot standby cluster
Specifies whether to enable the hot standby cluster.
-
If you Enable Hot Standby Storage Cluster, PolarDB deploys both a primary cluster (including compute nodes with mutual failover and primary storage) and a hot standby storage cluster in the current region. The primary cluster and the hot standby storage cluster each maintain three data replicas, for a total of six replicas. This provides a higher service level agreement (SLA).
-
If you Disable Hot Standby Storage Cluster, only the primary cluster with three data replicas is deployed. The unit price for storage is half of that when the feature is enabled, but the SLA is lower.
Storage Type
-
PolarDB Enterprise Edition supports two storage types: PSL5 and PSL4.
-
PSL5: A storage type supported in earlier PolarDB versions that offers high performance, reliability, and availability.
-
PSL4: A new storage type that uses Alibaba Cloud's proprietary Smart-SSD technology to compress and decompress data at the physical SSD level. This reduces storage costs per unit of data while keeping the performance impact under control.
NoteYou cannot change the storage type of an existing cluster. To switch the storage type, you must purchase a new cluster with the desired storage type and then migrate the data from the source cluster to the new cluster.
For a detailed comparison of the two storage types, see How to choose between PSL4 and PSL5.
-
Storage Billing Method
PolarDB supports two storage billing methods: Pay-as-you-go (pay-by-capacity) and Subscription.
-
Pay-as-you-go (pay-by-capacity): This method adopts a serverless model. You do not need to specify a storage capacity at purchase. Storage automatically scales as your data grows, and you are charged only for the storage space that you use.
-
Subscription: This method requires you to prepay for a specific amount of storage capacity when you purchase the cluster.
For more information about the storage billing methods, see Storage billing methods.
Note-
If the Billing Method is Subscription, you can set the Storage Billing Method to Pay-as-you-go (pay-by-capacity) or Subscription.
-
If the Billing Method is Pay-As-You-Go, this parameter is not configurable. The storage billing method defaults to Pay-as-you-go (pay-by-capacity).
Storage Fee
If the storage billing method is Pay-as-you-go (pay-by-capacity), you do not need to specify a storage capacity. PolarDB charges you hourly for your actual storage usage.
Storage Capacity
The amount of storage capacity to purchase for the Subscription (pay-by-space) billing method. The PolarDB Enterprise Edition storage capacity ranges from 50 GB to 500 TB and can be adjusted in increments of 10 GB.
NoteThis parameter is available only if the Billing Method is Subscription and the Storage Billing Method is Subscription.
Cluster Name
Enter a Cluster Name. The name must meet the following requirements:
-
The name must be 2 to 128 characters in length.
-
The name must start with a letter.
-
The name can contain digits, periods (.), underscores (_), and hyphens (-).
If you leave this field empty, a name is automatically generated. You can change the name after the cluster is created.
Subscription Duration
Select the cluster's Subscription Duration.
NoteThis parameter is available only if the Billing Method is Subscription.
Quantity
Select the Quantity for the cluster.
-
-
Complete the payment based on the selected Billing Method.
-
Pay-As-You-Go
By clicking Buy Now, you agree to the Terms of Service and any product-specific terms selected on this page.
-
Subscription
-
By clicking Buy Now, you agree to the Terms of Service and any product-specific terms selected on this page.
-
On the Confirm Order page, confirm the order details and payment method, and then click Pay.
-
NoteAfter the payment is complete, it takes 10 to 15 minutes to create the cluster. You can then view the new cluster on the Clusters page.
-
API reference
|
API |
Description |
|
You can call the CreateDBCluster operation to restore data from a backup set. Note
Set the CreationOption parameter to CloneFromPolarDB. |