Promote a migration

MySQL   |  PostgreSQL   |  PostgreSQL to AlloyDB

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:

1. Go to the Migration jobs page.

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

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

4. After the replication delay is at a minimum, you can initiate the promotion. To avoid data loss, make sure to:
   1. Stop all writes, running scripts, and client connections to the source database. The downtime period begins here.
   2. Wait until the replication delay is at zero, which means that the migration job has processed all outstanding changes.
   3. In the Migration job details page, click PROMOTE.
   4. In the Promote migration job? window, click PROMOTE.
   You can promote a migration even if the replication delay isn't at zero. This can reduce the database downtime, but may affect the accuracy of the data in the destination.

5. The migration job stops reading from the source and the substatus is Promote in progress. At this point, you cannot stop or undo the promotion process.
6. The destination instance is promoted to a primary writeable instance. The migration job status is Completed.
7. (Optional) For sources that use the 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.
8. The application can now be connected to the Cloud SQL instance and the migration job can be safely deleted.

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.

Previous

Set up cascading read replicas

Next

Review connection profiles

Send feedback