Error detection/correction and fault detection/recovery – Data processing system error or fault handling – Reliability and availability
Reexamination Certificate
2000-05-17
2003-05-06
Beausoliel, Robert (Department: 2184)
Error detection/correction and fault detection/recovery
Data processing system error or fault handling
Reliability and availability
C714S020000, C707S793000, C707S793000
Reexamination Certificate
active
06560719
ABSTRACT:
FIELD OF THE INVENTION
This invention relates to the recovery of original registry key data after providing synchronization and duplication of registry information as between a local platform and its facilities and a remote platform and its facilities.
BACKGROUND OF THE INVENTION
In database management, there is the concept of a “key” which is an identifier for a record or group of records in a data file, most often the key is defined as the contents of a single field called the “key field” in some database management programs and called “the index field” in others. In most database management systems, the keys (meaning the contents of a single key field or the composite key) are maintained in key tables which are specially indexed to speed record retrieval. In many database management systems, these key tables are called index files.
A key field is a field in a record structure or an attribute of a relational table that has been designated to be part of a key. A field can be keyed (or indexed) to improve or simplify the performance of retrieval and/or to update operations.
A key word is a characteristic word, phrase or code that is stored in a key field and used to conduct sorting or searching operations on records. This also applies to any of the dozens of words (also known as reserved words) that compose a given programming language or a set of operating system routines.
There is a factor called the “key word-in-context” which describes an automatic search methodology that creates indexes of document text or titles. Each key word is stored in the resulting index along with some surrounding text, usually the word or phrase that proceeds or follows the key word in the text or title.
In present day networks, there is a common configuration used in order to provide a local platform with facilities connected through a local area network over to a remote platform and remote facilities. The remote platform, and facilities are generally used as a backup system should the local platform and facilities fail. In such a case, then the operations are transferred to the remote platform and facilities in order that operations may be carried on. However, it is necessary that the remote platform and facilities be in synchronism or have data duplication of the local platform and facilities so that proper operations can occur without using invalid stale data or using data that is no longer correct.
In Windows Operating Systems there is a database designated as the Registry. This Registry database holds all varieties of information from system configurations to performance data to data about the applications available for use in the NT platform. This Registry is kept as a secured file on disk and a typical Registry is illustrated in FIG.
2
. The Registry can also be held in memory in addition to the disk file. Each item in the Registry is designated as a Registry Key.
In the earlier practice, in these situations involving a local platform and a remote backup platform, it was necessary for the user or operator to specifically provide for manually backing-up the Registry keys so that the remote platform would be updated with the present information residing in the local platform. These backup situations often required that certain periods of time, say during the night, or other times, could be used to transfer the data from the local program to the backup program when the time was available. However, this took considerable periods of time and effort to accomplish and there was always certain periods wherein there was no synchronization or duplication between the remote platform and the local platform.
The present invention eliminates the need to manually backup Registry keys. By scripting the object, which is the Component Object Model (COM) involved, one can automate the whole process with minimum operator effort and time consumption so that the remote platform will always hold the most up-to-date information. Thus, any applications that keep their settings and other vital information in the local Registry of the local platform can easily make themselves suitable for a fail-over strategy without worrying how the registry data are replicated and maintained in the remote standby platform. The remote backup registry key data in the remote platform ensures the continuing protection of any registry key data lost on the source local platform.
Now, however, another problem situation often arises when the system operator wishes to recover various data items. For example, the operator may wish to recover the original registry key data the existed at the remote destination backup platform before that particular remote registry key data was changed during operation of the automatic update component between the local and remote platforms.
And again, further, the operator may wish to recover and reconstitute the original local registry key at the local platform after some local platform fault or shutdown. To do this, there is then required an operation to access the corresponding remote registry key and transport the key data back to the local platform for restoration.
The methods for accomplishing these restoration operations are taught herein with references to
FIGS. 8 and 9
.
SUMMARY OF THE INVENTION
The present invention introduces a Component Object Model (COM) component that monitors a user-specified Registry on the local computer platform by duplicating the Registry keys over to a remote machine platform and instantly updating it whenever the monitored local key (including its values and subkeys) is modified.
A mechanism and method is provided (exposed through a COM object) to backup a specific Registry key from a local computer to a remote computer in order to synchronize the data involved upon the occurrence of any changes.
Most Windows applications today make use of the Registry in various different ways, and it is possible to use the described COM object to provide backup so that the remote or destination platform will always store a duplicate copy of the local registry key and be available should any problem occur within the local source platform.
It is often the case that the system operator needs to restore the remote original registry key data to replace the updated changed remote registry key data This is accomplished by storing the “original” remote registry key data on a remote disk file which can later be retrieved. On the other after a failure in the local platform, the operator will want to access original registry key data from the remote platform and convey it to the local platform to restore a particular local registry key. A special program using a remote backup subkey allows this restoration to be accomplished.
REFERENCES:
patent: 5958062 (1999-09-01), Komasaka et al.
patent: 6092213 (2000-07-01), Lennie et al.
patent: 6173417 (2001-01-01), Merrill
patent: 6324654 (2001-11-01), Wahl et al.
patent: 6363498 (2002-03-01), Howell
patent: 6397381 (2002-05-01), Delo et al.
patent: 6438749 (2002-08-01), Chamberlain
patent: 6496944 (2002-12-01), Hsiao et al.
www.estools,unisys.com/docs/ProgrammingGuide.pdf. Aug. 2002, pp. 9-109—9-119.*
Robichaux, Paul. Managing the Windows NT Registry.Apr. 1998.O'Reilly & Associates. pp. 66-92, 115-116.
Pham Thien Huu
Wilson Philip Douglas
Beausoliel Robert
Kozak Alfred W.
Rode Lise A.
Starr Mark T.
Unisys Corporation
LandOfFree
Method for recovery of original registry key file data does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Method for recovery of original registry key file data, we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method for recovery of original registry key file data will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3004530