Data Transmission Service:Migrate Amazon Aurora MySQL to Alibaba Cloud

Usage notes

• During a full data migration, DTS consumes read and write resources on the source and destination databases, increasing their load. If your databases have poor performance, low specifications, or high workloads (for example, if the source database has many slow SQL queries or tables without primary keys, or if deadlocks occur in the destination database), the increased load can strain your databases or even cause service interruptions. Perform the data migration during off-peak hours, such as when the CPU utilization of both databases is below 30%.

• If a source table lacks a primary key or a unique constraint and contains non-unique data, duplicate data may be created in the destination database.

• For columns with the FLOAT or DOUBLE data type, DTS reads their values by using the ROUND(COLUMN,PRECISION) function. If the precision is not explicitly defined, DTS migrates FLOAT values with a precision of 38 digits and DOUBLE values with a precision of 308 digits. Verify that these precisions meet your business requirements.

• If a source database name violates ApsaraDB RDS naming conventions, you must create a compliant database in the destination instance before configuring the task. Otherwise, DTS creates the database automatically.

  Note

  For more information about naming conventions and how to create a database, see Create a database and accounts.

• If a data migration task fails, DTS automatically attempts to resume it. Before you switch your business workloads to the destination instance, make sure to stop or release the task. This prevents an automatically resumed task from overwriting data in the destination instance with data from the source database.

Billing

Migration types

• Schema migration

  DTS migrates object schemas to the destination Alibaba Cloud RDS for MySQL instance. DTS supports schema migration for the following object types: tables, views, triggers, stored procedures, and stored functions. DTS does not support schema migration for events.

  Note

  • During schema migration, DTS changes the SQL SECURITY characteristic for views, stored procedures, and stored functions from DEFINER to INVOKER.

  • DTS does not migrate user accounts. As a result, any user that calls a view, stored procedure, or stored function in the destination instance must be granted the necessary read and write permissions.

• Full data migration

  DTS migrates all data of the selected objects from the source Amazon Aurora MySQL instance to the destination Alibaba Cloud RDS for MySQL instance.

  Note

  During a full data migration, concurrent INSERT operations cause fragmentation in the destination instance's tables. After the full data migration is complete, the destination instance's tablespace is larger than the source instance's.

• Incremental data migration

  After the full data migration is complete, DTS reads the binlog of the source Amazon Aurora MySQL instance to replicate incremental data changes to the destination Alibaba Cloud RDS for MySQL instance. Incremental data migration enables a smooth database migration with service continuity.

Database account permissions

For information about creating database accounts and granting permissions, see the following topics:

• For Amazon Aurora MySQL, follow the account creation instructions in Create an account for a self-managed MySQL database and configure binary logging.

• For ApsaraDB RDS for MySQL, see Create an account and Modify the permissions of an account.

Prerequisites

1. Log in to the Amazon Aurora console.

2. In the left-side navigation pane, click Database.

3. Click the DB identifier for the node with the Role of Writer instance.

4. On the Connectivity & security tab, click the name of the VPC security group.

5. On the Security Groups page, click the target Security Group ID.

6. On the Inbound rules tab, click Edit inbound rules.

7. On the Edit inbound rules page, click Add rule, add the CIDR blocks for the DTS servers in the destination database's region, and then click Save rules. For more information about the DTS CIDR blocks, see Add DTS Server IP Addresses to a Whitelist.

   Note

   • Add only the CIDR blocks for DTS servers in the destination database's region. For example, if your source database is in the Singapore region and your destination database is in the China (Hangzhou) region, you only need to add the CIDR blocks for DTS servers in the China (Hangzhou) region.

   • You can add multiple CIDR blocks to a single rule.

   • For more information, see the official AWS documentation or contact AWS Support.

8. Log in to the Amazon Aurora MySQL database and set the binlog retention period. Skip this step if incremental data migration is not required.

   call mysql.rds_set_configuration('binlog retention hours', 24);

   Note

   • This command sets the binlog retention period to 24 hours. The maximum retention period is 168 hours (7 days).

   • The binlog feature must be enabled for Amazon Aurora MySQL, and the binlog_format parameter must be set to ROW. If you use MySQL 5.6 or later, the binlog_row_image parameter must be set to FULL. For more information, refer to the official Amazon documentation or contact Amazon technical support.

Procedure (new console)

1. Navigate to the migration task list page for the destination region using one of the following methods.

   From the DTS console

   1. Log on to the Data Transmission Service (DTS) console.

   2. In the navigation pane on the left, click Data Migration.

   3. In the upper-left corner of the page, select the region where the migration instance is located.

   From the DMS console

   Note

   The actual operations may vary based on the mode and layout of the DMS console. For more information, see Simple mode console and Customize the layout and style of the DMS console.

   1. Log on to the Data Management (DMS) console.

   2. In the top menu bar, choose Data + AI > Data Transmission (DTS) > Data Migration.

   3. To the right of Data Migration Tasks, select the region where the migration instance is located.

2. Click Create Task to navigate to the task configuration page.

3. Configure the source and destination databases.

   Warning

   After you select the source and destination instances, we recommend that you carefully read the limits displayed at the top of the page. Otherwise, the task may fail or data inconsistency may occur.

   Section	Parameter	Description
   N/A	Task Name	DTS automatically generates a task name. We recommend that you specify a descriptive name for easy identification. The name does not need to be unique.
   Source Database	Select a DMS database instance.	You can choose whether to use an existing instance, as needed. If you use an existing instance, the database information below is automatically filled in. You do not need to enter it again. If you do not use an existing instance, you must configure the database information below. Note In the DMS console, you can click Add DMS Database Instance to register a database with DMS. For more information, see ApsaraDB Data Ingestion and Register a database hosted on a third-party cloud service or a self-managed database. In the DTS console, you can register a database with DTS on the Database Connections page or the new configuration page. For more information, see Manage database connections.
   	Database Type	Select MySQL.
   	Connection Type	Select Public IP Address.
   	Instance Region	Select the region where the source Amazon Aurora MySQL database is located. Note If the region where your Amazon Aurora MySQL database is located is not listed, you can select the region that is geographically closest to it.
   	Domain Name or IP	Enter the endpoint of the Amazon Aurora MySQL database. Note You can obtain the endpoint on the Connectivity & security tab of your Amazon Aurora MySQL instance. The endpoint includes the Endpoint and Port Number.
   	Port Number	Enter the service port of the Amazon Aurora MySQL database. The default value is 3306.
   	Database Account	Enter the database account. For the required permissions, see Permissions required for database accounts.
   	Database Password	Enter the password for the database account.
   	Encryption	Select Non-encrypted or SSL-encrypted based on your database configuration. If SSL encryption is not enabled for the Amazon Aurora MySQL database, select Non-encrypted. If SSL encryption is enabled for the Amazon Aurora MySQL database, select SSL-encrypted. You must also upload a CA Certificate and enter the CA Certificate Password.
   Destination Database	Select a DMS database instance.	You can choose whether to use an existing instance, as needed. If you use an existing instance, the database information below is automatically filled in. You do not need to enter it again. If you do not use an existing instance, you must configure the database information below. Note In the DMS console, you can click Add DMS Database Instance to register a database with DMS. For more information, see ApsaraDB Data Ingestion and Register a database hosted on a third-party cloud service or a self-managed database. In the DTS console, you can register a database with DTS on the Database Connections page or the new configuration page. For more information, see Manage database connections.
   	Database Type	Select MySQL.
   	Connection Type	Select Alibaba Cloud Instance.
   	Instance Region	Select the region where the destination ApsaraDB RDS for MySQL instance is located.
   	Replicate Data Across Alibaba Cloud Accounts	For this scenario, select No.
   	RDS Instance ID	Select the ID of the destination ApsaraDB RDS for MySQL instance.
   	Database Account	Enter the database account. For the required permissions, see Permissions required for database accounts.
   	Database Password	Enter the password for the database account.
   	Connection Method	Select Non-encrypted or SSL-encrypted based on your database requirements. If you set this parameter to SSL-encrypted, you must enable SSL encryption for the RDS for MySQL instance beforehand. For more information, see Quickly enable SSL encryption using a cloud certificate.

4. After you complete the configuration, click Test Connectivity and Proceed at the bottom of the page. In the CIDR Blocks of DTS Servers dialog box that appears, click Test Connectivity.

   Note

   Ensure that the IP address segments of the DTS service are automatically or manually added to the security settings of the source and destination databases to allow access from DTS servers. For more information, see Add DTS server IP addresses to a whitelist.

5. Configure the task objects.

   1. On the Configure Objects page, configure the objects that you want to migrate.

      Parameter	Description
      Migration Types	If you only need to perform a full migration, select both Schema Migration and Full Data Migration. To perform a migration with no downtime, select Schema Migration, Full Data Migration, and Incremental Data Migration. Note If you do not select Schema Migration, you must ensure that a database and tables to receive the data exist in the destination database. You can also use the object name mapping feature in the Selected Objects box as needed. If you do not select Incremental Data Migration, do not write new data to the source instance during data migration to ensure data consistency.
      Method to Migrate Triggers in Source Database	Select a method to migrate triggers based on your business requirements. If you are not migrating any triggers, you do not need to configure this parameter. For more information, see Configure trigger synchronization or migration. Note This can be configured only when Migration Types is set to Schema Migration.
      Enable Migration Assessment	Assesses whether the schemas of the source and destination databases, such as index length, stored procedures, and dependent tables, meet the requirements. Select Yes or No based on your business requirements. Note This can be configured only when Migration Types is set to Schema Migration. If you select Yes, the precheck may take longer. You can view the Assessment Result during the precheck. The assessment result does not affect the precheck result.
      Processing Mode of Conflicting Tables	Precheck and Report Errors: Checks whether tables with the same names exist in the destination database. If no tables with the same names exist, the precheck is passed. If tables with the same names exist, an error is reported during the precheck, and the data migration task does not start. Note If a table in the destination database has the same name but cannot be easily deleted or renamed, you can change the name of the table in the destination database. For more information, see Object name mapping. Ignore Errors and Proceed: Skips the check for tables with the same names. Warning Selecting Ignore Errors and Proceed may cause data inconsistency and business risks. For example: If the table schemas are consistent and a record in the destination database has the same primary key value as a record in the source database: During full migration, DTS keeps the record in the destination database. The record from the source database is not migrated. During incremental migration, DTS does not keep the record in the destination database. The record from the source database overwrites the record in the destination database. If the table schemas are inconsistent, only some columns of data may be migrated, or the migration may fail. Proceed with caution.
      Capitalization of Object Names in Destination Instance	You can configure the case sensitivity policy for the names of migrated objects, such as databases, tables, and columns, in the destination instance. By default, DTS default policy is selected. You can also choose to keep the case sensitivity consistent with the default policy of the source or destination database. For more information, see Case sensitivity of object names in the destination database.
      Source Objects	Select one or more objects from the Source Objects section. Click the icon and add the objects to the Selected Objects section. Note The granularity for selecting migration objects is schema, table, and column. If you select only tables or columns as migration objects, other objects such as views, triggers, and stored procedures are not migrated to the destination database.
      Selected Objects	To change the name of a single migration object in the target instance, right-click the object in the Selected Objects box. For more information, see Map individual schema, table, and column names. To change the names of multiple migration objects in the target instance, click Selected Objects in the upper-right corner of the Batch Edit box. For more information, see Map multiple schema, table, and column names. Note If you use the object name mapping feature, other objects that depend on the mapped objects may fail to be migrated. To specify WHERE conditions to filter data, right-click a table in the Selected Objects section and configure filter conditions in the dialog box that appears. For more information, see Set filter conditions. To select the SQL operations to migrate at the database or table level, right-click an object in the Selected Objects section and select the required SQL operations in the dialog box that appears.

   2. Click Next: Advanced Settings to configure advanced parameters.

      Parameter	Description
      Dedicated Cluster for Task Scheduling	By default, DTS schedules tasks on a shared cluster. You do not need to select one. If you want more stable tasks, you can purchase a dedicated cluster to run DTS migration tasks.
      Copy the temporary table of the Online DDL tool that is generated in the source table to the destination database.	If you use Data Management (DMS) or gh-ost to perform online DDL changes in the source database, you can choose whether to migrate the data from the temporary tables generated by the online DDL changes. Important DTS tasks do not support using tools such as pt-online-schema-change to perform online DDL changes. Otherwise, the DTS task fails. The processing methods for each phase are as follows: The Schema Migration and Full Data Migration phases do not allow DDL operations that change the database or table structure. Therefore, they are not controlled by the online DDL policy. Schema Migration: Not controlled by the online DDL policy. Related temporary tables are created. Full Data Migration: Not controlled by the online DDL policy. The migration of temporary tables is not included in the full migration objects. All tables whose names match the regular expression (^_(.+)_(?:gho|new)$ or ^_(.+)_(?:ghc|del|old)$) are filtered out. Incremental Data Migration: Controlled by the online DDL policy. Yes: Migrates data changes from temporary tables (for example, _table_name_gho) generated by online DDL operations. No, Adapt to DMS Online DDL and No, Adapt to gh-ost: Filters out data changes from temporary tables (for example, _table_name_gho) generated by tools such as gh-ost based on regular expression rules. Yes: Migrates the data from the temporary tables generated by online DDL changes. Note If online DDL changes generate a large amount of data in temporary tables, it may cause task latency. No, Adapt to DMS Online DDL: Does not migrate the data from the temporary tables generated by online DDL changes. It only migrates the original DDL statements executed using Data Management (DMS). Note This option causes tables in the destination database to be locked. No, Adapt to gh-ost: Does not migrate the data from the temporary tables generated by online DDL changes. It supports custom filtering rules. DTS filters out data changes from temporary tables (for example, _table_name_gho) generated by tools such as gh-ost based on regular expression rules. You can modify the default regular expressions used to match shadow and useless tables as needed: Shadow table: ^_(.+)_(?:gho|new)$ Useless table: ^_(.+)_(?:ghc|del|old)$ Note This option causes tables in the destination database to be locked.
      Whether to Migrate Accounts	Choose whether to migrate account information from the source database based on your business requirements. If you select Yes, you must also select the accounts to migrate and confirm their permissions. For more information, such as authorization methods, see Migrate database accounts.
      Retry Time for Failed Connections	After the migration task starts, if the connection to the source or destination database fails, DTS reports an error and immediately begins to retry the connection. The default retry duration is 720 minutes. You can customize the retry time to a value from 10 to 1440 minutes. We recommend that you set the duration to more than 30 minutes. If DTS reconnects to the source and destination databases within the specified duration, the migration task automatically resumes. Otherwise, the task fails. Note For multiple DTS instances that share the same source or destination, the network retry time is determined by the setting of the last created task. Because you are charged for the task during the connection retry period, we recommend that you customize the retry time based on your business needs, or release the DTS instance as soon as possible after the source and destination database instances are released.
      Retry Time for Other Issues	After the migration task starts, if a non-connectivity issue, such as a DDL or DML execution exception, occurs in the source or destination database, DTS reports an error and immediately begins to retry the operation. The default retry duration is 10 minutes. You can customize the retry time to a value from 1 to 1440 minutes. We recommend that you set the duration to more than 10 minutes. If the related operations succeed within the specified retry duration, the migration task automatically resumes. Otherwise, the task fails. Important The value of Retry Time for Other Issues must be less than the value of Retry Time for Failed Connections.
      Enable Throttling for Full Data Migration	During full migration, DTS consumes read and write resources on the source and destination databases, which may increase the database load. If required, you can enable throttling for the full migration task. You can set Queries per second (QPS) to the source database, RPS of Full Data Migration, and Data migration speed for full migration (MB/s) to reduce the load on the destination database. Note This configuration item is available only if you select Full Data Migration for Migration Types. You can also adjust the full migration speed after the migration instance is running.
      Enable Throttling for Incremental Data Migration	If required, you can also choose to set speed limits for the incremental migration task. You can set RPS of Incremental Data Migration and Data migration speed for incremental migration (MB/s) to reduce the load on the destination database. Note This configuration item is available only if you select Incremental Data Migration for Migration Types. You can also adjust the incremental migration speed after the migration instance is running.
      Environment Tag	Select an environment tag to identify the instance. In this example, you do not need to select a tag.
      Whether to delete SQL operations on heartbeat tables of forward and reverse tasks	Choose whether DTS writes heartbeat SQL information to the source database while the instance is running. Yes: Does not write heartbeat SQL information to the source database. The DTS instance may display latency. No: Writes heartbeat SQL information to the source database. This may interfere with source database operations like physical backups and cloning.
      Configure ETL	Based on your business needs, select whether to configure the ETL feature to process data. Yes: Configures the ETL feature. You must also enter data processing statements in the text box. No: Does not configure the ETL feature.
      Monitoring and Alerting	Select whether to set alerts and receive alert notifications based on your business needs. No: Does not set an alert. Yes: Configure alerts by setting an alert threshold and an alert notifications. If a migration fails or the latency exceeds the threshold, the system sends an alert notification.

   3. Click Next: Data Validation to configure a data validation task.

      For more information about the data validation feature, see Configure data validation.

