CN105574187B - A kind of Heterogeneous Database Replication transaction consistency support method and system - Google Patents

A kind of Heterogeneous Database Replication transaction consistency support method and system Download PDF

Info

Publication number
CN105574187B
CN105574187B CN201510976842.5A CN201510976842A CN105574187B CN 105574187 B CN105574187 B CN 105574187B CN 201510976842 A CN201510976842 A CN 201510976842A CN 105574187 B CN105574187 B CN 105574187B
Authority
CN
China
Prior art keywords
affairs
transaction
submitting
table
database
Prior art date
Application number
CN201510976842.5A
Other languages
Chinese (zh)
Other versions
CN105574187A (en
Inventor
付铨
孙峰
陈琦
周英飚
Original Assignee
武汉达梦数据库有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 武汉达梦数据库有限公司 filed Critical 武汉达梦数据库有限公司
Priority to CN201510976842.5A priority Critical patent/CN105574187B/en
Publication of CN105574187A publication Critical patent/CN105574187A/en
Application granted granted Critical
Publication of CN105574187B publication Critical patent/CN105574187B/en

Links

Abstract

The present invention provides a kind of Heterogeneous Database Replication transaction consistency support method and system based on submission table, it is carried out in Heterogeneous Database Replication environment in usage log, utilize the process for submitting transaction table record purpose client database to complete affairs, and it is periodically executed the inspection for restoring starting point, the transaction journal initial position for submitting transaction table to determine that needs retransmit is utilized in dubbing system failure.The present invention uses the Heterogeneous Database Replication based on transaction table, solves source database and purpose database both sides' affairs execute inconsistency that may be present, lead to the technical problem that both data is inconsistent.

Description

A kind of Heterogeneous Database Replication transaction consistency support method and system

Technical field

The present invention relates to a kind of transaction consistency support methods of Heterogeneous Database Replication, espespecially a kind of to be submitted based on affairs The Heterogeneous Database Replication transaction consistency support method and system of table.

Background technique

With the extensive use of Enterprise Informatization system, information system has become the pass that enterprise maintains business operating Key.The diversified type of service of enterprise leads to data access demand increasingly complex, while sharply riseing for data volume also causes Database server can't bear the heavy load.Enterprise guarantees the continuity of business, maximum limit there is an urgent need to improve the availability of information system It reduces because being lost brought by disaster or failure on degree ground.For this purpose, the data duplication of Distributed Heterogeneous Database is a kind of common Technological means.

Currently, extracting the transaction journal of source database, the data manipulation of source database is obtained, including insertion (INSERT), It deletes (DELETE), update (UPDATE), the destination of dubbing system is then sent to by network, destination reverts to original SQL statement executed on purpose database, be a kind of common database replication technology.It has the performance to source database It is small with data mode influences, very flexible mode can be used and configure various topological structures, support the operating system across isomery The advantages that with database copy of platform.

It ensures the transaction consistency of purpose database and source database, and has recovery data under any hardware and software failure The ability of duplication is this dubbing system problem in need of consideration.Presently, there are some data copy systems, such as Oracle GoldenGate the thing being drawn into is saved in the file of source and destination by the file management Copy Info of itself Business log, when hardware and software failure occurs in system, according to the log execution position saved in file, the letter such as position is extracted in log Breath, is positioned in the transaction journal of source database again, continues data reproduction process.

However, transaction management of the file management that dubbing system uses in the above method independently of purpose database, it can not Guarantee the consistency of duplication affairs.For example, dubbing system destination submits an affairs first, then stepped in the file of oneself Remember that failure has occurred before file reliably flushes to not volatile storage media in the ID and LSN of this affairs.After system reboot, Because the affairs of purpose database are submitted, the fault recovery of the database and transaction management mechanism will guarantee the lasting of affairs Property, i.e. influence of the affairs for data enters into force, but the internal file of dubbing system does not register this information correctly, causes When restoring data duplication, the log of this affairs is passed to purpose database again and executed by dubbing system, and same affairs execute repeatedly, The affairs for causing source database and purpose database are inconsistent.

It can be seen that traditional dubbing system manages Copy Info using own files, source database and mesh not can guarantee Database both sides' affairs execute consistency, need to invent the transaction consistency support method of new Heterogeneous Database Replication.

Summary of the invention

The present invention provides the transaction consistency support methods and system of a kind of Heterogeneous Database Replication, it is intended that When solving existing Heterogeneous Database Replication system using data duplication based on transaction journal, source database and purpose database are double Square affairs execute inconsistency that may be present, lead to the technical problem that both data is inconsistent.

To solve the above-mentioned problems, the invention adopts the following technical scheme:

A kind of Heterogeneous Database Replication transaction consistency support method based on submission table, includes the following steps:

The operating procedure of purpose database and source database transactional synchronization, specifically: it is created in purpose database and submits thing Business table, creates in the memory of dubbing system destination and does not submit transaction table;The operation log of affairs is obtained from source database, Dubbing system destination executes corresponding data manipulation according to the operation log in purpose database;Affairs are grasped for the first time Make information as a record insertion and do not submit transaction table, submits operation information to insert as a record last time of affairs Enter and submit transaction table, while never submitting the record deleted in transaction table and have been filed on affairs;

The regular check step of dubbing system destination, specifically: do not submit found in transaction table it is not yet submitting, most The affairs early occurred, all transaction journals before deleting the affairs in submitting transaction table, while being inserted in submitting transaction table Enter the check point record comprising transaction information not yet submitting, occurring earliest;

Fault recovery step, specifically: not yet submit, generation earliest is obtained from the check point record submitted in transaction table Transaction information, dubbing system source using the affairs as restore starting point, the relevant operation log of affairs is sent to destination; If submitting the record for not having the log to correspond to affairs in transaction table, dubbing system destination exists according to the operation log received Corresponding data operation is executed in purpose database.

Further, the specific implementation process of the purpose database and primary database transactional synchronization step are as follows:

11) it is created in purpose database and submits transaction table, created in dubbing system purpose end memory and do not submit transaction table;

