This topic describes how to upgrade the synchronization topology of a data synchronization instance from one-way to two-way in the Data Transmission Service (DTS). In this case, the requirements of business development are met. You can also configure the data synchronization instance in the reverse direction to achieve more efficient and comprehensive data interaction.
Prerequisites
The following conditions must be met when you upgrade synchronization topology from one-way to two-way:
Important
This feature is in canary release and available only to specific customers.
A instance to be upgraded is one-way synchronization topology, that is, Synchronization Topology is One-way Synchronization.
The types and versions of source database and destination database of the instance to be upgraded are compatible with that of two-way synchronization instance. For example, the source database and destination database of the instance run MySQL 8.0.
For more information, see Supported instances section of this topic and Overview of data synchronization scenarios.
The Status of the instance to be upgraded is Running.
The destination database of the instance to be upgraded has the required permissions.
For more information, see Permissions of destination database account section of this topic.
Supported instances
Source Database | Destination Database |
Source Database | Destination Database |
MySQL | MySQL and PolarDB for MySQL |
PolarDB for MySQL | MySQL and PolarDB for MySQL |
PostgreSQL | PostgreSQL and PolarDB for PostgreSQL |
PolarDB for PostgreSQL | PolarDB for PostgreSQL |
PolarDB (Compatible with Oracle) | PolarDB (Compatible with Oracle) |
Permissions of destination database account
Type | Required Permissions | Account Creation and Authorization Method |
Type | Required Permissions | Account Creation and Authorization Method |
MySQL | ApsaraDB RDS for MySQL Privileged account. Self-managed MySQL database SELECT, REPLICATION CLIENT, REPLICATION SLAVE, SHOW VIEW, and the permissions to create databases and tables.
| |
PolarDB for MySQL | Privileged account. | Create and manage a database account |
PostgreSQL | ApsaraDB RDS for PostgreSQL A privileged account that is the owner of the database. Self-managed PostgreSQL database. Permissions of the superuser role.
| |
PolarDB for PostgreSQL | A privileged account that is the owner of the database. | Create a database account and Database management |
PolarDB (Compatible with Oracle) | A privileged account that is the owner of the database. | Create a database account and Database management |
Usage notes
You can only upgrade the synchronization topology from one-way to two-way. You cannot downgrade the synchronization topology from two-way to one-way.
You cannot upgrade the synchronization topology from one-way to two-way for a data synchronization task between PolarDB-X 2.0 instances.
Procedure
Use one of the following methods to go to the Data Synchronization page and select the region in which the data synchronization instance resides.
Log on to the DTS console.
In the left-side navigation pane, click Data Synchronization.
In the upper-left corner of the page, select the region in which the data synchronization instance resides.
Log on to the DMS console.
In the top navigation bar, move the pointer over Data + AI and choose .
From the drop-down list to the right of Data Synchronization Tasks, select the region in which the data synchronization instance resides.
Find the destination instance.
Choose at the Actions column of the destination instance.
Click OK in the dialog box. The upgrade of the data synchronization instance is completed.
After the instance upgrade is completed, a data synchronization instance in the reverse direction that is Not Configured appears in the lower part of original data synchronization instance.
Configure the data synchronization instance in the reverse direction based on your business requirements.