Asynchronous Transaction Queue for Disaster Recovery Data Safety

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

High-volume transaction processing systems, particularly in financial institutions, face data loss risks during outages due to asynchronous mirroring methods over long distances, leading to unacceptable delays and financial losses, as prior art systems may lose data during disaster recovery scenarios, especially when using MQ network messaging technology that destroys message traffic.

Innovation Solution

A computer-implemented method and system where transaction messages are asynchronously written to a transaction processing computer and then synchronously written to a remote disaster recovery computer, ensuring no data loss by using a sending queue manager and a receiving queue manager to transmit and store messages securely across different sites.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of time

If asynchronous mirroring is used for disaster recovery, then execution time is reduced, but data loss risk increases

Engineering Contradiction:
Improveexecution timeVSAvoiddata loss risk
Core Design Contradiction:
Loss of timeVSReliability

Solution Approach 1:

The system performs preliminary actions by sending transaction messages to the disaster recovery system in advance before actual processing occurs. The message is routed to the disaster recovery system upfront, ensuring it is ready before any potential outage occurs, thus eliminating the need for lengthy recovery operations later while maintaining data integrity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary mechanism using message queues and routing systems that facilitate the transfer of transaction messages between the primary system and disaster recovery system. This intermediary layer enables asynchronous communication while maintaining message integrity, allowing the system to achieve fast execution without direct synchronous coupling that would cause delays.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If synchronous mirroring is used for disaster recovery, then data loss is prevented, but execution time increases unacceptably

Engineering Contradiction:
Improvedata loss preventionVSAvoidexecution time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by sending transaction messages to the disaster recovery system in advance before actual processing occurs. The message is routed to the disaster recovery system upfront, ensuring it is ready before any potential outage occurs, thus eliminating the need for lengthy recovery operations later while maintaining data integrity.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements continuous useful action through asynchronous message routing that operates continuously in the background without interrupting the primary transaction processing flow. The disaster recovery system continuously receives and processes messages asynchronously, ensuring uninterrupted data protection while maintaining acceptable execution times for business operations.

Inventive Principle:
Principle #20Continuity of useful action

3Speed

If asynchronous mirroring over long distances is used, then system responsiveness is improved, but data loss risk increases due to network outages

Engineering Contradiction:
Improvesystem responsivenessVSAvoiddata loss risk
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent introduces an intermediary mechanism using message queues and routing systems that facilitate the transfer of transaction messages between the primary system and disaster recovery system. This intermediary layer enables asynchronous communication while maintaining message integrity, allowing the system to achieve fast execution without direct synchronous coupling that would cause delays.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system implements beforehand cushioning by pre-positioning transaction messages at the disaster recovery system before outages occur. This creates a buffer or cushion of pre-transferred data that protects against potential network failures, ensuring data availability even when network conditions deteriorate during actual outages.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Productivity

If MQ network messaging technology is used, then transaction processing is streamlined, but message traffic is destroyed during disaster recovery

Engineering Contradiction:
Improvetransaction processing efficiencyVSAvoidmessage traffic loss
Core Design Contradiction:
ProductivityVSLoss of information

Solution Approach 1:

The patent applies the copying principle by creating and maintaining duplicate copies of transaction messages at both the primary system and disaster recovery system. Instead of relying on single-instance messages that may be destroyed, the system replicates message content across multiple locations, ensuring that even if original messages are lost, accurate copies remain available for recovery and reconciliation.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces an intermediary mechanism using message queues and routing systems that facilitate the transfer of transaction messages between the primary system and disaster recovery system. This intermediary layer enables asynchronous communication while maintaining message integrity, allowing the system to achieve fast execution without direct synchronous coupling that would cause delays.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS9971654B2Safe storing data for disaster recovery
Publication Date: 2018.05.15 JPMORGAN CHASE BANK NA
  • US9971654B2 patent drawing
  • US9971654B2 patent drawing
  • US9971654B2 patent drawing

AI summary

A computer-implemented method and system for safe storing data is disclosed. A sending queue manager associated with a client computer transmits an asynchronous write of a transaction message containing data to a receiving queue manager associated with a transaction processing computer not colocated with the client computer. The receiving queue manager transmits a synchronous write of the transaction message to a remote queue manager associated with a remote disaster recovery computer to safe store the transaction message before it can be operated upon by the transaction processing computer.