Data Transmission Service：Migrate data from a PolarDB-X 2.0 instance to an AnalyticDB for MySQL V3.0 cluster

Prerequisites

• The source PolarDB-X 2.0 instance is created and compatible with MySQL 5.7.
• The destination AnalyticDB for MySQL V3.0 cluster is created. For more information, see Create a cluster.
• The available storage space of the destination AnalyticDB for MySQL V3.0 cluster is larger than the total size of the data in the source PolarDB-X 2.0 instance.

Limits

Billing

Migration types

• Schema migration

  Data Transmission Service (DTS) migrates the schemas of objects from the source database to the destination database.

• Full data migration

  DTS migrates the existing data of objects from the source database to the destination database.

• Incremental data migration

  After full data migration is complete, DTS migrates incremental data from the source database to the destination database. Incremental data migration allows data to be migrated smoothly without interrupting services of self-managed applications during data migration.

SQL operations that can be migrated during incremental data migration

Permissions required for database accounts

For more information about how to create a database account and grant permissions to the database account, see the following topic:

Data type mappings

Procedure

1. Go to the Data Migration Tasks page.
   1. Log on to the Data Management (DMS) console.
   2. In the top navigation bar, click DTS.
   3. In the left-side navigation pane, choose DTS (DTS) > Data Migration.
   Note

   • Operations may vary based on the mode and layout of the DMS console. For more information, see Simple mode and Configure the DMS console based on your business requirements.
   • You can also go to the Data Migration Tasks page of the new DTS console.
2. From the drop-down list next to Data Migration Tasks, select the region in which the data migration instance resides.
   Note If you use the new DTS console, you must select the region in which the data migration instance resides in the upper-left corner.
3. Click Create Task. On the page that appears, configure the source and destination databases.
   
   Warning After you select the source and destination instances, we recommend that you read the limits displayed at the top of the page. This helps ensure that the task properly runs or prevent data inconsistency.

   Section	Parameter	Description
   N/A	Task Name	The name of the task. DTS automatically generates a task name. We recommend that you specify an informative name to identify the task. You do not need to specify a unique task name.
   Source Database	Select Instance	Select whether to use an existing instance. If you select an existing instance, DTS automatically applies the parameter settings of the instance. You do not need to configure the corresponding parameters again. If you do not use an existing instance, you must configure parameters for the source database.
   	Database Type	The type of the source database. Select PolarDB-X 2.0.
   	Access Method	The access method of the source database. Select Alibaba Cloud Instance.
   	Instance Region	The region in which the source PolarDB-X 2.0 instance resides.
   	Instance ID	The ID of the source PolarDB-X 2.0 instance.
   	Database Account	The database account of the source PolarDB-X 2.0 instance. For more information about the permissions that are required for the account, see the Permissions required for database accounts section of this topic.
   	Database Password	The password of the database account.
   Destination Database	Select Instance	Select whether to use an existing instance. If you select an existing instance, DTS automatically applies the parameter settings of the instance. You do not need to configure the corresponding parameters again. If you do not use an existing instance, you must configure parameters for the source database.
   	Database Type	The type of the destination database. Select AnalyticDB for MySQL 3.0.
   	Access Method	The access method of the destination database. Select Alibaba Cloud Instance.
   	Instance Region	The region in which the destination AnalyticDB for MySQL V3.0 cluster resides.
   	Instance ID	The ID of the destination AnalyticDB for MySQL V3.0 cluster.
   	Database Account	The database account of the destination AnalyticDB for MySQL V3.0 cluster. For information about the permissions that are required for the account, see the Permissions required for database accounts section of this topic.
   	Database Password	The password of the database account.

4. In the lower part of the page, click Test Connectivity and Proceed.
   If the source or destination database is an Alibaba Cloud database instance, such as an ApsaraDB RDS for MySQL or ApsaraDB for MongoDB instance, DTS automatically adds the CIDR blocks of DTS servers to the whitelist of the instance. If the source or destination database is a self-managed database hosted on an Elastic Compute Service (ECS) instance, DTS automatically adds the CIDR blocks of DTS servers to the security group rules of the ECS instance, and you must make sure that the ECS instance can access the database. If the source or destination database is a self-managed database that is deployed in a data center or provided by a third-party cloud service provider, you must manually add the CIDR blocks of DTS servers to the whitelist of the database to allow DTS to access the database. For more information about the CIDR blocks of DTS servers, see Add the CIDR blocks of DTS servers to the security settings of on-premises databases.

   Warning If the CIDR blocks of DTS servers are automatically or manually added to the whitelist of a database or an instance, or to the security group rules of an ECS instance, security risks may arise. Therefore, before you use DTS to migrate data, you must understand and acknowledge the potential risks and take preventive measures, including but not limited to the following measures: enhance the security of your username and password, limit the ports that are exposed, authenticate API calls, regularly check the whitelist or ECS security group rules and forbid unauthorized CIDR blocks, or connect the database to DTS by using Express Connect, VPN Gateway, or Smart Access Gateway.
5. Configure objects to migrate and advanced settings.
   

   Parameter	Description
   Migration Type	If you want to perform only full data migration, select Schema Migration and Full Data Migration. If you want to ensure service continuity during data migration, select Schema Migration, Full Data Migration, and Incremental Data Migration. Note If Full Data Migration is selected, you can migrate the schema and data of the table that is created by executing the CREATE TABLE statement to the destination database. If Incremental Data Migration is not selected, we recommend that you do not write data to the source instance during data migration. This ensures data consistency between the source and destination instances.
   Processing Mode of Conflicting Tables	Precheck and Report Errors: checks whether the destination database contains tables that have the same names as tables in the source database. If the source and destination databases do not contain identical table names, the precheck is passed. Otherwise, an error is returned during the precheck and the data migration task cannot be started. Note You can use the object name mapping feature to rename the tables that are migrated to the destination database. You can use this feature if the source and destination databases contain tables that have identical names and the tables in the destination database cannot be deleted or renamed. For more information, see Map object names. Ignore Errors and Proceed: skips the precheck for identical table names in the source and destination databases. Warning If you select Ignore Errors and Proceed, data inconsistency may occur, and your business may be exposed to potential risks. If the source and destination databases have the same schema, DTS does not migrate data records that have the same primary keys as data records in the destination database. If the source and destination databases have different schemas, only some columns are migrated or the data migration task fails. Proceed with caution.
   Merge Tables	Yes: If you select this option, DTS adds the __dts_data_source column to each table to record data sources. For more information, see Enable the multi-table merging feature. No: This option is selected by default. Note If you set this parameter to Yes, all of the selected source tables in the task are merged into the destination table. If you do not need to merge specific source tables, you can create a separate data migration task for these tables. Warning We recommend that you do not perform DDL operations to change the schemas of source databases or tables. Otherwise, data inconsistency may occur or the data migration task fails.
   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 You can select columns, tables, or databases as the objects to be migrated. If you select tables as the objects to be migrated, DTS does not migrate other objects such as views, triggers, or stored procedures to the destination database. If you select a database as the object to be migrated, DTS migrates data based on the following default rules: If the table to be migrated in the source database has a primary key, such as a single-column primary key or a composite primary key, the primary key columns are specified as the distribution keys. If the table to be migrated in the source database does not have a primary key, an auto-increment primary key column is automatically generated in the destination table. This may cause data inconsistency between the source and destination databases.
   Selected Objects	To rename an object that you want to migrate to the destination instance, right-click the object in the Selected Objects section. For more information, see Map the name of a single object. To rename multiple objects at a time, click Batch Edit in the upper-right corner of the Selected Objects section. For more information, see Map multiple object names at a time. Note If you use the object name mapping feature to rename an object, other objects that are dependent on the object may fail to be migrated. To specify WHERE conditions to filter data, right-click an object in the Selected Objects section. In the dialog box that appears, specify the conditions. For more information, see Use SQL conditions to filter data. To select the SQL operations performed on a specific database or table, right-click an object in the Selected Objects section. In the dialog box that appears, select the SQL operations that you want to migrate. For more information about the SQL operations that can be migrated, see SQL operations that can be migrated during incremental data migration.

