You can perform actions from the migration jobs list or from the single
migration page. You can perform an action on multiple jobs simultaneously
on migration jobs that all have the same status.
User action
Description
Start
Start migration jobs that were created without being started.
Stop
Stop a running migration job at any time. During either the full dump phase or the CDC phase, the data migration is halted, and the migration job status changes to Stopping and subsequently to Stopped.
If the migration job is stopped during the full dump phase, then you can delete or restart the job.
If the migration job is stopped during the change data capture (CDC) phase, then you can resume, promote, or delete the job.
If the time period between stopping the replication and resuming it is
too long, the log position may be lost and the migration job must be
deleted or recreated.
Resume
If a migration was stopped during the CDC phase, then it can
be resumed. Resuming the migration job resumes replication of the events
that were accumulated during the stopped time.
Restart
If the migration failed and isn't recoverable, or was stopped during a
full dump, then it can be restarted from the beginning.
Restarting the migration wipes all data from the destination instance; then the migration
restarts immediately, including with a new dump. If the dump was manually
provided, then it's highly likely that the restart will fail because the dump will be
out of date.
Delete
A migration job can be deleted. The outcome depends on the status of
the job:
If the migration job status was Completed, then the record is
deleted from the migration job list.
If the migration job was in any other status, then there's an option to
choose to delete the destination Cloud SQL instance/primary pair.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-05 UTC."],[[["You can manage migration jobs from both the migration jobs list and individual migration pages, and you can take simultaneous action on multiple jobs with the same status."],["Migration jobs can be started if they were created but not initially launched, and a running job can be stopped at any time, changing its status to `Stopping` and then `Stopped`."],["If a migration job is stopped during the change data capture (CDC) phase, you have the option to resume it to continue replication, promote it, or delete it, but if stopped for too long, log positions may be lost."],["Restarting a migration job is possible if it failed or was stopped during the full dump phase, which will wipe the destination data and restart from the beginning, but will likely fail if the dump was manually provided."],["Deleting a migration job removes it from the list, and if the job wasn't completed, there is an additional option to delete the destination Cloud SQL instance/primary pair."]]],[]]