Reviewing a migration job
Go to the Migration jobs page in the Google Cloud console.
Select a migration job to see its details page, which includes:
- Migration job metadata, such as the display name, ID, migration type, source connection profile, source database engine, destination, connectivity method, date and time that the migration job was created, and how long the migration job is running.
- Replication delay: The lag (in seconds) between the existing data in the destination database and the data in the source database being replicated into the destination database.
- Storage usage: The amount of storage used.
- Migration job status and substatus/additional information. Different actions are available depending on the migration job's status and substatus.
Migration job statuses
The following table lists, describes, and provides user actions for migration job statuses for Database Migration Service.
|Migration job status||Description||Possible substatus||Possible user actions|
|Not started||The migration job is ready but still not running. This status is relevant if the migration job was created but wasn't started.||None.||Start. Delete.|
|Starting...||The migration job is in the process of being started. This is an intermediate status that occurs when a migration job is
started. Starting the migration job takes between a few seconds and a few
minutes. The status changes to
|Running||The migration job is actively running.||Full dump, CDC, promote in progress. For MySQL RDS or sources with no SUPERUSER privileges: Waiting for source writes to stop, Preparing the dump.||Stop. Promote. Delete.|
|Completed||The migration job is completed. In the continuous migration type, this occurs after a successful promotion. In the one-time migration type, this occurs after the full dump phase is complete.||None.||Delete.|
|Failed||The migration job failed because of an error. Based on the type of error, the migration job may resume automatically, after the issue is fixed. Otherwise, the failure is unrecoverable, and the migration job needs to be restarted.||The last status before the migration job failed. Failed in CDC, Failed in full dump.||Restart. Delete. Promote.|
|Restarting||The migration job is in the process of being restarted.||None.||Delete.|
|Stopped||The migration job is stopped.||The last status before the migration job has stopped: Stopped in CDC, Stopped in full dump.||If in the CDC phase, then the migration job can be resumed, promoted, or deleted. If in the full dump phase, then the migration job can be restarted or deleted.|
|Resuming||The migration job is in the process of being resumed.||None.||Delete.|
|Stopping...||The migration job is in the process of stopping after
Migration job metrics
The following table lists and describes migration job metrics for Database Migration Service.
|Replication delay||Represents how much time the destination database is behind the source database. Use this metric when considering performing a promotion of a continuous migration. Replication delay should be zero at the time of the promotion in order to avoid data loss. Note this metric is only relevant in the CDC phase. For more information on job promotion, see Promote a migration.|
|Storage usage||Reflects how many GB are currently being used by the destination Cloud SQL instance. Use this metric to get a rough indication of migration job progress.|