Loosely coupled database clusters with client connection fail-over
First Claim
Patent Images
1. A method of providing highly-available database clusters which replicate at least one data file, the method comprising:
- receiving one or more data requests from a client application over a first client connection, the one or more data requests requesting access to data of a first data file;
associating a timestamp with each data request;
forwarding each data request to a first database management system capable of accessing the data of the first data file according to the data request;
forwarding each data request and each associated timestamp to a memory;
forwarding replication data to the memory, wherein the replication data is sufficient to indicate any changes made to the data of the first data file based on the one or more data requests and wherein each replication data includes a timestamp;
comparing the timestamps of one or more of the replication data to the timestamps of one or more of the data requests;
when the one or more of the data requests are determined to be redundant to the one or more of the replication data based on the timestamps, purging one of (a) one or more of the data requests and (b) one or more of the replication data; and
forwarding the other of (a) and (b) to a second database management system capable of accessing data of a second data file.
27 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
26 Claims
-
1. A method of providing highly-available database clusters which replicate at least one data file, the method comprising:
-
receiving one or more data requests from a client application over a first client connection, the one or more data requests requesting access to data of a first data file;
associating a timestamp with each data request;
forwarding each data request to a first database management system capable of accessing the data of the first data file according to the data request;
forwarding each data request and each associated timestamp to a memory;
forwarding replication data to the memory, wherein the replication data is sufficient to indicate any changes made to the data of the first data file based on the one or more data requests and wherein each replication data includes a timestamp;
comparing the timestamps of one or more of the replication data to the timestamps of one or more of the data requests;
when the one or more of the data requests are determined to be redundant to the one or more of the replication data based on the timestamps, purging one of (a) one or more of the data requests and (b) one or more of the replication data; and
forwarding the other of (a) and (b) to a second database management system capable of accessing data of a second data file. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16)
-
-
17. A method of performing replication in a database cluster having client connection failover, the method comprising:
-
monitoring a first system with a second system wherein at least a portion of a first data file of the first system is replicated in a second data file of the second system;
determining a need to move communication over a first connection between a client application and the first data file through the first system to a second connection between the client application and the second data file through the second system;
moving the communication to the second connection in a manner allowing the client application to not fail. - View Dependent Claims (18, 19, 20, 21, 22, 23, 24, 25, 26)
-
Specification