6. Save the task and run a precheck.

   • To view the parameters for configuring this instance when you call the API operation, move the pointer over the Next: Save Task Settings and Precheck button and click Preview OpenAPI parameters in the bubble that appears.

   • If you do not need to view or have finished viewing the API parameters, click Next: Save Task Settings and Precheck at the bottom of the page.

   Note

   • Before the migration task starts, DTS performs a precheck. The task starts only after it passes the precheck.

   • If the precheck fails, click View Details next to the failed check item, fix the issue based on the prompt, and then run the precheck again.

   • If a warning is reported during the precheck:

     • For check items that cannot be ignored, click View Details next to the failed item, fix the issue based on the prompt, and then run the precheck again.

     • For check items that can be ignored, you can click Confirm Alert Details, Ignore, OK, and Precheck Again to skip the alert item and run the precheck again. If you choose to ignore a warning, it may cause issues such as data inconsistency and pose risks to your business.

7. Purchase the instance.

   1. When the Success Rate is 100%, click Next: Purchase Instance.

   2. On the Purchase page, select the link specification for the data migration instance. For more information, see the following table.

      Category	Parameter	Description
      New Instance Class	Resource Group Settings	Select the resource group to which the instance belongs. The default value is default resource group. For more information, see What is Resource Management?
      	Instance Class	DTS provides migration specifications with different performance levels. The link specification affects the migration speed. You can select a specification based on your business scenario. For more information, see Data migration link specifications.

   3. After the configuration is complete, read and select Data Transmission Service (Pay-as-you-go) Service Terms.

   4. Click Buy and Start. In the OK dialog box that appears, click OK.

      You can view the progress of the migration task on the Data Migration Tasks list page.

      Note

      • If the migration task does not include incremental migration, it stops automatically after the full migration is complete. After the task stops, its Status changes to Completed.

      • If the migration task includes incremental migration, it does not stop automatically. The incremental migration task continues to run. While the incremental migration task is running, the Status of the task is Running.

