How to synchronize PolarDB-X 2.0 to ApsaraDB RDS for MySQL - Data Transmission Service

Prerequisites

A source PolarDB-X 2.0 instance is created.
A destination ApsaraDB RDS for MySQL instance is created. For more information, see Create an ApsaraDB RDS for MySQL instance.
The destination ApsaraDB RDS for MySQL instance must have more storage space than the source PolarDB-X 2.0 instance.

Limitations

Note

During schema synchronization, DTS synchronizes foreign keys from the source database to the destination database.
During full data synchronization and incremental data synchronization, DTS temporarily disables constraint checks and foreign key cascade operations at the session level. Data inconsistency may occur if cascade update or delete operations are performed on the source database while the task is running.

Type	Description
Source database limitations	Synchronized tables must have a primary key or a unique constraint. Otherwise, duplicate data may occur in the destination database. DTS does not support Enterprise Edition PolarDB-X 2.0 read-only instances as the source database. If you synchronize tables individually and perform edits, such as column name mapping, a single data synchronization task supports a maximum of 5,000 tables. To synchronize more than 5,000 tables, split them across multiple tasks or configure the task to synchronize the entire database. Otherwise, a request error may occur after you submit the task. Binary log requirements: You must enable the binary log feature in the PolarDB-X 2.0 console and set the binlog_row_image parameter to full. For more information, see Parameter settings. Otherwise, the precheck fails and the data synchronization task cannot start. For incremental data synchronization, you must retain the source database's binary logs for over 24 hours. For tasks that combine full and incremental synchronization, the retention period must be at least 7 days. After the full data synchronization is complete, you can reduce the retention period to 24 hours. The DTS SLA does not cover issues caused by an insufficient binary log retention period. If a table name in the source PolarDB-X 2.0 instance contains uppercase letters, DTS supports only schema synchronization for that table. DTS does not support synchronizing table groups (TABLEGROUP) or databases and tables that have the Locality attribute. DTS does not support synchronizing tables whose names are reserved keywords, such as `select`. DTS cannot synchronize partitions of databases in DRDS mode on a PolarDB-X 2.0 instance. Do not run DDL operations that change database or table schemas during schema synchronization or full synchronization. Otherwise, the synchronization task fails. Note During full synchronization, DTS queries the source database. This creates metadata locks that may block DDL operations on the source database. During the operation of a DTS synchronization task, changing the type of a broadcast table in the source PolarDB-X 2.0 instance (for example, changing a broadcast table to a regular table or a sharded table) is not supported. To change the table type, stop the synchronization task first, and then reconfigure the synchronization task after the change is complete.
Other limitations	Evaluate the performance of your source and destination databases before starting data synchronization. Perform the synchronization during off-peak hours, as initial full data synchronization consumes significant resources and increases the database load. Initial full data synchronization runs concurrent INSERT operations, which can cause table fragmentation in the destination database. Consequently, the destination instance may occupy more tablespace than the source instance after synchronization. Do not use tools like pt-online-schema-change to perform online DDL operations on the objects being synchronized in the source database. Otherwise, the synchronization task fails. During data synchronization, ensure that only DTS writes data to the destination database. Writing data from other sources can cause data inconsistency. For example, if you perform online DDL changes by using DMS while another process is writing to the destination, data loss may occur. If a DDL statement fails to execute on the destination database, the DTS task continues to run. You must check the task logs to find the failed DDL statement. For more information, see View task logs. If you write columns with names that differ only in case to the same table in the destination MySQL database, unexpected results may occur because MySQL column names are case-insensitive. If your data includes four-byte characters—such as rare Chinese characters or emojis—the destination database and table must use the utf8mb4 charset. Note If you use DTS to synchronize table schemas, set the `character_set_server` parameter at the instance level in the destination database to utf8mb4. After data synchronization completes (the instance's Status is Completed), you should use the `ANALYZE TABLE <table_name>` command to confirm that all data is written to the target table. For example, after the HA failover mechanism is triggered in the target MySQL database, data might be written only to memory, which can cause data loss. If a task fails, DTS support staff will attempt to restore it within eight hours. During restoration, they may restart the task or adjust its parameters. Note Only DTS task parameters are modified—not database parameters. Parameters that may be adjusted include those listed in Modify instance parameters.
Other precautions	DTS periodically updates the `dts_health_check`.`ha_health_check` table in the source database to advance the binary log file position.

Billing

Synchronization type	Pricing
Schema synchronization and full data synchronization	Free of charge.
Incremental data synchronization	Charged. For more information, see Billing overview.

Supported SQL operations

Operation type	SQL statement
DML	INSERT, UPDATE, DELETE
DDL	ALTER TABLE CREATE FUNCTION, CREATE INDEX, CREATE TABLE Note If the source database is a PolarDB-X 2.0 Enterprise Edition instance, CREATE FUNCTION and CREATE INDEX operations cannot be synchronized. DROP INDEX, DROP TABLE RENAME TABLE Note The RENAME TABLE operation may cause data inconsistencies. For example, if you select only a specific table as the synchronization object and then rename that table in the source instance during synchronization, data from that table will no longer be synchronized. To prevent this, configure the task to synchronize the entire database that contains the table. This ensures data synchronization continues after the table is renamed. TRUNCATE TABLE

Precautions

Procedure

Go to the data synchronization task list page in the destination region. You can do this in one of two ways.
DTS console
1. Log on to the DTS console.
2. In the navigation pane on the left, click Data Synchronization.
3. In the upper-left corner of the page, select the region where the synchronization instance is located.
DMS console
Note
The actual steps may vary depending on the mode and layout of the DMS console. For more information, see Simple mode console and Customize DMS console layout and style.
1. Log on to the DMS console.
2. In the top menu bar, choose Data + AI > DTS (DTS) > Data Synchronization.
3. To the right of Data Synchronization Tasks, select the region of the synchronization instance.
Click Create Task to open the task configuration page.

Configure the source and destination databases.

Warning

After you select the source and destination instances, review the Limits at the top of the page. Otherwise, the task may fail or data inconsistency may occur.

Category	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 Existing Connection	Select the registered database instance with DTS from the drop-down list. The database information below is automatically configured. Note In the DMS console, this configuration item is Select a DMS database instance. If you have not registered the database instance or do not need to use a registered instance, manually configure the database information below.
	Database Type	Select PolarDB-X 2.0.
	Connection Type	Select Alibaba Cloud Instance.
	Instance Region	Select the region where the source PolarDB-X 2.0 instance resides.
	Replicate Data Across Alibaba Cloud Accounts	This example shows synchronization within the same Alibaba Cloud account. Select No.
	Instance ID	Select the ID of the source PolarDB-X 2.0 instance.
	Database Account	Enter the database account for the source PolarDB-X 2.0 instance. The account must have the REPLICATION SLAVE, REPLICATION CLIENT, and SELECT permissions on the objects to be synchronized. Note For information on how to grant permissions, see Account permission issues during data synchronization.
	Database Password	Enter the password for the specified database account.
Destination Database	Select Existing Connection	Select the registered database instance with DTS from the drop-down list. The database information below is automatically configured. Note In the DMS console, this configuration item is Select a DMS database instance. If you have not registered the database instance or do not need to use a registered instance, manually configure the database information below.
	Database Type	Select MySQL.
	Connection Type	Select Alibaba Cloud Instance.
	Instance Region	Select the region where the destination ApsaraDB RDS for MySQL instance resides.
	Replicate Data Across Alibaba Cloud Accounts	This example shows synchronization within the same Alibaba Cloud account. Select No.
	RDS Instance ID	Select the ID of the destination ApsaraDB RDS for MySQL instance.
	Database Account	Enter the database account for the destination ApsaraDB RDS for MySQL instance. The account must have read and write permissions.
	Database Password	Enter the password for the specified database account.
	Connection Method	Select Non-encrypted or SSL-encrypted as needed. If you set this to SSL-encrypted, you must enable SSL encryption for the RDS for MySQL instance beforehand. For more information, see Use a cloud certificate to quickly enable SSL link encryption.

After completing the configuration, click Test Connectivity and Proceed at the bottom of the page.
Note
- Ensure that you add the CIDR blocks of the DTS servers (either automatically or manually) to the security settings of both the source and destination databases to allow access. For more information, see Add the IP address whitelist of DTS servers.
- If the source or destination is a self-managed database (i.e., the Access Method is not Alibaba Cloud Instance), you must also click Test Connectivity in the CIDR Blocks of DTS Servers dialog box.

Configure the task objects.

On the Configure Objects page, specify the objects to synchronize.

Parameter	Description
Synchronization Type	DTS always selects Incremental Data Synchronization. By default, you must also select Schema Synchronization and Full Data Synchronization. After the precheck, DTS initializes the destination cluster with the full data of the selected source objects, which serves as the baseline for subsequent incremental synchronization.
Processing Mode for Existing Destination Tables	Precheck and Report Errors: Checks for tables with the same names in the destination database. If any tables with the same names are found, an error is reported during the precheck and the data synchronization task does not start. Otherwise, the precheck is successful. Note If you cannot delete or rename the table with the same name in the destination database, you can map it to a different name in the destination. For more information, see Object name mapping. Ignore Errors and Proceed: Skips the check for tables with the same name in the destination database. Warning Selecting Ignore Errors and Proceed may cause data inconsistency and put your business at risk. For example: If the table schemas are consistent and a record in the destination database has the same primary key or unique key value as a record in the source database: During full data synchronization, DTS retains the destination record and skips the source record. During incremental synchronization, DTS overwrites the destination record with the source record. If the table schemas are inconsistent, data initialization may fail. This can result in only partial data synchronization or a complete synchronization failure. Use with caution.
Source Objects	In the Source Objects box, click the objects, and then click to move them to the Selected Objects box. Note You can select objects at the database, table, or column level. If you select only tables or columns, DTS does not synchronize other object types (such as views, triggers, and stored procedures).
Selected Objects	To rename a single object in the destination instance, right-click the object in the Selected Objects box. For more information, see Map a single object name. To rename multiple objects in bulk, click Batch Edit in the upper-right corner of the Selected Objects box. For more information, see Map multiple object names in bulk. Note To select SQL operations at the database or table level, right-click a synchronization object in the Selected Objects box and choose the desired SQL operations from the dialog box that appears. To set a WHERE clause to filter data, right-click a table in the Selected Objects box and set the filter conditions in the dialog box that appears. For more information, see Set filter conditions.

Click Next: Advanced Settings.

Parameter	Description
Dedicated Cluster for Task Scheduling	By default, DTS uses a shared cluster for tasks, so you do not need to make a selection. For greater task stability, you can purchase a dedicated cluster to run the DTS synchronization task. For more information, see What is a DTS dedicated cluster?.
Retry Time for Failed Connections	If the connection to the source or destination database fails after the synchronization task starts, 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 1,440 minutes. We recommend a duration of 30 minutes or more. If the connection is restored within this period, the task resumes automatically. Otherwise, the task fails. Note If multiple DTS instances (e.g., Instance A and B) share a source or destination, DTS uses the shortest configured retry duration (e.g., 30 minutes for A, 60 for B, so 30 minutes is used) for all instances. DTS charges for task runtime during connection retries. Set a custom duration based on your business needs, or release the DTS instance promptly after you release the source/destination instances.
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 Synchronization	During full data synchronization, DTS consumes read and write resources from the source and destination databases, which can increase their load. To mitigate pressure on the destination database, you can limit the migration rate by setting Queries per second (QPS) to the source database, RPS of Full Data Migration, and Data migration speed for full migration (MB/s). Note This parameter is available only if Synchronization Types is set to Full Data Synchronization. You can also adjust the rate of full data synchronization when the synchronization instance is running.
Enable Throttling for Incremental Data Synchronization	You can also limit the incremental synchronization rate to reduce pressure on the destination database by setting RPS of Incremental Data Synchronization and Data synchronization speed for incremental synchronization (MB/s).
Environment Tag	You can select an environment tag to identify the instance. In this example, no selection is needed.
Configure ETL	Choose whether to enable the extract, transform, and load (ETL) feature. For more information, see What is ETL? Valid values: Yes: Enables the ETL feature. Enter data processing statements in the code editor. For more information, see Configure ETL in a data migration or data synchronization task. No: Disables the ETL feature.
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.
Monitoring and Alerting	Choose whether to set up alerts. If the synchronization fails or the latency exceeds the specified threshold, DTS sends a notification to the alert contacts. No: No alerts are configured. Yes: Configures alerts. You must also set the alert threshold and alert notifications. For more information, see Configure monitoring and alerting during task configuration.

Click Data Verification to configure a data verification task.
To use the data verification feature, see Configure data verification.

Save the task and perform a precheck.
- To view the parameters for configuring this instance via an API operation, hover over the Next: Save Task Settings and Precheck button and click Preview OpenAPI parameters in the tooltip.
- If you have finished viewing the API parameters, click Next: Save Task Settings and Precheck at the bottom of the page.
Note
- Before a synchronization task starts, DTS performs a precheck. You can start the task only if the precheck passes.
- If the precheck fails, click View Details next to the failed item, fix the issue as prompted, and then rerun the precheck.
- If the precheck generates warnings:
  For non-ignorable warning, click View Details next to the item, fix the issue as prompted, and run the precheck again.
  For ignorable warnings, you can bypass them by clicking Confirm Alert Details, then Ignore, and then OK. Finally, click Precheck Again to skip the warning and run the precheck again. Ignoring precheck warnings may lead to data inconsistencies and other business risks. Proceed with caution.

Purchase the instance.

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

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?
New Instance Class	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.

After the configuration is complete, read and select Data Transmission Service (Pay-as-you-go) Service Terms.
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.