PolarDB allows you to create a ApsaraDB PolarDB MySQL-compatible edition cluster by using the Clone from RDS method. You can use the Clone from RDS method to create a PolarDB cluster that has the same data as the source ApsaraDB RDS instance. The created PolarDB cluster retains the accounts, databases, IP whitelist, and required parameters of the source RDS instance.

Prerequisites

  • The edition of the source RDS instance is ApsaraDB RDS for MySQL 5.6 or 5.7 High-availability Edition, and the storage type is local SSD.
    • For ApsaraDB RDS for MySQL 5.6, the minor version of the kernel must be 20190815 or later.
    • For ApsaraDB RDS for MySQL 5.7, the minor version of the kernel must be 20200331 or later.
    Note You can run the show variables like '%rds_release_date%'; command to view the minor version of the kernel for the source RDS instance. If the minor version of the kernel for the source RDS instance is earlier than the preceding version, you can upgrade the minor version of the kernel to the latest version. For more information, see Update the minor engine version of an ApsaraDB RDS for MySQL instance.
  • Transparent Data Encryption (TDE) and SSL are disabled on the source RDS instance. For more information, see TDE and SSL.
  • The table storage engine for the source RDS instance is InnoDB.
  • If Database Proxy (Safe Mode) is enabled for the RDS instance, a privileged account is created or the network connection mode of the RDS instance is switched to the high-performance mode. For more information see Create a privileged account and [Important] RDS network link upgrade. Check the database mode

Background information

PolarDB is a next-generation relational cloud database that is developed by Alibaba Cloud. The database service provides the following benefits:
  • Large storage capacity: up to 100 TB.
  • High performance: up to six times higher than the performance of MySQL.
  • Serverless storage: You do not need to purchase the storage capacity in advance. The storage capacity can be automatically scaled. You are charged for the amount of storage space that you use.
  • Temporary upgrade: supports temporary specification upgrades to handle short-term business peaks.

For more information, see Benefits.

Precautions

The incremental data of the source RDS instance cannot be synchronized to the created PolarDB cluster.

Note If you want to synchronize the incremental data of the source RDS instance to the PolarDB cluster in real time when you create the PolarDB cluster, follow the instructions in Create a ApsaraDB PolarDB MySQL-compatible edition cluster by migrating an ApsaraDB RDS for MySQL instance. This implements smooth migration without downtime.

Benefits

  • The cloning feature is provided free of charge.
  • No data loss occurs during the migration.

