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.

- 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.
- If the synchronization objects contain tables without primary keys, temporary tables prefixed with drs_ may exist after resetting a task during full synchronization. You need to manually delete the temporary tables.
Prerequisites
You have logged in to the DRS console.
Method 1
- In the task list on the Data Synchronization Management page, locate the target task and click Reset in the Operation column.
- 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.
- After the check is complete and the check success rate is 100%, click Start to submit the synchronization task again.
Method 2
Real-time Synchronization Scenarios Where Synchronization Tasks Can Be Reset
- MySQL->MySQL
- MySQL->PostgreSQL
- MySQL->TaurusDB
- MySQL -> GaussDB Centralized
- MySQL -> GaussDB Distributed
- MySQL->GaussDB(DWS)
- MySQL->MariaDB
- PostgreSQL->PostgreSQL
- PostgreSQL->GaussDB(DWS)
- PostgreSQL -> GaussDB Centralized
- PostgreSQL -> GaussDB Distributed
- DDM->MySQL
- DDM->DDM
- DDM->GaussDB(DWS)
- Oracle->MySQL
- Oracle->TaurusDB
- Oracle->GaussDB(DWS)
- Oracle->PostgreSQL
- Oracle -> GaussDB Centralized
- Oracle -> GaussDB Distributed
- Oracle->DDM
- DB2 for LUW -> GaussDB Centralized
- DB2 for LUW -> GaussDB Distributed
- DB2 for LUW->GaussDB(DWS)
- TiDB->TaurusDB
- Microsoft SQL Server->GaussDB(DWS)
- Microsoft SQL Server -> GaussDB Centralized
- Microsoft SQL Server -> GaussDB Distributed
- Microsoft SQL Server->Microsoft SQL Server
- Microsoft SQL Server->PostgreSQL
- MongoDB->DDS
- MariaDB->MariaDB
- MariaDB->MySQL
- MariaDB->TaurusDB
- TaurusDB->TaurusDB
- Cassandra->GeminiDB Cassandra
- Dynamo->GeminiDB Dynamo
- MySQL->MySQL
- MySQL->CSS/ES
- MySQL->Oracle
- MySQL->Kafka
- MySQL->MariaDB
- DDS->MongoDB
- DDS->Kafka
- DDM->MySQL
- DDM->Oracle
- DDM->Kafka
- TaurusDB->Kafka
- TaurusDB->CSS/ES
- TaurusDB->Oracle
- TaurusDB->MySQL
- TaurusDB->GaussDB(DWS)
- GaussDB Centralized -> GaussDB Centralized
- GaussDB Centralized -> GaussDB Distributed
- GaussDB Centralized -> GaussDB(DWS)
- GaussDB Centralized -> MySQL
- GaussDB Centralized -> Oracle
- GaussDB Centralized -> Kafka
- GaussDB Distributed -> GaussDB Distributed
- GaussDB Distributed -> GaussDB Centralized
- GaussDB Distributed -> GaussDB(DWS)
- GaussDB Distributed -> MySQL
- GaussDB Distributed -> Oracle
- GaussDB Distributed -> Kafka
- PostgreSQL->PostgreSQL
- PostgreSQL->Kafka
- MariaDB->MariaDB
- Microsoft SQL Server->Kafka
- MySQL->Kafka
- MySQL->CSS/ES
- MySQL -> GaussDB Centralized
- MySQL -> GaussDB Distributed
- Oracle-> Kafka
- Oracle -> GaussDB Centralized
- Oracle -> GaussDB Distributed
- GaussDB Centralized -> Oracle
- GaussDB Centralized -> Kafka
- GaussDB Distributed -> Oracle
- GaussDB Distributed -> Kafka
- PostgreSQL->Kafka
- DB2 for LUW -> GaussDB Centralized
- DB2 for LUW -> GaussDB Distributed
- Microsoft SQL Server->Kafka
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot