HPE Shadowbase Zero Downtime Migration (ZDM)

HPE Shadowbase ZDM software provides continuous availability, eliminates planned downtime (no downtime for the application during migration), and removes business risk from application upgrades.

HPE Shadowbase ZDM:

  • Provides continuous application services to all end users for complex migrations, upgrades, and conversions to achieve no application downtime:
    • Migrates to new hardware (homogeneous or heterogeneous)
    • Upgrades the operating system or database software
    • Converts from an older to a newer application version
  • Avoids the risk of classic big-bang conversions and outage windows:
    • Fully verifies the new environment before deploying
    • Cuts over users either gradually or at all at once to a known-working environment

Figure 1 illustrates how HPE Shadowbase software can achieve zero application downtime via a multi-node upgrade or a single-system upgrade. In both cases, the new (upgraded) database and the current database are kept synchronized by Shadowbase data replication, so that if an issue arises with the new system, it is easy to revert to the current system without incurring any downtime. This configuration also enables the stepwise migration of users from the current to the new system, enabling a controlled and safe incremental migration, as opposed to the risky, all-at-once big-bang approach. All possible migration steps are not represented by this figure; for more details, please refer to our white paper, Using HPE Shadowbase to Eliminate Planned Downtime via Zero Downtime Migration.

Diagram of HPE Shadowbase zero application downtime. Two ZDM examples, one a multi-node upgrade, the other a single-system upgrade. For a full image description, please see the paragraph that starts with "Figure 1 illustrates."

Figure 1 — HPE Shadowbase Zero Application Downtime

Solution Benefits:

  • Capacity Expansion — expand with symmetric or asymmetric nodes
  • Load Balancing — redistribute users and partitions across the network
  • Disaster Tolerance and Data Locality — disperse nodes geographically
  • Migrations — in increments, or initially to an active/active(A/A) environment
  • Operations — risk-free failover/recovery testing, or run and maintain unattended sites

Related Case Studies:
Related White Papers:
Related Solution Brief: