Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
On this page

Querying the Synchronization Progress

Updated on 2025-02-17 GMT+08:00

This section describes how to check the synchronization progress of each synchronization object.

  • During the full synchronization, DRS displays the progress overview. You can view the synchronization progress of structures, data, and indexes. The synchronization progress is displayed based on the number of synchronized objects. When the progress reaches 100%, the synchronization is complete. The synchronization of data and indexes is relatively slow.
  • During the full synchronization, you can view the synchronization progress of a specific object and the synchronization details. If the number of objects is the same as that of synchronized objects, the synchronization is complete. You can view the synchronization progress of each object in detail. During incremental synchronization, the progress details are not displayed. You can view the consistency status on the Synchronization Comparison tab.
  • During an incremental synchronization, DRS displays the incremental synchronization delay. You can determine the synchronization status between the source and destination databases based on the delay. If the delay is 0, the source and destination databases are instantaneously consistent, and no new transaction needs to be synchronized.

Prerequisites

You have logged in to the DRS console.

Procedure

  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 Synchronization Progress to view table synchronization progress.

    • Check the synchronization progress in percentage.
      • When a full synchronization is complete, the progress reaches 100%.
      • After the full synchronization is complete, the incremental synchronization starts. You can view the incremental synchronization delay on the Synchronization Progress tab.
      • You can also view the incremental synchronization delay on the Data Synchronization Management page. When the incremental synchronization delay exceeds the preset or default threshold, the value of the incremental synchronization delay is displayed in red in the task list.
      • When the delay is 0s, data in the source database is synchronized to the destination database in real time.
      NOTE:

      "Delay" refers to the delay from when the transaction was submitted to the source database to when it is synchronized to the destination database and executed.

      Transactions are synchronized as follows:

      1. Data is extracted from the source database.
      2. The data is transmitted over the network.
      3. DRS parses the source logs.
      4. The transaction is executed on the destination database.

      If the delay is 0, the source database is consistent with the destination database, and no new transactions need to be synchronized.

      CAUTION:

      Transactions that have been there for a long time without being submitted and frequent DDL operations may result in excessive synchronization delay.

    • View the synchronization progress details. In the Migration Details area, locate the target synchronization object and click View Details in the Operation column to view the synchronization progress.
      NOTE:

      The synchronization progress details only display the data synchronized in the full synchronization and the skipped structures and cannot be updated. The progress details are not displayed after incremental synchronization starts. You can compare synchronization items on the Synchronization Comparison page.

      Figure 1 Synchronization progress details

    • Skip synchronization objects. In the Migration Details area, locate the synchronization object and click View Details in the Operation column. On the displayed page, click Skip and Restart in the Operation column to skip the object.
      NOTE:
      • For a synchronization task from MySQL, MariaDB, TaurusDB, or TiDB, synchronization objects can be skipped during the full synchronization.
      • Migration objects that can be skipped include databases, functions, procedures, table_indexes, table_structure, and views.
      • After a synchronization object is skipped, the task will be resumed. If the task is paused or abnormal, the task will be restarted after you click Skip and Restart.
      • If a task is in the full synchronization state, an object may be synchronized before being skipped. In this case, skipping the object is not applied.
      • After an object is skipped, if operations associated with the object are still performed during subsequent synchronization, the task fails. For example, after table_structure is skipped, the task fails because the object is not found when indexes and data of the table are synchronized.
      • After an object is skipped, the result for a comparison is inconsistent.
      • Skipping table_structure of a table without a primary key will cause data inconsistency. In addition, the task may fail because the table is not found. Perform the operation after confirmation.
      • If a DRS task fails because the table is not found after you skip a table without a primary key, contact O&M engineers for the destination database to create the corresponding table in the destination database based on the table structure of the source database and error log information, and click Resume in the Operation column of the task to submit the task again.

  3. In the MySQL synchronization scenario, you can view the information about the source position and consumed position on the Synchronization Progress tab.

    NOTE:

    The displayed position information is updated every 10 seconds.

    Figure 2 Synchronization position information

  4. In synchronization with Oracle serving as the source, MySQL to Kafka synchronization, and GaussDB to Kafka synchronization, on the Synchronization Progress tab, view the number of DML operations (Insert, Delete, and Update) performed on the source database. In the upper right corner of the Task Monitoring list, refresh the list and view the latest monitoring data.

    Figure 3 Task monitoring

    NOTE:
    1. After you perform the DML operation on the source database and run the commit command to make the operation take effect, the operation data can be displayed in the Task Monitoring list.
    2. DRS collects statistics on the number of operations based on redo logs.
    3. For tables with large object (LOB) data type columns, Oracle records more information in redo logs than the information generated by the actual operations that is performed. The INSERT and UPDATE operations are first performed on non-LOB columns and then on LOB columns. DRS collects statistics only from the redo logs, so the number of recorded operations may be inconsistent with the actual number of changed rows according to operation audit.
    4. The Oracle MERGE statement can be converted into INSERT, UPDATE, and DELETE operations in the redo log. Thus, the number of rows changed by the MERGE statement are increased because the INSERT, UPDATE, and DELETE operations are separately recorded in the redo log.

  1. In the Oracle to GaussDB Centralized or Distributed, GaussDB Centralized to MySQL, GaussDB Distributed to MySQL, Oracle to MySQL (incremental), and Oracle to GaussDB(DWS) (incremental) synchronization scenarios, search for the detailed synchronization object information on the Synchronization Progress tab. The keywords for searching synchronization objects are case sensitive.

    Figure 4 Synchronization details

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback