Reliable database administration arrangement.

<u style="single">Technical Field</u>

The invention relates generally to database systems, and in particular relates to the administration of distribution of copies of portions of a database from a central node to peripheral nodes of a distributed processing system.

<u style="single">Background of the Invention</u>

Distributed processing systems--ones comprising a plurality of processing entities or locations, referred to herein as nodes--often depend upon a database for their operation. Illustrative examples of such systems are a multiprocessor computer that stores operational data in a database, and a distributed switching system, such as a PBX with remote modules, that stores call processing translations in a database.

To avoid known difficulties associated with using either a fully-­distributed or a fully-centralized database architecture, distributed processing systems often favor a database architecture which is intermediate between the two above-mentioned extremes: one wherein a "master" copy of the database is located at one, a central, node that manages the database centrally, but where "cache" copies of portions of the database are maintained locally at the other, peripheral, nodes. The peripheral nodes then communicate with the central node to obtain database information when that information is not in the local cache copy, and when updating their cache copies.

In distributed systems making use of this database architecture, the loss by a peripheral node of its database cache copy can adversely affect system performance. Such loss occurs, for example, if the peripheral node stores the cache copy in a volatile memory, such as a semiconductor memory, and it loses power to that memory. Even if the peripheral node stores the information in nonvolatile memory, such as a disk, it may lose the cache copy due to a node or a disk malfunction that mutilates the data in the cache copy. In the event of such a loss, the peripheral node must obtain a fresh cache copy from the central node. The time spent by the central node in providing this fresh copy, and the time spent by the peripheral node in awaiting the fresh copy, is time taken away from the nodes' normal activities. In particular, when the cache copies and the master database do not have the same format, it is very time-consuming for the central node to translate the requisite database portion from "master" copy format--such as a format suitable for operator retrieval and display--into "cache" copy format--­one suitable for transmission to the peripheral node and storage and use by the peripheral node. Hence, system performance suffers. It is therefore desirable to minimize the time spent in providing a peripheral node with a cache copy of the database.

<u style="single">Summary of the Invention</u>

The invention is directed to satisfying this desire of the prior art. According to the invention, a peripheral node of a distributed system is provided with a new cache copy of a portion of the database not directly from the master database, but from a separate, "boot", copy of a version of the cache copy that existed at some prior point in time, supplemented by a record of the changes that must be made to the boot copy to bring it up-to-date, i.e., to make it consistent with, the master database. The boot copy has the same format as the cache copy, but has a format different from that of the master database. An arrangement according to the invention maintains a database that has a plurality of modifiable­-e.g., updateable--portions. The portions have some particular format. The arrangement stores a record of changes, or modifications, that have been made to the database portions. The arrangement also generates boot copies of the database portions. The boot copies have a format that is different from the format of the database portions. Illustratively, generation of a boot copy involves translation of the database portion from the database's format--such as a display format--into the "cache copy" format--such as a machine-useable format. The arrangement responds to a request from a requester for a database portion by sending to the requester the boot copy corresponding to the requested portion and the presently-­stored record of modifications made to the requested portion. Illustratively, the arrangement characterized above is located at a central node of a distributed system, while cache copies of the database portions are located at peripheral nodes of the system, and requests for database portions are guests by the peripheral nodes to the central node for new cache copies of the database portions.

Because requests for database portions are satisfied by sending boot copies plus modifications, and not the database portions themselves, satisfaction of the requests avoids searching the master database itself for the desired portion and then translating the desired portion from master database format into the cache copy format; as mentioned above, the boot copies are "pre-translated". Hence, the requests can be satisfied with much less work, and more rapidly, thereby improving real-time response-and operational efficiency.

Preferably there is a storage facility, such as a table, associated with or corresponding to each database portion, and that storage facility records changes, or modifications, that have been made to the associated database portion. The arrangement responds to modifications of a database portion by making a record of the modification in the storage facility that corresponds to the modified portion. This feature avoids having to spend time searching through a common record of changes made to all database portions to select changes that were made to a particular portion. System performance is enhanced thereby.

Also preferably, the arrangement occasionally generates new, updated, boot copies. The new boot copies represent the old boot copies modified with the presently-recorded modifications to the database. However, for reliability purposes, the new boot copies are preferably generated not by modifying the old boot copies, but are generated anew from the database portions by translating anew the database portions. When it generates the new boot copies, the arrangement deletes the records of the modifications to the old boot copies that are represented in the new boot copies. Preferably, the generation of the new boot copies is undertaken by the arrangement when it does not have more pressing work to do. The generation of the new boot copies therefore does not adversely impact the performance of the arrangement; what it does do is improve the performance of the requesters of new cache copies, who are saved thereby from the effort of incorporating the changes into the old boot copies themselves.

These and other advantages and features of the invention will become more apparent from the following description of an illustrative embodiment of the invention considered together with the drawing.

<u style="single">Brief Description of the Drawings</u>

<ul id="ul0001" list-style="none"><li>FIG. 1 is a block diagram of a distributed PBX including an illustrative embodiment of the invention;</li><li>FIG. 2 is flow diagram of actions of the database manager of the PBX of FIG. 1 upon system initialization;</li><li>FIG. 3 is a flow diagram of database manager actions in response to a database change;</li><li>FIG. 4 is a flow diagram of database manager actions taken to periodically generate new boot copies of database portions; and</li><li>FIG. 5 is a flow diagram of database manager actions taken to supply system nodes with new copies of database portions.</li></ul>

<u style="single">Detailed Description</u>

FIG. 1 shows a distributed telephony switching system such as a private branch exchange (PBX). The switching system comprises a central, administrative, node 10 and a plurality of peripheral, call processing, nodes 11-12 interconnected by a communication medium. Each peripheral node 11-12 is connected to customers via communication links 14 which are, for example, telephone lines or trunks. Peripheral nodes 11-12 provide conventional call processing functions for their connected customers, whereas central node 10 provides specialized system-wide functions, such as call records and billing. Such systems are well known in the art. An example thereof is the IBM multi-module 9751 CBX.

Administrative node 10 includes a central administrative processor 20 connected to a non-volatile mass storage medium such as a disk 21. Processor 20 stores on disk 21 a master copy of a system management database, referred to herein as a master database 22. Database 22 includes call processing translations that peripheral nodes 11-12 need to perform their call processing functions. Database 22 is managed, i.e., controlled and maintained, by a database manager 23 program executing on processor 20.

A user interface 27, such as a computer terminal, is connected to processor 20. Inter alia, interface 27 enables an operator to inform database manager 23 of changes to database 22, so that manager 23 can keep database 22 up-to-date. For example, when a new customer is connected to the system of FIG. 1, or when an old customer changes location, and hence its connection to the system, an operator informs manager 23 of these changes through interface 27, so that manager 23 may update the call processing translations in database 22 accordingly.

Each peripheral node 11-12 includes a processor 30 for performing call processing functions. Each processor 30 includes a memory 31 in which it stores call processing programs and call processing translations. These translations are a part of master database 22. Because each node 11-12 serves different customers, each processor 30 typically requires different translations. Hence, the memory 31 of each processor 30 typically stores a different portion of database 22. The database portions stored in peripheral nodes 11-12 are referred to as cache copies 32 of the database portions. In the example of FIG. 1, master database 22 is shown as comprising a plurality of portions 24 designated A to Z, and each of the peripheral nodes 11-12 is shown as having a cache copy 32 of one of the portions 24, such that node 11 includes a cache copy 32 of database portion A and node 12 includes a cache copy 32 of database portion Z.

Associated with each master database portion 24 is a boot copy 25 of the portion, and a change table 26. Illustratively, boot copies 25 and change tables 26 are also stored on disk 21, although they may be stored in any non-­volatile memory in the system. A boot copy 25 is a copy of the cache copy 32 of the corresponding master database portion 24 which was created at some past point in time. Hence, boot copy 25 is a potentially-outdated copy that does not necessarily reflect the present, updated, contents of portion 24. A change table 26 is a stored record of all changes, updates, that have been made to a portion 24 since the corresponding boot copy 25 was created.

Database manager 23 uses boot copies 25 and change tables 26--as opposed to master database portions 24--to re-create lost or mutilated cache copies 32 in peripheral nodes 11-12. The administration and use of boot copies 25 and change tables 26 is diagrammed in FIGS. 2-5.

