All Products
Search

This Product

    PolarDB:Clone a cluster

    Document Center

    PolarDB:Clone a cluster

    Last Updated:Sep 25, 2023

    This topic describes how to create a new PolarDB for MySQL cluster by cloning the data of a source PolarDB for MySQL cluster.

    Precautions

    • The following data can be cloned:

      • Cluster account information.

      • The transparent data encryption (TDE) configurations can be cloned if the source cluster has TDE enabled.

    • The following data cannot be cloned:

      • Parameter settings.

      • The whitelist configurations of the source cluster.

      • Secure sockets layer (SSL) configurations.

    • Only the data that exists in the source cluster before the clone operation starts is cloned.

    Procedure

    1. Log on to the PolarDB console.
    2. In the upper-left corner of the console, select the region in which the cluster that you want to manage is deployed.

    3. Find the cluster that you want to clone and choose More > Clone Cluster in the Actions column.

    4. On the page that appears, specify the following parameters.

      Parameter

      Description

      Billing Method

      The billing method of the new cluster. Valid values: Subscription and Pay-as-you-go.

      • Subscription: When you create a cluster, you need to make a payment for the use of the cluster for a specific period of time.

      • Pay-as-you-go: When you create clusters, you do not need to make a payment first. You are charged for the computing and storage resources that you use.

      Clone Source Type

      The type of the clone source. The default value is Current Cluster. Use the default setting.

      Region

      The region where the new cluster is deployed. By default, the new cluster is deployed in the same region as that of the source cluster. For example, if the source cluster is deployed in the China (Hangzhou) region, the region of the new cluster is automatically set to China (Hangzhou). Keep the default setting.

      Primary Zone

      • A zone is an independent geographical location in a region. All of the zones in a region provide the same level of service performance.

      • You can choose to create your PolarDB for MySQL cluster in the same zone as an ECS instance or in a different zone from the zone of the instance.

      Network Type

      Only VPC is supported. Keep the default setting.

      VPC

      VSwitch

      Select a virtual private cloud (VPC) and a vSwitch from the drop-down lists. If you do not have a VPC, create a VPC and a vSwitch. To create a VPC and a vSwitch, visit the VPCs page.

      Note

      Make sure that the PolarDB for MySQL cluster is deployed in the same VPC as the ECS instance. Otherwise, the cluster and the ECS instance cannot communicate with each other over the internal network to provide optimal performance.

      Compatibility

      By default, the new cluster has the same compatibility as that of the source cluster. For example, if the compatibility of the source cluster is MySQL 8.0, , and , the compatibility of the new cluster is MySQL 8.0, , and . You do not need to change this parameter value.

      Edition

      By default, the edition of the new cluster is the same as that of the source cluster. For example, if the value of the Edition parameter for the source cluster is Cluster, the value of the Edition parameter for the new cluster is also Cluster. You do not need to select the value of this parameter.

      Node Specification

      Select a node specification. The maximum storage and performance of a cluster vary based on the node specification. For more information, see Compute node specifications of PolarDB for MySQL Enterprise Edition.

      Nodes

      • If your source cluster edition is Cluster Edition(Recommended) cluster, this parameter is set to one read-write node and one read-only node by default. You can select two nodes (a primary node and a read-only node) or one node (a primary node).

      • If your source cluster edition is Multi-master Cluster (Database/Table) Edition, the system automatically creates two primary nodes that have the same specifications. You do not need to configure this parameter.

      PolarProxy Type

      PolarDB for MySQL supports Standard Enterprise Edition and Dedicated Enterprise Edition.

      • Standard Enterprise Edition: If your cluster is a General-purpose cluster, you can select this database proxy type, which shares CPU resources with smart elastic scaling within seconds provided based on business loads.

      • Dedicated Enterprise Edition: If your cluster is Dedicated, you can select this database proxy type, which occupies all allocated CPU resources and provides better stability.

      Note

      PolarProxy Enterprise Edition is currently provided free-of-charge but may charge fees in the future.

      Enable Hot Standby Cluster

      • When this feature is enabled, the primary cluster and a hot-standby cluster for the primary PolarDB for MySQL cluster are deployed in the specified region. The primary cluster contains compute nodes that serve as standbys for each other, and primary storage. The two clusters each have three replicas, which adds up to six replicas. This delivers higher SLA than when this feature is disabled.

      • When this feature is disabled, only the primary cluster is deployed. The cluster has three replicas, and the storage unit price is half of that when this feature is enabled. This delivers lower SLA than when this feature is enabled.

      Storage Type

      PolarDB for MySQL supports the PSL5 and PSL4 storage types.

      • PSL5: the storage type supported by historical versions of PolarDB. This was the default storage type for PolarDB clusters purchased before June 7, 2022. It delivers higher performance, reliability, and availability.

      • PSL4: a new storage type for PolarDB for MySQL. PSL4 uses the Smart-SSD technology developed in-house by Alibaba Cloud to compress and decompress data at SSDs. This storage type can minimize the storage costs of data while maintaining a high disk performance.

        Note

        The storage types of existing clusters cannot be changed. To use PSL4, we recommend that you purchase a new cluster, set the storage type to PSL4, and then migrate data to the new cluster.

      Storage Engine

      PolarDB for MySQL supports InnoDB and InnoDB & X-Engine.

      • InnoDB: deploys only the InnoDB storage engine.

      • InnoDB & X-Engine:: deploys both InnoDB and X-Engine. After you select this option, set the ratio of X-Engine Memory Usage. For more information, see X-Engine Edition.

      Storage Billing Method

      PolarDB for MySQL supports the Pay-as-you-go and Subscription billing methods for the storage of your clusters.

      • Pay-as-you-go: The storage capacity is provided based on a serverless architecture. This way, you do not need to specify the storage capacity when you purchase clusters. The storage capacity of the clusters can be automatically scaled up as the volume of data increases. You are charged for the actual data volume. For more information, see Pay-as-you-go.

      • Subscription: You must purchase a specific amount of storage capacity when you create the cluster. For more information, see Subscription.

      Note

      If the Billing Method parameter is set to Subscription, you can select Pay-as-you-go or Subscription as the Storage Billing Method. If the Billing Method parameter is set to Pay-as-you-go, you cannot change the default value of this parameter, which is Pay-as-you-go.

      Storage Capacity

      The amount of storage capacity that you want to purchase for your cluster. The storage capacity ranges from 50 GB to 100 TB, in 10 GB increments.

      Note

      This parameter is available only when Storage Billing Method is set to Subscription.

      Storage Cost

      The storage cost. You do not need to change this parameter value. You are charged on an hourly basis based on the actual storage that you use. For more information, see Billable items overview .

      Note

      You do not need to specify the storage capacity when you create a cluster. The system scales the storage capacity when the amount of data is increased or decreased.

      Enable Binary Logging

      For more information about binary logging, see Enable binary logging.

      Cluster Name

      The name of 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 this parameter is left empty, the system automatically generates a cluster name. You can change the cluster name after the cluster is created.

      Purchase Plan

      This parameter is supported only when the value of the Billing Method parameter is Subscription.

      Number

      Valid values: 1 to 50. Default value: 1.

    5. Read and select the Terms of Service, and complete the rest of the steps based on the billing method of the cluster.

      • Pay-as-you-go

        Click Buy Now.

      • Subscription

        1. Click Buy Now.

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

      Note

      After you complete the payment, it requires 1 to 5 minutes to create the cluster. Then, you can view the new cluster on the Clusters page.