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.
|Start||Start migration jobs that were created without being started.|
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
Monitor your database server's replication slot and disk size. You can choose to delete the migration job, which will clean all replication slots and network traffic.
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.
If the migration failed and isn't recoverable, or was stopped during a full dump, then it can be restarted from the beginning.
If the replication has failed because of an error on one or more source or destination databases, then restarting the migration will wipe all data from any destination databases that are impacted by the errors.
If new databases were created on the source PostgreSQL server since starting the migration, then restarting the migration will also replicate the new databases into the destination instance.
|Delete||A migration job can be deleted. The outcome depends on the status of
|Promote||See Promote a migration.|
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 2023-06-08 UTC.