Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://cloud.google.com/database-migration/docs/postgres/migration-job-actions below:

Manage migration jobs | Database Migration Service

Stay organized with collections Save and categorize content based on your preferences.

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.

You can perform some of the actions on migration jobs only, while other actions can be performed also on selected databases in a migration job.

To make the following changes, edit the migration job:

• Change between migrating all databases and specific databases.
• Add or remove databases in any migration state or phase, as many times as you need. When you remove a database, Database Migration Service stops the replication process on that database but doesn't remove it from the destination. You must save the job after each change.
• Edit the data dump parallelism level of a running migration job. You must save and restart the job after you make the changes.

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. However, WAL logs will continue to accumulate in the replication slots, eventually leading to your source database running out of disk space. In addition, Database Migration Service will keep pulling a replication delay, which means that Database Migration Service will continue to consume network traffic.
• If the migration job is stopped during the change data capture (CDC) phase, then you can promote or delete the job.

Monitor the replication slot and disk size of your database server. 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.

• 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.

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-08-07 UTC.

[[["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-08-07 UTC."],[[["Migration jobs can be managed from the migration jobs list or a single migration page, with the ability to perform actions on multiple jobs simultaneously if they share the same status."],["You can edit a migration job to change between migrating all or specific databases, add or remove databases, and adjust the data dump parallelism level, but saving is needed for each change, and a restart is necessary after editing data dump parallelism."],["Stopping a migration job during the full dump phase halts data migration but retains WAL logs and network traffic, whereas stopping during CDC allows for job promotion or deletion."],["Resuming a migration job that was stopped in the CDC phase restarts the replication of accumulated events, and restarting a job from the beginning can wipe data from affected destination databases."],["Deleting a migration job will remove the record from the job list if completed, or it will offer an option to delete the destination instance if the job is in another status."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4