PolarDB allows you to create a PolarDB for MySQL 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 theshow 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 an account and [Important] RDS network link upgrade.
Background information
- 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.
Benefits
- The cloning feature is provided free of charge.
- No data loss occurs during the migration.
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 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.