12) operation log in source database is extracted, operation log includes affairs ID, Transaction Sequence number LSN and content;

13) if the affairs ID of operation log is that occur for the first time, show to be drawn into is first operation log of affairs, Then do not submit be inserted into transaction table one include first operation log LSN information of affairs transaction journal, in execution journal Hold specified data operation, return step 12);Otherwise, step 14) is executed;

14) if the log content being drawn into is shown to be submission operation, then follow the steps 15);If the log content being drawn into 16) data manipulation being shown to be other than submitting, thens follow the steps;

15) it is submitting transaction table to be inserted into the transaction journal comprising transaction commit operation log LSN information, thing will be submitted All data manipulations that business table and affairs are related to carry out affairs submission together, never delete to be equal in submission transaction table and submit affairs The transaction journal of ID;

16) corresponding data operation, return step 12 are executed);

Further, the specific implementation process of the regular check step of the purpose database are as follows:

21) the smallest record of sequence number LSN is found in transaction table not submitting, corresponding currently not yet submit, hair earliest Raw affairs remember that the sequence number LSN of the record is LSN0;

22) all records for being less than or equal to LSN0 are deleted in submitting transaction table;

23) check point record is inserted into submitting transaction table, check point record includes LSN0 information;

Further, the specific implementation process of the fault recovery step are as follows:

31) dubbing system source sends the request of inquiry checkpoint to dubbing system destination;

32) dubbing system destination in purpose data base querying to check point record, feed back by the LSN0 information stored Give dubbing system source;

33) dubbing system source searches for the transaction journal equal to LSN0 as extensive in the operation log file of source database This affairs and subsequent transaction associated oplog are successively sent to dubbing system destination by multiple starting point.

34) dubbing system destination is submitting transaction table according to the affairs ID of the operation log of recovery in purpose database root Middle search does not operate if searching the transaction journal equal to affairs ID, terminates;Otherwise purpose database is used according to recovery Operation log execute corresponding data operation.

A kind of Heterogeneous Database Replication transaction consistency safeguards system based on submission table, comprising: source database, purpose number According to library, dubbing system, the submission transaction table for being created in purpose database, be created in dubbing system purpose end memory do not submit thing Business table;

The operation log of affairs in source database is transmitted to destination by dubbing system source, and destination is in purpose database It is middle to execute corresponding data manipulation;Destination is not submitted the first time operation information of the affairs received as a record insertion The last time of affairs is submitted operation information to submit transaction table, never submission transaction table as a record insertion by transaction table It is middle to delete the record for having been filed on affairs;

