AnalyticDB for PostgreSQL (previously known as HybridDB for PostgreSQL) is a fast, easy-to-use, and cost-effective warehousing service that can process petabytes of data. This topic describes how to synchronize data from a DRDS instance to an AnalyticDB for PostgreSQL instance by using Data Transmission Service (DTS). The data synchronization feature is applicable to scenarios such as ad-hoc query and analysis, extract, transform, and load (ETL) operations, and data visualization.
Prerequisites
- A database is created in the DRDS instance based on one or more ApsaraDB RDS for MySQL instances.
- The tables to be synchronized from the source database contain primary keys.
- An AnalyticDB for PostgreSQL instance is created. For more information, see Create an instance.
Precautions
- 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%.
- We recommend that you do not scale up or down the DRDS instance, migrate frequently-accessed tables, change shard keys, or perform DDL operations on objects during data synchronization. Otherwise, data synchronization may fail.
- If you need to change the network type of a DRDS instance during data synchronization, you must submit a ticket to modify the network connection information.
- After a data synchronization task is started, new tables that are created in the source database can be synchronized. However, you must add the tables to the required objects. For more information see Add an object to a data synchronization task.
Limits
- You can select only tables as the objects to be synchronized.
- DTS does not synchronize the following types of data: JSON, GEOMETRY, CURVE, SURFACE, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON, and GEOMETRYCOLLECTION.
SQL operations that can be synchronized
INSERT, UPDATE, and DELETE
Term mappings
| DRDS | AnalyticDB for PostgreSQL |
|---|---|
| Database | Schema |
| Table | Table |
Procedure
- At the top of the Synchronization Tasks page, select the region where the destination instance resides.
- Configure the source and destination instances.
Section Parameter Description N/A Synchronization Task Name DTS automatically generates a task name. We recommend that you specify an informative name for easy identification. You do not need to use a unique task name. Source Instance Details Instance Type The value of this parameter is set to DRDS and cannot be changed. Instance Region The region of the source instance. The region is the same as the source region that you selected on the buy page. You cannot change the value of this parameter. DRDS Instance ID Select the ID of the DRDS instance. Destination Instance Details Instance Type The value of this parameter is set to AnalyticDB for PostgreSQL and cannot be changed. Instance Region The region of the destination instance. The region is the same as the destination region that you selected on the buy page. You cannot change the value of this parameter. Instance ID Select the ID of the AnalyticDB for PostgreSQL instance. Database Name Enter the name of the destination database in the AnalyticDB for PostgreSQL instance. Database Account Enter the database account of the destination AnalyticDB for PostgreSQL instance. Database Password Enter the password of the destination database account. - 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 In Existed Target Table - 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.
- Ignore
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.
Synchronization Type Select the types of operations that you want to synchronize based on your business requirements.
- Insert
- Update
- Delete
Select the objects to be synchronized N/A Select 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 Specify the name of an object in the destination instance.
- 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.
Note The page in this step appears only if you select Initial Schema Synchronization in Step 8. For more information about primary key columns and distribution columns, see Define constraints and Define table distribution. - In the lower-right corner of the page, click Precheck.
Note
- Before you can start the data synchronization task, a precheck is performed. 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. Troubleshoot the issues based on the
causes and run the precheck again.
- Wait until the initial synchronization is complete and the data synchronization task
is in the Synchronizing state.
On the Synchronization Tasks page, view the status of the data synchronization task.
