PolarDB allows you to create a PolarDB for MySQL cluster by using the Clone from RDS method.
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 the local SSD.
-
- For ApsaraDB RDS for MySQL 5.6, the minor version of the kernel for the RDS instance is 20190130 or later.
- For ApsaraDB RDS for MySQL 5.7, the minor version of the kernel for the RDS instance is 20200331 or later.
Note You can execute theshow variables like '%rds_release_date%'
statement to view the minor version of the kernel for the RDS instance. For more information about how to upgrade the minor version of the kernel, see Upgrade the minor engine version of an ApsaraDB RDS for MySQL instance. - Transparent data encryption (TDE) and secure sockets layer (SSL) are disabled on the source RDS instance.
- The source RDS instance uses InnoDB as the table storage engine.
- If Database Proxy (Safe Mode) is enabled for the RDS instance, a privileged account
is created. For more information, see Create a privileged account. Otherwise, the network connection mode of the RDS instance is changed to the high-performance
mode. For more information, see [Important] RDS network link upgrade.
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 a storage capacity in advance. The system can automatically scale the storage capacity. You are charged for the used storage capacity.
- Temporary specification scale-up: You can scale up cluster specifications to handle workload spikes.
For more information, see Benefits.
You can create a PolarDB cluster by using the Clone from RDS method. The created PolarDB cluster retains the accounts, databases, IP address whitelist, and required parameters
of the source RDS instance. The incremental data of the source RDS instance cannot
be synchronized to the created PolarDB cluster.
Note If you need to synchronize the incremental data of the source RDS instance to the
PolarDB cluster in real time when you create the PolarDB cluster, follow instructions in Create a PolarDB for MySQL cluster by using the Migration from RDS method. This achieves no service downtime during data migration.
Highlights
- The cloning feature is free.
- No data is lost during the cloning.
Procedure
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 clone from the RDS instance.
Related API operations
API | Description |
---|---|
CreateDBCluster | Creates a PolarDB cluster.
Note If you create a PolarDB cluster by using the Clone from RDS method, set the CreationOption parameter to CloneFromRDS.
|
What to do next
You must change the endpoint over which your application accesses the PolarDB cluster to the endpoint of the PolarDB cluster at the earliest opportunity. For more information, see View or apply for an endpoint.