Data input routing after failure

• US 20070226277A1
• Filed: 02/06/2007
• Published: 09/27/2007
• Est. Priority Date: 03/16/2001
• Status: Active Grant

• Current Assignee: RPX Corporation
• Original Assignee: Gravic Incorporated
• Inventors: Holenstein, Bruce, Holenstein, Paul
• Granted Patent: US 7,739,237 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/2064 while ensuring consistency
• CPC Class Codes: G06F 11/2069 Management of state, configuration or failover
• CPC Class Codes: G06F 11/2074 Asynchronous techniques
• CPC Class Codes: G06F 11/2076 Synchronous techniques
• CPC Class Codes: G06F 11/2079 Bidirectional techniques
• CPC Class Codes: G06F 16/2343 Locking methods, e.g. distributed locking or locking implementation details
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 2201/855 Details of asynchronous mirroring using a journal to transfer not-yet-mirrored changes
• CPC Class Codes: Y10S 707/99938 Concurrency, e.g. lock management in shared database
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

Tokens are used to prepare a target database for replication from a source database and to confirm the preparation in an asynchronous coordinated commit replication process. During a dual write replication process, transmission of the replicated data and locking of data records in the target database occurs only on updates.

Claims

1. A method of replicating data associated with a plurality of transactions in a replication system including a plurality of nodes connected via communication media in a topology, each node including a database, at least some of the nodes being able to independently receive and post transactions, the method comprising:

(a) initiating and performing transactions to be executed in a database at an originating node; and

(b) replicating the transactions to at least one or more other nodes by;

(i) pausing each transaction being executed in the database at the originating node prior to a commit operation for the transaction,

(ii) assigning a ready to commit token to the transaction,

(iii) sending the ready to commit token to the one or more other nodes,

(iv) determining at the one or more other nodes whether the respective databases are prepared for a commit operation for the transaction corresponding to the ready to commit token, and, if so, sending back the ready to commit token to the originating node, and

(v) executing a commit operation at the database of the originating node only upon receipt from at least one of the other nodes of the ready to commit tokens originally sent from the originating node,

wherein step (b) is performed asynchronously with respect to other transactions that are initiated in step (a).