COVID-19 Update — We are available to assist you during these trying times. Please contact us for assistance.

Switch Your Data Replication Engine to HPE Shadowbase Solutions

On and off switch

Data Replication is Critical in Today’s IT Landscape

It serves multiple purposes:

Therefore, most IT installations already have one or more data replication solutions installed on their systems to meet these needs.

Solution Brief: HPE Shadowbase Zero Downtime Migration

Finger on CDWhy replace an existing data replication solution?

Article: A Bank’s Crisis Migration to a New Data Replication Solution


As enterprises evolve, tech debt grows. Many IT teams understand the need to migrate, but have reservations:

The result: being stuck with an unsatisfactory solution

Unfortunately, many IT teams think that these conditions cannot be met and have no choice. They believe the potential costs in terms of downtime and data loss are too great to risk migrating.

Easily Migrate to HPE Shadowbase Solutions

Shadowbase Zero Downtime Migration (ZDM)

Fortunately, by design, HPE Shadowbase software offers several proven methods, approaches, and techniques to meet an enterprise’s requirements. A migration from an existing data replication product to Shadowbase solutions, or to a new Shadowbase version, can be undertaken while completely avoiding the risks associated with application service outage and data loss.

White Paper: Switching Replication Engines with Zero Downtime and Less Risk

White Paper: Using HPE Shadowbase Software to Eliminate Planned Downtime via Zero Downtime Migration

Methods for risk-free, successful migrations

By using one of the following methods, performing the migration is possible without taking either the application or the database offline – improving availability over other methods that do require an outage, and eliminating the inherent risk normally associated with this type of change.

The sections below review different techniques for leveraging multiple systems to perform the migration process, from a two-node “production/standby” environment, to a three-node “production/standby with a spare system” environment, to a four-node “platform refresh” environment.

Two nodes or “version independence”

2-system architecture

Figure 1 — Two-Node Approach

Version Independence completely avoids inter-operating between different software products or versions. This scalable method works well for companies with only two systems available using proof and verification steps for the migration, where the migration can occur over time and encompass an unlimited number of files and tables. This solution works well for production environments with limited resources — a production system and typically the standby system (assuming the environment has a disaster recovery solution in place).

Three nodes or “leveraging a spare system”

Figure 2 — Three-Node Approach

A better solution exists for environments with three nodes. This solution keeps the upgrade tasks, including the proof and verification steps, independent from the production environment until much later in the migration process.

Using this approach, an old disaster recovery standby (DRS) system is always available for production failover with the original configuration and working database while the new environment is built, tested, and prepared for the cutover.

Figure 3 — Four-Node Approach

Four nodes or “platform refresh”

For companies seeking a full hardware refresh of both the original production and DRS systems, an entirely new production and DRS configuration can be deployed and tested across four nodes. This solution is more complex to initially set up and configure, but it offers:

Note: Each of these approaches can be used with uni-directional and bi-directional replication environments.

HPE Shadowbase Software: The preferred solution with many benefits

 Many enterprises have migrated to HPE Shadowbase Software

 Case Studies

 Use Cases

HPE Remote Database Facility (RDF) migration

IT teams with HPE RDF should migrate to HPE Shadowbase Solutions. RDF was matured by HPE (October 2018), which means that for now the product is still supported; however, it will not be enhanced (no new additional functionality).

RDF limitations:

Fortunately, HPE Shadowbase products provide all of the RDF capabilities, plus additional features. HPE Shadowbase software should be actively considered by all RDF sites; many of which have already made the switch.

Additional HPE Shadowbase features:

Migrating HPE NonStop: Non-audited data, programs, and script files

Other HPE products are available to assist migrating to HPE Shadowbase solutions:

Note: Replacing a competing product with HPE Shadowbase software may require HPE Professional Services to replace existing customizations. Please contact us on how to assess your project.