Switching Replication Engines with Zero Downtime and Less Risk

Updating a Data Replication Engine

Sometimes it is necessary to change or update a data replication engine. Switching replication engines with zero downtime is a topic of immense complexity.

• A zero downtime migration will impose no downtime on either applications or users.
• The migration can take place during normal working hours and occur over an extended time, while the backup database is always available and fully synchronized with the production database.

Therefore, application availability can be ensured during the migration process.

Simplify Switching Live Replication Engines with Shadowbase Zero Downtime Migration (ZDM)

Customers have been using HPE Shadowbase Zero Downtime Migration (ZDM) for decades to upgrade their applications, database schema formats, file and table locations (or indices), operating systems, and perform a hardware refresh.

In these papers, we discuss how a data replication engine can be changed or upgraded without taking either the application or the database offline (of course, this approach also works in those simpler cases where an application outage is allowed).

Article:

Part 1 — Redundant Systems, Changing the Replication Engine, Interoperating Versions, and Version Independence

Part 2 — Version Independence Approach and how to Protect the Old Production Along with Standby Systems During the Upgrade

Part 3 — Various Methods to Upgrade While Avoiding Data Corruption or Data Oscillation (solving the so-called jagged edge problem)

White Paper:

Switching Replication Engines with Zero Downtime and Less Risk