Safe storing data for disaster recovery

• US 9,292,588 B1
• Filed: 07/20/2011
• Issued: 03/22/2016
• Est. Priority Date: 07/20/2011
• Status: Active Grant

• Current Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Original Assignee: JP Morgan Chase Bank, N.A. (JP Morgan Chase & Co)
• Inventors: Layne, Mitchell, Stranzl, Herb, Allaire, Thomas G., Raymond, Erol Toni
• Primary Examiner(s): Abbaszadeh, Jaweed A
• Assistant Examiner(s): Chen, Xuxing
• Application Number:
  US13/187,479
• Time in Patent Office: 1,707 Days
• Field of Search: 713/400, 711/104, 709/207
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/1474 in transactions G06F16/20 takes precedence
• CPC Class Codes: G06F 11/202 where processing functionality is redundant redundant communication control functionality G06F11/2005, redundant storage control functionality G06F11/2089
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2048 where the redundant components share neither address space nor persistent storage
• CPC Class Codes: G06F 11/2056 by mirroring
• CPC Class Codes: G06F 11/2082 Data synchronisation
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 2201/80 Database-specific techniques
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

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 collocated 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.

Claims

1. A computer-implemented method for safe storing data, the method comprising the steps of:

receiving the data, via an asynchronous write, on a programmed computer at a primary site from a remote client computer;

creating a copy of the data received on the programmed computer at the primary site;

transmitting the copy of the data received on the programmed computer at the primary site, via a synchronous write, to a programmed computer at a remote recovery site, wherein the data received is not operated on at the primary site prior to the copy of the data being transmitted synchronously to the remote recovery site and wherein the remote recovery site is not co-located with the primary site and the programmed computer at the primary site;

storing the transmitted copy of the data received in a database at the remote recovery site, wherein the database is communicatively coupled to the programmed computer at the remote recovery site;

operating on the data received at the primary site after the copy of the data has been stored at the remote recovery site; and

transmitting an electronic acknowledgement from the primary site to the remote client computer after storing the copy of the data at the remote recovery site, said electronic acknowledgement confirming the asynchronous write.

2. The method of claim 1, wherein the at least one memory component is configured as at least one message queue.

3. The method of claim 1, wherein saving the data to the at least one memory component at the remote recovery site further comprises executing a synchronous PUT command.

4. The method of claim 1, wherein receiving the data asynchronously at the primary site further comprises saving the data to at least one memory component communicatively coupled to the programmed computer at the primary site.

5. The method of claim 4, wherein the at least one memory component is configured as at least one message queue.

6. The method of claim 4, wherein saving the data to the at least one memory component at the primary site further comprises executing an asynchronous PUT command.

7. The method of claim 1, further comprising transmitting an electronic acknowledgement to the remote client computer after operating on the data at the primary site.

8. The method of claim 1, wherein the data comprises at least one message.

9. The method of claim 1, wherein the programmed computer at the primary site and the programmed computer at the remote recovery site are not colocated.

10. The method of claim 1, wherein the programmed computer at the primary site is communicatively coupled to the programmed computer at the remote recovery site by a data network.

11. A computer-based system for safe storing data, the system:

a programmed computer at a primary site for receiving the data, via an asynchronous write, from a remote client computer, wherein the programmed computer creates a copy of the data received on the programmed computer at the primary site;

a transmission engine for transmitting the copy of the data received on the programmed computer at the primary site, via a synchronous write, to a programmed computer at a remote recovery site, wherein the data received is not operated on at the primary site prior to the copy of the data being transmitted synchronously to the remote recovery site and wherein the remote recovery site is not co-located with the primary site and the programmed computer at the primary site;

a storage engine for storing the transmitted copy of the data received in a database at the remote recovery site, wherein the database is communicatively coupled to the programmed computer at the remote recovery site;

an operation engine for operating on the data received at the primary site after the copy of the data has been stored at the remote recovery site; and

an acknowledgement transmission engine for transmitting an electronic acknowledgement from the primary site to the remote client computer after storing the copy of the data at the remote recovery site, said electronic acknowledgement confirming the asynchronous write.

12. The system of claim 11, wherein the at least one memory component is configured as at least one message queue.

13. The system of claim 11, wherein saving the data to the at least one memory component at the remote recovery site further comprises executing a synchronous PUT command.

14. The system of claim 11, wherein receiving the data asynchronously at the primary site further comprises saving the data to at least one memory component communicatively coupled to the programmed computer at the primary site.

15. The system of claim 14, wherein the at least one memory component is configured as at least one message queue.

16. The system of claim 14, wherein saving the data to the at least one memory component at the primary site further comprises executing an asynchronous PUT command.

17. The system of claim 11, wherein the acknowledgement transmission engine transmits an electronic acknowledgement to the remote client computer after operating on the data at the primary site.

18. The system of claim 11, wherein the data comprises at least one message.

19. The system of claim 11, wherein the programmed computer at the primary site and the programmed computer at the remote recovery site are not colocated.

20. The system of claim 11, wherein the programmed computer at the primary site is communicatively coupled to the programmed computer at the remote recovery site by a data network.