FIG. 2 shows activities of database manager 23 upon system initialization. In response to an initialization command, received at step 200, manager 23 retrieves a portion 24 of master database 22 from disk 21, at step 201. Master database 22 is stored in a format suitable for display to, and interaction with, an operator at user interface 27, not in machine-useable format. Manager 23 therefore translates the retrieved portion from the display format to a machine-­useable format, at step 202. Manager 23 then sends the translated portion to a corresponding peripheral node 11-12, at step 203. The sent copy becomes the cache copy 32 at the receiving peripheral node 11-12. Manager 23 also creates a boot copy 25 of that same translated copy of master database portion 24, at step 204, by copying the translated information into a new--the boot copy--file. Furthermore, manager 23 creates and initializes--clears--a change table for that portion 24, at step 205. Manager 23 then checks whether all peripheral nodes 11-­12 have been serviced, at step 206. If not, manager 23 returns to step 201 to service another node 11-12 and to provide it with a copy of its corresponding database portion. If all nodes 11-12 have been serviced, manager 23 exits, at step 207.

FIG. 3 shows activities of database manager 23 upon receipt of a change to the contents of master database 22, such as from user interface 27. In response to receiving the change, at step 300, manager 23 enters the change in master database 22, thereby modifying the contents of database 22, at step 301. Manager 23 also determines which portions 24 were affected by this change, i.e., the contents of which portions 24 were modified, at step 302. Manager 23 then sends the change to the peripheral nodes 11-12 which store cache copies 32 of the affected portions 24, at step 303. The receiving nodes 11-12 enter the change in their cache copies 32. Having completed the change, manager 23 enters a record of the change in change tables 26 which correspond to portions 24 which were affected by the change, at step 304, and exits, at step 305.

FIG. 4 shows activities performed by database manager 23 to update boot copies 25. Periodically--for example, upon the timing out of an operating system timer--database manager 23 is issued an interrupt indicating that it is time to update boot copies 25. This is a low-priority interrupt, and hence manager 23 may not respond to it immediately upon receiving it, at step 400. When higher-­priority work has been completed, manager 23 responds to the interrupt by duplicating the first two steps 201-202 of FIG. 2 to generate a new boot copy 25 of a database portion 24, at steps 401-402, respectively.

This is the functional equivalent of retrieving the contents of a change table 26 corresponding to a first database portion 24 and modifying the present boot copy 25 of the database portion 24 by making the changes indicated by the retrieved contents of change table 26, as shown in FIG. 4 by the dotted-line steps 406 and 407. However, conversion of a portion 24 into a boot copy 25 may possibly introduce error into the boot copy 25. For reliability purposes--to prevent these errors from propagating--the approach of steps 406-407 is not favored, and the approach of steps 401-402 is used instead.

New boot copy 25 is caused at steps 401-402 or steps 406-407 to reflect the present, up-to-date, contents of the corresponding database portion 24. The record of the changes is no longer needed, so manager 23 erases--zeroes out-­-the contents of change table 26 which corresponds to the newly-updated boot copy 25, at step 403. Manager 23 then checks if all boot copies 25 have been updated, at step 404. If not, manager 23 returns to step 401 to update another boot copy 25. If all boot copies 25 have been updated, manager 23 exits, at step 405.

Memories 31 of peripheral nodes 11-12 typically are volatile memories. Hence, whenever power to a memory is lost, its contents are lost. Furthermore, memories 31 illustratively have no local back-up. Hence, whenever the contents of a memory 31 become lost or mutilated, a replacement therefor is not locally available. In either case, a new cache copy 32 of the database portion contents of memory 31 must be obtained from a source of such information, which in this example is administrative node 10.

FIG. 5 shows the activities performed by database manager 23 to supply a peripheral node 11-12 with a new cache copy 32 of a database portion. In response to receiving a request from a node 11-12 for a new copy of a database portion 24, at step 500, manager 23 retrieves boot copy 25 that corresponds to the requested portion 24, at step 501. Manager 23 also retrieves the contents of change table 26 that corresponds to the requested portion 24, at step 502. Manager 23 then sends the retrieved boot copy 25, and the changes to the boot copy 25 that are specified by the retrieved change table 26 contents, to the requesting node 11-12, at step 505. Manager 23 then exits, at step 504. The requesting node 11-12 receives the sent boot copy 25 and the changes, and creates therefrom a new cache copy 32.

Of course, it should be understood that various changes and modifications to the illustrative embodiment described above will be apparent to those skilled in the art. For example, change tables 26 and boot copies 25 need not be stored at adminstrative node 10, but may be stored anywhere in the system, such as at an independent database node, or in back-up storage of call processing nodes 11-12 when such storage is provided. Also, administrative node 10 may also serve as a call processing node and have its own cache copy 32 of its corresponding database portion 24. Such changes and modifications can be made without departing from the spirit and the scope of the invention and without diminishing its attendant advantages. It is therefore intended that all such changes and modifications be covered by the following claims.