PolarDB:Clone a cluster

Prerequisites

Before you begin, ensure that you have:

• A virtual private cloud (VPC) and a vSwitch in the region where you want to deploy the new cluster

Steps

1. Log on to the PolarDB console. In the left-side navigation pane, click Clusters. In the upper-left corner, select the region of the source cluster, and then find the cluster in the list.

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

3. Configure the parameters for the new cluster.

   If you select ESSD AutoPL, you can configure Provisioned IOPS for AutoPL disks to increase IOPS beyond the initial maximum of 50,000. The configurable maximum is an additional 50,000, bringing the theoretical maximum to 100,000 IOPS.

   Billing

   Parameter	Description
   Product type	Billing method for the new cluster. Select Subscription (pay upfront for a fixed period) or Pay-as-you-go (charged hourly based on actual usage).
   Purchase planSubscribe	Subscription duration. Available only when Product type is set to Subscription.
   Number	Number of clusters to create. Valid values: 1–50. Default: 1.

   Infrastructure

   Parameter	Description
   Clone source type	Source of the clone. Defaults to Current Cluster. Keep the default.
   Region	Region where the new cluster is deployed. Defaults to the same region as the source cluster. Keep the default.
   Primary zone	Availability zone within the region. You can place the new cluster in the same zone as your Elastic Compute Service (ECS) instance or in a different zone.
   Network type	Only VPC is supported. Keep the default.
   VPC / vSwitch	Select the VPC and vSwitch for the new cluster. Make sure the cluster and your ECS instance are in the same VPC so they can communicate over the internal network. If you don't have a VPC, create one on the VPCs page.

   Cluster configuration

   Parameter	Description
   Compatibility	MySQL version. Defaults to the same version as the source cluster.
   Edition	Cluster edition. Defaults to the same edition as the source cluster.
   Node specification	Compute specification for each node. Affects maximum storage capacity and performance. For available specifications, see Compute node specifications of PolarDB for MySQL Enterprise Edition.
   Nodes	Number of nodes. For Cluster Edition (Recommended) clusters, the default is one primary node and one read-only node. You can select one primary node plus one read-only node, or one primary node only. For Multi-master Cluster (Limitless) clusters, two primary nodes are created by default.
   PolarProxy type	Proxy type for the new cluster. Standard Enterprise Edition (shared CPU, elastic scaling, available for General-purpose clusters) or Dedicated Enterprise Edition (dedicated CPU, better stability, available for Dedicated clusters). PolarProxy Enterprise Edition is currently free of charge but may be charged in the future.
   Enable hot standby cluster	Deploys a hot standby storage cluster in a secondary zone or a different data center. When the primary zone fails, the hot standby cluster takes over read and write operations. For details, see High availability modes (hot standby clusters). Note You cannot change 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) after creation. To make this change, create a new cluster with the target mode and migrate data using Data Transmission Service (DTS). The Three Zones mode can only be selected at creation and cannot be changed to other modes or vice versa later.
   Cluster name	Name for the new cluster. Must be 2–256 characters and cannot start with http:// or https://. If left blank, a name is generated automatically.

   Storage

   Parameter	Description
   Storage type	Select a storage type compatible with the source cluster. If the source cluster uses ESSD, only ESSD is available. If the source cluster uses PSL4 or PSL5, you can select either. See the storage type reference below.
   Storage engine	InnoDB (InnoDB only) or InnoDB & X-Engine (both engines). If you select InnoDB & X-Engine, specify the X-Engine memory usage ratio. For details, see X-Engine Edition.
   Storage billing method	Pay-as-you-go (serverless, auto-scales with data volume, charged by actual usage) or Subscription (purchase a fixed storage capacity upfront). If Product type is Pay-as-you-go, storage billing is fixed at Pay-as-you-go.
   Storage capacity	Amount of storage to purchase. Ranges from 50 GB to 500 TB in 10 GB increments. Available only when Storage billing method is Subscription.
   Storage cost	Display-only field showing estimated storage cost. You do not need to change this value. You are charged on an hourly basis based on actual storage usage.
   Enable binary logging	Enables binary logging for the new cluster. For details, see Enable binary logging.

   Storage type reference

   Storage type	Description	Best for
   ESSD	Enterprise SSD with up to 1 million random read/write input/output operations per second (IOPS). Available at PL0, PL1, PL2, and PL3 performance levels, plus ESSD AutoPL (which decouples IOPS from capacity and reduces total cost of ownership (TCO)).	High-performance workloads requiring low latency.
   PSL5	Default storage type for clusters purchased before June 7, 2022. High performance, reliability, and availability.	Finance, e-commerce, and large-scale internet services.
   PSL4	Uses Smart-SSD technology to compress and decompress data at the SSD level, reducing storage costs.	Cost-sensitive workloads.

4. Read and accept the Terms of Service, then complete the purchase based on your billing method:

   • Pay-as-you-go: Click Buy Now.

   • Subscription: Click Buy Now, confirm the order and payment method on the Purchase page, then click Subscribe.

Result

The cluster is created within 1–5 minutes. Once it appears on the Clusters page with a Running status, it is ready to use. If the cluster is no longer needed, delete it to avoid ongoing charges.