A full restoration copies all historical data from a source PolarDB cluster to a new cluster. After verifying the data on the new cluster, you can migrate it back to the source cluster. You can restore data from a backup set or to a specific point in time. This topic describes how to perform a point-in-time restoration (PITR).
Precautions
The restored cluster contains the data and account information from the source cluster but not its parameter settings.
Procedure
-
Log on to the PolarDB console. In the left-side navigation pane, click Clusters. Select the region for your cluster, and then click the target cluster ID.
-
In the left-side navigation pane, choose .
-
Perform a point-in-time restoration.
-
To restore within the same region:
On the Backup and Restoration page, click Point-in-time Restoration.
-
To restore to a different region:
-
On the Backup and Restoration page, select the region containing the data you want to restore.
-
Click Point-in-time Restoration.
-
-
-
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 to Point in Time.
Region
Select the destination region for the restoration.
Note-
If cross-region backup is enabled, you can restore to either the source region or the destination region.
-
If cross-region backup is not enabled, this is automatically set to the region of the source cluster. No selection is required.
Backup point in time
Select the point in time to which you want to restore the data.
NoteYou can restore your cluster to any point in time within the last 7 days.
Primary Zone
Select the Primary Zone for the cluster.
NoteIn a region with two or more availability zones, PolarDB automatically replicates data to a secondary availability zone for disaster recovery.
Network Type
This parameter is fixed to VPC. No action is required.
VPC
Select the VPC and VSwitch for the cluster. We recommend using the same settings as the source cluster.
NoteFor optimal performance and internal network connectivity, create the PolarDB cluster and the ECS instances that connect to it in the same VPC.
VSwitch
Compatibility
This parameter is automatically set to match the Compatibility of the source cluster. No action is required.
Service Edition
This parameter is automatically set to match the Service Edition of the source cluster. No action is required.
Edition
This parameter is automatically set to match the Edition of the source cluster. No action is required.
Specification Edition
CPU Architecture
This parameter is automatically set to match the CPU Architecture of the source cluster. No action is required.
Node Specifications
Select a Node Specifications. Different specifications have different maximum storage capacities and performance. For more information, see and .
NoteTo ensure the restored cluster functions correctly, we recommend selecting a Node Specifications equal to or higher than the source cluster's specification.
Nodes
The default value is 2.
NoteBy default, a new cluster includes one primary node and one read-only node. After creation, you can add read-only nodes for a total of one primary and up to 15 read-only nodes. For more information, see .
Database proxy type
This parameter is fixed to Enterprise Dedicated Edition. No action is required.
Enable hot standby cluster
Select whether to Enable Hot Standby Cluster.
-
If you Enable Hot Standby Storage Cluster, PolarDB deploys both a primary cluster (with replica compute nodes and primary storage) and a hot standby storage cluster in the current region. The primary cluster and the hot standby cluster each maintain three data replicas, for a total of six replicas, providing higher SLA assurance.
-
If you Disable Hot Standby Storage Cluster, only the primary cluster with three data replicas is deployed. The storage cost is halved, but the SLA is lower.
Storage Type
-
PolarDB Enterprise Edition supports PSL5 and PSL4 storage types:
-
PSL5: A legacy storage type in PolarDB. It provides high performance, reliability, and availability.
-
PSL4: A new storage type that uses Alibaba Cloud's proprietary technology. It compresses and decompresses data at the physical SSD level, reducing storage costs per unit of data while maintaining controllable performance impact.
NoteThe storage type of an existing cluster cannot be changed. To switch types, you must create a new cluster with the desired storage type and migrate your data.
For a detailed comparison of the two storage types, see .
-
Storage Billing Method
PolarDB supports two storage billing methods: pay-by-capacity and Subscription.
-
Pay-by-capacity: This method uses a serverless approach. You do not need to specify a capacity when you purchase the cluster. Storage capacity automatically scales as your data grows, and you are charged only for the actual storage space your data uses.
-
Subscription: You pre-purchase a specific amount of storage space for your cluster.
For more information about storage billing, see .
Note-
If the billing method is Subscription, you can choose either pay-by-capacity or Subscription for the Storage Billing Method.
-
If the billing method is Pay-As-You-Go, this parameter is unavailable. The storage billing method defaults to pay-by-capacity.
Storage Fee
If the storage billing method is pay-by-capacity, you do not need to specify a storage capacity. PolarDB bills you hourly based on the actual storage space used.
Storage Capacity
The amount of storage space to pre-purchase. For a PolarDB Enterprise Edition cluster, the storage capacity ranges from 50 GB to 500 TB and can be adjusted in increments of 10 GB.
NoteThis parameter is available only when 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:
-
Must be 2 to 128 characters in length.
-
Must start with a letter or a Chinese character.
-
Can contain digits, periods (.), underscores (_), and hyphens (-).
If you leave this field blank, a name is automatically generated. You can change the name after the cluster is created.
Subscription Duration
Select the Subscription Duration for the cluster.
NoteThis parameter is available only when the billing method is set to Subscription.
Quantity
Select the Quantity of clusters to purchase.
-
-
Complete the payment based on your selected billing method.
-
Pay-As-You-Go
By clicking Buy Now, you agree to the terms of service and any selected product-specific terms.
-
Subscription
-
By clicking Buy Now, you agree to the terms of service and any selected product-specific terms.
-
On the Payment page, confirm the order details and payment method, and then click Pay.
-
Note-
After a successful purchase, cluster creation takes 10 to 15 minutes. You can then view the new cluster on the Clusters page.
-
The total time for a point-in-time restoration consists of the time to restore from the backup set (snapshot) plus the time to apply physical logs. If the write workload was high since the last backup set was created, applying the physical logs may take a significant amount of time. For more information, see .
-
Related APIs
|
API |
Description |
|
You can call the CreateDBCluster operation to restore a PolarDB cluster. Note
Set the CreationOption parameter to CloneFromPolarDB. |