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.
- Migration job status and substatus, and additional information. Different actions are available depending on the migration job's status and substatus.
Migration job statuses
Overview
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. |
None. | Delete. |
| Running | The migration job is actively running. | CDC, Promote in progress. | Stop. Promote. Delete. |
| Completed | The migration job is completed. In the continuous migration type, this occurs after a successful promotion. | 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. | If in the CDC phase, then the migration job can be resumed, promoted, 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 Stop was
invoked. This is an intermediate status that occurs when a user stops a
migration job. Stopping the job takes around a
minute, during which the status is Stopping. Subsequently, the status
changes to Stopped. |
None. | Delete. |
Migration job metrics
Overview
The following table lists and describes migration job metrics for Database Migration Service.
| Migration metric | Description |
|---|---|
| Replication delay | 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 change data capture (CDC) phase. For more information on job promotion, see Promote a migration. |
| Storage usage in total bytes | Reflects how many GB are currently being used by the destination AlloyDB for PostgreSQL instance. Use this metric to get a rough indication of migration job progress. |
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-01-30 UTC.