Stay organized with collections Save and categorize content based on your preferences.
Promotion means that the destination Cloud SQL instance is disconnected from the source, and is promoted from a replica instance to a primary instance.
For continuous migrations, you can initiate the promotion process after it's time to move reads and writes to the destination.
For one-time migrations, the Cloud SQL instance is ready as soon as the dump and load is complete, and user-invoked promotion isn't required.
To promote a migration without loss of information, follow these steps:
Click the migration job that represents the migration that you want to promote. The Migration job details page appears.
After the full dump phase has completed and the migration job is in CDC phase, the option for promotion is available.
Immediately after transitioning to the CDC phase, depending on the size of the dump, there may be a long replication delay because the Cloud SQL destination instance catches up on changes that occurred during the dump and load.
Wait for the replication delay to trend down significantly, ideally on the order of minutes or seconds. The replication delay is available for review on the migration job page.
Promote in progress. At this point, you cannot stop or undo the promotion process.Completed.pg_cron extension: The pg_cron extension (or any cron settings associated with the extension) isn't migrated by Database Migration Service, but it is supported in Cloud SQL for PostgreSQL destinations. If you use the pg_cron extension in your source databases, you can re-install it on your destination instance.Migration jobs that have failed or were manually stopped during CDC phase can be promoted, but this may mean a gap between the data on the source and the destination.
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."],[[["Promotion of a migration job turns the destination Cloud SQL instance from a replica into a primary instance, disconnecting it from the source."],["For continuous migrations, promotion should be initiated after the decision to switch reads and writes to the destination has been made, while one-time migrations are ready after the dump and load process completes."],["Before promoting, it's crucial to stop all writes and connections to the source database and wait for the replication delay to reach zero to avoid data loss."],["The promotion process can be initiated in the Migration job details page by clicking \"Promote,\" and once started, it cannot be stopped or reversed."],["If the `pg_cron` extension is used in the source database, it is not migrated by Database Migration Service, but can be reinstalled on the destination instance after promotion."]]],[]]
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