PolarDB:Clone a cluster

Notes

PolarDB Enterprise Edition and Standard Edition differ in this feature.

Procedure

1. Log in to the PolarDB console，In the navigation pane on the left, click Clusters. Select the Region where the cluster is deployed, and then click the cluster ID to go to the cluster details page。

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

3. Set the following parameters on the configuration page:

   Parameter	Description
   Product type	You can select Subscription or Pay-As-You-Go. Subscription: When you create a database cluster, you must pay upfront for its compute services. Pay-As-You-Go: When you create a database cluster, you do not pay upfront for compute services. Charges are deducted only when you use the database compute services.
   Clone source type	By default, Clone Source Cluster is selected. No changes are required.
   Region	This is the geographical location of the cloned cluster. The cloned cluster and source cluster are in the same region by default. For example, if the source cluster is in China (Hangzhou), the cloned cluster is also in China (Hangzhou), and no selection is required.
   Primary Zone	An availability zone is an independent physical area within a region. There is no material difference between availability zones. You can deploy PolarDB and ECS in the same availability zone or in different availability zones.
   Network Type	Only VPC (Virtual Private Cloud) is supported. No selection is required.
   VPC VPC and vSwitch	Select a VPC and vSwitch from the drop-down lists. If you do not have a VPC, create a new VPC and vSwitch first. Note Make sure that PolarDB 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.
   Compatibility	The cloned cluster has the same compatibility as the source cluster by default. For example, if the source cluster's Compatibility is MySQL 8.0, the cloned cluster's Compatibility is also MySQL 8.0, and no selection is required.
   Edition	The cloned cluster has the same edition as the source cluster by default. For example, if the source cluster's Edition is Cluster Edition (2-16 nodes) (Recommended), the cloned cluster's Edition is also Cluster Edition (2-16 nodes) (Recommended), and no selection is required.
   Node Specifications	Select Node Specifications. Different specifications have different maximum storage capacities and performance. For more information, see Compute node specifications for Enterprise Edition.
   Nodes	If the source cluster series is Cluster Edition (Recommended), the system displays two nodes by default: one primary node and one read-only node. You can select two nodes (one primary node and one read-only node) or one node (a primary node). If the source cluster series is Multi-master Cluster (Limitless) Edition, the system creates two primary nodes with the same specifications by default. No selection is required.
   Database proxy type	PolarDB supports two database 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, second-level elastic resource scaling based on workload. 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 available free of charge. The start date for billing has not been 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).
   Storage Type	The configuration follows the storage type of the source cluster. If the source cluster uses an ESSD cloud disk, only an ESSD cloud disk can be selected. If the source cluster uses PSL4 or PSL5, you can select 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 workloads that require extremely high concurrent I/O performance and extremely stable read/write latency. AutoPL ESSD: Compared with PL0, PL1, PL2, and PL3 ESSDs, AutoPL ESSDs decouple IOPS from capacity, which allows flexible configuration and on-demand adjustment. This reduces the overall total cost of ownership (TCO). Important For more information about the performance of ESSD cloud disks, see ESSDs. After the storage space of an ESSD cloud disk is full, the disk is locked and 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: InnoDB engine. InnoDB & X-Engine: A hybrid deployment engine of InnoDB and X-Engine. After you select this option, you can set the ratio for the high-compression engine. For more information about the high-compression engine, see 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): Pay-by-capacity uses a serverless model. You do not need to select a capacity when purchasing a cluster. Storage capacity automatically scales online as data grows, and you are charged only for the actual storage space used. For more information, see Pay-as-you-go. Subscription: Subscription storage billing requires you to pay upfront for the cluster's storage capacity when you purchase a database cluster. For more information, see Subscription. Note When Billing Method is Subscription, Storage Billing Method supports Pay-by-capacity (Pay-as-you-go) or Subscription. When Billing Method is Pay-As-You-Go, this configuration is not supported, and storage is billed by capacity by default.
   Storage Capacity	Subscription: The amount of storage capacity that must be purchased in advance. The storage capacity ranges from 50 GB to 500 TB, and the minimum adjustment increment is 10 GB. Note This configuration is supported only when Storage Billing Method is Subscription.
   Storage Fee	No selection is required. The system charges by the hour based on actual data usage. For more information, see Billable items. Note You do not need to select a storage capacity when you create the cluster. Storage capacity automatically scales as the data volume increases or decreases.
   Enable binary logging	Select Enable binary logging. For more information about binary logging, see Enable binary logging.
   Cluster Name	Enter a cluster name. The cluster 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 it after the cluster is created.
   Subscription Duration	This parameter is supported only when the source cluster's Product type is Subscription.
   Quantity	Valid values range from 1 to 50. The default value is 1.

4. Read and select the service agreement, and 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 Payment page, confirm the unpaid order information and payment method, and then click Pay.

   Note

   After the order is placed, it takes 1 to 10 minutes to activate the service. You can then find the new cloned cluster in Clusters.