Clone a cluster

Usage notes

The cloning feature works differently for PolarDB Enterprise Edition and Standard Edition.

Procedure

1. Log on to the PolarDB console.

2. In the navigation pane on the left, click Clusters.

3. In the upper-left corner, select the region where the cluster is deployed.

4. Find the target cluster. In the Actions column, click More > Clone Data to New Cluster.

5. On the configuration page, set the following parameters.

   Parameter	Description
   Product type	The billing method for the cluster. You can select Subscription or Pay-As-You-Go. Subscription: You prepay for compute nodes when you create the cluster. Storage space is billed hourly based on actual usage. Pay-As-You-Go: You are billed hourly for both compute nodes and storage space based on actual usage. No upfront payment is required.
   Operation type	By default, Clone to New Cluster is selected. You do not need to change this setting.
   Region	The region where the new cluster is created. By default, the cloned cluster is created in the same region as the source cluster. For example, if the source cluster is in the China (Hangzhou) region, the cloned cluster is also created in China (Hangzhou). This setting cannot be changed.
   Primary Zone	A zone is a distinct physical location within a region. There are no functional differences between zones in the same region. You can create your PolarDB cluster and ECS instances in the same or different zones.
   Network Type	Only 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 or vSwitch, you must create a new VPC and vSwitch first. Note For optimal performance, ensure that the PolarDB cluster and the ECS instances that you want to connect to are in the same VPC. Otherwise, they cannot communicate over the internal network.
   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 Oracle syntax compatible 2.0, the Compatibility of the cloned cluster is also PostgreSQL 14 Oracle syntax compatible 2.0. This setting cannot be changed.
   Service Edition	By default, the new cluster has the same Service Edition as the source cluster. You do not need to change this setting.
   Edition	By default, the cloned cluster has the same edition as the source cluster. For example, if the Edition of the source cluster is Cluster Edition [Recommended], the Edition of the cloned cluster is also Cluster Edition [Recommended]. This setting cannot be changed.
   Specification Edition	Select the Specification Edition for the cluster. You can choose between General-purpose and Dedicated. dedicated specification: Each cluster has exclusive access to 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 specification: Clusters on the same server share idle compute resources, such as CPU, to improve resource utilization and cost-effectiveness.
   CPU Architecture	By default, the new cluster has the same CPU Architecture as the source cluster. You do not need to change this setting.
   Node Specifications	Select the Node Specifications. Different specifications offer different performance levels and maximum storage capacities. For more information, see Compute node specifications for Enterprise Edition or Compute node specifications for Standard EditionCompute node specifications.
   Nodes	The default value is 2. Note A new cluster is created with one primary node and one read-only node by default. You can add up to 15 read-only nodes after the cluster is created. For more information, see Add or remove nodesAdd or remove nodes.
   PolarProxy type	The default value is Dedicated Enterprise.
   Enable hot standby storage cluster	Choose whether to enable this feature. If you enable this feature, PolarDB deploys a primary cluster (which includes mutually backed-up compute nodes and primary storage) and a hot standby storage cluster in the current region. Each cluster maintains three data replicas (for a total of six), providing a higher Service Level Agreement (SLA). If you disable this feature, 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 the PSL5 and PSL4 storage types: PSL5: The original storage type for PolarDB, delivering high performance, reliability, and availability. PSL4: A new storage type for PolarDB that uses Alibaba Cloud's proprietary Smart-SSDSmart-SSD technology. This technology compresses and decompresses data at the physical SSD level, which lowers storage costs with minimal impact on performance. Note You cannot change the storage type of an existing cluster. To switch storage types, purchase a new cluster with the desired storage type and then migrate data from the original cluster to the new cluster. For a detailed comparison of the two storage types, see Choose between PSL4 and PSL5Choose between PSL4 and PSL5. PolarDB Standard Edition supports the following five Storage Type: ESSD PL0: an ESSD that provides PL0 performance. ESSD PL1: Compared with PL0, ESSD PL1 delivers 5 times the IOPS and approximately 2 times the throughput. ESSD PL2: Compared with PL1, ESSD PL2 delivers approximately 2 times the IOPS and throughput. ESSD PL3: Compared with PL2, ESSD PL3 delivers 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, low read/write latency. ESSD AutoPL: Decouples IOPS from storage capacity, which allows you to flexibly configure and adjust performance as needed to reduce the total cost of ownership (TCO). For more information about ESSD performance, see ESSDs. Important If an ESSD runs out of storage space, it becomes locked and read-only.
   Storage Billing Method	PolarDB supports two storage billing methods: pay-as-you-go and Subscription. pay-as-you-go: This elastic option automatically scales storage capacity as your data grows. You are billed only for the storage space you use. Subscription: You must prepay for a fixed storage capacity when you purchase the cluster. For more information about these billing methods, see Storage billing methodsStorage billing methods. Note If Product type is set to Subscription, you can set Storage Billing Method to pay-as-you-go or Subscription. If Product type is set to Pay-As-You-Go, the pay-as-you-go storage billing method is used by default.
   Storage Fee	If you select the pay-as-you-go storage billing method, you do not need to specify a storage capacity. PolarDB bills you hourly based on your actual storage usage. You can also purchase a storage plan to reduce costs. For more information, see Purchase a storage planPurchase a storage plan.
   Storage Capacity	The storage capacity to purchase for a subscription. The storage capacity of a PolarDB Enterprise Edition cluster ranges from 50 GB to 500 TB and can be adjusted in 10 GB increments. Note This parameter is available only when Product type is Subscription and Storage Billing Method is Subscription.
   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 blank, the system automatically generates a name. You can change the name after the cluster is created.
   Subscription Duration	This parameter is available only if the Product type of the source cluster is Subscription.
   Quantity	The number of clusters to create. The value can range from 1 to 50. The default is 1.

6. Read and agree to the Terms of Service, and then click Buy Now.

   • Pay-As-You-Go

     Click Buy Now to complete the purchase.

   • Subscription

     1. Click Buy Now.

     2. On the Unpaid Orders page, confirm the order details and payment method, and then click Subscribe.

   Note

   After the payment is complete, it takes 1 to 5 minutes to create the cluster. You can then view the newly cloned cluster on the Clusters page.