SYSTEMS AND METHODS FOR PROVIDING CLIENT CONNECTION FAIL-OVER
First Claim
Patent Images
1. A database cluster for providing client connection fail-over, the database cluster comprising:
- a first computing system comprising;
a first management module configured to form a client connection with and receive at least one transaction from a client, and a first database management system (DBMS) in communication with the first management module to receive and execute the at least one transaction on data stored in one or more data files;
a replication module configured to record replication data indicating changes made to the data stored in the one or more data files based on the at least one transaction; and
a second computing system in communication with the replication module, the second computing system comprising;
a second management module configured to receive a copy of the at least one transaction from the first computing system, the second management module being further configured to purge at least one of (i) the copy of the at least one transaction and (ii) the replication data when the copy of the at least one transaction is redundant to the replication data, wherein the second management module is configured to monitor a performance of the first computing system and the first management module is configured to monitor a performance of the second computing system, and wherein when the second management module determines that an unbalanced workload exists between the first and the second computing systems, the second management module transparently assumes the client connection and begins to receive additional transactions from the client to be executed against the one or more data files.
25 Assignments
0 Petitions
Accused Products
Abstract
Aspects of embodiments of the present disclosure include a highly available database cluster employing replication between two or more data files. The cluster also can maintain a connection with potentially geographically remote client application programs, including non-fault tolerant application programs, even in the event of one of the database management systems (DBMS) of the cluster becoming unavailable.
-
Citations
20 Claims
-
1. A database cluster for providing client connection fail-over, the database cluster comprising:
-
a first computing system comprising;
a first management module configured to form a client connection with and receive at least one transaction from a client, and a first database management system (DBMS) in communication with the first management module to receive and execute the at least one transaction on data stored in one or more data files;
a replication module configured to record replication data indicating changes made to the data stored in the one or more data files based on the at least one transaction; and
a second computing system in communication with the replication module, the second computing system comprising;
a second management module configured to receive a copy of the at least one transaction from the first computing system, the second management module being further configured to purge at least one of (i) the copy of the at least one transaction and (ii) the replication data when the copy of the at least one transaction is redundant to the replication data, wherein the second management module is configured to monitor a performance of the first computing system and the first management module is configured to monitor a performance of the second computing system, and wherein when the second management module determines that an unbalanced workload exists between the first and the second computing systems, the second management module transparently assumes the client connection and begins to receive additional transactions from the client to be executed against the one or more data files. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A method of providing transparent fail-over to a client connection, the method comprising:
-
monitoring statistics of a client connection between a first database management system (DBMS) and a client, wherein said monitoring is performed by a connection manager of a second DBMS;
replicating data between a first file in communication with the first DBMS and a second file in communication with the second DBMS;
determining from the statistics a need, based on an unbalanced workload between the first DBMS and the second DBMS, to transparently move the client connection from the first DBMS to the second DBMS while keeping the client connection alive from a perspective of the client;
rerouting the client connection to the second DBMS; and
establishing communication between the second DBMS and the client over the client connection. - View Dependent Claims (10, 11, 12, 14, 15, 16, 17, 18)
-
-
13. The method of claim 13, wherein said determining if the copy of the data request is redundant comprises comparing the timestamp of the data request with a timestamp of the replication data.
-
19. A system for providing transparent fail-over to a client connection, the system comprising:
-
means for monitoring statistics of a client connection between a first database management system (DBMS) and a client, said monitoring means being associated with a second DBMS;
means for storing replication data indicating changes made to data of a first data file based on a transaction sent from the client to the first DBMS;
means for receiving a copy of the transaction;
means for determining if the copy of the transaction is redundant to the replication data, and when the copy of the transaction is determined to be redundant to the replication data, purging one of (i) the copy of the transaction and (ii) the replication data;
determining from the statistics a need to transparently move the client connection to the second DBMS while keeping the client connection alive from a perspective of the client;
rerouting the client connection to the second DBMS; and
establishing communication between the second DBMS and the client over the client connection. - View Dependent Claims (20)
-
Specification