APPARATUS AND METHOD FOR SYNCHRONIZING EMBEDDED DATABASES OF APPLICATIONS IN A FAILOVER CLUSTER

• US 20080209260A1
• Filed: 02/27/2007
• Published: 08/28/2008
• Est. Priority Date: 02/27/2007
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Vykunta, Venkateswara Rao
• Application Number:
  US11/679,737
• Publication Number:
  US 20080209260A1
• Time in Patent Office: Days
• US Class Current: 714/6
• CPC Class Codes: G06F 11/1482 by means of middleware or OS functionality
• 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/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups

Abstract

A method and computer program product in accordance with the invention includes identifying, by an application upon startup, redundant applications running in a failover cluster. Each of the application and redundant applications includes an embedded database for storing data. The application determines which embedded database of the applications contains the most recent version of data, retrieves the most recent version of data, and writes this version to its embedded database. The application then notifies the other applications and waits for the other applications to complete replication to their embedded databases. The application may then commence operation, replicate changes to its embedded database to the other applications, and generate a timestamp indicating the time the changes are made.

Claims

1. A method for synchronizing embedded databases of applications in a failover:

cluster, the method comprising;

identifying, by an application upon startup, redundant applications running in a failover cluster, wherein each of the application and redundant applications comprises an embedded database;

determining which embedded database of the application and redundant applications contains the most recent version of data;

retrieving the most recent version of data;

writing the most recent version to the embedded database of the application;

notifying the redundant applications that the most recent version has been written to the embedded database of the application;

waiting for the redundant applications to write the most recent version to their respective embedded databases;

commencing operation, by the application, after notifying the redundant applications and waiting for the redundant applications;

replicating, while the application is operating, changes made to the embedded database of the application to the embedded databases of the redundant applications; and

generating, by the application while operating, a timestamp indicating the time the changes were made to the embedded database of the application.

2. The method of claim 1, wherein determining further comprises comparing timestamps of the embedded databases of the application and redundant applications to determine which embedded database contains the most recent version of data.

3. The method of claim 1, wherein identifying further comprises compiling a list of redundant applications running in the failover cluster.

4. A computer program product to synchronize embedded databases of applications in a failover cluster, the program product comprising a computer-readable medium storing a computer-readable program that when executed on a computer causes the computer to:

identify, by an application upon startup, redundant applications running in a failover cluster, wherein each of the application and redundant applications comprises an embedded database;

determine which embedded database of the application and redundant applications contains the most recent version of data;

retrieve the most recent version of data;

write the most recent version to the embedded database of the application;

notify the redundant applications that the most recent version has been written to the embedded database of the application;

wait for the redundant applications to write the most recent version to their respective embedded databases;

commence operation, by the application, after notifying the redundant applications and waiting for the redundant applications;

replicate, while the application is operating, changes made to the embedded database of the application to the embedded databases of the redundant applications; and

generate, by the application while operating, a timestamp corresponding to the time the changes are made to the embedded database of the application.

5. The computer program product of claim 4, wherein determining further comprises comparing timestamps of the embedded databases of the application and redundant applications to determine which embedded database contains the most recent version of data.

6. The computer program product of claim 4, wherein identifying further comprises compiling a list of redundant applications running in the failover cluster.