Procedure (legacy console)

1. Log on to the DTS console.

   Note

   If you are automatically redirected to the Data Management (DMS) console, you can click the icon in the lower-right corner and then click to return to the classic DTS console.

2. In the left-side navigation pane, click Data Migration.

3. At the top of the Migration Tasks page, select the region of the destination cluster.

4. In the upper-right corner of the page, click Create Data Migration Task.

5. Configure the source and destination databases.

   Section	Parameter	Description
   N/A	Task name	DTS automatically generates a task name. For easy identification, specify a descriptive name. The task name does not need to be unique.
   Source database	Instance type	Select self-managed database with a public IP address.
   	Instance region	If you set instance type to self-managed database with a public IP address, you do not need to configure Instance Region.
   	Database type	Select MySQL.
   	Hostname or IP address	Enter the endpoint of the source Amazon Aurora MySQL database. Note You can obtain the endpoint on the Basic Information page of the Amazon Aurora MySQL instance. In the Amazon RDS console, select the writer instance and click the Connectivity & security tab. In the Endpoint & port section, copy the endpoint. The endpoint is in the *.rds.amazonaws.com format. The default port is 3306.
   	Port	Enter the service port of the Amazon Aurora MySQL database. The default value is 3306.
   	Database account	Enter the database account for the Amazon Aurora MySQL database. See Database account permissions for the required permissions.
   	Database password	Enter the password for the database account. Note After you enter the source database information, you can click Test Connectivity next to Database Password to verify that the information is correct. If the information is correct, the message Passed is displayed. If the message Failed is displayed, click Diagnose next to the Failed message and adjust the source database information based on the prompts.
   Destination database	Instance type	Select RDS Instance.
   	Instance region	Select the region where the destination ApsaraDB RDS instance is located.
   	RDS instance ID	Select the ID of the destination ApsaraDB RDS instance.
   	Database account	Enter the database account for the destination ApsaraDB RDS instance. See Database account permissions for the required permissions.
   	Database password	Enter the password for the database account. Note After you enter the destination database information, you can click Test Connectivity after Database Password to verify that the entered information is correct. If the information is correct, a Passed message is displayed. If a Failed message is displayed, click Diagnose after Failed and adjust the destination database information based on the prompts.
   	Connection mode	Select Non-encrypted or SSL-encrypted based on your requirements. If you select SSL-encrypted, you must enable SSL encryption for the ApsaraDB RDS instance in advance. For more information, see Set SSL encryption. Note The Encryption parameter is available only in the Chinese mainland and China (Hong Kong) regions.

6. After you complete the configuration, click Authorize Whitelist and Move to Next Step in the lower-right corner of the page.

   For Alibaba Cloud sources and destinations (such as ApsaraDB RDS or ECS-hosted databases), DTS automatically adds its server CIDR blocks to the whitelist or security group. For external databases, such as those in a data center or on another cloud, you must manually add the CIDR blocks to grant DTS access. For the IP addresses to add, see CIDR blocks of DTS servers.

   Warning

   Adding the public CIDR blocks of DTS servers, whether automatically or manually, may introduce security risks. By using this product, you acknowledge and accept these potential risks. You are responsible for implementing basic security measures, including but not limited to using strong passwords, restricting open ports, using authentication for internal API calls, regularly reviewing and restricting unnecessary network segments, or connecting through private networks such as Express Connect, VPN Gateway, or Smart Access Gateway.

7. Select the migration types and the objects to migrate.

   Parameter	Description
   Migration types	For a full data migration only, select both Schema Migration and Full Data Migration. To perform a migration with no downtime, select Schema Migration, Full Data Migration, and Incremental Data Migration. Note If you do not select Incremental Data Migration, do not write new data to the source Amazon Aurora MySQL database during the data migration to ensure data consistency.
   Migration objects	In the Migration Objects box, select the objects to migrate, and then click to move them to the Selected Objects box. Note You can select objects at the database, table, or column level. By default, the names of migrated objects in the destination database are the same as in the source database. If you want to change the names of the migrated objects, use the object name mapping feature. For more information, see Object name mapping. If you use the object name mapping feature, other objects that depend on a renamed object might fail to migrate.
   Map object names	This feature allows you to rename migrated objects in the destination instance. For more information, see Object name mapping.
   Retry duration upon network failure	The default retry duration is 12 hours. You can also specify a custom duration. If DTS reconnects to the source and destination databases within the specified duration, the migration task automatically resumes. Otherwise, the task fails. Note DTS charges fees for the task running during connection retries. To avoid unnecessary charges, specify a retry duration that suits your business needs. Alternatively, release the DTS instance promptly after the source and destination instances are decommissioned.
   Copy temporary tables from online DDL operations	If you use Data Management (DMS) to perform online DDL changes in the source database, you can choose whether to migrate data from the temporary tables created during the online DDL changes. Yes: Migrates data from the temporary tables created during online DDL changes. Note If the temporary tables created during online DDL changes contain a large amount of data, the migration task may experience delays. No: Does not migrate data from the temporary tables created during online DDL changes. Only the original DDL data from the source database is migrated. Note This option causes table locks in the destination database.

8. After you complete the configuration, click Precheck and Start in the lower-right corner of the page.

   Note

   • Before the migration task starts, DTS runs a precheck. The task can start only after it passes the precheck.

   • If the precheck fails, click the icon next to the failed item to view details.

     • Fix the issues as prompted and run the precheck again.

     • If you do not need to fix the warning items, you can select Ignore and then click Ignore Warnings and Rerun Precheck to run the precheck again.

9. After the task passes the precheck, click Next.

10. In the Confirm Settings dialog box that appears, select a Instance Class and select the Data Transmission Service (pay-as-you-go) Service Terms checkbox.

11. Click Buy and Start to begin the migration.

    • Schema migration + Full data migration

      Allow the task to complete automatically. Stopping it manually may result in incomplete data.

    • Schema migration + Full data migration + Incremental data migration

      The migration task does not stop automatically. You must stop it manually.

      Important

      Choose an appropriate time to stop the task manually, such as during off-peak hours or when you are ready to switch your business to the destination cluster.

      1. Wait until the migration task enters the Incremental Data Migration phase and the status shows Undelayed. Then, stop writing data to the source database for several minutes. During this time, the status of Incremental Data Migration may show a latency.

      2. Wait for the Incremental Data Migration status to show Undelayed again. Then, manually stop the migration task.

12. Switch your workloads to the destination ApsaraDB RDS instance.