Review a migration job

MySQL | PostgreSQL | PostgreSQL to AlloyDB

To review details about the migration job, follow these steps:

In the Google Cloud console, go to the Migration jobs page.

Go to Migration jobs
On the Jobs tab, click the name of your migration job.

The migration job details page opens.
View the migration job metadata, such as the migration job 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.
On the Databases tab, when the migration job is running, you can view the following information for each database that you selected for migration:
- Name. The name of your migration job.
- Status. For more information, see Migration job statuses.
- Phase. The migration phase indicates whether the migration job is performing a full dump or a change data capture (CDC) operation.
- Replication delay. For more information, see Migration job metrics.
- Errors. The errors that occurred during the migration job.
- View logs. Links to the logs for the migration job.
On the Monitoring tab, from the View list, select one of the following options to view the metrics:
- Aggregated shows the metrics diagrams for all databases included in your migration job.
- Databases shows the metrics diagrams for databases that you selected for migration.

Migration job statuses

MySQL | PostgreSQL | PostgreSQL to AlloyDB

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.
Running with errors	This status means that Database Migration Service encountered errors with your migration. Faulty operations will be retried, and errors clear automatically once the underlying issue is resolved. Database Migration Service continues migrating data unaffected by the error.	CDC.	Stop. Restart. Promote (when the job is in the CDC phase).
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

MySQL | PostgreSQL | PostgreSQL to AlloyDB

Database Migration Service collects and displays migration job metrics that represent the health and progress of your data migration process.

The following table lists and describes the migration job metrics that you can view on the migration job details page. You can view the following metrics for all databases included in your migration job or only the databases that you selected for migration:

Migration metric	Description
Replication delay	Use this metric when you consider 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 being used by the destination AlloyDB for PostgreSQL instance. Use this metric to get a rough indication of migration job progress.

You can view all Database Migration Service Cloud Monitoring metrics that relate to migration job performance in the Metrics Explorer. To view each diagram directly in Cloud Monitoring, click More chart options > View in Metrics Explorer.

You can use the following metrics to monitor your migrations:

The migration_job/initial_sync_complete metric indicates when the full dump phase is complete for a specific database or the entire migration job. You can view this metric on a migration level or a database level by applying the database label. If the database label is present, the metric value is for that particular database. If the label is not populated, the metric value is for the entire migration job.
The migration_job/max_replica_bytes_lag metric shows the size of log data that are not yet replicated to the destination. You can view this metric on a migration level or a database level by applying the database label. If the database label is present, the metric value is for that particular database. If the label is not populated, the metric value is for the entire migration job.
The migration_job/max_replica_sec_lag metric shows the time (in seconds) that the destination database is behind the source database. You can view this metric only at the migration level.

For more information about the Metrics Explorer, see Create charts with Metrics Explorer.

Create a source connection profile

Manage migration jobs