The timing of dubbing system destination finds affairs not yet submitting, occurring earliest not submitting in transaction table, mentioning All transaction journals before deleting the affairs in transaction table are handed over, while being inserted into one comprising not yet submitting in submitting transaction table , the check point record of the transaction information occurred earliest;

Dubbing system destination obtains affairs not yet submitting, occurring earliest from the check point record submitted in transaction table Information, dubbing system source is using the affairs as starting point is restored, by this affairs in source database and the relevant operation of subsequent transaction Log is sent to destination;If submitting in transaction table does not have a record of the affairs, dubbing system destination is according to receiving Operation log executes corresponding data operation in purpose database.

The present invention, which compares the prior art, following superiority:

The present invention submits transaction table to save the affairs having been filed on and not yet submit earliest using one in purpose database Affairs, the update of this table is submitted together with corresponding affairs, takes full advantage of the fault recovery function of purpose database itself Can, the information that the operation for replicating affairs itself and affairs execute is synthesized into an affairs, is submitted together.In this way, affairs Atomicity ensure that affairs itself data manipulation and affairs successful execution information store consistency, and affairs execute Information storage is the foundation of dubbing system fault recovery, to ensure that the transaction consistency and data one of Heterogeneous Database Replication Cause property.Overcome the checkpoint information of dubbing system in conventional method and purpose database to separate storage issuable inconsistent Property.

Detailed description of the invention

Fig. 1 is reconstructed model schematic diagram of the invention.

Fig. 2 is the present invention in data reproduction process, for submitting transaction table and the management process of transaction table not being submitted to show It is intended to.

Fig. 3 is the flow diagram that the present invention checks point process.

Fig. 4 is the flow diagram of failover procedure of the present invention.

Fig. 5 is an example schematic according to the invention, wherein Fig. 5 (a) is the t1 moment to submit transaction table and do not submit Transaction table schematic diagram, Fig. 5 (b) are check point record insertion process schematic diagram, and Fig. 5 (c) is failover procedure schematic diagram.

Specific embodiment

In order to make the objectives, technical solutions, and advantages of the present invention clearer, with reference to the accompanying drawings and embodiments, right The present invention is further elaborated.It should be appreciated that the specific embodiments described herein are merely illustrative of the present invention, and It is not used in the restriction present invention.As long as in addition, technical characteristic involved in the various embodiments of the present invention described below Not constituting a conflict with each other can be combined with each other.

The present invention includes three steps: the operating procedure of purpose database and primary database transactional synchronization, purpose database Regular check step and fault recovery step.The following detailed description of:

Fig. 2 is the operating procedure flow chart of the object of the invention database Yu primary database transactional synchronization, specifically:

11) a submission transaction table is created in purpose database, field requires as follows.

In the memory of dubbing system, transaction table is not submitted in creation one, and field requires as follows.

12) in source database, dubbing system extracts the operation log in source database, and log includes affairs ID, affairs sequence Row number LSN and content.

13) if the affairs ID of operation log is that occur for the first time, show to be drawn into is first operation log of affairs, Then do not submit be inserted into transaction table one include first operation log LSN information of affairs transaction journal, in execution journal Hold specified data operation, return step 12);Otherwise, step 14) is executed.

14) if the log content being drawn into is shown to be submission operation, then follow the steps 15);If the log content being drawn into 16) data manipulation for example INSERT, DELETE, the UPDATE being shown to be other than submitting, then follow the steps.

15) it is submitting transaction table to be inserted into the transaction journal comprising transaction commit operation log LSN information, thing will be submitted All data manipulations that business table and affairs are related to carry out affairs submission together, never delete to be equal in submission transaction table and submit affairs The transaction journal of ID.

16) the corresponding sentence of this log is generated in purpose database and execute corresponding data operation, return step 12).

Fig. 3 is the regular check flow chart of steps of the object of the invention database, passes through timer, clocked flip checkpoint mistake Journey, the time to execution following steps:

21) the smallest record of sequence number LSN is found in transaction table not submitting, corresponding currently not yet submit, hair earliest Raw affairs remember that the sequence number LSN of the record is LSN0.

22) all records for being less than or equal to LSN0 are deleted in submitting transaction table, i.e. execution sentence: DELETE FROM " is mentioned Hand over transaction table " WHERE " submitting LSN "≤LSN0.

