A large Japanese e-commerce company provides 24×7 shopping on a high-volume Java* cell phone application hosted by a four-node Oracle RAC in a Linux cluster (Figure 1). Oracle was used for the authorization system of a new digital money service with 300 tables.
HPE decided to use HPE Shadowbase software to satisfy the ZDM requirements, and enlisted Gravic to assist.
In the original architecture, the provider used a custom tool to perform monthly batch backups from the production to the Cold DR system.
A. It started capturing the production database changes with HPE Shadowbase software to an interim staging database.
B. It performed its normal monthly backup from the old production environment to the Cold DR site.
C. It used Ispirer for the initial load of the data from the Cold DR site to the new production environment.
D. It then started HPE Shadowbase replication of the change data from the staging database to the new production environment.
E. For subsequent synchronization of the data between the systems, the customer relied on HPE Shadowbase Log Source for Oracle to continue to read the Oracle logs from the old production environment to push the database change data to the staging database server. It then replayed the changes from there to the new production environment.
F. During the project, HPE Shadowbase software was installed on the old production environment (to capture the database changes), the intermediate Linux staging database server (to store and forward the database changes), and the new NonStop production environment (to apply the database changes into the new production database).
Note: When it came time to redeploy the payments application on NonStop X, HPE worked with the customer to convert all SQL statements using SQLWays from Ispirer – a company that specializes in providing tools to better facilitate database migrations converting database schema (DDL), data and server-side business logic from Oracle.
According to HPE, “After completing the data replication, the customer migrated the online application from old Oracle systems to new NonStop SQL in 15 minutes.”
Step 4: Copy the Change Data from the Staging Database to the New Production Database for Synchronization
Step 5: Migrate the Users to the New Production System, Preserving the Old Environment (in Case of Fail-back)
Contact us or your HPE Shadowbase representative, and learn how Shadowbase software will benefit you.
Related White Paper: Using HPE Shadowbase Software to Eliminate Planned Downtime via Zero Downtime Migration
Related Solution Brief: HPE Shadowbase Zero Downtime Migration
*Java is a registered trademark of Oracle and its affiliates