Help Center> Data Replication Service> Real-Time Synchronization> Task Management> Task Life Cycle> Resetting a Synchronization Task
Updated on 2023-04-26 GMT+08:00
View PDF

Resetting a Synchronization Task

During real-time synchronization, you can reset the synchronization tasks in one of the following statuses so that you do not need to configure the tasks again.

  • Paused
  • Failed

For details about the synchronization scenarios where synchronization tasks can be reset, see Real-time Synchronization Scenarios Where Synchronization Tasks Can Be Reset.

  • For a many-to-one synchronization task, only the parent task can be reset.
  • For a MySQL many-to-one synchronization task, only the subtask can be reset.
  • Resetting a task does not clear the destination database. You can determine whether to clear the destination database based on your service requirements.
    • Full and full+incremental tasks: To ensure data consistency before and after synchronization, manually clear the destination database and reset the task. After the task is reset, full synchronization is performed again. You do not need to configure the task again.
    • Incremental tasks: Only incremental data is synchronized. You can directly reset the task without clearing the destination database.

Prerequisites

You have logged in to the DRS console.

Method 1

  1. In the task list on the Data Synchronization Management page, locate the target task and click Reset in the Operation column.
  2. In the displayed dialog box, check the synchronization task again.

    If a many-to-one synchronization task fails to be reset, click the name of the failed subtask in the failure details to view the failure cause of the task.

  3. After the check is complete and the check success rate is 100%, click Start to submit the synchronization task again.

Method 2

  1. On the Data Synchronization Management page, click the target synchronization task name in the Task Name/ID column.
  2. On the displayed page, click the Synchronization Progress tab, and click Reset in the upper left corner.
  3. Perform 2 to 3 from method 1.

Real-time Synchronization Scenarios Where Synchronization Tasks Can Be Reset

To the cloud
  • MySQL->MySQL
  • MySQL->PostgreSQL
  • MySQL->GaussDB(for MySQL)
  • MySQL -> GaussDB primary/standby
  • MySQL->GaussDB(DWS)
  • PostgreSQL->PostgreSQL
  • DDM->DDM
  • Oracle->MySQL
  • Oracle->GaussDB(for MySQL)
  • Oracle->GaussDB(DWS)
  • Oracle->PostgreSQL
  • Oracle -> GaussDB primary/standby
  • Oracle -> GaussDB distributed
  • DB2 for LUW -> GaussDB primary/standby
  • DB2 for LUW -> GaussDB distributed
  • DB2 for LUW->GaussDB(DWS)
  • TiDB->GaussDB(for MySQL)
  • Microsoft SQL Server->GaussDB(DWS)
  • Microsoft SQL Server -> GaussDB primary/standby
  • Microsoft SQL Server -> GaussDB distributed
  • Microsoft SQL Server->Microsoft SQL Server
  • MongoDB->DDS
From the cloud
  • MySQL->MySQL
  • MySQL->CSS/ES
  • MySQL->Oracle
  • MySQL->Kafka
  • DDM->DDM
  • DDS->MongoDB
  • GaussDB(for MySQL)->Kafka
  • GaussDB(for MySQL)->CSS/ES
  • GaussDB(for MySQL)->Oracle
  • GaussDB(for MySQL)->MySQL
  • GaussDB primary/standby -> GaussDB primary/standby
  • GaussDB primary/standby -> GaussDB distributed
  • GaussDB primary/standby -> GaussDB(DWS)
  • GaussDB primary/standby -> MySQL
  • GaussDB primary/standby -> Oracle
  • GaussDB primary/standby -> Kafka
  • GaussDB distributed -> GaussDB distributed
  • GaussDB distributed -> GaussDB primary/standby
  • GaussDB distributed -> GaussDB(DWS)
  • GaussDB distributed -> Oracle
  • GaussDB distributed -> Kafka
  • PostgreSQL->Kafka
Self-built -> Self-built
  • MySQL->Kafka
  • MySQL->CSS/ES
  • Oracle-> Kafka
  • Oracle -> GaussDB primary/standby
  • Oracle -> GaussDB distributed
  • GaussDB primary/standby -> Oracle
  • GaussDB primary/standby -> Kafka
  • GaussDB distributed -> Oracle
  • GaussDB distributed -> Kafka
  • PostgreSQL->Kafka
Parent topic: Task Life Cycle