This step cleaning submit transaction table, for occur earliest do not submit affairs start before, it is just submitted Affairs are had been filed on, have been not necessarily to continue to save in submitting transaction table, therefore cleaned up.

It should be noted that deletes here is not only transaction journal, the check point record equal to LSN0 is also deleted.Inspection It makes an inventory of record and refers to detailed description in step 23).

23) check point record is inserted into submitting transaction table, check point record includes LSN0 information.

In order to be distinguished with transaction journal, can " affairs ID " field value to check point record be separately provided, be for example set as 0, Because the ID of normal transaction is a positive integer, the record one that Transaction ID field is 0 is special, indicates the note of checkpoint " the submitting LSN field " of record, this record is equal to LSN0, represents when this checkpoint occurs, all earliest hairs for not submitting affairs Raw affairs, the log LSN of first operation.Execute sentence: INSERT INTO " submit transaction table " VALUES (0, LSN0)。

Fig. 4 displaying duplication system restarts rear source according to the record of submission table in purpose database because the system failure terminates Determine the initial position of duplication.Detailed process are as follows:

When dubbing system because communication failure, dubbing system or source database or purpose Database Systems failure exception terminate Afterwards, restart dubbing system.

31) source sends the request of inquiry checkpoint to destination.

32) destination inquires check point record in the submission table of purpose database, and the LSN0 information stored is anti- It feeds source;Execute sentence: SELECT " submitting LSN " FROM " submitting transaction table " WHERE " affairs ID "=0.

33) source searches for the transaction journal equal to LSN0 as starting point is restored in source database journal file, successively will Subsequent operation log is sent to destination.

Affairs corresponding less than the log of this LSN0 have been filed in purpose database, no longer need to capable execution.

34) after purpose terminates to transaction journal, according to the search in " submitting transaction table " of the affairs ID in log recording.I.e. Execute sentence:

SELECT*FROM " submitting transaction table " corresponding affairs ID of WHERE " affairs ID "=log recording.

Affairs ID exists in submitting transaction table, i.e. the SELECT statement result set of step 65) is not sky, then ignores this day Will record, if it is empty, then destination generates the corresponding sentence of this log and executes on purpose database.

Above step 31), 32), 33), 34) move in circles execution, until dubbing system restores normal

The following detailed description of an example:

Fig. 5 (a) is the t1 moment to submit transaction table and do not submit transaction table schematic diagram, and purpose database is receiving thing for the first time When the log of business ID=3, the record for being inserted into affairs ID=3, LSN=99 in transaction table is not being submitted, is submitting affairs ID=2's When affairs, the record for being inserted into affairs ID=3, LSN=98 in transaction table is not being submitted, is deleting ID=2 in transaction table not submitting Transaction journal.

Fig. 5 (b) is check point record insertion process schematic diagram, does not submit in transaction table and shows ID=3, starting LSN=99 Affairs be the affairs occurred earliest not yet submitted, then affairs submit table in delete earlier than the affairs record i.e. delete thing The record of business ID=2, LSN=98, while being inserted into the check point record of affairs ID=0, LSN=99.

Fig. 5 (c) is failover procedure schematic diagram.Check point record is found in submitting transaction table, knows recovery starting point For the affairs of ID=3, LSN=99.

As it will be easily appreciated by one skilled in the art that the foregoing is merely illustrative of the preferred embodiments of the present invention, not to The limitation present invention, any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should all include Within protection scope of the present invention.

Claims (5)

