how to clone a new PolarDB cluster from a source PolarDB cluster - PolarDB

You can create a new PolarDB cluster by cloning the data from a source PolarDB cluster.

Usage notes

This feature varies between the PolarDB Enterprise Edition and Standard Edition.

PolarDB edition	Usage notes
PolarDB Enterprise Edition	The following data can be cloned: Source cluster account information. If transparent data encryption (TDE) is enabled for the source cluster before cloning, the TDE settings can also be cloned to the new cluster. The following data of the source cluster cannot be cloned: The parameter settings. The whitelist settings. The SSL settings. Only data that exists in the source cluster before the cloning starts can be cloned. Data written to the source cluster after the cloning starts is not cloned.
PolarDB Standard Edition	The following data of the source cluster can be cloned: Account information for the source cluster. The parameter settings. The whitelist settings. If TDE is enabled for the source cluster before cloning, the TDE settings can also be cloned to the new cluster. The following data cannot be cloned: Source cluster SSL configuration. Only data that exists in the source cluster before the cloning starts can be cloned. Data written to the source cluster after the cloning starts is not cloned.

Procedure

Log on to the PolarDB console.
In the navigation pane on the left, click Clusters.
In the upper-left corner, select the region where the cluster is deployed.
Find the target cluster, and in the Actions column, click More > Clone Data to New Cluster.

On the configuration page, set the following parameters:

Parameter	Description
Product Type	You can select Subscription or Pay-as-you-go. Subscription: Pay for compute nodes when you create the cluster. Storage is billed hourly based on actual data volume, and the fees are deducted from your account. Pay-as-you-go: No upfront payment is required. Compute nodes and storage space are billed hourly based on actual data volume, and the fees are deducted from your account.
Operation type	By default, Clone an independent cluster is selected. You do not need to change this setting.
Region	The region where the cloned cluster is located. By default, the cloned cluster and the source cluster are in the same region. For example, if the source cluster is in China (Hangzhou), the cloned cluster is also in China (Hangzhou). You do not need to select a region.
Primary zone	A zone is an independent physical area within a region. There are no significant differences between zones. You can create the PolarDB cluster and the ECS instance in the same zone or in different zones.
Network type	Only virtual private cloud (VPC) is supported. You do not need to change this setting.
VPC	Select a VPC and a vSwitch from the drop-down lists. If you do not have a VPC, create a VPC and a vSwitch. Note Make sure that the PolarDB cluster and the ECS instance that you want to connect are in the same VPC. Otherwise, they cannot communicate over the internal network for optimal performance.
vSwitch
Compatibility	By default, the cloned cluster has the same compatibility as the source cluster. For example, if the Compatibility of the source cluster is PostgreSQL 14, the Compatibility of the cloned cluster is also PostgreSQL 14. You do not need to change this setting.
Product version	By default, the product version is the same as that of the source cluster. You do not need to change this setting.
Series	By default, the series of the cloned cluster is the same as that of the source cluster. For example, if the Series of the source cluster is Cluster Edition (Recommended), the Series of the cloned cluster is also Cluster Edition (Recommended). You do not need to change this setting.
Sub-series	Select a sub-series for the cluster. General-purpose and Dedicated sub-series are supported. Dedicated: Each cluster exclusively uses its allocated compute resources, such as CPU, and does not share them with other clusters on the same server. This provides more stable and reliable performance. General-purpose: Different clusters on the same server share idle compute resources, such as CPU. This resource reuse improves cost-effectiveness.
CPU architecture	By default, the CPU architecture is the same as that of the source cluster. You do not need to change this setting.
Node specifications	Select the node specifications. Different specifications provide different maximum storage capacities and performance levels. For more information, see Compute node specifications for Enterprise Edition or Compute node specifications for Standard Edition.
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 more nodes, up to one primary node and 15 secondary nodes. For more information about how to add or remove nodes, see Add or remove nodes.
Database proxy type	The default value is Dedicated Enterprise Edition.
Enable hot standby storage cluster	Select whether to enable the hot standby storage cluster feature. If you enable this feature, PolarDB deploys a primary cluster (which contains cross-zone 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 Service-Level Agreement (SLA) and reliability. If you disable this feature, only the primary cluster with three data replicas is deployed. The unit price for storage is half of the price when this feature is 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 earlier versions of PolarDB. It provides good performance and high reliability and availability. PSL4: A new storage type for PolarDB. It uses the smart-SSD technology developed by Alibaba Cloud to compress and decompress data at the physical SSD level. This lowers the storage price per unit of data while maintaining controllable performance impact. 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 original cluster to the new cluster. For a detailed comparison of the two storage types, see How to choose between PSL4 and PSL5. PolarDB Standard Edition supports the following five storage types: PL0 ESSD: A performance level 0 (PL0) ESSD. 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 storage 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 ESSDs. Important When a disk is full, it becomes locked and read-only.
Storage billing method	PolarDB supports two storage billing methods: Pay-as-you-go (by capacity) and Subscription (by space). Pay-as-you-go (by capacity): This is a serverless method. You do not need to select a capacity when you purchase the cluster. The storage scales automatically as your data grows, and you are charged only for the storage space that you use. Subscription (by space): You must pre-pay for the storage space of the cluster when you purchase it. For more information about the two storage billing methods, see Storage billing methods. Note If you set Billing method to Subscription, you can select Pay-as-you-go (by capacity) or Subscription (by space) for Storage billing method. If you set Billing method to Pay-as-you-go, this parameter is not configurable. The system defaults to Pay-as-you-go (by capacity) for storage.
Storage fee	If the storage billing method is Pay-as-you-go (by capacity), you do not need to select a capacity. PolarDB bills you hourly based on actual usage.
Storage capacity	The amount of storage space to purchase for the subscription (by space) billing method. The storage capacity of a PolarDB Enterprise Edition cluster ranges from 50 GB to 500 TB. The minimum adjustment increment is 10 GB. Note This parameter is available only if you set Billing method to Subscription and Storage billing method to Subscription (by space).
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 blank, the system automatically generates a cluster name. You can change the name after the cluster is created.
Subscription duration	This parameter is available only if the Billing method of the source cluster is Subscription.
Quantity	The value can be from 1 to 50. The default value is 1.

Read and select the service agreement, and then click Buy Now.
- Pay-as-you-go
  Click Buy Now.
- Subscription
  1. Click Buy Now.
  2. On the Payment page, confirm the unpaid order information and payment method, and then click Purchase.
Note
After the purchase is successful, it takes 1 to 5 minutes for the service to be activated. You can then find the newly cloned cluster in the Clusters list.