CN105573859A - Data recovery method and device of database - Google Patents
Data recovery method and device of database Download PDFInfo
- Publication number
- CN105573859A CN105573859A CN201410545761.5A CN201410545761A CN105573859A CN 105573859 A CN105573859 A CN 105573859A CN 201410545761 A CN201410545761 A CN 201410545761A CN 105573859 A CN105573859 A CN 105573859A
- Authority
- CN
- China
- Prior art keywords
- data
- database
- backed
- backup
- abnormal
- 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.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
Abstract
The embodiment of the invention discloses a data recovery method and device of a database. The method comprises the following steps of verifying data in a database index with data in a database file to determine abnormal data in the database when the database encounters a data abnormality situation; looking for a log file and a backup file of the database according to the abnormal data, and acquiring data to be backed up corresponding to the abnormal data; and substituting the abnormal data with the data to be backed up.
Description
Technical field
The present invention relates to field of data storage, particularly relate to a kind of data reconstruction method and equipment of database.
Background technology
At present, database is that database stops service or database to provide service under the state of exception for the general processing mode of data exception.But, sometimes when database is abnormal, need the date restoring of database to state for the previous period.Now, if database cannot recover data in mode fast and accurately, will database be caused cannot to provide correct data for a long time, and cause the not convenient of user or cause relevant business cannot normal operation.
Summary of the invention
For solving the problems of the technologies described above, the embodiment of the present invention expects the data reconstruction method and the equipment that provide a kind of database, improves stability and the work efficiency of service operation.
Technical scheme of the present invention is achieved in that
First aspect, embodiments provides a kind of data recovery apparatus of database, it is characterized in that, described data recovery apparatus comprises: detecting unit, verification unit, search unit and recovery unit, wherein,
, in operational process, there is data exception for detecting described database, and when detecting described database and occurring data exception, trigger described verification unit in described detecting unit;
Described verification unit, for detect when described detecting unit described database there is data exception time, data in data in described database index and described database file are verified, determine the abnormal data in described database, and search unit described in being transferred to by described abnormal data;
Describedly search unit, the described abnormal data for determining according to described verification unit searches journal file and the backup file of described database, obtains the to be backed up data corresponding with described abnormal data, and described data to be backed up are transferred to described recovery unit;
Described recovery unit, for replacing described abnormal data by described data described to be backed up of searching unit acquisition.
Further, described detecting unit, for when described database execution architecture query language SQL access or more new data time, detect described data exception; Or, detect described database and extremely exit; Or, detect described database and extremely exit rear startup.
Further, described in search unit, for searching described journal file according to described abnormal data, obtain data to be backed up corresponding with described abnormal data in described journal file; And,
When not finding the to be backed up data corresponding with described abnormal data in described journal file, searching described backup file according to described abnormal data, obtaining data to be backed up corresponding with described abnormal data in described backup file; And,
When not finding the to be backed up data corresponding with described abnormal data in described backup file, remove described abnormal data.
Further, described recovery unit, for removing the abnormal data in described database; And described data to be backed up are inserted in described database.
Further, described data recovery apparatus also comprises backup units, for backing up the data in described database according to the backup policy preset, obtains described backup file.
Further, described backup units, for: according to the system busy extent of the periodic quantity preset and/or described database, described database is backed up.
Further, described backup units, for: back up meeting other data of significance level preset in described database.
Further, described backup units, also for: before according to described default backup policy the data in described database being backed up, the journal file of described database is removed, and indicates described database again to record described journal file.
Second aspect, embodiments provides a kind of data reconstruction method of database, it is characterized in that, described method comprises:
When data exception appears in described database, the data in the data in described database index and described database file are verified, determines the abnormal data in described database;
Search journal file and the backup file of described database according to described abnormal data, obtain the to be backed up data corresponding with described abnormal data;
Described data to be backed up are replaced described abnormal data.
Further, there is data exception in described database, comprising: when described database execution architecture query language SQL access or more new data time, described data exception; Or described database is abnormal to be exited; Or described database is abnormal exits rear startup.
Further, described journal file and the backup file searching described database according to described abnormal data, obtains the to be backed up data corresponding with described abnormal data, comprising:
Search described journal file according to described abnormal data, obtain data to be backed up corresponding with described abnormal data in described journal file;
When not finding the to be backed up data corresponding with described abnormal data in described journal file, searching described backup file according to described abnormal data, obtaining data to be backed up corresponding with described abnormal data in described backup file;
When not finding the to be backed up data corresponding with described abnormal data in described backup file, remove described abnormal data.
Further, described described data to be backed up are replaced described abnormal data, comprising:
Remove the abnormal data in described database; And described data to be backed up are inserted in described database.
Further, described method also comprises: back up the data in described database according to the backup policy preset, obtain described backup file.
Further, the described backup policy according to presetting backs up the data in described database, comprising:
According to the system busy extent of the periodic quantity preset and/or described database, described database is backed up.
Further, the described backup policy according to presetting backs up the data in described database, comprising:
Back up meeting other data of significance level preset in described database.
Further, before backing up the data in described database according to described default backup policy, described method also comprises: removed by the journal file of described database, and indicates described database again to record described journal file.
Embodiments provide a kind of data reconstruction method and equipment of database, by carrying out data check when database is abnormal, and by backup and journal file, abnormal data is recovered, thus improve stability and the work efficiency of service operation.
Accompanying drawing explanation
The data reconstruction method schematic flow sheet of a kind of database that Fig. 1 provides for the embodiment of the present invention;
Mapping relations schematic diagram between data in a kind of database index value that Fig. 2 provides for the embodiment of the present invention and database;
For the structural representation of the file of date restoring in a kind of database that Fig. 3 provides for the embodiment of the present invention;
The data recovery apparatus structural representation of a kind of database that Fig. 4 provides for the embodiment of the present invention;
The data recovery apparatus structural representation of the another kind of database that Fig. 5 provides for the embodiment of the present invention.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly and completely described.
See Fig. 1, it illustrates the data reconstruction method flow process of a kind of database that the embodiment of the present invention provides, the method can be applied in described database, and the method can comprise:
Data in data in described database index and described database file are verified, determine the abnormal data in described database by S101: when data exception appears in described database;
Exemplarily, in the present embodiment, there is data exception in described database, can comprise: when described database execution architecture query language SQL access or more new data time, described data exception, such as: the index of database has occurred that repeat key or index value are an illegal value; Or described database is abnormal to be exited; Or described database is abnormal exits rear startup etc.After these abnormal generations, all need by determining whether these abnormal conditions are because the exception of data or index causes.
Exemplarily, data in data in described database index and described database file are verified, can verify according to the mapping relations between the data in the described database index value shown in Fig. 2 and described database, specifically can comprise the following steps: the table that first during acquisition data exception, database is operating; Then the index of this table is compared one by one with the data in database file, judge the accuracy of data thus: if consistent, then illustrate accurately; If inconsistent, then illustrate inaccurate, these data are abnormal data.
S102: journal file and the backup file of searching described database according to described abnormal data, obtains the to be backed up data corresponding with described abnormal data;
Exemplarily, for the file of date restoring in described database as shown in Figure 3, described journal file and the backup file searching described database according to described abnormal data, obtains the to be backed up data corresponding with described abnormal data, comprising:
Search described journal file according to described abnormal data, obtain data to be backed up corresponding with described abnormal data in described journal file; And,
When not finding the to be backed up data corresponding with described abnormal data in described journal file, searching described backup file according to described abnormal data, obtaining data to be backed up corresponding with described abnormal data in described backup file; And,
When not finding the to be backed up data corresponding with described abnormal data in described backup file, remove described abnormal data, it should be noted that, when in journal file and backup file all less than the to be backed up data corresponding with described abnormal data, so illustrate that the importance information of described abnormal data is lower, therefore, can directly delete by just unessential abnormal data.
Also it should be noted that, owing to there is certain time interval between backup at every turn, so within this time interval, only have journal file can reflect the data manipulation of database, such as the amendment of database of record and the binlog daily record of potential act of revision, this file can be used for making up the data recording loss that the time interval due to two backup files causes, thus data to be backed up can be reflected as much as possible, and the data cases in that moment of data exception appears in database.
S103: described data to be backed up are replaced described abnormal data;
Exemplarily, described described data to be backed up are replaced described abnormal data, specifically can comprise:
Remove the abnormal data in described database; And described data to be backed up are inserted in described database.
Particularly, in the present embodiment, first the abnormal data in database can be disposed, then data to be backed up be formed an insert statement and be inserted in database.
It should be noted that, because data to be backed up obtain from journal file and backup file, and journal file is database records in operational process, therefore, in the present embodiment, described method can also comprise: back up the data in described database according to the backup policy preset.
Alternatively, the described backup policy according to presetting backs up the data in described database, comprising:
According to the busy extent of the periodic quantity preset and/or described database, described database is backed up.
Such as, can back up database termly, also can when database running status to be idle, the cpu of such as database takies when disk I/O that is lower and database reads idle and backs up, and also both can be carried out taking into consideration the time of carrying out backing up.
Understandable, backing up obtained backup file to database, can be backup logic, such as load operation; Also can be physical backup, such as export operation.Preferably first carry out backup logic in the present embodiment, because physical backup needs the data backing up whole database, therefore usually to use when severely subnormal appears in database.
Alternatively, the described backup policy according to presetting backs up the data in described database, comprising:
Back up meeting other data of significance level preset in described database.
Such as, data in database can be carried out partition of the level according to importance degree, the data lower for importance information can not back up, thus make when data exception appears in the data that these importance information are lower, directly carry out delete processing and just can recover database.
Alternatively, before backing up the data in described database according to described default backup policy, described method also comprises: removed by the journal file of described database, and indicates described database again to record described journal file;
In the present embodiment, because journal file carries out record by database, therefore, in time backing up, the data before backup time have been kept in backup file, so, part content in journal file before backup time just there is no need to preserve, so the present embodiment preferably, by referred database, the part content in journal file before backup time is deleted, thus the storage space of database can be saved.Understandably, when data exception appears in database, the data of preserving in journal file are the data between backup time to data exception moment; And the data before backup time are kept in backup file.
Embodiments provide a kind of data reconstruction method of database, by verifying data when data exception appears in database, note abnormalities data, and replaced by abnormal data according to the journal file of database and backup file, thus improve stability and the work efficiency of service operation.
Based on the technical conceive that previous embodiment is identical, see Fig. 4, it illustrates data recovery apparatus 40 structure of a kind of database that the embodiment of the present invention provides, this equipment 40 is applied in database, particularly, this equipment 40 can be separately exist in outside database, also can be coupled in a database by the mode of hardware and software, the embodiment of the present invention does not do concrete restriction to this, this equipment 40 can comprise: detecting unit 401, verification unit 402, search unit 403 and recovery unit 404, wherein
, there is data exception for detecting described database in described detecting unit 401, and when detecting described database and occurring data exception, trigger described verification unit 402 in operational process;
Described verification unit 402, for detect when described detecting unit 401 described database there is data exception time, data in data in described database index and described database file are verified, determine the abnormal data in described database, and search unit 403 described in being transferred to by described abnormal data;
Describedly search unit 403, described abnormal data for determining according to described verification unit 402 searches journal file and the backup file of described database, obtain the to be backed up data corresponding with described abnormal data, and described data to be backed up are transferred to described recovery unit 404;
Described recovery unit 404, for searching the data described to be backed up that unit 403 obtains replace described abnormal data by described.
Exemplarily, described detecting unit 401, for when described database execution architecture query language SQL access or more new data time, detect described data exception; Or, detect described database and extremely exit; Or, detect described database and extremely exit rear startup.
Exemplarily, the table that when verification unit 402 specifically may be used for obtaining data exception, database is operating; The index of this table is compared one by one with the data in database file, judges the accuracy of data thus: if consistent, then illustrate accurately; If inconsistent, then illustrate inaccurate, these data are abnormal data.
Exemplarily, described in search unit 403, for searching described journal file according to described abnormal data, obtain data to be backed up corresponding with described abnormal data in described journal file; And,
When not finding the to be backed up data corresponding with described abnormal data in described journal file, searching described backup file according to described abnormal data, obtaining data to be backed up corresponding with described abnormal data in described backup file; And,
When not finding the to be backed up data corresponding with described abnormal data in described backup file, remove described abnormal data.It should be noted that, when in journal file and backup file all less than the to be backed up data corresponding with described abnormal data, so illustrate that the importance information of described abnormal data is lower, therefore, can directly delete by just unessential abnormal data.
Exemplarily, described recovery unit 404, for removing the abnormal data in described database; And described data to be backed up are inserted in described database.Particularly, in the present embodiment, the abnormal data in database can first be disposed by recovery unit 404, then data to be backed up is formed an insert statement and is inserted in database.
It should be noted that, because data to be backed up obtain from journal file and backup file, and journal file is database records in operational process, therefore, in the present embodiment, see Fig. 5, described data recovery apparatus 40 also comprises backup units 405, for backing up the data in described database according to the backup policy preset, obtain described backup file.
Alternatively, described backup units 405, for: according to the system busy extent of the periodic quantity preset and/or described database, described database is backed up.
Such as, backup units 405 can back up database termly, also can when database running status to be idle, the cpu of such as database takies when disk I/O that is lower and database reads idle and backs up, and also both can be carried out taking into consideration the time of carrying out backing up.
Understandable, backup units 405 pairs of databases back up obtained backup file, can be backup logics, such as load operation; Also can be physical backup, such as export operation.Preferably first carry out backup logic in the present embodiment, because physical backup needs the data backing up whole database, therefore usually to use when severely subnormal appears in database.
Alternatively, described backup units 405, for: back up meeting other data of significance level preset in described database.
Such as, data in database can be carried out partition of the level according to importance degree by backup units 405, the data lower for importance information can not back up, thus make when data exception appears in the data that these importance information are lower, directly carry out delete processing and just can recover database.
Alternatively, described backup units 405, also for: before according to described default backup policy the data in described database being backed up, the journal file of described database is removed, and indicates described database again to record described journal file.
Because journal file carries out record by database, therefore, when backup units 405 backs up time, data before backup time have been kept in backup file, and so, the part content in journal file before backup time just there is no need to preserve, so, the present embodiment preferably, deleted by referred database by backup units 405, thus can save the storage space of database by the part content in journal file before backup time.Understandably, when data exception appears in database, the data of preserving in journal file are the data between backup time to data exception moment; And the data before backup time are kept in backup file.
Embodiments provide a kind of data recovery apparatus 40 of database, by carrying out data check when database is abnormal, and by backup and journal file, abnormal data is recovered, thus improve stability and the work efficiency of service operation.
Those skilled in the art should understand, embodiments of the invention can be provided as method, system or computer program.Therefore, the present invention can adopt the form of hardware embodiment, software implementation or the embodiment in conjunction with software and hardware aspect.And the present invention can adopt in one or more form wherein including the upper computer program implemented of computer-usable storage medium (including but not limited to magnetic disk memory and optical memory etc.) of computer usable program code.
The present invention describes with reference to according to the process flow diagram of the method for the embodiment of the present invention, equipment (system) and computer program and/or block scheme.Should understand can by the combination of the flow process in each flow process in computer program instructions realization flow figure and/or block scheme and/or square frame and process flow diagram and/or block scheme and/or square frame.These computer program instructions can being provided to the processor of multi-purpose computer, special purpose computer, Embedded Processor or other programmable data processing device to produce a machine, making the instruction performed by the processor of computing machine or other programmable data processing device produce device for realizing the function of specifying in process flow diagram flow process or multiple flow process and/or block scheme square frame or multiple square frame.
These computer program instructions also can be stored in can in the computer-readable memory that works in a specific way of vectoring computer or other programmable data processing device, the instruction making to be stored in this computer-readable memory produces the manufacture comprising command device, and this command device realizes the function of specifying in process flow diagram flow process or multiple flow process and/or block scheme square frame or multiple square frame.
These computer program instructions also can be loaded in computing machine or other programmable data processing device, make on computing machine or other programmable devices, to perform sequence of operations step to produce computer implemented process, thus the instruction performed on computing machine or other programmable devices is provided for the step realizing the function of specifying in process flow diagram flow process or multiple flow process and/or block scheme square frame or multiple square frame.
The above, be only preferred embodiment of the present invention, be not intended to limit protection scope of the present invention.
Claims (16)
1. a data recovery apparatus for database, is characterized in that, described data recovery apparatus comprises: detecting unit, verification unit, search unit and recovery unit, wherein,
, in operational process, there is data exception for detecting described database, and when detecting described database and occurring data exception, trigger described verification unit in described detecting unit;
Described verification unit, for detect when described detecting unit described database there is data exception time, data in data in described database index and described database file are verified, determine the abnormal data in described database, and search unit described in being transferred to by described abnormal data;
Describedly search unit, the described abnormal data for determining according to described verification unit searches journal file and the backup file of described database, obtains the to be backed up data corresponding with described abnormal data, and described data to be backed up are transferred to described recovery unit;
Described recovery unit, for replacing described abnormal data by described data described to be backed up of searching unit acquisition.
2. data recovery apparatus according to claim 1, is characterized in that, described detecting unit, for when described database execution architecture query language SQL access or more new data time, detect described data exception; Or, detect described database and extremely exit; Or, detect described database and extremely exit rear startup.
3. data recovery apparatus according to claim 1, is characterized in that, described in search unit, for searching described journal file according to described abnormal data, obtain data to be backed up corresponding with described abnormal data in described journal file; And,
When not finding the to be backed up data corresponding with described abnormal data in described journal file, searching described backup file according to described abnormal data, obtaining data to be backed up corresponding with described abnormal data in described backup file; And,
When not finding the to be backed up data corresponding with described abnormal data in described backup file, remove described abnormal data.
4. data recovery apparatus according to claim 1, is characterized in that, described recovery unit, for removing the abnormal data in described database; And described data to be backed up are inserted in described database.
5. the data recovery apparatus according to any one of Claims 1-4, is characterized in that, described data recovery apparatus also comprises backup units, for backing up the data in described database according to the backup policy preset, obtains described backup file.
6. data recovery apparatus according to claim 5, is characterized in that, described backup units, for: according to the system busy extent of the periodic quantity preset and/or described database, described database is backed up.
7. data recovery apparatus according to claim 5, is characterized in that, described backup units, for: back up meeting other data of significance level preset in described database.
8. data recovery apparatus according to claim 5, it is characterized in that, described backup units, also for: before according to described default backup policy the data in described database being backed up, the journal file of described database is removed, and indicates described database again to record described journal file.
9. a data reconstruction method for database, is characterized in that, described method comprises:
When data exception appears in described database, the data in the data in described database index and described database file are verified, determines the abnormal data in described database;
Search journal file and the backup file of described database according to described abnormal data, obtain the to be backed up data corresponding with described abnormal data;
Described data to be backed up are replaced described abnormal data.
10. method according to claim 9, is characterized in that, data exception appears in described database, comprising: when described database execution architecture query language SQL access or more new data time, described data exception; Or described database is abnormal to be exited; Or described database is abnormal exits rear startup.
11. methods according to claim 9, is characterized in that, described journal file and the backup file searching described database according to described abnormal data, obtain the to be backed up data corresponding with described abnormal data, comprising:
Search described journal file according to described abnormal data, obtain data to be backed up corresponding with described abnormal data in described journal file;
When not finding the to be backed up data corresponding with described abnormal data in described journal file, searching described backup file according to described abnormal data, obtaining data to be backed up corresponding with described abnormal data in described backup file;
When not finding the to be backed up data corresponding with described abnormal data in described backup file, remove described abnormal data.
12. methods according to claim 9, is characterized in that, described described data to be backed up are replaced described abnormal data, comprising:
Remove the abnormal data in described database; And described data to be backed up are inserted in described database.
13. methods according to any one of claim 9 to 12, it is characterized in that, described method also comprises: back up the data in described database according to the backup policy preset, obtain described backup file.
14. methods according to claim 13, is characterized in that, the described backup policy according to presetting backs up the data in described database, comprising:
According to the system busy extent of the periodic quantity preset and/or described database, described database is backed up.
15. methods according to claim 13, is characterized in that, the described backup policy according to presetting backs up the data in described database, comprising:
Back up meeting other data of significance level preset in described database.
16. methods according to claim 13, it is characterized in that, before according to described default backup policy the data in described database being backed up, described method also comprises: removed by the journal file of described database, and indicates described database again to record described journal file.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410545761.5A CN105573859A (en) | 2014-10-15 | 2014-10-15 | Data recovery method and device of database |
| PCT/CN2015/074734 WO2016058333A1 (en) | 2014-10-15 | 2015-03-20 | Data recovery method and device for database, and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410545761.5A CN105573859A (en) | 2014-10-15 | 2014-10-15 | Data recovery method and device of database |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105573859A true CN105573859A (en) | 2016-05-11 |
Family
ID=55746049
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410545761.5A Withdrawn CN105573859A (en) | 2014-10-15 | 2014-10-15 | Data recovery method and device of database |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN105573859A (en) |
| WO (1) | WO2016058333A1 (en) |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106095808A (en) * | 2016-05-30 | 2016-11-09 | 厦门市美亚柏科信息股份有限公司 | The method and apparatus that a kind of MDB file fragmentation recovers |
| CN107315655A (en) * | 2017-06-02 | 2017-11-03 | 北京潘达互娱科技有限公司 | The ranking list data reconstruction method and device of a kind of real-time statistics |
| CN107766490A (en) * | 2017-10-17 | 2018-03-06 | 链家网（北京）科技有限公司 | Automatic operation method, system, equipment and the storage medium of SQL files |
| CN107885617A (en) * | 2017-10-19 | 2018-04-06 | 用友网络科技股份有限公司 | Export method, system, computer equipment and the readable storage medium storing program for executing of business datum |
| CN108459925A (en) * | 2018-02-10 | 2018-08-28 | 深圳市先河系统技术有限公司 | The restorative procedure of private clound equipment and its database, the device with store function |
| CN109062736A (en) * | 2018-08-20 | 2018-12-21 | 广州视源电子科技股份有限公司 | A kind of data back up method, device, equipment and storage medium |
| CN110737718A (en) * | 2018-07-18 | 2020-01-31 | 杭州海康威视系统技术有限公司 | Data backup method and device |
| CN111737056A (en) * | 2020-06-24 | 2020-10-02 | 中国银行股份有限公司 | File breakpoint reentrant method and device |
| CN112100143A (en) * | 2020-09-25 | 2020-12-18 | 平安科技（深圳）有限公司 | File compression storage method, device, equipment and storage medium |
| CN116737467A (en) * | 2023-08-15 | 2023-09-12 | 金篆信科有限责任公司 | Method, device, system and medium for automatic detection and repair of database |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111625396B (en) * | 2019-02-27 | 2023-05-26 | 阿里云计算有限公司 | Backup data verification method, server and storage medium |
| CN112363865A (en) * | 2020-10-19 | 2021-02-12 | 深圳云天励飞技术股份有限公司 | Database fault recovery method and device and face image search system |
| CN112749043B (en) * | 2021-01-15 | 2022-07-08 | 苏州浪潮智能科技有限公司 | Database disaster recovery method, system, device and medium |
| CN114077599B (en) * | 2021-10-15 | 2023-04-14 | 国电南瑞科技股份有限公司 | Method, device and system for constructing transformer sensing quantity database supporting dynamic data repair |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060047626A1 (en) * | 2004-08-24 | 2006-03-02 | Microsoft Corporation | Generating an optimized restore plan |
| US20060224636A1 (en) * | 2005-04-05 | 2006-10-05 | Microsoft Corporation | Page recovery using volume snapshots and logs |
| CN101495970A (en) * | 2005-06-24 | 2009-07-29 | 信科索尔特公司 | System and method for high performance enterprise data protection |
| CN101923573A (en) * | 2010-08-09 | 2010-12-22 | 哈尔滨工程大学 | Rapid database data recovery method aiming at data loss |
| CN102609337A (en) * | 2012-01-19 | 2012-07-25 | 北京神州数码思特奇信息技术股份有限公司 | Rapid data recovery method for memory database |
| WO2014120137A1 (en) * | 2013-01-30 | 2014-08-07 | Hewlett-Packard Development Company, L.P. | Recovering pages of a database |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| GB0208143D0 (en) * | 2002-04-09 | 2002-05-22 | Ibm | Data recovery system |
| CN100562858C (en) * | 2007-09-12 | 2009-11-25 | 华为技术有限公司 | The methods, devices and systems of EMS memory data-base remote disaster tolerance |
-
2014
- 2014-10-15 CN CN201410545761.5A patent/CN105573859A/en not_active Withdrawn
-
2015
- 2015-03-20 WO PCT/CN2015/074734 patent/WO2016058333A1/en active Application Filing
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060047626A1 (en) * | 2004-08-24 | 2006-03-02 | Microsoft Corporation | Generating an optimized restore plan |
| US20060224636A1 (en) * | 2005-04-05 | 2006-10-05 | Microsoft Corporation | Page recovery using volume snapshots and logs |
| CN101495970A (en) * | 2005-06-24 | 2009-07-29 | 信科索尔特公司 | System and method for high performance enterprise data protection |
| CN101923573A (en) * | 2010-08-09 | 2010-12-22 | 哈尔滨工程大学 | Rapid database data recovery method aiming at data loss |
| CN102609337A (en) * | 2012-01-19 | 2012-07-25 | 北京神州数码思特奇信息技术股份有限公司 | Rapid data recovery method for memory database |
| WO2014120137A1 (en) * | 2013-01-30 | 2014-08-07 | Hewlett-Packard Development Company, L.P. | Recovering pages of a database |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106095808A (en) * | 2016-05-30 | 2016-11-09 | 厦门市美亚柏科信息股份有限公司 | The method and apparatus that a kind of MDB file fragmentation recovers |
| CN107315655A (en) * | 2017-06-02 | 2017-11-03 | 北京潘达互娱科技有限公司 | The ranking list data reconstruction method and device of a kind of real-time statistics |
| CN107315655B (en) * | 2017-06-02 | 2020-05-19 | 北京潘达互娱科技有限公司 | Ranking list data recovery method and device for real-time statistics |
| CN107766490A (en) * | 2017-10-17 | 2018-03-06 | 链家网（北京）科技有限公司 | Automatic operation method, system, equipment and the storage medium of SQL files |
| CN107885617B (en) * | 2017-10-19 | 2021-05-11 | 用友网络科技股份有限公司 | Method, system, computer device and readable storage medium for exporting business data |
| CN107885617A (en) * | 2017-10-19 | 2018-04-06 | 用友网络科技股份有限公司 | Export method, system, computer equipment and the readable storage medium storing program for executing of business datum |
| CN108459925A (en) * | 2018-02-10 | 2018-08-28 | 深圳市先河系统技术有限公司 | The restorative procedure of private clound equipment and its database, the device with store function |
| CN108459925B (en) * | 2018-02-10 | 2022-05-31 | 深圳市先河系统技术有限公司 | Private cloud equipment, database repairing method thereof and device with storage function |
| CN110737718A (en) * | 2018-07-18 | 2020-01-31 | 杭州海康威视系统技术有限公司 | Data backup method and device |
| CN109062736A (en) * | 2018-08-20 | 2018-12-21 | 广州视源电子科技股份有限公司 | A kind of data back up method, device, equipment and storage medium |
| CN111737056A (en) * | 2020-06-24 | 2020-10-02 | 中国银行股份有限公司 | File breakpoint reentrant method and device |
| CN112100143A (en) * | 2020-09-25 | 2020-12-18 | 平安科技（深圳）有限公司 | File compression storage method, device, equipment and storage medium |
| CN112100143B (en) * | 2020-09-25 | 2023-03-21 | 平安科技（深圳）有限公司 | File compression storage method, device, equipment and storage medium |
| CN116737467A (en) * | 2023-08-15 | 2023-09-12 | 金篆信科有限责任公司 | Method, device, system and medium for automatic detection and repair of database |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2016058333A1 (en) | 2016-04-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105573859A (en) | Data recovery method and device of database | |
| US9372762B2 (en) | Systems and methods for restoring application data | |
| US10204019B1 (en) | Systems and methods for instantiation of virtual machines from backups | |
| US8250033B1 (en) | Replication of a data set using differential snapshots | |
| KR101556435B1 (en) | Database backing-up and recovering method and device | |
| US8392423B2 (en) | Data set index record preservation | |
| US20130246358A1 (en) | Online verification of a standby database in log shipping physical replication environments | |
| US20160203201A1 (en) | Data backup method and apparatus | |
| US10866866B2 (en) | Query fault processing method and processing apparatus | |
| WO2018006587A1 (en) | File storage method, terminal, and storage medium | |
| CN111078667A (en) | Data migration method and related device | |
| CN109491834B (en) | Data recovery method and device applied to database | |
| US8370815B2 (en) | Electronic device and method for debugging programs | |
| CN105556462A (en) | Writing to files and file meta-data | |
| CN117112522A (en) | Concurrent process log management method, device, equipment and storage medium | |
| US8595271B1 (en) | Systems and methods for performing file system checks | |
| US9471409B2 (en) | Processing of PDSE extended sharing violations among sysplexes with a shared DASD | |
| CN114490570A (en) | Production data synchronization method and device, data synchronization system and server | |
| US11645333B1 (en) | Garbage collection integrated with physical file verification | |
| CN108984343B (en) | Virtual machine backup and storage management method based on content analysis | |
| CN114791901A (en) | Data processing method, device, equipment and storage medium | |
| CN110688071A (en) | Data synchronization method and system for reducing data synchronization quantity | |
| CN110658989B (en) | System and method for backup storage garbage collection | |
| CN116257531B (en) | Database space recovery method | |
| CN112650447B (en) | Backup method, system and device for ceph distributed block storage |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20160511 |
|
| WW01 | Invention patent application withdrawn after publication |