1. a kind of based on the Heterogeneous Database Replication transaction consistency support method for submitting table, which is characterized in that including walking as follows It is rapid:
The operating procedure of purpose database and source database transactional synchronization, specifically: it is created in purpose database and submits transaction table, It is created in the memory of dubbing system destination and does not submit transaction table;The operation log of affairs, duplication are obtained from source database System destination executes corresponding data manipulation according to the operation log in purpose database;By affairs, operation is believed for the first time Breath does not submit transaction table as a record insertion, the non-first time of affairs is operated and to submit the information of operation as one Transaction table is submitted in record insertion, while never submitting the record deleted in transaction table and have been filed on affairs;
The regular check step of dubbing system destination, specifically: hair not yet submit, earliest is found in transaction table not submitting Raw affairs, all transaction journals before deleting the affairs in submitting transaction table, while one is inserted into submitting transaction table Item includes the check point record of transaction information not yet submitting, occurring earliest;
Fault recovery step, specifically: thing not yet submitting, occurring earliest is obtained from the check point record submitted in transaction table The relevant operation log of affairs is sent to destination using the affairs as starting point is restored by business information, dubbing system source;If The record for not having the log to correspond to affairs in transaction table is submitted, then dubbing system destination is according to the operation log received in purpose Corresponding data operation is executed in database.
2. according to claim 1 based on the Heterogeneous Database Replication transaction consistency support method for submitting table, feature It is, the specific implementation process of the purpose database and source database transactional synchronization step are as follows:
11) it is created in purpose database and submits transaction table, created in dubbing system purpose end memory and do not submit transaction table;
12) operation log in source database is extracted, operation log includes affairs ID, Transaction Sequence number LSN and content;
13) if the affairs ID of operation log is that occur for the first time, show to be drawn into is first operation log of affairs, then exists It does not submit and is inserted into the transaction journal comprising first operation log LSN information of affairs in transaction table, execution journal content refers to Fixed data manipulation, return step 12);Otherwise, step 14) is executed;
14) if the log content being drawn into is shown to be submission operation, then follow the steps 15);If the log content being drawn into shows It is the data manipulation other than submitting, thens follow the steps 16);
15) it is submitting transaction table to be inserted into the transaction journal comprising transaction commit operation log LSN information, transaction table will be submitted All data manipulations being related to affairs carry out affairs submission together, never delete to be equal in submission transaction table and submit affairs ID's Transaction journal;
16) corresponding data operation, return step 12 are executed).
3. it is according to claim 1 or 2 based on the Heterogeneous Database Replication transaction consistency support method for submitting table, it is special Sign is, the specific implementation process of the regular check step of the dubbing system destination are as follows:
21) the smallest record of sequence number LSN is found in transaction table not submitting, it is corresponding it is currently not yet submitting, occur earliest Affairs remember that the sequence number LSN of the record is LSN0;
22) all records for being less than or equal to LSN0 are deleted in submitting transaction table;
23) check point record is inserted into submitting transaction table, check point record includes LSN0 information.
4. according to claim 3 based on the Heterogeneous Database Replication transaction consistency support method for submitting table, feature It is, the specific implementation process of the fault recovery step are as follows:
31) dubbing system source sends the request of inquiry checkpoint to dubbing system destination;
32) in purpose data base querying to check point record, the LSN0 information stored feeds back to multiple dubbing system destination System source processed;
33) dubbing system source is searched for the transaction journal equal to LSN0 in the operation log file of source database and is used as and restores This affairs and subsequent transaction associated oplog are successively sent to dubbing system destination by point;
34) dubbing system destination is searched in submitting transaction table in purpose database root according to the affairs ID of the operation log of recovery Rope does not operate if searching the transaction journal equal to affairs ID, terminates;Otherwise to purpose database according to the behaviour of recovery Make log and executes corresponding data operation.
5. a kind of based on the Heterogeneous Database Replication transaction consistency safeguards system for submitting table characterized by comprising source data Library, dubbing system, the submission transaction table for being created in purpose database, is created in dubbing system purpose end memory at purpose database Do not submit transaction table;
The operation log of affairs in source database is transmitted to destination by dubbing system source, and destination is held in purpose database The corresponding data manipulation of row;The first time operation information of the affairs received is not submitted affairs by destination The non-first time of affairs is operated and submits transaction table to submit the information of operation to be inserted into as a record, never submitted by table The record for having been filed on affairs is deleted in transaction table;
The timing of dubbing system destination finds affairs not yet submitting, occurring earliest not submitting in transaction table, submitting thing All transaction journals before deleting the affairs in business table, at the same submit transaction table in insertion one comprising not yet submit, The check point record of the transaction information occurred earliest;
Dubbing system destination obtains affairs letter not yet submitting, occurring earliest from the check point record submitted in transaction table Breath, dubbing system source is using the affairs as starting point is restored, by this affairs in source database and subsequent transaction relevant operation day Will is sent to destination;If submitting in transaction table does not have the record of the affairs, dubbing system destination is according to the behaviour received It is operated as execution corresponding data in purpose database is aimed at day.
CN201510976842.5A 2015-12-23 2015-12-23 A kind of Heterogeneous Database Replication transaction consistency support method and system CN105574187B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201510976842.5A CN105574187B (en) 2015-12-23 2015-12-23 A kind of Heterogeneous Database Replication transaction consistency support method and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201510976842.5A CN105574187B (en) 2015-12-23 2015-12-23 A kind of Heterogeneous Database Replication transaction consistency support method and system

