Switch Your Data Replication Engine to HPE Shadowbase Solutions
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
Why Replace an Existing Data Replication Solution?
- Support is unsatisfactory
- Pricing is extremely expensive
- Functionality is limited
- Platform support isn’t keeping pace with recent releases
- Mature or discontinued without new features
- Complicated to understand/difficult to retain knowledgeable staff
- New version installation (a complete software upgrade) is required, and the new version is inadequate
- Unsupported on current or new hardware
- Supplier is not vendor-approved and sold by HPE
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:
- Will the Shadowbase solution work as expected?
- Will the Shadowbase solution fill all of the customizations of the existing software?
- Is Shadowbase replication fast enough to keep pace with the application?
- Is Shadowbase software easy to learn and maintain?
- How will the migration occur without interrupting the mission-critical application?
- Full business continuity protection is necessary during the migration in the event production fails, so how does the production and backup keep synchronized during the migration?
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”
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:
- the least amount of impact to existing production,
- far less risk than the other approaches,
- and only affects the production system very late in the migration process (at the actual point of cutover).
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
- HPE’s strategic go-forward data replication solution
- Provides zero downtime migrations, including “platform refreshes”
- Performs successful deployments at hundreds of worldwide mission-critical application environments
- Fully supports Enscribe, SQL/MP, SQL/MX, NonStop X (x86), and virtualized HPE NonStop platforms
- Easy ordering process within normal HPE software licensing channels
- Favorable comparison pricing to other solutions, and “we are easy to do business with”
- Outstanding global support provided by HPE GNSC
- Professional Services provided by HPE or its regional reseller/system integrator
- Competing solutions are often supposedly bundled into an “enterprise-wide” license
- Watch for an “annual audit” and backward/forward charges for usage, and have the vendor unbundle the license
- Perform an HPE Shadowbase Proof-of-Concept/Trial to move the project forward
Many Companies Have Migrated
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 requires Expand (TCP/IP is not supported).
- RDF is limited to:
- Asynchronous active/passive (only) business continuity replication
- Synchronous active/passive (only) business continuity replication (via RDF/ZLT, which requires XP SAN arrays – a distance-limited solution)
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:
- Sizzling-Hot-Takeover (SZT) and Active/Active Replication
- Zero Data Loss (ZDL) and Synchronous Replication (does not require XP SAN arrays)
- Data Integration and Application Integration
- Data Transformation
- Replication to Non-NonStop
- Platforms (e.g., Linux, Windows, Unix, Solaris, AIX, and HP-UX)
- Databases (e.g., Oracle, SQL Server, DB2, SAP HANA, Sybase, and MySQL)
- Communications over Expand and TCP/IP
- Shadowbase User Exits provide extensibility
- Add custom code snippets into the replication engine
- Compare and Repair Data
- Identify source and target database discrepancies
- Validate that the source and target match (repair the target database when they do not)
- Run while database(s) are actively being read and updated (does not require an outage)
- Intelligent false-positive recognition (e.g., mismatch in databases from replication latency)
- HPE Shadowbase Software Essentials (tools and utilities for data management)
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.