This topic describes how to synchronize data from an ApsaraDB RDS for MySQL instance to an AnalyticDB for PostgreSQL instance by using Data Transmission Service (DTS). The data synchronization feature provided by DTS allows you to transfer and analyze data with ease.
- The tables of ApsaraDB RDS for MySQL to be synchronized from the source database contain primary keys.
- The destination AnalyticDB for PostgreSQL instance is created. For more information, see Create an AnalyticDB for PostgreSQL instance.
DTS uses read and write resources of the source and destination databases during initial full data synchronization. This may increase the loads of the database servers. If the database performance is unfavorable, the specification is low, or the data volume is large, database services may become unavailable. For example, DTS occupies a large amount of read and write resources in the following cases: a large number of slow SQL queries are performed on the source database, the tables have no primary keys, or a deadlock occurs in the destination database. 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. For example, you can synchronize data when the CPU utilization of the source and destination databases is less than 30%.
|Synchronization type||Task configuration fee|
|Schema synchronization and full data synchronization||Free of charge.|
|Incremental data synchronization||Charged. For more information, see Billing overview.|
- You can select only tables as the objects to be synchronized.
- DTS does not synchronize the following types of data: BIT, VARBIT, GEOMETRY, ARRAY, UUID, TSQUERY, TSVECTOR, and TXID_SNAPSHOT.
- Prefix indexes cannot be synchronized. If the source database contains prefix indexes, data may fail to be synchronized.
- We recommend that you do not use gh-ost or pt-online-schema-change to perform DDL operations on objects during data synchronization. Otherwise, data synchronization may fail.
SQL operations that can be synchronized
- DML operations: INSERT, UPDATE, and DELETE
- DDL operation: ADD COLUMN
Note The CREATE TABLE operation is not supported. To synchronize data from a new table, you must add the table to the selected objects. For more information, see Add an object to a data synchronization task.
Supported synchronization topologies
- One-way one-to-one synchronization
- One-way one-to-many synchronization
- One-way many-to-one synchronization
|MySQL||AnalyticDB for PostgreSQL|
- Purchase a data synchronization instance. For more information, see Purchase a DTS instance. Note On the buy page, set Source Instance to MySQL, set Target Instance to AnalyticDB for PostgreSQL, and set Synchronization Topology to One-Way Synchronization.
- Log on to the DTS console.
- In the left-side navigation pane, click Data Synchronization.
- At the top of the Synchronization Tasks page, select the region where the destination instance resides.
- Find the data synchronization instance and click Configure Synchronization Channel in the Actions column.
- Configure the source and destination instances.
Section Parameter Description N/A Synchronization 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 Instance Details Instance Type Select RDS Instance. Instance Region The source region that you selected on the buy page. The value of this parameter cannot be changed. RDS Instance ID The ID of the source ApsaraDB RDS for MySQL instance. Database Account The database account of the ApsaraDB RDS for MySQL instance.Note If the database engine of the source ApsaraDB RDS for MySQL instance is MySQL 5.5 or MySQL 5.6, you do not need to configure the Database Account and Database Password parameter. Database Password The password of the database account. Encryption Select Non-encrypted or SSL-encrypted. If you want to select SSL-encrypted, you must enable SSL encryption for the ApsaraDB RDS instance before you configure the data synchronization task. For more information, see Configure SSL encryption on an ApsaraDB RDS for MySQL instance.Note The Encryption parameter is available only within regions in the Chinese mainland and the China (Hong Kong) region. Destination Instance Details Instance Type The value of this parameter is set to AnalyticDB for PostgreSQL and cannot be changed. Instance Region The destination region that you selected on the buy page. The value of this parameter cannot be changed. Instance ID The ID of the destination AnalyticDB for PostgreSQL instance. Database Name The name of the destination database. Database Account The initial account of the AnalyticDB for PostgreSQL instance. For more information, see Create a database account.Note You can also enter an account that has the RDS_SUPERUSER permission. For more information, see Manage users and permissions. Database Password The password of the database account.
- In the lower-right corner of the page, click Set Whitelist and Next. 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 Elastic Compute Service (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 synchronization policy and the objects to be synchronized.
Setting Parameter Description Select the synchronization policy Initial Synchronization You must select both Initial Schema Synchronization and Initial Full Data Synchronization in most cases. After the precheck, DTS synchronizes the schemas and data of the required objects from the source instance to the destination instance. The schemas and data are the basis for subsequent incremental synchronization. Processing Mode of Conflicting Tables
- Clear Target Table
Skips the Schema Name Conflict item during the precheck. Clears the data in the destination table before initial full data synchronization. If you want to synchronize your business data after testing the data synchronization task, you can select this mode.
Skips the Schema Name Conflict item during the precheck. Adds data to the existing data during initial full data synchronization. If you want to synchronize data from multiple tables to one table, you can select this mode.
Select the types of operations that you want to synchronize based on your business requirements.
Select the objects to be synchronized N/A
Select one or more tables from the Available section and click the icon to move the tables to the Selected section.Note
- You can select only tables as the objects to be synchronized.
- You can use the object name mapping feature to change the names of the columns that are synchronized to the destination database. For more information, see Rename an object to be synchronized.
Rename Databases and Tables N/A
You can use the object name mapping feature to rename the objects that are synchronized to the destination instance. For more information, see Object name mapping.
Replicate Temporary Tables When DMS Performs DDL Operations N/AIf you use Data Management (DMS) to perform online DDL operations on the source database, you can specify whether to synchronize temporary tables generated by online DDL 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, the data synchronization task may be delayed.
- 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 Connections N/ABy default, if DTS fails to connect to the source or destination database, DTS retries within the next 720 minutes (12 hours). You can specify the retry time based on your needs. If DTS reconnects to the source and destination databases within the specified time, DTS resumes the data synchronization task. Otherwise, the data synchronization task fails.Note When DTS retries a connection, you are charged for the DTS instance. We recommend that you specify the retry time based on your business needs. You can also release the DTS instance at your earliest opportunity after the source and destination instances are released.
- Clear Target Table
- Specify the primary key column and distribution column of the table that you want to synchronize to the AnalyticDB for PostgreSQL instance.
- In the lower-right corner of the page, click Precheck. 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, click the icon next to each failed item to view details.
- After you troubleshoot the issues based on the causes, run a precheck again.
- If you do not need to troubleshoot the issues, ignore failed items and run a precheck again.
- Close the Precheck dialog box after the following message is displayed: The precheck is passed. Then, the data synchronization task starts.
- Wait until the initial synchronization is complete and the data synchronization task
is in the Synchronizing state. You can view the status of the data synchronization task on the Synchronization Tasks page.