Publications (2)

Publication Number Publication Date
CN105574187A CN105574187A (en) 2016-05-11
CN105574187B true CN105574187B (en) 2019-02-19

Family

ID=55884318

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201510976842.5A CN105574187B (en) 2015-12-23 2015-12-23 A kind of Heterogeneous Database Replication transaction consistency support method and system

Country Status (1)

Country Link
CN (1) CN105574187B (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106777270A (en) * 2016-12-28 2017-05-31 中国民航信息网络股份有限公司 A kind of Heterogeneous Database Replication parallel execution system and method based on submission point time line locking
CN107016075A (en) * 2017-03-27 2017-08-04 聚好看科技股份有限公司 Company-data synchronous method and device
CN107391306B (en) * 2017-07-27 2019-12-10 国家电网公司 Heterogeneous database backup file recovery method
CN110262929B (en) * 2018-08-13 2020-01-07 武汉达梦数据库有限公司 Method for ensuring consistency of copying affairs and corresponding copying device

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1784677A (en) * 2004-03-31 2006-06-07 微软公司 System and method for a consistency check of a database backup
CN103198159A (en) * 2013-04-27 2013-07-10 国家计算机网络与信息安全管理中心 Transaction-redo-based multi-copy consistency maintaining method for heterogeneous clusters
CN104216955A (en) * 2014-08-20 2014-12-17 百度在线网络技术(北京)有限公司 Methods and devices for operating data and managing events and distributed system

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7281023B2 (en) * 2003-12-15 2007-10-09 At&T Knowledge Ventures, L.P. Architecture of database application with robust online recoverability

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1784677A (en) * 2004-03-31 2006-06-07 微软公司 System and method for a consistency check of a database backup
CN103198159A (en) * 2013-04-27 2013-07-10 国家计算机网络与信息安全管理中心 Transaction-redo-based multi-copy consistency maintaining method for heterogeneous clusters
CN104216955A (en) * 2014-08-20 2014-12-17 百度在线网络技术(北京)有限公司 Methods and devices for operating data and managing events and distributed system

Also Published As

Publication number Publication date
CN105574187A (en) 2016-05-11

Similar Documents

Publication Publication Date Title
US7885922B2 (en) Apparatus and method for creating a real time database replica
US7406487B1 (en) Method and system for performing periodic replication using a log
US8874515B2 (en) Low level object version tracking using non-volatile memory write generations
JP4791051B2 (en) Method, system, and computer program for system architecture for any number of backup components
Baker et al. Megastore: Providing scalable, highly available storage for interactive services
US8214612B1 (en) Ensuring consistency of replicated volumes
ES2605936T3 (en) Automatic maintenance and repair systems and procedures for databases or file systems
JP5254611B2 (en) Metadata management for fixed content distributed data storage
CN101809558B (en) Asynchronous remote data replication system and method
CN101253484B (en) Method for storing data from client and the client
JP2004303025A (en) Information processing method, its execution system, its processing program, disaster recovery method and system, storage device for executing the processing, and its control processing method
US7389314B2 (en) Database backup, refresh and cloning system and method
KR101014089B1 (en) System and method for a consistency check of a database backup
US7472129B2 (en) Lossless recovery for computer systems with map assisted state transfer
US8239356B2 (en) Methods and apparatuses for data protection
US7266718B2 (en) Computer system for recovering data based on priority of the data
CN100375048C (en) method of restoring database to the prior state
US20080243878A1 (en) Removal
US10430298B2 (en) Versatile in-memory database recovery using logical log records
US6873995B2 (en) Method, system, and program product for transaction management in a distributed content management application
US7925633B2 (en) Disaster recovery system suitable for database system
US7363444B2 (en) Method for taking snapshots of data
US8250033B1 (en) Replication of a data set using differential snapshots
US20050028026A1 (en) Method and system for backing up and restoring data of a node in a distributed system
US20060136472A1 (en) Achieving cache consistency while allowing concurrent changes to metadata

Legal Events

Date Code Title Description
C06 Publication
C10 Entry into substantive examination
GR01