Synchronize data from a PolarDB for MySQL cluster to an AnalyticDB for MySQL V3.0 cluster - Data Transmission Service

This topic describes how to synchronize data from a PolarDB for MySQL cluster to an AnalyticDB for MySQL V3.0 cluster by using Data Transmission Service (DTS). After you synchronize data, you can use AnalyticDB for MySQL to build internal business intelligence (BI) systems, interactive query systems, and real-time report systems.

Prerequisites

The source PolarDB for MySQL cluster is created. For more information, see Purchase a pay-as-you-go cluster and Purchase a subscription cluster.
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 cluster is larger than the total size of the data in the source PolarDB for MySQL cluster.

Limits

Note By default, DTS disables FOREIGN KEY constraints for the destination database in a data synchronization task. Therefore, the cascade and delete operations of the source database are not synchronized to the destination database.


Category	Description
Limits on the source database	The tables to be synchronized must have PRIMARY KEY or UNIQUE constraints and all fields must be unique. Otherwise, the destination database may contain duplicate data records. If you select tables as the objects to be synchronized and you need to edit tables (such as renaming tables or columns) in the destination database, up to 1,000 tables can be synchronized in a single data synchronization task. If you run a task to synchronize more than 1,000 tables, a request error occurs. In this case, we recommend that you split the tables, configure multiple tasks to synchronize the tables, or configure a task to synchronize the entire database. The following requirements for binary logs must be met: The binary logging feature must be enabled. The value of the loose_polar_log_bin parameter must be set to on. Otherwise, error messages are returned during precheck and the data synchronization task cannot be started. If you perform only incremental data synchronization, the binary logs of the source database must be stored for more than 24 hours. If you perform both full data synchronization and incremental data synchronization, the binary logs of the source database must be stored for at least seven days. After full data synchronization is completed, you can set the retention period to more than 24 hours. Otherwise, DTS may fail to obtain the binary logs and the task may fail. In extreme cases, data may be inconsistent or lost. Make sure that you set the retention period of binary logs based on the preceding requirements. Otherwise, the Service Level Agreement (SLA) of DTS does not guarantee service reliability and performance. During data synchronization, do not perform DDL operations to modify the primary key or add comments, for example, `ALTER TABLE table_name COMMENT='Table comments';`. The operations do not take effect.
Other limits	Prefix indexes cannot be synchronized. If the source database contains prefix indexes, data may fail to be synchronized. Read-only nodes of the source PolarDB for MySQL cluster cannot be synchronized. Due to the limits of AnalyticDB for MySQL, if the disk space usage of the nodes in an AnalyticDB for MySQL cluster reaches 80%, the task is delayed and error messages are returned. We recommend that you estimate the required disk space based on the objects that you want to synchronize. You must ensure that the destination cluster has sufficient storage space. Before you synchronize data, evaluate the impact of data synchronization on the performance of the source and destination databases. We recommend that you synchronize data during off-peak hours. During full data synchronization, DTS uses read and write resources of the source and destination databases. This may increase the loads of the database servers. During full data synchronization, concurrent INSERT operations cause fragmentation in the tables of the destination database. After full data synchronization is completed, the tablespace of the destination database is larger than that of the source database. We recommend that you do not use gh-ost or pt-online-schema-change to perform DDL operations on source tables during data synchronization. Otherwise, data synchronization may fail. If you use only DTS to write data to the destination database, you can use Data Management (DMS) to perform online DDL operations on source tables during data synchronization. For more information, see Change schemas without locking tables. During data synchronization, we recommend that you use only DTS to write data to the destination database. This prevents data inconsistency between the source and destination databases. If you use tools other than DTS to write data to the destination database, data loss may occur in the destination database when you use DMS to perform online DDL operations.

Billing


Synchronization type	Task configuration fee
Schema synchronization and full data synchronization	Free of charge.
Incremental data synchronization	Charged. For more information, see Pricing.

Supported synchronization topologies

One-way one-to-one synchronization
One-way one-to-many synchronization
One-way many-to-one synchronization

SQL operations that can be synchronized


Operation type	SQL statement
DML	INSERT, UPDATE, and DELETE
DDL	CREATE TABLE, DROP TABLE, RENAME TABLE, TRUNCATE TABLE, ADD COLUMN, and DROP COLUMN

Warning If the data type of a field in the source table is changed during data synchronization, an error message is reported and the data synchronization task is interrupted. Assume that the name of the field is customer. You can submit a ticket or perform the following steps to troubleshoot the issue:

