Data Transmission Service:Migrate data from an ApsaraDB RDS for MySQL instance on RDS Enterprise Edition to an ApsaraDB RDS for MySQL instance on Cluster Edition

Step 1: Open the Data Migration page

Use one of the following methods:

Step 2: Create a task and configure source and destination databases

1. Click Create Task.

2. Configure the source and destination databases using the parameters in the following table.

   Warning

   After configuring the source and destination databases, review the Limits displayed at the top of the page before proceeding. Skipping this step may result in task failure or data inconsistency.

   Category	Parameter	Description
   —	Task Name	DTS generates a name automatically. Specify a descriptive name to make the task easy to identify. The name does not need to be unique.
   Source Database	Select Existing Connection	If the source instance is already registered with DTS, select it from the drop-down list — DTS populates the remaining fields automatically. For details, see Manage database connections. Otherwise, fill in the fields below. In the DMS console, use the Select a DMS database instance drop-down list.
   	Database Type	Select MySQL.
   	Access Method	Select Cloud Instance.
   	Instance Region	Select the region of the source ApsaraDB RDS for MySQL instance.
   	Cross-account	Select No (same Alibaba Cloud account).
   	RDS Instance ID	Select the ID of the source instance.
   	Database Account	Enter the database account. For permission requirements, see Required permissions.
   	Database Password	Enter the password for the database account.
   	Connection Method	Select Non-encrypted or SSL-encrypted. To use SSL encryption, enable SSL on the source instance before configuring the task. For details, see Use a cloud certificate to enable SSL encryption.
   Destination Database	Select Existing Connection	If the destination instance is already registered with DTS, select it from the drop-down list — DTS populates the remaining fields automatically. For details, see Manage database connections. Otherwise, fill in the fields below. In the DMS console, use the Select a DMS database instance drop-down list.
   	Database Type	Select MySQL.
   	Access Method	Select Cloud Instance.
   	Instance Region	Select the region of the destination ApsaraDB RDS for MySQL instance.
   	Cross-account	Select No (same Alibaba Cloud account).
   	RDS Instance ID	Select the ID of the destination instance.
   	Database Account	Enter the database account. For permission requirements, see Required permissions.
   	Database Password	Enter the password for the database account.
   	Connection Method	Select Non-encrypted or SSL-encrypted. To use SSL encryption, enable SSL on the destination instance before configuring the task. For details, see Use a cloud certificate to enable SSL encryption.

3. Click Test Connectivity and Proceed.

   Note

   DTS must be able to reach both the source and destination databases. If you have security group or whitelist restrictions, add the CIDR blocks of DTS servers to the allowed list. For details, see Add DTS server IP addresses to a whitelist.

Step 3: Select objects and configure migration settings

1. On the Configure Objects page, configure the following settings:

   Setting	Description
   Migration Types	Select the migration types based on your strategy. See Choose a migration strategy. Note If you do not select Schema Migration, create the target database and tables in the destination before the task runs and enable object name mapping in Selected Objects.
   Method to Migrate Triggers in Source Database	Select how to handle triggers. Required only when both Schema Migration and Incremental Data Migration are selected. For details, see Configure the method to synchronize or migrate triggers.
   Enable Migration Assessment	Select Yesalert notification settings to evaluate schema compatibility (index length, stored procedures, dependent tables) before migration. Available only when Schema Migration is selected. Selecting Yes increases precheck time; the assessment result does not affect the precheck result.
   Processing Mode of Conflicting Tables	Precheck and Report Errors (default): The precheck fails if the source and destination have tables with identical names. Use object name mapping to resolve conflicts. For details, see Map object names. Ignore Errors and Proceed: Skips the precheck. During full migration, DTS keeps the existing destination row if a primary key conflict occurs. During incremental migration, DTS overwrites the existing row. Use with caution — incompatible schemas may cause partial migration or task failure.
   Whether to migrate Event	Select Yes to migrate events. If you select Yes, complete the additional steps described in Synchronize or migrate events.
   Capitalization of Object Names in Destination Instance	By default, DTS default policy is selected. Change this if you need object name capitalization to match the source or destination. For details, see Specify the capitalization of object names in the destination instance.
   Source Objects	Select objects from the Source Objects section and click to move them to Selected Objects. Selecting tables or columns excludes other object types (views, triggers, stored procedures) from migration.
   Selected Objects	To rename a single object in the destination, right-click it in Selected Objects. For details, see Map the name of a single object. To rename multiple objects at once, click Batch Edit. For details, see Map multiple object names at a time. Note Object name mapping may cause migration to fail for objects that depend on the renamed object. To filter rows using a WHERE clause, right-click the table in Selected Objects. For details, see Set a filter condition. To select specific DML or DDL operations for incremental migration at the database or table level, right-click the object in Selected Objects and configure the operations.

