Updated on 2024-03-28 GMT+08:00

Editing Synchronization Objects

This section describes how to edit synchronization objects in an incremental synchronization task.

  • For a normal incremental task, you can edit synchronization objects by adding or deleting databases and tables to be synchronized.
  • For a failed incremental task, you can edit synchronization objects by changing the objects to be synchronized. If an incremental synchronization fails due to incorrect synchronization objects, you can use this function to remove the databases or tables and submit the task again to restore the task.
  • During synchronization object editing of a failed incremental task, do not resume or reset the synchronization task before it is started. Otherwise, the synchronization object cache will be cleared, and the synchronization objects fail to be edited.

    For details about the synchronization scenarios where synchronization objects can be edited in the incremental phase, see Real-time Synchronization Scenarios Where Synchronization Objects Can Be Edited.

Prerequisites

You have logged in to the DRS console.

Method 1

  1. On the Data Synchronization Management page, locate the target synchronization task and click Edit in the Operation column.

    Figure 1 Editing synchronization objects

  2. On the Set Synchronization Task page, change the objects to be synchronized and click Next.

    • You can search the expanded database using regular expressions.
    • If the object name contains spaces, the spaces before and after the object name are not displayed. If there are multiple spaces between the object name and the object name, only one space is displayed.
    • The name of the selected synchronization object cannot contain spaces.

  3. On the Process Data page, set rules for a new table by referring to Processing Data.

    The processing rules for a synchronized table cannot be modified.

  4. On the Check Task page, check the synchronization task.

    • If any check fails, review the cause and rectify the fault. After the fault is rectified, click Check Again.

      For details about how to handle check failures, see Solutions to Failed Check Items in Data Replication Service User Guide.

    • If all check items are successful, click Next.
      Figure 2 Pre-check

      You can proceed to the next step only when all checks are successful. If there are any items that require confirmation, view and confirm the details first before proceeding to the next step.

  5. On the Confirm Task page, specify Start Time, confirm that the configured information is correct, and click Next.
  6. Go back to the Data Synchronization Management page. In the synchronization task list, the current task status is Incremental synchronization, and a subtask in the Modifying task status is generated. After the subtask change is complete, incremental synchronization is performed for the edited synchronization objects.

Method 2

  1. On the Data Synchronization Management page, click the target synchronization task.
  2. On the displayed page, click the Synchronization Mapping tab and click Edit to the right of the synchronization object.
  3. Perform 2 to 6 from method 1.

Real-time Synchronization Scenarios Where Synchronization Objects Can Be Edited

To the cloud
  • MySQL -> MySQL
  • MySQL -> GaussDB(for MySQL)
  • MySQL -> GaussDB Primary/Standby
  • MySQL -> GaussDB Distributed
  • MySQL->MariaDB
  • DDM -> DDM
  • DDM -> GaussDB(DWS)
  • Oracle -> MySQL
  • Oralce -> PostgreSQL
  • Oracle -> GaussDB Primary/Standby
  • Oracle -> GaussDB Distributed
  • Oracle -> GaussDB(DWS)
  • Oracle -> GaussDB(for MySQL)
  • PostgreSQL -> PostgreSQL
  • PostgreSQL -> GaussDB Distributed
  • PostgreSQL -> GaussDB Primary/Standby
  • MariaDB -> MariaDB
  • MariaDB->MySQL
  • MariaDB->GaussDB(for MySQL)
  • DB2 for LUW -> GaussDB Distributed
  • DB2 for LUW -> GaussDB Primary/Standby
  • DB2 for LUW -> GaussDB(DWS)
  • Microsoft SQL Server -> GaussDB(DWS)
  • Microsoft SQL Server -> GaussDB Distributed
  • Microsoft SQL Server -> GaussDB Primary/Standby
  • GaussDB(for MySQL) -> GaussDB(for MySQL)
From the cloud
  • MySQL -> MySQL
  • MySQL -> CSS/ES
  • MySQL -> Kafka
  • MySQL -> Oracle
  • MySQL->MariaDB
  • DDM -> Kafka
  • DDS -> Kafka
  • PostgreSQL -> PostgreSQL
  • PostgreSQL -> Kafka
  • MariaDB -> MariaDB
  • GaussDB(for MySQL) -> MySQL
  • GaussDB(for MySQL) -> CSS/ES
  • GaussDB(for MySQL) -> GaussDB(DWS)
  • GaussDB(for MySQL) -> Oracle
  • GaussDB(for MySQL) -> Kafka
  • GaussDB Primary/Standby -> MySQL
  • GaussDB Primary/Standby -> Oracle
  • GaussDB Primary/Standby -> Kafka
  • GaussDB Primary/Standby -> GaussDB(DWS)
  • GaussDB Primary/Standby -> GaussDB Distributed
  • GaussDB Primary/Standby -> GaussDB Primary/Standby
  • GaussDB Distributed -> MySQL
  • GaussDB Distributed -> Oracle
  • GaussDB Distributed -> Kafka
  • GaussDB Distributed -> GaussDB(DWS)
  • GaussDB Distributed -> GaussDB Distributed
  • GaussDB Distributed -> GaussDB Primary/Standby
  • Microsoft SQL Server->Kafka
Self-built -> Self-built
  • MySQL -> CSS/ES
  • MySQL -> Kafka
  • MySQL -> GaussDB Primary/Standby
  • Oracle -> Kafka
  • Oracle -> GaussDB Primary/Standby
  • Oracle -> GaussDB Distributed
  • PostgreSQL -> Kafka
  • DB2 for LUW -> GaussDB Distributed
  • DB2 for LUW -> GaussDB Primary/Standby
  • GaussDB Primary/Standby -> Oracle
  • GaussDB Primary/Standby -> Kafka
  • GaussDB Primary/Standby -> GaussDB Primary/Standby
  • GaussDB Distributed -> Oracle
  • GaussDB Distributed -> Kafka
  • GaussDB Distributed -> GaussDB Distributed
  • Microsoft SQL Server->Kafka