AnalyticDB for MySQL
In the destination AnalyticDB for MySQL V3.0 cluster, create a table named customer_new that has the same schema as the customer table.
Execute the INSERT INTO SELECT statement to copy the data of the customer table and insert the data into the customer_new table. This ensures that the data of the two tables is consistent.
Rename or delete the customer table. Then, change the name of the customer_new table to customer.
Restart the data synchronization task in the DTS console.

Procedure

Go to the Data Synchronization page of the new DTS console.

Note You can also log on to the Data Management console. In the top navigation bar, click DTS. Then, in the left-side navigation pane, choose DTS (DTS) > Data Synchronization.
In the upper-left corner of the page, select the region where the data synchronization instance resides.

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 in the upper part of the page. This ensures that you create and run the data synchronization task.


Section	Parameter	Description
N/A	Task Name	The task name that DTS automatically generates. We recommend that you specify a descriptive name that makes it easy to identify the task. You do not need to use a unique task name.
Source Database	Database Type	Select PolarDB for MySQL.
	Access Method	Select Alibaba Cloud Instance.
	Instance Region	Select the region where the source PolarDB for MySQL cluster resides.
	PolarDB Cluster ID	Select the ID of the source PolarDB for MySQL cluster.
	Database Account	Enter the database account of the source PolarDB for MySQL cluster. The account must have the read permissions on the objects to be synchronized.
	Database Password	The password of the database account.
Destination Database	Database Type	Select AnalyticDB for MySQL 3.0.
	Access Method	Select Alibaba Cloud Instance.
	Instance Region	Select the region in which the destination AnalyticDB for MySQL V3.0 cluster resides.
	Instance ID	Select the ID of the destination AnalyticDB for MySQL V3.0 cluster.
	Database Account	Enter the database account of the destination AnalyticDB for MySQL V3.0 cluster. The account must have the read and write permissions on the destination database.
	Database Password	The password of the database account.

In the lower part of the page, click Test Connectivity and Proceed.
Note
- You do not need to modify the security settings for ApsaraDB instances (such as ApsaraDB RDS for MySQL and ApsaraDB for MongoDB) and ECS-hosted databases. DTS automatically adds the CIDR blocks of DTS servers to the whitelists of ApsaraDB instances or the security group rules of ECS instances. For more information, see Add the CIDR blocks of DTS servers to the security settings of on-premises databases.
- After data synchronization is complete, we recommend that you remove the CIDR blocks of DTS servers from the whitelists or security groups.

Select the objects to migrate.

Basic Settings Basic Settings (Merge Tables + Select SQL Operations)


Parameter	Description
Task Stages	Incremental Data Synchronization is selected by default. You must also select Schema Synchronization and Full Data Synchronization. After the precheck is complete, DTS synchronizes the historical data of selected objects from the source instance to the destination cluster. The historical data is the basis for subsequent incremental synchronization.
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 synchronization 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 identical table 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, and a data record has the same primary key as an existing data record in the destination database: During full data synchronization, DTS does not synchronize the data record to the destination database. The existing data record in the destination database is retained. During incremental data synchronization, DTS synchronizes the data record to the destination database. The existing data record in the destination database is overwritten. If the source and destination databases have different schemas, initial data synchronization may fail. In this case, only part of the columns are synchronized, or the data synchronization task fails.
DDL and DML Operations to Be Synchronized	Select the DDL and DML operations that you want to synchronize. For more information, see SQL operations that can be synchronized. Note To select the SQL operations performed on a specific database or table, perform the following steps: In the Selected Objects section, right-click an object. In the dialog box that appears, select the SQL operations that you want to synchronize.
Merge Tables	Yes: In online transaction processing (OLTP) scenarios, sharding is implemented to speed up the response to business tables. In online analytical processing (OLAP) scenarios, you can store a large amount of data in a single table. It makes your SQL queries more efficient. This way, you can merge multiple source tables that have an identical schema into a single destination table. This feature allows you to synchronize data from multiple tables in the source database to a single table in the destination database. Note After you select multiple tables from the source database, you must change the names of these tables to the name of the destination table by using the object name mapping feature. For more information about how to use this feature, see Map object names. DTS adds a column named `__dts_data_source` to the destination table. This column is used to record the data source. The data type of this column is TEXT. The values of this column are in the following format: `data synchronization instance ID:source database name:source schema name:source table name`. This allows DTS to identify each source table. Example: `dts******:dtstestdata:testschema:customer1`. If you set this parameter to Yes, all the selected source tables in the task are merged into a destination table. If you want to merge only part of the source tables, you must create a separate data synchronization 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 migration task fails. No: the default value.
Select Objects	Select one or more objects from the Source Objects section and click the icon to add the objects to the Selected Objects section. Note You can select columns, tables, or databases as objects to synchronize. If you select tables or columns as the objects to synchronize, DTS does not synchronize other objects such as views, triggers, and stored procedures to the destination database.
Rename Databases and Tables	To rename an object in 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 in the destination instance, click Batch Edit in the upper-right corner of the Selected Objects section. For more information, see Map multiple object names at a time.
Filter data	You can specify WHERE conditions to filter data. For more information, see Use SQL conditions to filter data.
Select the SQL operations to be synchronized	In the Selected Objects section, right-click an object. In the dialog box that appears, select the SQL operations that you want to synchronize. For more information, see SQL operations that can be synchronized.

Advanced Settings Advanced Settings (Capitalization of Object Names in Destination Instance + Replicate Temporary Tables When DMS Performs DDL Operations + Next: Configure Database and Table Fields)

Advanced Settings (Capitalization of Object Names in Destination Instance + Replicate Temporary Tables When DMS Performs DDL Operations + Next: Configure Database and Table Fields)


Parameter	Description
Set Alerts	Specifies whether to set alerts for the data synchronization task. If you select yes, DTS sends notifications to contacts if the task fails or the synchronization latency exceeds the upper limit. No: does not set alerts. Yes: sets alerts. In this case, you must also set the alert threshold and alert contacts.
Capitalization of Object Names in Destination Instance	Specifies the capitalization of database names, table names, and column names in the destination instance. By default, DTS default policy is selected. You can select other options to make sure that the capitalization of object names is consistent with that of the source or destination database. For more information,see Specify the capitalization of object names in the destination instance.
Replicate Temporary Tables When DMS Performs DDL Operations	In this scenario, DTS cannot synchronize DDL operations. You must set this parameter to No. However, DTS may support DDL operations for this scenario in the future. In this case, if you use DMS to perform online DDL operations on the source database, you can specify whether to synchronize temporary tables generated by the operations. Yes: DTS synchronizes the data of temporary tables generated by online DDL operations. Note If online DDL operations generate a large amount of data, latency may occur in the data synchronization task. No: DTS does not synchronize the data of temporary tables generated by online DDL operations. Only the original DDL data of the source database is synchronized. Note If you select No, the tables in the destination database may be locked.
Retry Time for Failed Connection	Specifies the retry time range for failed connections. Valid values: 10 to 1440. Unit: minutes. Default value: 120. We recommend that you set the retry time range to more than 30 minutes. If DTS reconnects to the source and destination databases within the specified time range, DTS resumes the data synchronization task. Otherwise, the data synchronization task fails. Note If an instance serves as the source or destination database of multiple data synchronization tasks, the less value that is specified for the instance 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 needs. You can also release the DTS instance at your earliest opportunity after the source and destination instances are released.

In the lower part of the page, click Next: Configure Database and Table Fields. On the page that appears, set the primary key column and distribution key column of the tables that you want to synchronize to the destination AnalyticDB for MySQL cluster.

Note If you select Schema Synchronization for the synchronization type, you must specify the type, primary key column, and distribution key for the tables that you want to synchronize to the AnalyticDB for MySQL V3.0 cluster. For more information, see CREATE TABLE.
Click Next: Save Task Settings and Precheck in the lower part of the page.
Note
- Before you can start the data synchronization task, DTS performs a precheck. You can start the data synchronization task only after the task passes the precheck.
- If the task fails to pass the precheck, you can click the icon next to each failed item to view details.
  
  After you troubleshoot the issues based on the causes, you can run a precheck again.
  
  If you do not need to troubleshoot the issues, you can ignore failed items and run a precheck again.
Wait until the Success Rate becomes 100%. Then, click Next: Purchase Instance.

On the Purchase Instance page, specify the billing method and specifications for the data synchronization instance. The following table describes related parameters.


Section	Parameter	Description
Parameters	Billing method	Subscription: You pay for your subscription when you create an instance. The subscription billing method is more cost-effective than the pay-as-you-go billing method for long-term use. Pay-as-you-go: A pay-as-you-go instance is billed on an hourly basis. For short-term use, we recommend that you select the pay-as-you-go billing method. If you no longer need a pay-as-you-go instance, you can release the instance to reduce costs.
	Instance Class	DTS provides several instance classes that have different performance in synchronization speed. You can select an instance class based on your business scenario. For more information, see Specifications of data synchronization instances.
	Subscription Duration	If you select the subscription billing method, set the subscription duration and the number of instances that you want to create. The subscription duration can be one to nine months or one to three years. Note This parameter is available only if you select the subscription billing method.

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