Docs

RDS for MySQL

Migrating data

Creating and initiating a migration task

Database transmission service (DTS) provides a variety of database migration services. This topic describes how to use DTS to create and initiate a data migration task, using the migration of a self-hosted MySQL in a VPC to Volcano Engine RDS for MySQL as an example.

Prerequisites

A Volcano Engine account has been registered with real name authentication completed. For account creation methods and real-name authentication, refer to How to register an account and Real-name authentication.

Meet the supported database types and constraints for migration. For more Details, refer to Usage restrictions.

Procedure

In the upper-left corner of the top menu bar, select the target region.

Click Create task in the Migration task list.

Configure the following parameters on the Create a migration task page.

Parameter			Description
Task name			Enter a task name. This is required. The name must meet the following conditions: Must start with a letter. It must contain no more than 32 characters. It can contain only Chinese characters, letters, digits, underscores (_), and hyphens (-).
Link specification			DTS supports four different links to meet business requirements of different levels. For more details about link specifications, refer to Product specification.
Source database information	Instance type	Currently, only "MySQL" is supported.
		Access method	The currently supported access methods are "Volcano Engine RDS", "self-managed MySQL in the VPC", and "PublicMySQL". Description: This topic uses "self-managed MySQL in the VPC" as an example.
		MySQL instance	Select the source MySQL instance from the drop-down list. Note: This configuration is supported only when "Volcano Engine RDS" is used as the access method.
		Host address	Enter the host address of the source self-managed instance. Note: This configuration is supported only when "self-managed MySQL in the VPC" or "PublicMySQL" is used as the access method.
		Port	Enter the port number of the source self-hosted instance. Note: This configuration is supported only when "self-managed MySQL in the VPC" or "PublicMySQL" is used as the access method.
		VPC	Select the VPC network of the source instance from the drop-down list. Note: This configuration is supported only when 'self-managed MySQL in the VPC' is used as the access method.
		Database account	Enter the database account for the source instance.
		Database password	Enter the password for the source instance database account. Note: After entering the password, you can click Test connection, and then perform subsequent configuration after the test is passed. If access restrictions are set for your instance, you should grant access permissions for the DTS CIDR block so that you can continue the migration task.You can click \\View DTS IP segment\\* to view and copy the CIDR block. You can click \\View DTS IP segment\\* to view and copy the CIDR block.
Target database information	Instance type	Currently, only "MySQL" is supported.
		Access method	The currently supported access methods are "Volcano Engine RDS", "self-managed MySQL in the VPC", and "PublicMySQL". Note: This topic uses "RDS for MySQL" as an example.
		MySQL instance	Select the target MySQL instance from the drop-down list. Note: This configuration is supported only when "Volcano Engine RDS" is used as the access method.
		Host address	Enter the localhost of the target self-managed instance. Note: This configuration is supported only when "self-managed MySQL in the VPC" or "PublicMySQL" is used as the access method.
		Port	Enter the port number of the target self-hosted instance. Note: This configuration is supported only when "self-managed MySQL in the VPC" or "PublicMySQL" is used as the access method.
		VPC	Select the VPC for the target instance from the drop-down list. Note: This configuration is supported only when 'self-managed MySQL in the VPC' is used as the access method.
		Database account	Enter the database account of the target instance.
		Database password	Enter the password corresponding to the database account of the target instance. Note: After entering the password, you can click Test connection, and then perform subsequent configuration after the test is passed. If access restrictions are set for your instance, you should grant access permissions for the DTS CIDR block so that you can continue the migration task.You can click \\View DTS IP segment\\* to view and copy the CIDR block. You can click \\View DTS IP segment\\* to view and copy the CIDR block.

Click Next step: configure migration object.

Configure the following parameters on the Configure migration objects page.

tip

If you do not currently need to initiate the migration task, you can click Save in the lower-right corner of the page after the migration objects are configured.

After saving, it jumps back to the Migration task list page. For configuration instructions, refer to Configure migration task.

Parameter	Description
Migration type	Select the migration type based on your business needs: If you only need full migration, select Structural migration and Full migration at the same time. If you must perform non-stop migration, you select Structural migration, Full migration, and Incremental migration at the same time. Note: If Incremental migration is not selected, do not write new data to the source instance during data migration to ensure data consistency.
Migration object	Select the objects to be migrated in the Migration objects box, and you can confirm the migration objects in the Selected objects box on the right. Note: If a migration object is not an entire database, OnlineDDL is not supported, and automatic migration of new objects and relevant modifications are not supported for incremental migration. Migration objects can be selected at the database or table level. If a migration object selected is a table, other objects (such as views, triggers, functions, and stored procedures) will not be moved to the destination database.

Click Pre-check and start.

You can perform the following operations based on the precheck result:

Click Details in the Action column of the precheck result to view the detailed alert information and modify the database and table based on the alert information.

Click Ignore in the Action column to ignore the alert and continue to initiate the migration task.

tip

If you choose to Ignore the alert and initiate the migration task, it can cause data inconsistencies and business risks.

For details about pre-check items, refer to Pre-check items.

Read and check the service agreement in the lower-left corner, and click Start task in the lower-right corner.

After the task is created, you can return to the console and view the progress of the migration task in the Migration task list.

FAQ

Why do some GROUP BY queries fail after migrating a MySQL 5.6 instance to RDS for MySQL?

RDS for MySQL is compatible with MySQL 5.7 and 8.0. In MySQL 5.7 and later versions, the ONLY_FULL_GROUP_BY mode is enabled by default, which applies stricter validation to GROUP BY syntax, causing some non-standard GROUP BY queries to fail.

Last updated: 2026.08.21 16:00:28