Procedure

  1. Log on to the PolarDB console.
  2. In the upper-left corner of the console, select the region where the cluster is deployed.
  3. Click Create Cluster.
  4. Set Product Type to Subscription or Pay-As-You-Go.
    • Subscription: If you use this billing method, you must pay for compute nodes when you create the cluster. You are charged by hour for the amount of storage space consumed by your data. These fees are deducted from your account on an hourly basis.
    • Pay-As-You-Go: If you use this billing method, you are charged for the used resources. An upfront payment is not required. You are charged by hour for the compute nodes and the amount of storage space consumed by your data. These fees are deducted from your account on an hourly basis.
  5. Set the following parameters.
    Parameter Description
    Region The region where the source ApsaraDB RDS for MySQL instance is located.
    Note The PolarDB cluster to be created must also be deployed in this region.
    Create Type Select Clone from RDS.
    RDS Engine Type The database engine of the source RDS instance. The default value of this parameter is MySQL and cannot be changed.
    RDS Engine Version The engine version of the source RDS instance. You can select 5.6 or 5.7.
    Source RDS Instance The source RDS instance. Read-only instances are not included in the available source RDS instances.
    Primary Availability Zone

    Each zone is an independent geographical location in a region. All zones in a region provide the same services.

    You can choose to create your PolarDB cluster within the same zone as the Elastic Compute Service (ECS) instance or in a different zone.

    You need to specify only the primary zone. The system selects a secondary zone.

    Network Type The network type of the PolarDB cluster. The value of this parameter cannot be changed.
    VPC

    VSwitch

    		 The virtual private cloud (VPC) and the vSwitch to which the PolarDB cluster belongs. Make sure that the PolarDB cluster and the ECS instance to be connected are deployed within the same VPC. Otherwise, the cluster and the ECS instance cannot communicate over the internal network for optimal performance.
    Compatibility The database engine version of the PolarDB cluster. The default version is the same as the engine version of the source RDS instance and cannot be changed.
    Edition The edition of the cluster. This parameter is automatically set to Cluster (2-16 Nodes) (Recommended). You do not need to specify this parameter.
    Node Specification The node specifications of the cluster. You can specify node specifications based on your business requirements. We recommend that you select specifications that are the same as or more advanced than the specifications of the source RDS instance. For more information about PolarDB node specifications, see Specifications of compute nodes.
    Nodes The number of nodes to be created in the cluster. You do not need to specify this parameter. The system creates a read-only node of the same specifications as the primary node.
    Storage Cost The storage cost. You do not need to specify this parameter. You are charged by hour for the amount of storage space consumed by your data. For more information, see Specifications and pricing.
    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.
    Time Zone The time zone of the cluster. The default value is UTC+08:00.
    Table Name Case Sensitivity Specifies whether table names of the cluster are case-sensitive. The default value is Not Case-sensitive (Default). If table names are case-sensitive in your on-premises database, select Case-sensitive to facilitate data migration.
    Note The value of this parameter cannot be changed after the cluster is created. Proceed with caution.
    Release Cluster The backup retention policy that is used when you delete or release the cluster. Default value: Retain Last Automatic Backup (Automatic Backup before Release) (Default). Valid values:
    • Retain Last Automatic Backup (Automatic Backup before Release) (Default): retains the last backup when you delete the cluster.
    • Retain All Backups: retains all backups when you delete the cluster.
    • Delete All Backups (Cannot be restored): deletes all backups when you delete the cluster.
    Note You may be charged for the backups that are retained after you delete or release a cluster. For more information, see Release a cluster.
    Cluster Name
    • The name of the new cluster. It must be 2 to 128 characters in length and can contain letters, digits, periods (.), underscores (_), and hyphens (-). It must start with a letter.
    • If you leave this parameter empty, the system generates a cluster name. You can change the cluster name after the cluster is created.
    Resource Group The resource group of the cluster. Select a resource group from available resource groups. For more information, see Create a resource group.
    Note A resource group contains a group of resources that belong to an Alibaba Cloud account. Resource groups allow you to manage these resources in a centralized manner. A resource belongs to only one resource group. For more information, see Use RAM to create and authorize resource groups.
  6. If you create a subscription cluster, set Purchase Plan and Number and click Buy Now in the right corner.
  7. On the Confirm Order page, confirm your order information. Read and accept the terms of service, and then click Activate Now.

    After you complete the activation, it takes 10 to 15 minutes to create the cluster. Then, the newly created cluster is displayed on the Clusters page.

    Note
    • If nodes in the cluster are in the Creating state, the cluster is being created and unavailable. The cluster is available only if it is in the Running state.
    • Make sure that you have selected the region where the cluster is deployed. Otherwise, you cannot view the cluster.
    • We recommend that you purchase subscription PolarDB storage plans to store a large amount of data. Storage plans are more cost-effective than pay-as-you-go storage. You are offered larger discounts if you purchase storage plans that provide larger storage capacities. For more information, see Together with storage plans.
  8. On the Purchase page, confirm the unpaid order and the payment method and click Purchase.
  9. Log on to the PolarDB console and check the status of the new PolarDB cluster.

FAQ

Is the source RDS instance affected when data is cloned from the RDS instance?

No, the source RDS instance is not affected when data is cloned from the RDS instance.

References

API Description
CreateDBCluster Creates a PolarDB cluster.
Note If you create a PolarDB cluster by cloning an ApsaraDB RDS for MySQL instance, set CreationOption to CloneFromRDS.

What to do next

You must change the endpoint over which your application accesses the database to the endpoint of the PolarDB cluster at the earliest opportunity. For more information, see Apply for a cluster endpoint or a primary endpoint.