SYSTEM FOR SYNCHRONIZING REPLICAS OF A DATABASE

• US 20080244334A1
• Filed: 06/12/2008
• Published: 10/02/2008
• Est. Priority Date: 03/10/2005
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: VARGHESE, John
• Granted Patent: US 7,725,766 B2
• Time in Patent Office: Days
• US Class Current: 714/48
• CPC Class Codes: G06F 11/2097 maintaining the standby controller/processing unit updated initialisation or re-synchronisation thereof G06F11/1658 and subgroups
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

A system for synchronizing replicas of a database. The system detects a failure of update data from a first replica to be applied to a second replica and determines a cause of the failure. The system also resolves the cause of the failure. According to the system disclosed herein, the present invention synchronizes the replicas of the database without requiring manual intervention.

Claims

1. A database system comprising:

a first server site comprising a first replica of a database;

a second server site coupled to the first server site, the second server site comprising a second replica of the database; and

a client coupled to the first replica wherein the client is operable to;

send update data from a first replica to a second replica;

automatically detect a failure of the update data from the first replica to be applied to the second replica;

automatically determine a cause of the failure and where the cause of the failure occurred, wherein the determining comprises;

determining if the failure was due to a packet being lost, wherein the packet contains the update data;

parsing metadata, wherein the parsed metadata indicates if an account is locked out; and

determining if the second replica is up-to-date;

automatically resolve the cause of the failure, wherein the resolving comprises;

requesting for a packet to be resent if the cause of the failure is due to the packet being lost;

unlocking an account if the cause of the failure is due to the account being locked out;

deleting an object if the cause of the failure is due to the object not being deleted during a previous export;

notifying an appropriate authority of the failure if corrective actions need to be taken by the appropriate authority;

resending the update data;

applying the update data to the second replica; and

recording update data in an operations log.

2. The system of claim 1 further comprising a server that fetches metadata for the client.

3. The system of claim 2 wherein the metadata indicates if an account has been locked out.

4. The system of claim 2 wherein the metadata indicates if the second replica is up-to-date.

5. A computer-readable storage medium containing program instructions for synchronizing replicas of a database, the program instructions which when executed by a computer system cause the computer system to execute a method comprising:

sending update data from a first replica to a second replica;

automatically detecting a failure of the update data from the first replica to be applied to the second replica;

automatically determining a cause of the failure and where the cause of the failure occurred, wherein the determining comprises;

determining if the failure was due to a packet being lost, wherein the packet contains the update data;

parsing metadata, wherein the parsed metadata indicates if an account is locked out; and

determining if the second replica is up-to-date;

automatically resolving the cause of the failure, wherein the resolving comprises;

requesting for a packet to be resent if the cause of the failure is due to the packet being lost;

unlocking an account if the cause of the failure is due to the account being locked out;

deleting an object if the cause of the failure is due to the object not being deleted during a previous export;

notifying an appropriate authority of the failure if corrective actions need to be taken by the appropriate authority;

resending the update data;

applying the update data to the second replica; and

recording update data in an operations log.