6. Click Next: Advanced Settings to configure advanced settings.
   

   Parameter	Description
   Set Alerts	Specifies whether to set alerts for the data migration task. If the task fails or the migration latency exceeds the threshold, the alert contacts will receive notifications. Valid values: No: does not set alerts. Yes: sets alerts. If you select Yes, you must also set the alert threshold and alert contacts. For more information, see Configure monitoring and alerting when you create a DTS task.
   Retry Time for Failed Connections	The retry time range for failed connections. If the source or destination database fails to be connected after the data migration task is started, DTS immediately retries a connection within the time range. Valid values: 10 to 1440. Unit: minutes. Default value: 720. We recommend that you set the parameter to a value greater than 30. If DTS reconnects to the source and destination databases within the specified time range, DTS resumes the data migration task. Otherwise, the data migration task fails. Note If you set different retry time ranges for multiple data migration tasks that have the same source or destination database, the shortest retry time range that is set takes precedence. When DTS retries a connection, you are charged for the DTS instance. We recommend that you specify the retry time range based on your business requirements. You can also release the DTS instance at your earliest opportunity after the source and destination instances are released.
   Configure ETL	Specifies whether to configure the extract, transform, and load (ETL) feature. For more information, see What is ETL?. Valid values: Yes: configures the ETL feature. You can enter data processing statements in the code editor. For more information, see Configure ETL in a data migration or data synchronization task. No: does not configure the ETL feature.
   Whether to delete SQL operations on heartbeat tables of forward and reverse tasks	Specifies whether to write SQL operations on heartbeat tables to the source database while the DTS instance is running. Yes: does not write SQL operations on heartbeat tables. In this case, a latency of the DTS instance may be displayed. No: writes SQL operations on heartbeat tables. In this case, specific features such as physical backup and cloning of the source database may be affected.

7. Specify the primary key columns and distribution key columns of the tables that you want to migrate to the AnalyticDB for MySQL cluster.
   

   Note

   • If you select Schema Migration as Task Stages, you must specify the Type, Primary Key Column, and Distribution Key parameters for the tables that you want to migrate to the AnalyticDB for MySQL V3.0 cluster. For more information, see CREATE TABLE.
   • In the Primary Key Column field, you can specify multiple columns to form a composite primary key. In this case, you must specify one or more primary key columns as the distribution keys.
8. In the lower part of the page, click Next: Save Task Settings and Precheck.
   Note

   • Before you can start the data migration task, DTS performs a precheck. You can start the data migration task only after the task passes the precheck.
   • If the task fails to pass the precheck, click View Details next to each failed item. After you troubleshoot the issues based on the causes, run a precheck again.
   • If an alert is triggered for an item during the precheck:
     • If an alert item cannot be ignored, click View Details next to the failed item and troubleshoot the issues. Then, run a precheck again.
     • If an alert item can be ignored, click Confirm Alert Details. In the View Details dialog box, click Ignore. In the message that appears, click OK. Then, click Precheck Again to run a precheck again. If you ignore the alert item, data inconsistency may occur, and your business may be exposed to potential risks.
9. Wait until the Success Rate value becomes 100%. Then, click Next: Purchase Instance.
10. On the Purchase Instance page, specify the Instance Class parameter for the data migration instance. The following table describes the parameter.

    Section	Parameter	Description
    Parameters	Instance Class	DTS provides several instance classes that vary in the migration speed. You can select an instance class based on your business scenario. For more information, see Specifications of data migration instances.

11. Read and select the check box to agree to Data Transmission Service (Pay-as-you-go) Service Terms.
12. Click Buy and Start to start the data migration task. You can view the progress of the task in the task list.