PolarDB:Restore from a backup set

Usage notes

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

Procedure

1. Log in to the PolarDB console. In the navigation pane, click Clusters. Select the region where the cluster is located, and then click the cluster ID.

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

3. Restore data to a new cluster.

   • To restore data in the same region:

     Find the target backup set and click Restore Data to New Cluster in the Actions column.

   • To restore data to a different region:

     1. On the Backup and Restoration page, select the region where the target backup set is located.

     2. Find the target backup set and click Restore Data to New Cluster in the Actions column.

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

   • Subscription: You prepay for compute resources for a specific period.

   • pay-as-you-go: You are charged for the compute resources you use, with no upfront payment.

   • Serverless: You are billed for compute nodes, storage capacity, backup storage (only for usage exceeding the free quota), and SQL Insights (optional). For more information, see Serverless billing.

5. Configure the following parameters.

   Parameter	Description
   Cloned By	Select Restore from Backup Set.
   Region	Select the destination region. Note If cross-region backup is enabled, you can restore data to the source or destination region. If cross-region backup is disabled, the new cluster is created in the same region as the source cluster by default.
   Backup Set	Select the backup set that you want to restore. Note The Backup Start Time for each backup set is displayed. You can use this time to identify the backup set.
   Primary Zone	Select the primary zone for the new cluster. Note In a region with two or more zones, PolarDB automatically replicates data to a secondary zone for disaster recovery.
   Minimum Read-only Nodes	Minimum Read-only Nodes: The minimum number of read-only nodes. Valid values: 0 to 15. Maximum Read-only Nodes: The maximum number of read-only nodes. Valid values: 0 to 15. Note The number of read-only nodes automatically scales up or down within the specified range based on the workload. For more information about the scaling policy, see Auto scaling. To ensure high availability for your serverless cluster, we recommend setting Minimum Read-only Nodes to 1. Minimum PCUs per Node: The minimum number of PCUs for each node in the cluster. Valid values: 0.25 to 31 PCUs. Maximum PCUs per Node: The maximum number of PCUs for each node in the cluster. Valid values: 1 to 32 PCUs. Note Serverless uses PCUs as the unit for per-second billing and resource scaling. One PCU is equivalent to approximately 1 vCPU core and 2 GB of memory. The PCUs of a node dynamically scale within the specified range, with a minimum scaling step of 0.5 PCU. Example: If you set Minimum PCUs per Node to 2 and Maximum PCUs per Node to 16, the default specification for each node in the serverless cluster is 2 PCUs (about 2 vCPU cores and 4 GB of memory). When the system detects an increase in workload, it automatically scales up the PCUs of the primary node or read-only nodes. However, the number of PCUs cannot exceed 16. Note These parameters are available only when the billing method is Serverless.
   Maximum Read-only Nodes
   Minimum PCUs per Node
   Maximum PCUs per Node
   Network Type	This is fixed to VPC. No selection is required.
   VPC	Select the VPC and vSwitch for the cluster. We recommend using the same VPC and vSwitch as the source cluster. Note To ensure optimal performance, make sure the PolarDB cluster and any connecting ECS instances are in the same VPC. Otherwise, they cannot communicate over the internal network.
   vSwitch
   Compatibility	The new cluster inherits the compatibility of the source cluster by default. No selection is required. For example, if the source cluster is compatible with MySQL 8.0, this value is also fixed to MySQL 8.0.
   Minor Version	Select 8.0.1 or 8.0.2. Note This parameter is available only when Compatibility is set to MySQL 8.0.
   Edition	The new cluster inherits the edition of the source cluster by default. No selection is required. 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 editions.
   Database Type	PolarDB for MySQL Cluster Edition supports two specification types: General Specification and Dedicated Specification. Dedicated: Each cluster exclusively uses its allocated compute resources, such as CPUs, without sharing them with other clusters on the same server. This ensures more stable and reliable performance. General-purpose: Different clusters on the same server share idle compute resources to maximize utilization and cost-effectiveness. For a detailed comparison of the two types, see Comparison between general-purpose and dedicated compute nodes.
   CPU Architecture	The new cluster inherits the CPU architecture of the source cluster by default. No selection is required.
   Node Specifications	Select the Node Specifications. Different specifications offer different maximum storage capacities and performance levels. For more information, see Compute node specifications for Enterprise Edition. Note To ensure the restored cluster runs properly, we recommend selecting a Node Specifications equal to or higher than that of the source cluster.
   Nodes	If the source cluster is Cluster Edition, the system defaults to two nodes (one read-write and one read-only). You can choose to create two nodes (one read-write and one read-only) or one node (read-write only). If the source cluster is Multi-master Cluster (Limitless) Edition, the system automatically creates two primary nodes with identical specifications. No selection is required.
   PolarProxy type	PolarDB supports two PolarProxy types: Standard Enterprise Edition and Dedicated Enterprise Edition. Standard Enterprise Edition: Paired with the General-purpose specification type. It shares physical CPU resources and provides intelligent, per-second resource scaling based on the workload. Dedicated Enterprise Edition: Paired with the Dedicated specification type. It uses dedicated physical CPU resources for better performance stability. Note The Enterprise Edition of PolarProxy is currently free of charge. Future billing policies are to be determined.
   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 Migration 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).
   Cross-zone strong consistency	Specifies whether to enable strong consistency deployment across three zones.
   Storage Type	This setting is determined by the storage type of the source cluster. If the source cluster uses ESSD, you can only select ESSD. If the source cluster uses PSL4 or PSL5, you can select either PSL4 or PSL5. ESSD cloud disks are a new generation of ultra-high-performance disk products from Alibaba Cloud. ESSDs are built on a new-generation distributed block storage architecture, combined with 25 GE networks and RDMA technology, providing up to 1 million random read/write IOPS and lower one-way latency per disk. ESSDs are divided into the following categories: PL0 ESSD: A performance level (PL) 0 ESSD. PL1 ESSD: A PL1 ESSD delivers five times the IOPS and approximately twice the throughput of a PL0 ESSD. PL2 ESSD: A PL2 ESSD delivers approximately twice the IOPS and throughput of a PL1 ESSD. PL3 ESSD: A PL3 ESSD delivers up to 10 times the IOPS and 5 times the throughput of a PL2 ESSD. It is suitable for business scenarios that require extremely high concurrent I/O performance and stable, low read/write latency. AutoPL ESSD: Compared to PL0, PL1, PL2, and PL3 ESSDs, AutoPL ESSDs decouple IOPS from capacity, allowing for flexible configuration and on-demand adjustments. This reduces the overall Total Cost of Ownership (TCO). Important For more information about the performance of ESSD cloud disks, see ESSD cloud disks. When an ESSD cloud disk's storage space is full, it becomes read-only. To avoid business disruptions, you can enable automatic storage scaling for ESSD cloud disks. PSL4 and PSL5 are storage types that PolarDB provides for different business scenarios. The differences are as follows: Storage type Features Use cases PSL5 (PolarStore Level 5) This storage class was used in earlier versions of PolarDB and is the default for clusters purchased before June 7, 2022. It offers higher performance, reliability, and availability. Business-critical workloads that require high performance and reliability, such as finance, e-commerce, government services, and medium-to-large internet businesses. PSL4 (PolarStore Level 4) A new PolarDB storage class that uses Alibaba's proprietary smart-SSD technology. This technology compresses and decompresses data at the physical SSD layer, which reduces storage costs with a manageable performance impact. Cost-sensitive applications that prioritize high cost-effectiveness. Note Storage class conversion rules: Some product series support upgrading the storage class from PSL4 to PSL5. Downgrading the storage class is not supported. You cannot downgrade PSL5 storage to PSL4 storage. To switch from PSL5 storage to PSL4 storage, purchase a new cluster and migrate the data using either a migration tool like Data Transmission Service (DTS) or a major version upgrade.
   Storage Engine	PolarDB supports two engine types: InnoDB and InnoDB & X-Engine. InnoDB: Deploys only 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 X-Engine usage. For more information, see Introduction to X-Engine. Note This parameter is not supported by the Standard Edition of PolarDB for MySQL.
   Storage Billing Method	PolarDB supports two storage billing methods: Pay-as-you-go and Subscription. Pay-as-you-go: This serverless approach does not require you to select a storage capacity at the time of purchase. Storage automatically expands as data grows, and you are charged only for the actual storage space used. For more information, see Pricing for pay-as-you-go storage. Subscription: You must prepay for the cluster's storage space. For more information, see Pricing for subscription storage. Note If the main Billing Method is Subscription, the Storage Payment Method can be either Pay-as-you-go or Subscription. If the main Billing Method is Pay-as-you-go, this setting is not available, and storage is billed on a pay-as-you-go basis by default.
   Storage Capacity	The amount of storage capacity to pre-purchase for the Subscription method. The storage capacity ranges from 50 GB to 500 TB, in increments of 10 GB. Note This setting is available only when the Storage Payment Method is set to Subscription.
   Storage Fee	You do not need to select a capacity upfront. PolarDB bills you hourly based on actual usage.
   Enable binary logging	Specifies whether to enable binary logging. For more information, 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 field empty, the system automatically generates a cluster name. You can modify the 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 configuring the parameters, confirm the cluster configuration, check the cost, and read the terms of service. Then, click Buy Now.

7. After completing the purchase, it takes 10 to 15 minutes to create the cluster. You can then view the new cluster on the Clusters page of the PolarDB console.

   Note

   • When the status of nodes in the cluster is Creating, the cluster is not ready for use. The cluster is ready for use only when its status changes to Running.

   • Make sure you have selected the correct region in the upper-left corner of the console. Otherwise, you may not be able to find your cluster.

API reference