2. Click Next: Advanced Settings and configure the following:

   Setting	Description
   Dedicated Cluster for Task Scheduling	By default, DTS uses a shared cluster. Purchase a dedicated cluster for improved stability. For details, see What is a DTS dedicated cluster.
   Copy the temporary table of the Online DDL tool that is generated in the source table to the destination database.	Controls how DTS handles temporary tables generated by online DDL tools. Important pt-online-schema-change is not supported — using it causes task failure. Select one of: Yes — migrates data from temporary tables (may introduce latency if temporary tables are large). No, Adapt to DMS Online DDL — migrates only the original DDL operations from DMS (may lock destination tables). No, Adapt to gh-ost — migrates only the original DDL operations from gh-ost (may lock destination tables; supports custom regular expressions to filter shadow tables).
   Whether to Migrate Accounts	Select Yes to migrate account information from the source, then select the accounts and confirm their permissions.
   Retry Time for Failed Connections	The time range (in minutes) during which DTS retries if the source or destination connection fails. Valid range: 10–1,440. Default: 720. Set this to a value greater than 30. If DTS reconnects within this window, the task resumes automatically. Note If multiple tasks share the same database, the most recently specified retry time applies. DTS charges for the instance during the retry period.
   Retry Time for Other Issues	The time range (in minutes) during which DTS retries failed DDL or DML operations. Valid range: 1–1,440. Default: 10. Set this to a value greater than 10. This value must be less than Retry Time for Failed Connections.
   Enable Throttling for Full Data Migration	Limits resource usage during full data migration by setting Queries per second (QPS) to the source database, RPS of Full Data Migration, and Data migration speed for full migration (MB/s). Available only when Full Data Migration is selected.
   Enable Throttling for Incremental Data Migration	Limits resource usage during incremental migration by setting RPS of Incremental Data Migration and Data migration speed for incremental migration (MB/s). Available only when Incremental Data Migration is selected.
   Environment Tag	Optional. Select a tag to identify the instance by environment.
   Whether to delete SQL operations on heartbeat tables of forward and reverse tasks	Controls whether DTS writes heartbeat SQL to the source database. Yes — does not write heartbeat SQL (latency may appear on the DTS instance). No — writes heartbeat SQL to the source (may affect physical backup and cloning of the source).
   Configure ETL	Select Yes to enable the extract, transform, and load (ETL) feature and enter data processing statements. For an overview, see What is ETL?. For configuration steps, see Configure ETL in a data migration or data synchronization task.
   Monitoring and Alerting	Select Yes to receive notifications when the task fails or migration latency exceeds your threshold. Configure the alert threshold and notification settings. For details, see Configure monitoring and alerting when you create a DTS task.

3. Click Next Step: Data Verification to configure a data verification task. For details, see Configure a data verification task.

Step 4: Run the precheck

• To preview the API parameters for this task configuration, hover over Next: Save Task Settings and Precheck and click Preview OpenAPI parameters.

• Click Next: Save Task Settings and Precheck to save settings and start the precheck.

Step 5: Purchase the instance and start migration

1. Wait until Success Rate reaches 100%, then click Next: Purchase Instance.

2. On the Purchase Instance page, configure the following:

   Section	Parameter	Description
   New Instance Class	Resource Group	The resource group for the migration instance. Default: default resource group. For details, see What is Resource Management?
   	Instance Class	Select an instance class based on the required migration speed. For details, see Instance classes of data migration instances.

3. Select the Data Transmission Service (Pay-as-you-go) Service Terms check box.

4. Click Buy and Start, then click OK in the confirmation dialog.

Track task progress on the Data Migration page.

Migration types

• Schema migration: Migrates the schemas of selected objects — tables, views, triggers, stored procedures, and stored functions — from the source to the destination. Note that the routine_body of stored procedures and stored functions, and the select_statement of views cannot be modified during migration. DTS changes the SECURITY attribute from DEFINER to INVOKER for views, stored procedures, and functions, and sets the DEFINER to the destination database account. Note that the SECURITY attribute and DEFINER cannot be modified during migration. DTS does not migrate user information. To call a view, stored procedure, or stored function in the destination, grant read and write permissions to INVOKER.

• Full data migration: Migrates the historical data of selected objects from the source to the destination.

• Incremental data migration: After full data migration completes, continuously syncs new changes from the source to the destination. This keeps your application online during the migration and lets you cut over at any time.

Billing

Supported SQL operations for incremental migration

Limitations