PolarDB:Full restoration method 1: Restore data to a point in time

Precautions

The restored cluster contains the data and account information from the source cluster, but it does not include the parameter settings.

Procedure

1. Log on to the PolarDB console. In the navigation pane on the left, click Clusters. Select the region where your cluster is located, and then click the cluster ID to open the cluster details page.

2. In the navigation pane on the left, choose Settings and Management > Backup and Restoration.

3. Restore data to a point in time.

   • Same-region restoration:

     On the Backup and Restoration page, click Point-in-time Restoration.

     

   • Cross-region restoration:

     1. On the Backup and Restoration page, select the region that contains the backup data that you want to restore.

     2. Click Point-in-time Restoration.

     

4. On the Clone Instance page, select a Product Type for the new cluster.

   • Subscription: Pay for the compute nodes when you create the cluster. The storage space is billed hourly based on the actual data volume, and the fees are deducted from your account.

   • Pay-as-you-go: No upfront payment is required. Both the compute cluster and storage space are billed hourly based on the actual data volume. The fees are deducted from your account. If you need the cluster for only a short period, select pay-as-you-go. You can release the cluster when it is no longer needed to save costs.

5. Set the following parameters.

   Parameter Name	Description
   Operation Type	Select Restore to Point in Time.
   Region	Select the destination region for the restoration. Note If you enable cross-region backup, you can restore data to the source region or the destination region. If you do not enable cross-region backup, the new cluster is in the same region as the source cluster by default. You do not need to select a region.
   Backup point in time	Select the point in time to which you want to restore data. Note You can restore data to any point in time within the last seven days.
   Primary Zone	Select the primary zone for the cluster. Note In regions with two or more zones, PolarDB automatically replicates data to the secondary zone for disaster recovery.
   Network Type	This parameter is fixed to VPC. You do not need to select it.
   VPC Network	Select the VPC and vSwitch for the cluster. We recommend that you use the same VPC and vSwitch as the source cluster. Note Ensure that the PolarDB cluster and the ECS instance that you want to connect to are in the same VPC. Otherwise, they cannot communicate over the internal network for optimal performance.
   vSwitch
   Compatibility	This parameter is automatically set to the Compatibility value of the original cluster. You do not need to change this value. For example, if the Compatibility of the original cluster is PostgreSQL 14 (fully compatible with PostgreSQL 14), the Compatibility here is also fixed to PostgreSQL 14.
   Product Version	This parameter is automatically set to the Product Edition of the original cluster. You do not need to change this value.
   Series	This parameter is automatically set to the Edition of the original cluster. You do not need to select a value.
   Subseries	Select a Specification Type for the cluster. General-purpose and Dedicated specification types are available: Dedicated: The cluster exclusively uses its allocated compute resources, such as CPU, and does not share them with other clusters on the same server. This provides better performance stability and reliability. General-purpose: Different clusters on the same server make full use of each other's idle compute resources, such as CPU. This resource multiplexing provides better cost-effectiveness.
   CPU Architecture	This parameter is automatically set to the CPU Architecture of the original cluster. You do not need to select a value.
   Node Specifications	Select the node specifications. Different specifications provide different maximum storage capacities and performance levels. For more information, see Product specifications or . Note To ensure that the restored cluster runs properly, we recommend that you select node specifications that are higher than those of the source cluster.
   Number of Nodes	The default value is 2. Note A new cluster has one primary node and one secondary node by default. After the cluster is created, you can add up to 15 secondary nodes. For more information about how to add or remove nodes, see Add or remove nodes or .
   Database Proxy Type	This parameter is fixed to Dedicated Enterprise Edition. You do not need to select it.
   Enable Hot Standby Cluster	Select whether to enable the hot standby cluster. If you enable the hot standby storage cluster, PolarDB deploys a primary cluster (including compute nodes and primary storage) and a hot standby storage cluster in the current region. The primary cluster and the hot standby storage cluster each have three data replicas, for a total of six replicas. This provides a higher SLA guarantee. If you disable the hot standby storage cluster, only the primary cluster (with three data replicas) is retained. The unit price for storage is half of the price with the feature enabled, but the cluster's SLA is lower.
   Storage Type	PolarDB Enterprise Edition supports two storage types: PSL5 and PSL4: PSL5: A storage type supported in previous versions of PolarDB. It offers high performance, reliability, and availability. PSL4: A new storage type for PolarDB. It uses smart-SSD technology developed by Alibaba Cloud to compress and decompress data at the physical SSD level. This technology lowers the storage price per unit of data while keeping the performance impact manageable. Note You cannot change the storage type of an existing cluster. To change the storage type, purchase a new cluster with the desired storage type and migrate the data from the old cluster to the new one. For a detailed comparison of the two storage types, see or How to choose between PSL4 and PSL5. PolarDB Standard Edition supports the following five storage types: PL0 ESSD: An ESSD of performance level 0. PL1 ESSD: Compared to a PL0 ESSD, a PL1 ESSD provides 5 times the IOPS and about 2 times the throughput. PL2 ESSD: Compared to a PL1 ESSD, a PL2 ESSD provides about 2 times the IOPS and throughput. PL3 ESSD: Compared to a PL2 ESSD, a PL3 ESSD provides up to 10 times the IOPS and 5 times the throughput. It is suitable for business scenarios that require extremely high concurrent I/O performance and stable read/write latency. ESSD AutoPL disk: Unlike PL0, PL1, PL2, and PL3 ESSDs, an ESSD AutoPL disk decouples IOPS from capacity. You can flexibly configure and adjust IOPS as needed to reduce the total cost of ownership (TCO). For more information about the performance of ESSDs, see ESSD cloud disks. Important When the storage space of a cloud disk is full, the disk is locked and becomes read-only.
   Storage Billing Type	PolarDB supports two storage billing types: Pay-by-capacity (Pay-as-you-go) and Pay-by-space (Subscription): Pay-by-capacity (Pay-as-you-go): This is a serverless method. You do not need to select a capacity when you purchase the cluster. The storage automatically scales out online as your data grows. You are charged only for the storage space that your data occupies. Pay-by-space (Subscription): You must prepay for the storage space of the cluster when you purchase it. For more information about the two storage billing types, see Storage billing methods or . Note If Product Type is set to Subscription, you can set Storage Billing Type to Pay-by-capacity (Pay-as-you-go) or Pay-by-space (Subscription). If Product Type is set to Pay-as-you-go, this parameter is not available. The storage is billed by Pay-by-capacity (Pay-as-you-go) by default.
   Storage Fee	When Storage Billing Type is set to Pay-by-capacity (Pay-as-you-go), you do not need to select a capacity. PolarDB charges you hourly based on your actual usage.
   Storage Space	The amount of storage space to pre-purchase for the pay-by-space (subscription) billing type. The storage space for PolarDB Enterprise Edition ranges from 50 GB to 500 TB. The minimum adjustment increment is 10 GB. Note This parameter is available only when Product Type is set to Subscription and Storage Billing Type is set to Pay-by-space (Subscription).
   Cluster Name	Enter a cluster name. The name must meet the following requirements: It must be 2 to 128 characters in length. It must start with a letter or a Chinese character. It can contain digits, periods (.), underscores (_), and hyphens (-). If you leave this parameter empty, the system automatically generates a cluster name. You can change the name after the cluster is created.
   Subscription Duration	Select the subscription duration for the cluster. Note This parameter is available only when Billing Method is set to Subscription.
   Quantity	Select the quantity of clusters to purchase.

6. Complete the payment based on the selected Product Type.

   • Pay-as-you-go

     Click Buy Now. By clicking this button, you acknowledge that you have read and agree to the Terms of Service and the specific terms for the products you have selected on this page, if any.

   • Subscription

     1. Click Buy Now. By clicking this button, you acknowledge that you have read and agree to the Terms of Service and the specific terms for the products you have selected on this page, if any.

     2. On the Payment page, confirm the order information and payment method, and then click Pay.

   Note

   • After you complete the purchase, the cluster creation process takes 10 to 15 minutes. You can then find the new cluster in the Clusters list.

   • The total time for a point-in-time restore is the sum of the time required to restore from the backup set (snapshot) and the time required to apply physical logs. If a long time has passed since the last backup set was created and the write payload was high, applying the physical logs may take longer. For more information, see Redo log backup or .

Related API operations