System for Highly Available Transaction Recovery for Transaction Processing Systems

• US 20080162593A1
• Filed: 02/14/2008
• Published: 07/03/2008
• Est. Priority Date: 02/22/2002
• Status: Abandoned Application

• Current Assignee: BEA Systems Incorporated (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Somogyi, Alexander J., Fung, Priscilla C.
• Application Number:
  US12/030,998
• Publication Number:
  US 20080162593A1
• Time in Patent Office: Days
• US Class Current: 707/202
• CPC Class Codes: G06F 11/1662 the resynchronized component or unit being a persistent storage device re-synchronization of failed mirror storage G06F11/2082; rebuild or reconstruction of parity RAID storage G06F11/1008
• CPC Class Codes: G06F 11/2028 eliminating a faulty processor or activating a spare
• CPC Class Codes: G06F 11/2038 with a single idle spare processing component
• CPC Class Codes: G06F 11/2046 where the redundant components share persistent storage G06F11/2043 takes precedence
• CPC Class Codes: H04L 1/22 using redundant apparatus to increase reliability
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A highly available transaction recovery service migration system in accordance with one embodiment of the present invention implements a server'"'"'s Transaction Recovery Service (TRS) as a migratable service. In one embodiment of the present invention, the TRS is a server instance or software module implemented in JAVA. The TRS migrates to an available server that resides in the same cluster as the failed server. The migrated TRS obtains the TLOG of the failed server, reads the transaction log, and performs transaction recovery on behalf of the failed server. The migration may occur manually or automatically on a migratable services framework. The TRS of the failed server migrates back in a fail back operation once the failed primary server is restarted. Failback operation may occur whether recovery is completed or not. This expedites recovery and improves availability of the failed server thereby preserving the efficiency of the network and other servers.

Claims

1. A system for recovering transactions comprising:

a primary server having a transaction log, and

a backup server, wherein upon a failure of the primary server, the backup server is operable to read the transaction log and perform recovery on behalf of the failed primary server.

2. The system of claim 1, wherein the primary server and backup server reside in a cluster.

3. The system of claim 1, wherein transaction recovery is accomplished automatically.

4. The system of claim 1, wherein transaction recovery is accomplished manually.

5. The system of claim 1, wherein transaction recovery is accomplished manually by an administrator.

6. The system of claim 1, further comprising a migratable framework and a transaction recovery service configured to receive support from the migratable service framework for manual migration.

7. The system of claim 1, further comprising a migratable framework and a transaction recovery service configured to receive support from the migratable service framework for automatic migration.

8. A cluster of servers configured to provide transaction recovery comprising:

a primary server having a transaction log, the primary server and transaction log residing in the cluster; and

a backup server residing in the cluster and having access to the transaction log, the backup server operable to read the transaction log and perform recovery on behalf of the failed primary server.

9. The cluster of servers of claim 8, wherein transaction recovery is accomplished automatically.

10. The cluster of servers of claim 8, wherein transaction recovery is accomplished manually by an administrator.

11. The cluster of servers of claim 8, further comprising a migratable framework residing in the cluster and a transaction recovery service configured to receive support from the migratable service framework for manual migration.

12. The cluster of servers of claim 8, further comprising a migratable framework residing in the cluster and a transaction recovery service configured to receive support from the migratable service framework for automatic migration.

13. A computer readable medium including code to implement:

a primary server having a transaction log, and

a backup server, wherein upon a failure of the primary server, the backup server is operable to read the transaction log and perform recovery on behalf of the failed primary server.

14. The computer readable medium of claim 13, wherein the primary server and backup server reside in a cluster.

15. The computer readable medium of claim 13, wherein transaction recovery is accomplished automatically.

16. The computer readable medium of claim 13, wherein transaction recovery is accomplished manually.

17. The computer readable medium of claim 13, wherein transaction recovery is accomplished manually by an administrator.

18. The computer readable medium of claim 13, further comprising a migratable framework and a transaction recovery service configured to receive support from the migratable service framework for manual migration.

19. The computer readable medium of claim 13, further comprising a migratable framework and a transaction recovery service configured to receive support from the migratable service framework for automatic migration.