By checking the migration progress, you can learn about the progress of the corresponding data migration instance. Migration tasks run in the following order: struct migration > full data migration > incremental data migration.
When the status is Migrating struct, it means that the task is migrating the struct. At this time, you need to pay attention to the progress bar of the struct migration. When the progress bar reaches 100%, it means the migration is complete.
When the status is Full data migration started, it means that the task is migrating full data. At this time, you need to pay attention to the progress bar of the full data migration. When the progress bar reaches 100%, it means the migration is complete.
When the status is Incremental data migration started, it means that the task is migrating incremental data. You need to pay attention to the latency of the incremental data migration.
Procedure
On the Instance List page in the Data Migration module, select the corresponding instance, and click the instance ID to go to the Instance Management page.
On the Instance Management page, view the instance status and the migration progress.
Instructions on the Latency of Incremental Data Migration
Formula for calculating the latency: Latency = Current time on the source instance - Time of the latest record for successful migration to the destination instance in the incremental data log of the source instance. The unit is seconds.
No latency: The offset for completing migration through DTS is the same as the latest offset in the source database. All the incremental data generated in the source database is already migrated to the destination database.
Latency-1 ms: After the task is started, no DDL or DML operations are performed on the tables migrated in this task.
Not running: The task does not proceed to the incremental data migration phase, or the task is paused.
Note:
The calculation of the latency depends on the incremental data log of the source database. Therefore, when no DDL or DML operations are performed on the source database for a long time, the latency gradually increases and cannot accurately represent the actual migration latency. To obtain the actual latency, you can run SQL statements on the source database to refresh the metric.