A RetroSearch Logo

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

Search Query:

Showing content from https://cloud.google.com/database-migration/docs/mysql/migration-types below:

Types of migration | Database Migration Service

Types of migration

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


Overview Continuous migration

Continuous (sometimes referred to as ongoing or online) migration is a continuous flow of changes from a source to a destination that follows an initial full dump and load. In the case of a migration, when the time comes to switch to use the destination for reads and writes, perform a

promote

operation. Promotion means that the destination Cloud SQL instance is disconnected from the source, and is promoted from a replica instance to a primary instance.

Continuous migration follows these steps:

  1. Initially, a snapshot is taken of the source database. This incurs a short (under 10 seconds) lockout on the database tables, one at a time, as the dump is created. The source can continue accepting writes.

    You might need to perform additional steps if you're using Amazon RDS and you don't have SUPERUSER privileges. For more information, see Migrating from RDS MySQL without SUPERUSER privileges.

  2. After the initial dump is taken, it's loaded into the destination.

  3. After the load is completed, the ongoing changes (also known as change data capture or CDC) are processed.

    The delay between when a write occurs on the source and the current time is known as the Replication delay.
  4. When the time comes to switch to using the destination, stop writing to the source and initiate a promotion. This allows the application to read and write against the destination database.

  5. Dependent applications can experience downtime for at least the duration of the replication delay at the time of the decision to promote.

One-time migration

This type of migration is a single point-in-time snapshot of the database, taken from the source and applied to the destination. This is essentially a dump and load, where the destination is ready to be used when the load completes. Any applications that depend on the source database can experience downtime during the migration process because there can be no new writes to this database while the migration is in progress.

One-time migration follows these steps:

  1. Stop writing to the source database.

  2. Initiate a dump of the source database.

  3. After the dump is complete, it's loaded into the destination. When the load is completed, a promotion is initiated automatically. The destination database now becomes the primary database, and dependent applications should read and write to it.

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."],[[["Continuous migration involves a full initial data dump and load, followed by an ongoing flow of changes from the source to the destination, with a `promote` operation switching the destination to primary."],["Continuous migration requires a snapshot to be taken, with a brief lockout on database tables, followed by an initial load, and then ongoing changes being captured and processed until promotion."],["One-time migration is a single snapshot of the source database, transferred to the destination as a one-time dump and load, where the destination is ready for use after the load is finished."],["One-time migration requires no further work after the load is completed, and writes to the source must be stopped."],["Dependent applications might encounter downtime during the replication delay in continuous migration or during the entire migration process in a one-time migration."]]],[]]


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