US 2006/0235904 A1Published application

Method for preserving access to system in case of disaster

OwnerRajesh Kapurinventor

Life of this patent

Estimating the term…

Loading patent…

Abstract

A method for preserving access to document data within a system in a separate location, wherein said document data is stored in a system filestore associated with a system database, the system database containing reference data to point to the document data within the system filestore, in case of disaster to the primary system such as, earthquake, the secondary system can be used, the method comprising steps of: creating a replicated server containing the system database and filestore; determining that a insert, update, delete command has been issued within the primary production system database upon its system tables excepting those containing reference information that uniquely identifies the production system database from its replica on the network fabric; transferring and recording the commands above to the database system tables of the replica based on time of earliest recorded data; transferring recorded document data to secondary filestore using incremental filestore backup transfers;

Claims27

Dependent claims

A method for preserving access to document data entered by the user community within a primary system located on a primary server to a separate location, wherein said document data is stored in a system filestore associated with a system database, the system database containing reference data to point to the document data within the system filestore, by use of a replicated server containing a secondary system as a disaster recovery system the method comprising steps of:

(a) creating said replicated server containing the secondary system in which the reference data is configured to point to document data in a secondary system filestore the document data periodically being updated by copying data from the primary filestore and containing system database tables that mirror the primary system database tables save those tables containing reference data that uniquely identify the secondary sytem from the primary on a network;
(b) determining that an insert, an update, or an delete command has been issued within the primary production system database upon its system tables excepting those containing reference information that uniquely identifies the primary system from the secondary system on the network fabric;
(c) transferring and recording the said issued commands upon the primary system database tables to the database system tables of the secondary system based on time of earliest recorded data;
(d) in the event of failure of the primary system or of the network between the primary and replica server, changing the secondary system's database and or the secondary filestore so that the secondary system database corresponds with either the secondary or primary filestore.

1 more element

Dependencies are inferred from the claim text.

Facts

Application: 11/389,597Filed 27 Mar 2006
Priority: CA 2,504,07014 Apr 2005
Published: 19 Oct 2006
Term ends: Not estimatedThe source records don’t support an estimate.

Classification4 codes

G06F 11/2097
Using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements: maintaining the standby controller/processing…
G06F 11/2094
Where persistent mass storage functionality or persistent mass storage control functionality is redundant: redundant storage or storage space
G06F 2201/80
Indexing scheme relating to error detection, to error correction, and to monitoring: database-specific techniques
G06F
Computing and data processing