Stay organized with collections
Save and categorize content based on your preferences.
Migrations are often time consuming and complex. It is possible that after the
data migration and cutover, you might face inconsistent performance or issues.
We recommend building in fallback mechanisms to avoid significant impact in case of an error
during migration, allowing you to switch back to the source database with
minimal downtime.
Reverse replication lets you fallback by replicating data written on
Spanner back to your source database. If you need to fallback,
reverse replication lets you point your application to the source database and
continue serving requests without significant downtime.
Your reverse replication process needs to do the following:
Handle changes in data types or content.
Reverse any transformations performed during the migration.
Push the data to the appropriate destination, taking into account
sharding schemes on the source database.
Consider the following high-level approach to building a reverse replication
flow:
Read the changes that occur on Spanner.
(Optional) Disable the forward change data capture (CDC) migration before enabling reverse replication.
Since Spanner is a distributed database, capture and
temporarily order all changes before writing to your source database.
[[["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-28 UTC."],[],[],null,["# Configure cutover and fallback mechanisms\n\nMigrations are often time consuming and complex. It is possible that after the\ndata migration and cutover, you might face inconsistent performance or issues.\n\nWe recommend building in fallback mechanisms to avoid significant impact in case of an error\nduring migration, allowing you to switch back to the source database with\nminimal downtime.\n\nReverse replication lets you fallback by replicating data written on\nSpanner back to your source database. If you need to fallback,\nreverse replication lets you point your application to the source database and\ncontinue serving requests without significant downtime.\n\nYour reverse replication process needs to do the following:\n\n- Handle changes in data types or content.\n- Reverse any transformations performed during the migration.\n- Push the data to the appropriate destination, taking into account sharding schemes on the source database.\n\nConsider the following high-level approach to building a reverse replication\nflow:\n\n1. Read the changes that occur on Spanner.\n2. (Optional) Disable the forward change data capture (CDC) migration before enabling reverse replication.\n3. Since Spanner is a distributed database, capture and temporarily order all changes before writing to your source database.\n4. Write the data to your source database."]]
