PolarDB:Clone a cluster

Limitations

The clone feature behaves differently for PolarDB Enterprise Edition and Standard Edition.

Procedure

1. Log on to the PolarDB console. In the upper-left corner, select the region where your cluster is located. In the left-side navigation pane, click Clusters.

2. In the Actions column, click More > Clone Data to New Cluster.

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

   Parameter	Description
   Product type	You can select Subscription or Pay-As-You-Go. Subscription: You prepay for the compute resources when you create the cluster. Pay-As-You-Go: You are charged for the compute resources that you use without making an upfront payment.
   Clone source type	Defaults to Source Cluster. You do not need to change this setting.
   Region	The region where the cloned cluster is created. This is automatically set to the same region as the source cluster and cannot be changed.China (Hangzhou)China (Hangzhou)
   Primary Zone	An availability zone is a distinct physical location within a region. All availability zones in the same region are interconnected with low-latency networks. You can create the PolarDB cluster and your ECS instance in the same or different availability zones.
   Network Type	Only VPC is supported. You do not need to change this setting.
   VPC vSwitch	Select a VPC and vSwitch from the drop-down lists. If you do not have a VPC, create a VPC and a vSwitch first. Note Make sure that your 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.
   Compatibility	By default, the cloned cluster has the same compatibility as the source cluster. For example, if the Compatibility of the source cluster is MySQL 8.0, , or , the Compatibility of the cloned cluster is also MySQL 8.0, , or , respectively. 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 (2-16 nodes) (Recommended), the Edition of the cloned cluster is also Cluster Edition (2-16 nodes) (Recommended). You do not need to change this setting.
   Node Specifications	Select a Node Specifications. Different specifications provide different maximum storage capacities and performance. For more information, see Compute node specifications of Enterprise Edition.
   Nodes	If your source cluster is of the Cluster Edition (Recommended), two nodes (one primary node and one read-only node) are displayed by default. You can select two nodes (one primary node and one read-only node) or one node (a primary node). If your source cluster is of the Multi-master Cluster (Limitless) Edition Edition, two primary nodes of the same specifications are created by default. You do not need to change this setting.
   PolarProxy type	PolarDB supports two proxy types: Standard Enterprise Edition and Dedicated Enterprise Edition. Standard Enterprise Edition: This proxy type is used with the General-purpose cluster specification. It shares physical CPU resources and provides intelligent resource scaling that responds to workload changes within seconds. Dedicated Enterprise Edition: This proxy type is used with the Dedicated cluster specification. It uses dedicated physical CPU resources for better performance stability. Note PolarProxy Enterprise Edition is currently free of charge. The billing start date will be announced later.
   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).
   Storage Type	This is automatically configured based on the source cluster's storage type. If the source cluster uses an ESSD, you can only select an 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 storage engine types: InnoDB and InnoDB & X-Engine. InnoDB: The InnoDB storage engine. InnoDB & X-Engine: A hybrid deployment of InnoDB and X-Engine. If you select this option, you can configure the X-Engine ratio. For more information, see X-Engine (high compression engine) overview.
   Storage Billing Method	PolarDB supports two storage billing methods: Pay-by-capacity (Pay-as-you-go) and Subscription. Pay-by-capacity (Pay-as-you-go): This method is serverless. You do not need to specify a storage capacity when you purchase a cluster. The storage capacity 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 storage. Subscription: You pay upfront for a fixed amount of storage when you purchase the cluster. For more information, see Pricing for pay-by-plan storage. Note If the Billing Method is Subscription, you can select Pay-by-capacity (Pay-as-you-go) or Subscription for the Storage Billing Method. If the Billing Method is Pay-As-You-Go, this setting is not available, and storage is billed by capacity by default.
   Storage Capacity	The storage capacity to pre-purchase for a Subscription cluster. Valid values range from 50 GB to 500 TB. The minimum adjustment increment is 10 GB. Note This setting is available only when the Storage Billing Method is Subscription.
   Storage Fee	No configuration is required. The system charges you hourly based on actual usage. For more information, see Billable Items Overview, , or . Note You do not need to select a storage capacity when you create the cluster. The storage capacity automatically scales with your data volume.
   Enable binlog	Select whether to enable binlog. For more information about binlog, 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 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 when the Product type of the source cluster is Subscription.
   Quantity	Valid values: 1 to 50. Default value: 1.

4. Read and select the terms of service, and then complete the purchase based on the cluster's billing method.

   • Pay-As-You-Go

     Click Buy Now.

   • Subscription

     1. Click Buy Now.

     2. On the Purchase page, confirm the order details and payment method, and then click Pay.

   Note

   After the order is placed, it takes 1 to 10 minutes to create the cluster. You can then find the new cluster on the Clusters page.