Credit Card Application Availability to Survive Disasters

  • Copy link to clipboard
  • Email link
  • Print

Situation

The largest U.S. processor of credit card transactions provides ATM and point-of-sale (POS) card management services for a variety of financial and commercial firms on HPE NonStop systems.

Problem

  1. The original configuration was vulnerable to failure and needed an easy to implement and reliable disaster recovery solution.
  2. The customer required flexibility in the database mappings to allow for differing file/table partitioning layouts between the source and target systems.

Solution

Diagram of a credit card application posting its transactions to an active NonStop database, with Shadowbase uni-directional replication sending the transaction changes from the active database to the passive database. If the active NonStop fails for some reason, users are connected to the passive database by the credit card company's IT team.

Figure 1 — HPE Shadowbase Active/Passive Disaster Recovery Architecture

Figure 1 depicts the processor’s new architecture: the CMA users update the active, HPE NonStop source server, and Shadowbase uni-directionally replicates the database changes to the passive, HPE NonStop target server. If the primary system fails, the IT team can disconnect the users from the active server, start the applications on the target node, and connect them to the passive backup server.

Outcomes

HPE Shadowbase Products of Interest

Contact us or your HPE Shadowbase representative, and learn how Shadowbase software will benefit you.

Further Reading

Related White Paper: Choosing a Business Continuity Solution to Match Your Business Availability Requirements

Related Solution Briefs: