PolarDB:Method 2 for full restoration: Restore data to an earlier point in time

Usage notes

• The restored cluster contains the data and account information of the source cluster. It does not contain the parameter settings of the source cluster.

• The time range available for data restoration depends on the Log Retention Period (Days) period specified in the backup settings. The default period is 7 days.

Procedure

1. Log on to the PolarDB console. In the navigation pane on the left, click Clusters. Select the Region where the cluster is deployed and 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 specific point in time.

   • To restore data within the same region:

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

   • To restore data to a different region:

     1. On the Backup and Restoration page, select the region that contains the backup data.

     2. Click Point-in-time Restoration.

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

   • Subscription: You pay for computing resources in advance when you create the database cluster.

   • Pay-as-you-go: You do not need to pay for computing resources in advance when you create a database cluster. You are charged for the computing resources that you use.

   • Serverless: The fees include compute node fees, storage capacity fees, backup storage fees (charged only when the free quota is exceeded), and SQL Explorer fees (optional). For more information about billing, see Serverless billing.

5. Set the following parameters.

   Parameter	Description
   Clone 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 data to the source region and the destination region. If cross-region backup is not enabled, the destination region is the same as the source cluster's region by default and does not need to be selected.
   Point in Time	Select the point in time to which you want to restore data. Note The range of time points to which you can restore data depends on the Log Retention Period (Days) period specified in the backup settings. The default period is 7 days.
   Primary Zone	Select the primary zone for the cluster. Note In regions that have two or more zones, PolarDB automatically replicates data to the secondary zone for disaster recovery.
   Minimum Number of Read-only Nodes	Minimum Read-only Nodes: Set the minimum number of read-only nodes that can be added. Valid values: 0 to 15. Maximum Read-only Nodes: Set the maximum number of read-only nodes that can be added. Valid values: 0 to 15. Note The number of read-only nodes automatically increases or decreases within the specified range based on the workload. For more information about the scaling policy, see Auto scaling. To ensure high availability for the serverless cluster, set Minimum Read-only Nodes to 1. Minimum PCUs Per Node: Set the minimum number of PCUs per node in the cluster. Valid values: 0.25 PCU to 31 PCU. Maximum PCUs Per Node: Set the maximum number of PCUs per node in the cluster. Valid values: 1 PCU to 32 PCU. Note Serverless uses PCUs for second-level billing and resource scaling. One PCU is equal to the service capability of about 1 core and 2 GB of memory. The PCUs of a node are dynamically adjusted within the specified range based on the workload. The minimum scaling unit is 0.5 PCU. Example: If you set Minimum PCUs Per Node to 2 PCU and Maximum PCUs Per Node to 16 PCU, the default specification for nodes in the serverless cluster is 2 PCU (about 2 cores and 4 GB of memory). When the system detects an increased workload, it automatically increases the number of PCUs for the primary or read-only nodes. Based on the settings, the number of PCUs can be increased to a maximum of only 16 PCU (about 16 cores and 32 GB of memory). Note These parameters are available only when the product type is Serverless.
   Maximum Number of Read-only Nodes
   Minimum PCUs per Node
   Maximum PCUs per Node
   Network Type	This parameter is fixed to VPC. You do not need to configure this parameter.
   VPC Network	Select the VPC and vSwitch for the cluster. We recommend that you select the same VPC and vSwitch as the source cluster. Note Make sure 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 to achieve optimal performance.
   vSwitch
   Compatibility	This parameter is fixed to the compatibility version of the source cluster. You do not need to configure this parameter. For example, if the original cluster's compatibility is MySQL 8.0 (fully compatible with MySQL 8.0), this parameter is also fixed to MySQL 8.0.
   Minor Version	Select 8.0.1 or 8.0.2. Note This parameter is valid only if the Compatibility parameter is set to MySQL 8.0.
   Edition	This parameter is fixed to the edition of the source cluster. You do not need to configure this parameter. For example, if the source cluster is Cluster Edition, the edition of the new cluster is also fixed to Cluster Edition. For more information, see Enterprise Edition product series.
   Database Type	PolarDB for MySQL Cluster Edition supports two sub-editions: General Specification and Dedicated Specification. Dedicated: Each cluster exclusively uses its allocated computing resources, such as CPUs, without sharing them with other clusters on the same server. This provides better performance stability and reliability. General-purpose: Different clusters on the same server share idle computing resources, such as CPUs. This resource multiplexing improves cost-effectiveness. For a detailed comparison of the two types, see General-purpose and Dedicated specifications.
   CPU Architecture	This parameter is fixed to the CPU architecture of the source cluster. You do not need to configure this parameter.
   Node Specifications	Select the node specifications. Different specifications offer different maximum storage capacities and performance levels. For more information, see Enterprise Edition compute node specifications. Note To ensure the restored cluster runs properly, we recommend selecting node specifications that are the same as or higher than those of the source cluster.
   Number of Nodes	If your source cluster is Cluster Edition, the system displays two nodes by default (one read/write node and one read-only node). You can choose two nodes (one read/write node and one read-only node) or one node (a read/write node). If your source cluster is Multi-master Cluster (Limitless) Edition, the system creates two primary nodes with the same specifications by default. You do not need to configure this parameter.
   Database Proxy Type	PolarDB supports two database proxy types: Standard Enterprise Edition and Dedicated Enterprise Edition. Standard Enterprise Edition: This type is for clusters with General-purpose specifications. It shares physical CPU resources and provides intelligent, second-level resource scaling based on business workloads. Dedicated Enterprise Edition: This type is for clusters with Dedicated specifications. It exclusively uses physical CPU resources and offers better performance stability. Note PolarProxy Enterprise Edition is currently free of charge. The future billing date is yet to be determined.
   Enable No-activity Suspension	If you enable No-activity Suspension, you must set the Detection Period for No-activity Suspension. The detection period can range from 5 minutes to 24 hours. Note These parameters are available only when the product type is Serverless.
   Enable Hot Standby Cluster	PolarDB provides multiple high availability modes. After you enable the hot standby storage cluster feature for a PolarDB cluster, a hot standby storage cluster is created in the secondary zone of the region in which the PolarDB cluster resides or in a different data center in the same zone. The hot standby storage cluster has independent storage resources. Whether the hot standby storage cluster has independent compute resources varies based on the high availability mode. When the PolarDB cluster in the primary zone fails, the hot standby storage cluster immediately takes over and handles read and write operations and storage tasks. Note For more information about the hot standby storage cluster and related solutions, see High availability modes (hot standby clusters). Rules for changing high availability modes: You cannot directly change the high availability mode of a cluster from Double Zones (Hot Standby Storage Cluster Enabled) or Double Zones (Hot Standby Storage and Compute Clusters Enabled) to Single Zone (Hot Standby Storage Cluster Disabled). For such change of the high availability mode, we recommend that you purchase a new cluster and select the Single Zone (Hot Standby Storage Cluster Disabled) high availability mode for the cluster. Then, migrate the existing cluster to the new cluster by using Data Transmission Service (DTS). For information about how to migrate an existing cluster to a new cluster, see Migrate data between PolarDB for MySQL clusters. You can select the Three Zones high availability mode only when you purchase a new cluster. You cannot change the high availability mode of a cluster from Three Zones to other high availability modes and vice versa. You can manually change the high availability mode of a cluster from Single Zone (Hot Standby Storage Cluster Disabled) to a different high availability mode. For more information, see High availability modes (hot standby clusters).
   Three-zone Strong Consistency Deployment	Specifies whether to enable three-zone strong consistency deployment.
   Storage Class	This follows the storage class configuration of the source cluster. If the source cluster uses an enterprise SSD (ESSD), you can only select an ESSD. If the source cluster uses PSL4 or PSL5, you can select PSL4 or PSL5. ESSDs are ultra-high performance disks developed by Alibaba Cloud. ESSDs use a next-generation distributed block storage architecture and support 25 Gigabit Ethernet networks and Remote Direct Memory Access (RDMA). Each ESSD has low one-way latency and can deliver up to 1 million random read/write IOPS. ESSDs are divided into the following categories: PL0 ESSD: Basic performance level. PL1 ESSD: Delivers 5× higher IOPS and ~2× higher throughput than PL0. PL2 ESSD: Delivers ~2× higher IOPS and throughput than PL1. PL3 ESSD: Delivers up to 10× higher IOPS and 5× higher throughput than PL2, ideal for scenarios requiring extreme concurrent I/O performance and stable low read/write latency. ESSD AutoPL disk: Decouples IOPS from capacity, allowing flexible configuration and on-demand adjustments to reduce total cost of ownership (TCO). Important For ESSD performance details, see ESSD. When a disk's storage space is full, the disk is locked and becomes read-only. To avoid service disruption, you can enable automatic ESSD storage expansion. PSL4 and PSL5 are storage types designed by PolarDB for different scenarios. Differences are as follows: Storage class Features Scenarios PSL5 (PolarStore Level 5) A storage class supported in earlier versions of PolarDB. It is the default storage class for PolarDB clusters purchased before June 7, 2022. It provides better performance, reliability, and availability. Business scenarios that require high performance and reliability, where the database is a core system. Such scenarios include finance, e-commerce, government services, and medium-to-large Internet businesses. PSL4 (PolarStore Level 4) PolarDB launched this new storage class that uses Alibaba's proprietary smart-SSD technology. This technology compresses and decompresses data at the physical SSD disk layer. This lowers the storage price per unit of data while keeping the performance impact under control. Application scenarios that require cost reduction and high cost-effectiveness. Note Storage class conversion rules: Some product series support storage class upgrades, which means that PSL4 storage can be upgraded to PSL5 storage. Downgrading the storage class is not supported. You cannot downgrade PSL5 storage to PSL4 storage. To switch from PSL5 storage to PSL4 storage, you can purchase a new cluster and migrate the data from the original cluster to the new cluster using a migration tool such as DTS or the major version upgrade feature.
   Storage Engine	PolarDB supports two engine types: InnoDB and InnoDB & X-Engine. InnoDB: The InnoDB engine. InnoDB & X-Engine:: A hybrid deployment of InnoDB and X-Engine. After you select this option, you can set the proportion of the high-compression engine. For more information about the high-compression engine, see High-compression engine (X-Engine). Note This parameter is not supported for PolarDB for MySQL Standard Edition.
   Storage Billing Method	PolarDB supports two storage billing methods: Pay-as-you-go and Subscription. Pay-as-you-go: This is a serverless method. You do not need to select a capacity when you make a purchase. The storage automatically scales as your data grows, and you are charged only for the actual storage space used. For more information, see Pricing for pay-by-capacity (pay-as-you-go). Subscription: You must pay for the storage space of the database cluster in advance when you purchase it. For more information, see Pricing for pay-by-space (subscription). Note When Billing Method is Subscription, Storage Payment Method can be set to Pay-as-you-go or Subscription. When Billing Method is Pay-as-you-go, this parameter is not supported, and the system defaults to pay-as-you-go storage.
   Storage Capacity	The amount of storage capacity to pre-purchase for Subscription. The storage capacity ranges from 50 GB to 500 TB, with a minimum adjustment of 10 GB. Note This parameter is available only when Storage Payment Method is set to Subscription.
   Storage Fee	You do not need to select a capacity when you make a purchase. PolarDB charges you hourly based on actual usage.
   Enable Binlog	Specifies whether to enable binary logging. For more information about binary logging, see Enable binary logging.
   Cluster Name	Enter a name for the cluster. The name must meet the following requirements: It cannot start with http:// or https://. It must be 2 to 256 characters in length. If you leave this empty, the system automatically generates a cluster name. You can change the cluster name after the cluster is created.
   Inherit Tags from Source Cluster	Specifies whether to inherit tags from the source cluster.
   Duration	Select the subscription duration for the cluster. Note This parameter is available only when Billing Method is set to Subscription.
   Quantity	Select the number of clusters to purchase.

6. After you configure the parameters, confirm the cluster configuration and fee, read and accept the terms of service, and then click Buy Now.

7. After you complete the purchase, it takes 10 to 15 minutes for the system to create the cluster. The new cluster then appears in the cluster list on the PolarDB console.

   Note

   • If a node's status is Creating, the cluster is still being created and is unavailable. The cluster is ready for use only when its status changes to Running.

   • Make sure that you have selected the correct region in the upper-left corner of the page. Otherwise, you cannot view the created cluster.

Related API operations