CN105045678A - Database recovery method and apparatus - Google Patents
Database recovery method and apparatus Download PDFInfo
- Publication number
- CN105045678A CN105045678A CN201510400419.0A CN201510400419A CN105045678A CN 105045678 A CN105045678 A CN 105045678A CN 201510400419 A CN201510400419 A CN 201510400419A CN 105045678 A CN105045678 A CN 105045678A
- Authority
- CN
- China
- Prior art keywords
- storehouse
- data
- master library
- database
- preset duration
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
Links
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Embodiments of the invention provide a database recovery method and apparatus used for a database system consisting of a main database and a slave database. Initially, data of the slave database are the same as data of the main database. The method comprises the steps of obtaining a completed operation in the main database according to a time order; after the operation is obtained each time, executing the same operation in the slave database after a predetermined time period is delayed based on currently obtained operation completion time; when an error occurs in the main database, determining an erroneous operation that causes the error; judging whether the erroneous operation is executed in the slave database; and if the erroneous operation is not executed in the slave database, using the data of the slave database to carry out recovery on the data of the main database. According to the scheme provided by the embodiments of the invention, an operation status prior to the erroneous operation can be precisely recovered, thereby avoiding data loss to a very large extent, reducing the loss as far as possible and improving the security and reliability of database operation.
Description
Technical field
The present invention openly relates to database technology, particularly relates to database restoring method and device.
Background technology
In the operation of database uses, there will be the situation of the database operating instruction performing mistake because of reasons such as software program problem or attended operation errors unavoidably, data in database have been carried out wrong amendment.These maloperations gently then affect data accuracy, heavy then cause heavy economic losses, as sequence information mistake, and user account remaining sum mistake etc.
In the related, in order to retrieve a loss when there is maloperation, eliminate the effects of the act, traditional way is timed backup database mostly, and such as backup every day is once, then when needs recover data, and can by database recovery to state during backup.
Summary of the invention
For overcoming Problems existing in correlation technique, the present invention openly provides a kind of database restoring method and device, to promote safety and reliability when database runs.
According to the first aspect of disclosed embodiment of the present invention, provide a kind of database restoring method, described method is used for by master library and the Database Systems that form from storehouse, identical with the data of described master library from the data in storehouse described in time initial; Described method comprises:
Obtain completed operation on described master library in chronological order;
After getting described operation, postpone preset duration based on the deadline of the described operation of current acquisition after, perform identical operation described from storehouse at every turn;
When mistake appears in described master library, determine the faulty operation led to errors;
Judge whether described faulty operation performs from storehouse described;
If described faulty operation not yet performs from storehouse described, then recover from the data of data to described master library in storehouse described in using.
Optionally, describedly obtain completed operation on described master library in chronological order, comprising:
Sequentially read the operation be documented in master library Operation Log.
Optionally, described based on the deadline of the described operation of current acquisition, postpone preset duration after perform identical operation described from storehouse, comprising:
Obtain the described current time from storehouse;
Judge whether the deadline of the described operation of current acquisition and the difference of described current time are less than described preset duration;
If be less than described preset duration, then return and obtain the described step from the current time in storehouse;
If be more than or equal to described preset duration, then perform the operation identical with described operation described from storehouse.
Optionally, recover from the data of the data in storehouse to described master library described in described use, comprising:
In the described operation executed from storehouse before described faulty operation;
The described data data to described master library current from storehouse are used to repair, to make the date restoring of described master library to the state performed before described faulty operation.
Optionally, described method also comprises:
Input according to user is modified to described preset duration.
According to the second aspect of disclosure embodiment, provide a kind of database recovery device, described device is used for by master library and the Database Systems that form from storehouse, identical with the data of described master library from the data in storehouse described in time initial; Described device comprises:
Master library operation acquisition module, for obtaining completed operation on described master library in chronological order, after getting described operation, triggers from storehouse async backup module at every turn;
From storehouse async backup module, for based on the deadline of the described operation of the current acquisition of master library operation acquisition module, after postponing preset duration, perform identical operation described from storehouse;
Recover judge module, for when mistake appears in described master library, determine the faulty operation led to errors, judge whether described faulty operation performs from storehouse described, if described faulty operation not yet performs from storehouse described, then trigger data recovers module;
Data recovery module, recovers from the data of data to described master library in storehouse described in using.
Optionally, described master library operation acquisition module comprises:
Order reading submodule, for sequentially reading the operation be documented in master library Operation Log;
Backup triggers module, after getting described operation, triggers from storehouse async backup module at every turn.
Optionally, describedly to comprise from storehouse async backup module:
Time obtains submodule, for obtaining the described current time from storehouse;
Time contrast submodule, whether the difference for the deadline and described current time that judge the described operation of current acquisition is less than described preset duration, if be less than described preset duration, then the triggered time obtains submodule, if be more than or equal to described preset duration, then perform the operation identical with described operation described from storehouse.
Optionally, described data recovery module comprises:
Recover to prepare submodule, in the described operation executed from storehouse before described faulty operation;
Data restore submodule, for using the described data data to described master library current from storehouse to repair, to make the date restoring of described master library to the state performed before described faulty operation.
Optionally, described device also comprises:
Duration modified module, modifies to described preset duration for the input according to user.
According to the third aspect of disclosure embodiment, provide a kind of database recovery device, described device is used for by master library and the Database Systems that form from storehouse, and identical with the data of described master library from the data in storehouse described in time initial, described device comprises:
Processor;
For the storer of storage of processor executable instruction;
Wherein, described processor is configured to:
Obtain completed operation on described master library in chronological order;
After getting described operation, postpone preset duration based on the deadline of the described operation of current acquisition after, perform identical operation described from storehouse at every turn;
When mistake appears in described master library, determine the faulty operation led to errors;
Judge whether described faulty operation performs from storehouse described;
If described faulty operation not yet performs from storehouse described, then recover from the data of data to described master library in storehouse described in using.
The technical scheme that embodiment of the present disclosure provides can comprise following beneficial effect:
In the related, when occurring that mistake needs to recover data, because probably there occurs a lot of operation between current time and backup time, but correlation technique can only return to backup time, so may cause the loss of data.And in disclosure scheme, the state of the last operation of faulty operation can be returned to.In other words, correlation technique can only be accurate to last " moment " when recovering data, and disclosure scheme then can be as accurate as last " operation ", and this just largely avoid the loss of data, loss is reduced to little as far as possible, improve safety and reliability when database runs.
Should be understood that, it is only exemplary and explanatory that above general description and details hereinafter describe, and can not limit the disclosure.
Accompanying drawing explanation
Accompanying drawing to be herein merged in instructions and to form the part of this instructions, shows embodiment according to the invention, and is used from instructions one and explains principle of the present invention.
Fig. 1 is the process flow diagram of a kind of database restoring method according to an exemplary embodiment;
Fig. 2 is the schematic diagram copying master library operation from storehouse according to an exemplary embodiment;
Fig. 3 is the process flow diagram of a kind of database restoring method according to an exemplary embodiment;
Fig. 4 is the process flow diagram of a kind of database restoring method according to an exemplary embodiment;
Fig. 5 is the block diagram of a kind of database recovery device according to an exemplary embodiment;
Fig. 6 is the block diagram of a kind of database recovery device according to an exemplary embodiment;
Fig. 7 is the block diagram of a kind of database recovery device according to an exemplary embodiment;
Fig. 8 is the block diagram of a kind of database recovery device according to an exemplary embodiment;
Fig. 9 is the block diagram of a kind of database recovery device according to an exemplary embodiment;
Figure 10 is the block diagram of a kind of device for database recovery according to an exemplary embodiment.
Embodiment
Here will be described exemplary embodiment in detail, its sample table shows in the accompanying drawings.When description below relates to accompanying drawing, unless otherwise indicated, the same numbers in different accompanying drawing represents same or analogous key element.Embodiment described in following exemplary embodiment does not represent all embodiments consistent with the present invention.On the contrary, they only with as in appended claims describe in detail, the example of apparatus and method that aspects more of the present invention are consistent.
Fig. 1 is the process flow diagram of a kind of database restoring method according to an exemplary embodiment.Described method can be used for by master library and the Database Systems that form from storehouse, identical with the data of described master library from the data in storehouse described in time initial.
Shown in Figure 1, described method can comprise:
In step S101, obtain completed operation on described master library in chronological order.
Such as, describedly obtain completed operation on described master library in chronological order, can comprise:
Sequentially read the operation be documented in master library Operation Log.
Usually after database completing an operation, the time that database can be recorded this operation in order and complete in its Operation Log.So read the Operation Log of master library, just completed operation on master library can be got one by one.
In step s 102, after getting described operation, postpone preset duration based on the deadline of the described operation of current acquisition after, perform identical operation described from storehouse at every turn.
Above two steps can be regarded as and utilize from storehouse the process that master library backs up.
Perform the operation identical with master library and also can be described as the operation copying master library.Size the present embodiment for preset duration does not limit, and user can be arranged as required when initial, such as, can be set to 30 minutes; In addition also can modify to described preset duration according to the input of user.
From storehouse as the backup database of master library, time initial, store the data identical with master library.Backup procedure is then a kind of async backup, change in the process of (namely completing various operation on master library) at master library, also make, from storehouse, same change occurs, and compared with master library, can preset duration be postponed from the change in storehouse, such as, postpone 30 minutes.
Exemplarily this scene can be shown in Figure 2,201 is master library in fig. 2,202 is from storehouse, the Operation Log of master library is write after operation on master library is finished, then can be read the Operation Log of master library by I/O thread from storehouse, operation in master library Operation Log is written to from the pending operating list in storehouse, in order each operating delay was performed from storehouse by SQL thread after 30 minutes.
With further reference to shown in table 1, can also can see in Table 1, replicate the operations master library from storehouse, and from the operation storehouse all than operating delay identical on master library 30 minutes.
Table 1
| Time | Operation on master library | From the operation storehouse |
| 05:30 | Operation 1 | |
| 05:33 | Operation 2 | |
| 05:42 | Operation 3 | |
| ... | ... | |
| 06:00 | ... | Operation 1 |
| 06:03 | ... | Operation 2 |
| 06:12 | ... | Operation 3 |
| ... | ... | ... |
In step s 103, when mistake appears in described master library, the faulty operation led to errors is determined.
Such as, can position faulty operation in the Operation Log of master library.
In step S104, judge whether described faulty operation performs from storehouse described.
In step S105, if described faulty operation not yet performs from storehouse described, then recover from the data of data to described master library in storehouse described in using.
Above three steps can be regarded as and utilize from storehouse the process that master library recovers.
Like this when finding that master library occurs wrong, if mistake is found in the preset duration perform this faulty operation on master library after, identical faulty operation is not yet performed from storehouse when also namely finding mistake, so this mistake just can be repaired, can use and from the data in storehouse, master library be repaired, thus retrieve the data of master library.
It should be noted that, in some cases, if error detection is more late, performed identical faulty operation from storehouse when finding mistake, so just need other technologies to recover master library, this kind of situation is not within discussion category of the present disclosure.
Shown in Figure 3, in the present embodiment or the disclosure some other embodiments, perform identical operation described from storehouse postpone preset duration based on the deadline of the described operation of current acquisition after, can comprise:
In step S301, obtain the described current time from storehouse.
In step s 302, judge whether the deadline of the described operation of current acquisition and the difference of described current time are less than described preset duration;
In step S303, if be less than described preset duration, then return step S301.
In step s 304, if be more than or equal to described preset duration, then perform the operation identical with described operation described from storehouse.
In some cases, when needing to recover, the operation before not yet may performing faulty operation from storehouse, now in order to enable master library return to the state before faulty operation, can make the progress pulling up to master library from storehouse.Such as, suppose that faulty operation is operation 18, but only perform operation 10 from storehouse, so first can allow from storehouse performing operation 17 always, namely reach the state of master library before executable operations 18, thus make master library can by the state returned to from storehouse before operation 18.
So shown in Figure 4, in the present embodiment or the disclosure some other embodiments, recover from the data of data to described master library in storehouse described in using, can comprise:
In step S401, in the described operation executed from storehouse before described faulty operation.
In step S402, the described data data to described master library current from storehouse are used to repair, to make the date restoring of described master library to the state performed before described faulty operation.
Certainly in other embodiments of the disclosure, also other modes can be adopted to use described to recover from the data of data to described master library in storehouse, such as, the seasonal step stopping performing master library from storehouse of mistake can also there is, then use and from the data storehouse, master library is repaired, step before executing faulty operation again on master library, thus the date restoring of master library also can be made to the state performed before described faulty operation.This present embodiment is not limited.
In the related, when occurring that mistake needs to recover data, because probably there occurs a lot of operation between current time and backup time, but correlation technique can only return to backup time, so may cause the loss of data.And in disclosure scheme, the state of the last operation of faulty operation can be returned to.In other words, correlation technique can only be accurate to last " moment " when recovering data, and disclosure scheme then can be as accurate as last " operation ", and this just largely avoid the loss of data, loss is reduced to little as far as possible, improve safety and reliability when database runs.
Fig. 5 is the block diagram of a kind of database recovery device according to an exemplary embodiment.Described device is used for by master library and the Database Systems that form from storehouse, identical with the data of described master library from the data in storehouse described in time initial.
Shown in Figure 5, described device comprises:
Master library operation acquisition module 501, for obtaining completed operation on described master library in chronological order, after getting described operation, triggers from storehouse async backup module at every turn;
From storehouse async backup module 502, for based on the deadline of the described operation of the current acquisition of master library operation acquisition module, after postponing preset duration, perform identical operation described from storehouse;
Recover judge module 503, for when mistake appears in described master library, determine the faulty operation led to errors, judge whether described faulty operation performs from storehouse described, if described faulty operation not yet performs from storehouse described, then trigger data recovers module;
Data recovery module 504, recovers from the data of data to described master library in storehouse described in using.
Shown in Figure 6, in the present embodiment or the disclosure some other embodiments, describedly can to comprise from storehouse async backup module 502:
Time obtains submodule 601, for obtaining the described current time from storehouse;
Time contrast submodule 602, whether the difference for the deadline and described current time that judge the described operation of current acquisition is less than described preset duration, if be less than described preset duration, then the triggered time obtains submodule, if be more than or equal to described preset duration, then perform the operation identical with described operation described from storehouse.
Shown in Figure 7, in the present embodiment or the disclosure some other embodiments, described data recovery module 504 can comprise:
Recover to prepare submodule 701, in the described operation executed from storehouse before described faulty operation;
Data restore submodule 702, for using the described data data to described master library current from storehouse to repair, to make the date restoring of described master library to the state performed before described faulty operation.
Shown in Figure 8, in the present embodiment or the disclosure some other embodiments, described master library operation acquisition module 501 can comprise:
Order reading submodule 801, for sequentially reading the operation be documented in master library Operation Log;
Backup triggers module 802, after getting described operation, triggers from storehouse async backup module at every turn.
Shown in Figure 9, in the present embodiment or the disclosure some other embodiments, described device can also comprise:
Duration modified module 505, modifies to described preset duration for the input according to user.
About the device in above-described embodiment, wherein the concrete mode of modules executable operations has been described in detail in about the embodiment of the method, will not elaborate explanation herein.
In the related, when occurring that mistake needs to recover data, because probably there occurs a lot of operation between current time and backup time, but correlation technique can only return to backup time, so may cause the loss of data.And in disclosure scheme, the state of the last operation of faulty operation can be returned to.In other words, correlation technique can only be accurate to last " moment " when recovering data, and disclosure scheme then can be as accurate as last " operation ", and this just largely avoid the loss of data, loss is reduced to little as far as possible, improve safety and reliability when database runs.
The disclosure also discloses a kind of database recovery device, and described device is used for by master library and the Database Systems that form from storehouse, and identical with the data of described master library from the data in storehouse described in time initial, described device comprises:
Processor;
For the storer of storage of processor executable instruction;
Wherein, described processor is configured to:
Obtain completed operation on described master library in chronological order;
After getting described operation, postpone preset duration based on the deadline of the described operation of current acquisition after, perform identical operation described from storehouse at every turn;
When mistake appears in described master library, determine the faulty operation led to errors;
Judge whether described faulty operation performs from storehouse described;
If described faulty operation not yet performs from storehouse described, then recover from the data of data to described master library in storehouse described in using.
The disclosure also discloses a kind of non-transitory computer-readable recording medium, when the instruction in described storage medium is performed by the processor of equipment, make equipment can perform a kind of database restoring method, described method is used for by master library and the Database Systems that form from storehouse, identical with the data of described master library from the data in storehouse described in time initial, described method comprises:
Obtain completed operation on described master library in chronological order;
After getting described operation, postpone preset duration based on the deadline of the described operation of current acquisition after, perform identical operation described from storehouse at every turn;
When mistake appears in described master library, determine the faulty operation led to errors;
Judge whether described faulty operation performs from storehouse described;
If described faulty operation not yet performs from storehouse described, then recover from the data of data to described master library in storehouse described in using.
Figure 10 is the block diagram of a kind of device for database recovery according to an exemplary embodiment.Such as, this device 2900 may be provided in a server.
With reference to Figure 10, device 2900 comprises processing components 2922, and it comprises one or more processor further, and the memory resource representated by storer 2932, can such as, by the instruction of the execution of processing components 2922, application program for storing.The application program stored in storer 2932 can comprise each module corresponding to one group of instruction one or more.In addition, processing components 2922 is configured to perform instruction, to perform the method for above-mentioned server side.
Device 2900 can also comprise the power management that a power supply module 2926 is configured to actuating unit 2900, and a wired or wireless network interface 2950 is configured to device 2900 to be connected to network, and input and output (I/O) interface 2958.Device 2900 can operate the operating system based on being stored in storer 2932, such as WindowsServerTM, MacOSXTM, UnixTM, LinuxTM, FreeBSDTM or similar.
Those skilled in the art, at consideration instructions and after putting into practice invention disclosed herein, will easily expect other embodiment of the present invention.The application is intended to contain any modification of the present invention, purposes or adaptations, and these modification, purposes or adaptations are followed general principle of the present invention and comprised the undocumented common practise in the art of the disclosure or conventional techniques means.Instructions and embodiment are only regarded as exemplary, and true scope of the present invention and spirit are pointed out by appended claim.
Should be understood that, the present invention is not limited to precision architecture described above and illustrated in the accompanying drawings, and can carry out various amendment and change not departing from its scope.Scope of the present invention is only limited by appended claim.
Claims (11)
1. a database restoring method, is characterized in that, described method is used for by master library and the Database Systems that form from storehouse, identical with the data of described master library from the data in storehouse described in time initial; Described method comprises:
Obtain completed operation on described master library in chronological order;
After getting described operation, postpone preset duration based on the deadline of the described operation of current acquisition after, perform identical operation described from storehouse at every turn;
When mistake appears in described master library, determine the faulty operation led to errors;
Judge whether described faulty operation performs from storehouse described;
If described faulty operation not yet performs from storehouse described, then recover from the data of data to described master library in storehouse described in using.
2. method according to claim 1, is characterized in that, describedly obtains completed operation on described master library in chronological order, comprising:
Sequentially read the operation be documented in master library Operation Log.
3. method according to claim 1, is characterized in that, described based on the deadline of the described operation of current acquisition, postpone preset duration after perform identical operation described from storehouse, comprising:
Obtain the described current time from storehouse;
Judge whether the deadline of the described operation of current acquisition and the difference of described current time are less than described preset duration;
If be less than described preset duration, then return and obtain the described step from the current time in storehouse;
If be more than or equal to described preset duration, then perform the operation identical with described operation described from storehouse.
4. method according to claim 1, is characterized in that, recovers, comprising described in described use from the data of the data in storehouse to described master library:
In the described operation executed from storehouse before described faulty operation;
The described data data to described master library current from storehouse are used to repair, to make the date restoring of described master library to the state performed before described faulty operation.
5. method according to claim 1, is characterized in that, described method also comprises:
Input according to user is modified to described preset duration.
6. a database recovery device, is characterized in that, described device is used for by master library and the Database Systems that form from storehouse, identical with the data of described master library from the data in storehouse described in time initial; Described device comprises:
Master library operation acquisition module, for obtaining completed operation on described master library in chronological order, after getting described operation, triggers from storehouse async backup module at every turn;
From storehouse async backup module, for based on the deadline of the described operation of the current acquisition of master library operation acquisition module, after postponing preset duration, perform identical operation described from storehouse;
Recover judge module, for when mistake appears in described master library, determine the faulty operation led to errors, judge whether described faulty operation performs from storehouse described, if described faulty operation not yet performs from storehouse described, then trigger data recovers module;
Data recovery module, recovers from the data of data to described master library in storehouse described in using.
7. device according to claim 6, is characterized in that, described master library operation acquisition module comprises:
Order reading submodule, for sequentially reading the operation be documented in master library Operation Log;
Backup triggers module, after getting described operation, triggers from storehouse async backup module at every turn.
8. device according to claim 6, is characterized in that, describedly comprises from storehouse async backup module:
Time obtains submodule, for obtaining the described current time from storehouse;
Time contrast submodule, whether the difference for the deadline and described current time that judge the described operation of current acquisition is less than described preset duration, if be less than described preset duration, then the triggered time obtains submodule, if be more than or equal to described preset duration, then perform the operation identical with described operation described from storehouse.
9. device according to claim 6, is characterized in that, described data recovery module comprises:
Recover to prepare submodule, in the described operation executed from storehouse before described faulty operation;
Data restore submodule, for using the described data data to described master library current from storehouse to repair, to make the date restoring of described master library to the state performed before described faulty operation.
10. device according to claim 6, is characterized in that, described device also comprises:
Duration modified module, modifies to described preset duration for the input according to user.
11. 1 kinds of database recovery devices, is characterized in that, described device is used for by master library and the Database Systems that form from storehouse, and identical with the data of described master library from the data in storehouse described in time initial, described device comprises:
Processor;
For the storer of storage of processor executable instruction;
Wherein, described processor is configured to:
Obtain completed operation on described master library in chronological order;
After getting described operation, postpone preset duration based on the deadline of the described operation of current acquisition after, perform identical operation described from storehouse at every turn;
When mistake appears in described master library, determine the faulty operation led to errors;
Judge whether described faulty operation performs from storehouse described;
If described faulty operation not yet performs from storehouse described, then recover from the data of data to described master library in storehouse described in using.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510400419.0A CN105045678B (en) | 2015-07-09 | 2015-07-09 | Database restoring method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510400419.0A CN105045678B (en) | 2015-07-09 | 2015-07-09 | Database restoring method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105045678A true CN105045678A (en) | 2015-11-11 |
| CN105045678B CN105045678B (en) | 2018-10-26 |
Family
ID=54452242
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510400419.0A Active CN105045678B (en) | 2015-07-09 | 2015-07-09 | Database restoring method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105045678B (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105528264A (en) * | 2015-12-18 | 2016-04-27 | 福建随行软件有限公司 | Anti-misoperation data recovery method and system |
| CN106802895A (en) * | 2015-11-26 | 2017-06-06 | 阿里巴巴集团控股有限公司 | For repair data storehouse for database data method and apparatus |
| CN110263095A (en) * | 2019-05-31 | 2019-09-20 | 众安在线财产保险股份有限公司 | Backup and recovery method, apparatus, computer equipment and storage medium |
| CN115454951A (en) * | 2022-10-18 | 2022-12-09 | 读书郎教育科技有限公司 | Teaching data sharing system |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1659522A (en) * | 2002-04-19 | 2005-08-24 | 电脑联合想象公司 | Method and system for disaster recovery |
| CN101034364A (en) * | 2007-04-02 | 2007-09-12 | 华为技术有限公司 | Method, device and system for implementing RAM date backup |
| CN101038591A (en) * | 2007-04-11 | 2007-09-19 | 华为技术有限公司 | Method and system for synchronizing data base |
| CN101187888A (en) * | 2007-12-11 | 2008-05-28 | 浪潮电子信息产业股份有限公司 | Method for coping database data in heterogeneous environment |
| CN101216843A (en) * | 2008-01-17 | 2008-07-09 | 四川大学 | Multi-point multi-level data real time backup method |
| CN102945195A (en) * | 2012-11-26 | 2013-02-27 | 国电南瑞科技股份有限公司 | Master-standby redundancy replication method based on SQLite databases |
| CN102968479A (en) * | 2012-11-19 | 2013-03-13 | 嘉兴电力局 | Safety zone crossing database backup method |
| CN103019875A (en) * | 2012-12-19 | 2013-04-03 | 北京世纪家天下科技发展有限公司 | Method and device for realizing double main reconstruction of database |
| CN103136070A (en) * | 2011-11-30 | 2013-06-05 | 阿里巴巴集团控股有限公司 | Method and device for processing data disaster tolerance |
| CN103345470A (en) * | 2013-05-31 | 2013-10-09 | 深圳市沃信科技有限公司 | Database disaster tolerance method, database disaster tolerance system and server |
| CN103699548A (en) * | 2012-09-27 | 2014-04-02 | 阿里巴巴集团控股有限公司 | Method and equipment for recovering database data by using logs |
| CN103870357A (en) * | 2012-12-17 | 2014-06-18 | 中国移动通信集团河南有限公司 | Method and system for carrying out data replication |
-
2015
- 2015-07-09 CN CN201510400419.0A patent/CN105045678B/en active Active
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1659522A (en) * | 2002-04-19 | 2005-08-24 | 电脑联合想象公司 | Method and system for disaster recovery |
| CN101034364A (en) * | 2007-04-02 | 2007-09-12 | 华为技术有限公司 | Method, device and system for implementing RAM date backup |
| CN101038591A (en) * | 2007-04-11 | 2007-09-19 | 华为技术有限公司 | Method and system for synchronizing data base |
| CN101187888A (en) * | 2007-12-11 | 2008-05-28 | 浪潮电子信息产业股份有限公司 | Method for coping database data in heterogeneous environment |
| CN101216843A (en) * | 2008-01-17 | 2008-07-09 | 四川大学 | Multi-point multi-level data real time backup method |
| CN103136070A (en) * | 2011-11-30 | 2013-06-05 | 阿里巴巴集团控股有限公司 | Method and device for processing data disaster tolerance |
| CN103699548A (en) * | 2012-09-27 | 2014-04-02 | 阿里巴巴集团控股有限公司 | Method and equipment for recovering database data by using logs |
| CN102968479A (en) * | 2012-11-19 | 2013-03-13 | 嘉兴电力局 | Safety zone crossing database backup method |
| CN102945195A (en) * | 2012-11-26 | 2013-02-27 | 国电南瑞科技股份有限公司 | Master-standby redundancy replication method based on SQLite databases |
| CN103870357A (en) * | 2012-12-17 | 2014-06-18 | 中国移动通信集团河南有限公司 | Method and system for carrying out data replication |
| CN103019875A (en) * | 2012-12-19 | 2013-04-03 | 北京世纪家天下科技发展有限公司 | Method and device for realizing double main reconstruction of database |
| CN103345470A (en) * | 2013-05-31 | 2013-10-09 | 深圳市沃信科技有限公司 | Database disaster tolerance method, database disaster tolerance system and server |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106802895A (en) * | 2015-11-26 | 2017-06-06 | 阿里巴巴集团控股有限公司 | For repair data storehouse for database data method and apparatus |
| CN106802895B (en) * | 2015-11-26 | 2020-06-02 | 阿里巴巴集团控股有限公司 | Method and device for repairing database backup data |
| CN105528264A (en) * | 2015-12-18 | 2016-04-27 | 福建随行软件有限公司 | Anti-misoperation data recovery method and system |
| CN105528264B (en) * | 2015-12-18 | 2018-08-21 | 福建随行软件有限公司 | Fool proof data reconstruction method and its system |
| CN109117314A (en) * | 2015-12-18 | 2019-01-01 | 福建随行软件有限公司 | A kind of fool proof data back up method and system |
| CN109165121A (en) * | 2015-12-18 | 2019-01-08 | 福建随行软件有限公司 | Restore the method and system for the data being misused |
| CN109240854A (en) * | 2015-12-18 | 2019-01-18 | 福建随行软件有限公司 | Data reconstruction method and system |
| CN109165121B (en) * | 2015-12-18 | 2021-03-23 | 福建随行软件有限公司 | Method and system for recovering misoperation data |
| CN110263095A (en) * | 2019-05-31 | 2019-09-20 | 众安在线财产保险股份有限公司 | Backup and recovery method, apparatus, computer equipment and storage medium |
| CN110263095B (en) * | 2019-05-31 | 2021-10-01 | 众安在线财产保险股份有限公司 | Data backup and recovery method and device, computer equipment and storage medium |
| CN115454951A (en) * | 2022-10-18 | 2022-12-09 | 读书郎教育科技有限公司 | Teaching data sharing system |
| CN115454951B (en) * | 2022-10-18 | 2023-06-30 | 读书郎教育科技有限公司 | Teaching data sharing system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105045678B (en) | 2018-10-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9372908B2 (en) | Merging an out of synchronization indicator and a change recording indicator in response to a failure in consistency group formation | |
| US7539980B1 (en) | Method and apparatus for concurrency testing within a model-based testing environment | |
| CN106354583B (en) | A kind of heat backup method and system of MySQL database | |
| US8285679B2 (en) | Creating a buffer point-in-time copy relationship for a point-in-time copy function executed to create a point-in-time copy relationship | |
| US9251230B2 (en) | Exchanging locations of an out of synchronization indicator and a change recording indicator via pointers | |
| CN105045678A (en) | Database recovery method and apparatus | |
| CN104252481A (en) | Dynamic check method and device for consistency of main and salve databases | |
| CN105824846B (en) | Data migration method and device | |
| CN109918229B (en) | Database cluster copy construction method and device in non-log mode | |
| CN107025224B (en) | Method and equipment for monitoring task operation | |
| US20180121302A1 (en) | Data mirror volume verification | |
| CN110008129B (en) | Reliability test method, device and equipment for storage timing snapshot | |
| US8751762B2 (en) | Prevention of overlay of production data by point in time copy operations in a host based asynchronous mirroring environment | |
| CN110263095B (en) | Data backup and recovery method and device, computer equipment and storage medium | |
| CN102385537B (en) | Disk failure processing method of multi-copy storage system | |
| CN103810060A (en) | Data backup method and system thereof based on distributed database | |
| US20150378630A1 (en) | Method and Device of Data Protection, Storage Equipment | |
| CN105574026A (en) | Method and device for service supporting by using non-relational database | |
| CN103279408A (en) | RAID (redundant array of inexpensive disk) performance testing method | |
| US9015116B2 (en) | Consistent replication of transactional updates | |
| CN108241543B (en) | Method, service server and system for executing service operation breakpoint | |
| CN104298773A (en) | Automatic base switching system and method for ETL operations | |
| US20160147612A1 (en) | Method and system to avoid deadlocks during a log recovery | |
| CN105630625A (en) | Method and device for detecting consistency between data copies | |
| CN105630626B (en) | Transaction backup processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |