This topic describes how to migrate data from an ApsaraDB RDS for MySQL database to a user-created MySQL database by using Data Transmission Service (DTS). This is applicable to scenarios such as data analysis and functional test.
- The tables to be migrated from the ApsaraDB RDS for MySQL database contain primary keys or UNIQUE NOT NULL indexes.
- The available storage space of the user-created MySQL database is greater than the total size of the data in the ApsaraDB RDS for MySQL database.
- The version of the user-created MySQL database is the same as that of the ApsaraDB RDS for MySQL database. This ensures compatibility.
- DTS uses read and write resources of the source and destination databases during full data migration. This may increase the database load. If the database performance is unfavorable, the specification is low, or the data volume is large, database services may become unavailable. For example, DTS occupies a large amount of read and write resources in the following cases: a large number of slow SQL queries are performed on the source database, the tables have no primary keys, or a deadlock occurs in the destination database. Before you migrate data, evaluate the performance of the source and destination databases. We recommend that you migrate data during off-peak hours. For example, you can migrate data when the CPU usage of the source and destination databases is less than 30%.
- If your ApsaraDB RDS for MySQL database does not have primary key or unique constraints and each field in the database has duplicate values, the data migrated to the destination database may be duplicated.
- Concurrent insertions are performed during full data migration. This results in table fragmentation in the destination instance. After a full data migration task is completed, the tablespace of the destination instance is larger than that of the source instance.
- If a data migration task fails, DTS attempts to resume the task. In this case, before you switch your workloads to the destination database, you must stop or release the task. Otherwise, the data in the source database will overwrite the data in the destination database after the task is resumed.
- DTS supports schema migration of the following objects: tables, views, triggers, stored
procedures, and stored functions.
Note During schema migration, the
DEFINERmode of views, stored procedures, and stored functions is shifted to the
- The information of the source database account cannot be migrated. If you need to use views, stored procedures, and stored functions, you must grant read and write permissions to the destination database account.
|Migration type||Migration channel fee||Public network traffic fee|
|Schema migration or full data migration||Free of charge||Migrating data from Alibaba Cloud over the Internet incurs fees. For more information, see Pricing.|
|Incremental data migration||Billed. For more information, see Pricing.|
SQL operations that can be synchronized during incremental data migration
|Operation type||SQL statements|
|DML||INSERT, UPDATE, DELETE, and REPLACE|
Permissions required for database accounts
|ApsaraDB RDS for MySQL database||The read permission for the objects to be migrated|
|User-created MySQL database||The read/write permissions for the objects to be migrated|
For more information about how to create and authorize a database account, see the following topics:
- Log on to the DTS console.
- In the left-side navigation pane, click Data Migration.
- At the top of Migration Tasks the page, select the region where the destination cluster resides.
- In the upper-right corner of the page, click Create Migration Task.
- Configure the information about the source and destination databases for the data
Section Parameter Description N/A Task Name DTS automatically generates a task name. We recommend that you use an informative name for easy identification. You do not need to use a unique task name. Source Database Instance Type Select RDS Instance. Instance Region Select the region where the source RDS instance resides. RDS Instance ID Select the ID of the source RDS instance. Database Account Enter the database account of the source RDS instance. For more information about permissions required for the account, see #section_0zj_ekr_6i9. Database Password Enter the password for the database account.Note After the source database information is specified, click Test Connectivity next to Database Password to verify whether the specified information is valid. If the specified information is valid, the Passed message appears. If the Failed message appears, click Check in the Failed message. Modify the source database information based on the instructions. Encryption Select Non-encrypted or SSL-encrypted. If you want to select SSL-encrypted, you must enable SSL encryption for the RDS instance before configuring the data migration task. For more information, see Configure SSL encryption for an RDS for MySQL instance.Note The Encryption parameter is available only in mainland China and Hong Kong(China). Destination Database Instance Type Select User-Created Database in ECS Instance. Instance Region Select the region where the ECS instance resides. ECS Instance ID Select the ID of the ECS instance that is connected to the user-created MySQL database. Database Type Select MySQL. Port Number Enter the service port number of the user-created MySQL database. In this example, enter 3306. Database Account Enter the account of the user-created MySQL database. For more information about permissions required for the account, see #section_0zj_ekr_6i9. Database Password Enter the password for the account of the user-created MySQL database.Note After the destination database information is specified, click Test Connectivity next to Database Password to verify whether the specified information is valid. If the specified information is valid, the Passed message appears. If the Failed message appears, click Check in the Failed message. Modify the destination database information based on the instructions. Encryption Select Non-encrypted or SSL-encrypted. In this example, Non-encrypted is selected.
- In the lower-right corner of the page, click Set Whitelist and Next.
Note The CIDR blocks of DTS servers are automatically added to the whitelist of the source RDS instance and the inbound rule of the destination ECS instance. This ensures that DTS servers can connect to the source and destination instances.
- Configure migration types and objects.
Item Description Migration types
Note If Incremental Data Migration is not selected, do not write data into the source database during full data migration. This ensures data consistency between the source and destination databases.
- To perform only full data migration, select Schema Migration and Full Data Migration.
- If you want to migrate data without disruptions to your business, select Schema Migration, Full Data Migration, and Incremental Data Migration.
Objects to be migrated
Select the objects to be migrated in the Available section and click icon to move them to the Selected section.Note
- Objects to be migrated can be databases, tables, or columns.
- The selected objects are not renamed after the migration by default. If you want to rename the objects migrated to the destination instance, you can use the object name mapping feature provided by DTS. For more information, see Object name mapping.
- If you use the object name mapping feature for an object, objects that depend on the object may fail to be migrated.
- Click Precheck on the lower right of the page.
- A precheck is performed for a data migration task. A data migration task can be started only if it passes the precheck.
- If the precheck fails, click icon corresponding to each failed item to view the details. Fix the problems as instructed and run the precheck again.
- After the precheck is passed, click Next.
- On the Confirm Settings dialog box that appears, specify Channel Specification and select the Data Transmission Service (Pay-As-You-Go) Service Terms.
- Click Buy and Start to start the data migration task.
- Schema migration and full data migration
Do not manually stop a migration task. Otherwise, data migrated to the destination database will be incomplete. Wait until the data migration task stops when it is complete.
- Schema migration, full data migration, and incremental data migration
An incremental data migration task does not automatically end. You must manually end the migration task.Note Select an appropriate time point to manually end the migration task. For example, you can end the migration task during off-peak hours or before you switch your workloads to the destination cluster.
- When the task progress bar switches to Incremental Data Migration and the message The migration task is not delayed appears, stop writing new data to the source database for a few minutes. Then, the progress bar will show the latency of the incremental data migration.
- When the status of incremental data migration changes to The migration task is not delayed, manually stop the migration task.
- Schema migration and full data migration