System for taking backup in a data base

• US 5,548,750 A
• Filed: 12/08/1993
• Issued: 08/20/1996
• Est. Priority Date: 12/08/1992
• Status: Expired due to Term

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Sanchez, Ivan M., Larsson, Bo E. S.
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): PHAM, CUAN
• Application Number:
  US08/162,899
• Time in Patent Office: 986 Days
• Field of Search: 395/600, 395/575, 395/700, 395/425, 395/250, 395/400
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 2201/805 Real-time
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

For backing up in a distributed real time data base on primary memory in operation, all data in the data base are structured as belonging to one of several logic data bases. The logic data can, but need not, extend over several processors. A backup function of a certain logic data base is activated by sending a message to a central backup handler, which has information regarding processors, over which the current backup system extends, and synchronizes the backup function over processor borders. The synchronization includes that local data base handlers are informed that backup will be started and that a new transaction log is being created, in which all transactions that have not attained a commit state and which shall therefore not be included in the backup are logged. The backup will only contain changes of transactions in the old transaction log.

Claims

1. A backup system for a real time data base on primary memory in operation, said data base being distributed over a number of processors which execute a plurality of functionalities, said backup system comprising:

a plurality of logic data bases, of which each is able to extend over several of said processors, and each has a backup functionality associated with it, wherein all data in said real time data bases is distributed over said logic data bases,

a central backup handler, which has information regarding processors, over which the backup system extends,

a local database handler for each processor, and

activating functionality for activating said backup functionality of a current one of said logic data bases by sending a message to said central backup handler to perform synchronization of the backup functionality over processors over which said current logic data base extends,

said synchronization including that the local data base handlers are informed that backup will be started and that a new transaction log should be created, in which all transactions which shall not be included in the backup are logged, and backup will only contain changes of transactions in an earlier transaction log.

2. A system according to claim 1, wherein said activating functionality activates said backup functionality of a logic database periodically or at a command of an operator.

3. A system according to claim 1, wherein said synchronization includes the central backup handler instructing the local data base handlers to set a backup flag in the current logic data base informing the local data base handlers that backup will be started and causing them to change behavior with respect to storing objects located in the current logic data base, and the local data base handlers after the backup flag has been set acknowledging this to the central backup handler.

4. A system according to claim 3, wherein the central backup handler instructs local log handlers of current processors to create a new transaction log when all local data base handlers have acknowledged that the backup flag has been set.

5. A system according to claim 4, wherein the new transaction log includes a backup synchronization variable that is used by the local data base handler and by local backup handlers to decide whether objects shall be included in a backup, and the central backup handler instructs the local log handlers to change a value of said variable in the new transaction log and the object thereof shall not be included in the backup.

6. A system according to claim 5, wherein the backup synchronization variable is collected by a coordinator for a transaction in connection with entering a commit value into the transaction log indicating that the transaction has attained a commit state, and the value of the backup synchronization variable and the commit value is sent to all participating transactions, which in turn distribute the backup synchronization value to different data base objects, and all objects in the transaction get a same backup synchronization value.

7. A system according to claim 1, further comprising a counter for indicating a number of proceeding transactions in a COMMIT state towards an old transaction log, said synchronization including that at zero count of the counter the central backup handler is informed that there is no coordinator for any transaction in the current processor wishing updatings to be included in the backup.

8. A system according to claim 1, wherein copying of objects is initiated after local log handlers have been informed that the local data base handler has made all changes from transactions, which shall be included in the backup, visible in the data base.

9. A system according to claim 8, wherein making changes visible includes synchronization among the local data base handler, backup handler and log handler.

10. A system according to claim 9, wherein said synchronization being performed by the local log handler keeps up with a number of transactions existing in an earlier transaction log, the number of transactions being counted down as the transaction enters a predetermined end message in the earlier transaction log, entering the predetermined end message being carried through when the local data base handler has performed the changes in the data base and informed this to the transaction.

11. A system according to claim 9, wherein the central backup handler instructs all local backup handlers, when a number of transactions in the old transaction log is zero in all local log handlers, to begin copying the objects to be included in a backup to the backup area, said objects having been backup marked by the local data base handler in response to its change of behavior when the backup flag was set.

12. A system according to claim 1, wherein objects are copied to a backup area, and an earlier backup is stored in a primary memory until a new backup is ended, whereupon the earlier backup is stored in a secondary memory.