CN103699548A - Method and equipment for recovering database data by using logs - Google Patents
Method and equipment for recovering database data by using logs Download PDFInfo
- Publication number
- CN103699548A CN103699548A CN201210369540.8A CN201210369540A CN103699548A CN 103699548 A CN103699548 A CN 103699548A CN 201210369540 A CN201210369540 A CN 201210369540A CN 103699548 A CN103699548 A CN 103699548A
- Authority
- CN
- China
- Prior art keywords
- data
- database
- time
- module
- calamity
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1458—Management of the backup or restore process
- G06F11/1469—Backup restoration techniques
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to a method and equipment for recovering database data by using logs. The method comprises the steps: converting business data in applications, which are distributed and run on one or more servers, into log data in real time in a predetermined format; receiving and storing the log data in one or more disaster backup log files; parsing the log data in the disaster backup log files in a predetermined time period into data with a database format, wherein the data with the database format is taken as parsed data; reconstructing the parsed data according to predetermined rules, so as to obtain reconstructed business data; updating the reconstructed business data to a standby database. The converting and receiving of the logs are real-time, so that when a database is damaged, data, lost after the last backup time point, of a regular database backup mechanism can be recovered.
Description
Technical field
The application relates generally to data processing field, relates in particular to a kind of method and apparatus of storage, processing and recovery of data.
Background technology
For the system that relates to data, the appropriate preservation of data is absolutely necessary.The for example preservation of Taobao's system to its user's shopping information, Alipay system is to preservation of user account information etc., and these data are generally held in database, yet, when database damages, will cause the loss of data.
At present, generally can adopt database schedule backup mechanism to back up and avoid database to damage the loss causing database.This mechanism can comprise master data base and standby database conventionally; master data base is stored real-time complete data; DB Backup program and equipment backup to standby database every the time interval of one section of setting by the data of master data base; when master data base is damaged, system just can be used standby database.Two databases have identical complete data layout and structure conventionally, so can very directly switch from master data base the data of using standby database.
Yet, the time interval of backup is generally a few minutes, several hours, so this backup actions is not to occur in real time, (as special situation, also can be set as to the extremely short time time interval to back up in realtime, but can consume a large amount of system resource like this, so conventionally do not adopt in this way.So), under the situation that master data base is damaged, data during the time point that the time point backing up for the last time from DB Backup program and equipment damages to master data base are not backed up to standby database, this partial data has been lost, and this is the problem that this database schedule backup mechanism exists.
Summary of the invention
It is a kind of by the method and apparatus of usage log restore database data that the application's fundamental purpose is to provide, data loss problem during the time point that the time point backing up for the last time from DB Backup program in the database schedule backup mechanism existing with solution prior art damages to master data base, wherein:
According to the application aspect, a kind of method that database data is recovered is provided, comprise the following steps: with predetermined format, convert the business datum distributing and operate in the application program on one or more server to daily record data in real time; Receive described daily record data and be stored in one or more calamities in journal file; Calamity in predetermined amount of time resolves to and possesses the data that the data of database format obtain as parsing for the daily record data in journal file; The data that parsing is obtained rebuild to obtain the business datum of reconstruction according to pre-defined rule; And the service data updating of rebuilding is arrived to standby database.
According to the method for the application's embodiment, also comprise, each of data that possesses database format has unique identifier, and wherein, described analyzing step also comprises: by described, possess the data of database format and the data of standby database are compared, the data that the different data that possess database format of unique identifier are obtained as parsing.
According to the method for the application's embodiment, analyzing step also comprises, the data that parsing is obtained store calamity into for volatile data base.
According to the method for the application's embodiment, reconstruction procedures also comprises, calamity is compared for the data of the data in volatile data base and standby database, and by calamity, for data markers errorless in volatile data base, be the business datum of rebuilding; It by calamity, for data markers wrong in volatile data base, is the business datum of not rebuilding.
Method according to the application's embodiment, also comprises, described analyzing step is carried out concurrently in multiple servers, and wherein, described reconstruction procedures is carried out in separate unit server.
Method according to the application's embodiment, also comprises, described one or more calamities are arranged in one or more home server of application program or one or more long-range calamity for server for journal file.
According to the method for the application's embodiment, also comprise, the start time of described predetermined amount of time early than or equal the time point that database backups to standby database for the last time, and the end time of described predetermined amount of time is later than or equals the time point that database breaks down.
Method according to the application's embodiment, also comprises, each business datum in business datum has time identifier, and reconstruction procedures also comprises that the data that parsing obtained according to described time identifier sort.
Method according to the application's embodiment, also comprises, the service data updating of rebuilding, in standby database process, under the situation that the partial data of standby database is modified, is backed up this partial data before revising.
According to the application aspect, a kind of equipment that database data is recovered is provided, comprise: daily record modular converter, it converts with predetermined format the business datum distributing and operate in the application program on one or more server to daily record data in real time; Daily record receiver module, it receives the daily record data of daily record modular converter output and is stored in one or more calamities in journal file; Log analyzing module, its calamity in setting-up time section resolves to and possesses the data that the data of database format obtain as parsing for the daily record data in journal file; Rebuild business data module, it is resolved by log analyzing module the data that obtain and according to pre-defined rule, rebuilds to obtain the business datum of reconstruction; And renewal business data module, it arrives standby database by the service data updating of rebuilding business data module reconstruction.
According in the equipment of the embodiment of the present application, each of data that possesses database format has unique identifier, and wherein, log analyzing module comprises the first comparing module, be configured to possess the data of database format and the data of standby database are compared, the data that the different data that possess database format of unique identifier are obtained as parsing by described.
According in the equipment of the embodiment of the present application, the data that log analyzing module is configured to parsing to obtain store calamity into for volatile data base.
According in the equipment of the embodiment of the present application, reconstruction business data module comprises, the second comparing module, is configured to calamity to compare for the data of the data in volatile data base and standby database, is the business datum of rebuilding by calamity for data markers errorless in volatile data base; It to calamity, for data markers wrong in volatile data base, is the business datum of not rebuilding.
According in the equipment of the embodiment of the present application, log analyzing module works in multiple servers concurrently, and wherein, rebuilds business data module and work in separate unit server.
According in the equipment of the embodiment of the present application, also comprise, the start time of described predetermined amount of time early than or equal the time point that database backups to standby database for the last time, and the end time of described predetermined amount of time is later than or equals the time point that database breaks down.
According in the equipment of the embodiment of the present application, each business datum in business datum has time identifier, and rebuilds business data module and be also configured to sort to resolving the data that obtain according to described time identifier.
According in the equipment of the embodiment of the present application, upgrade business data module and be configured to, under situation that the partial data when standby database is modified, this partial data before revising be backed up.
Compared with prior art, according to the application's technical scheme, can when application program is moved, with predetermined format, convert business datum to daily record data in real time and output to calamity for journal file in, when database damages, can for the Data Analysis of journal file, be the data that possess database format by calamity, undergo reconstruction, be updated to standby database.Because this method is carried out in real time application program is in service, time point this method that the time point backing up for the last time from DB Backup program and equipment damages to master data base is also being carried out, the business datum during the time point that the time point that its net result can recover to back up for the last time from DB Backup program and equipment damages to master data base.
Accompanying drawing explanation
Accompanying drawing described herein is used to provide further understanding of the present application, forms the application's a part, and the application's schematic description and description is used for explaining the application, does not form the improper restriction to the application.In the accompanying drawings:
Fig. 1 is the entire system structural representation that can implement the embodiment of the present application.
Fig. 2 is the module fundamental diagram according to the embodiment of the present application.
Fig. 3 is the method flow diagram that can implement the application.
Embodiment
The application's main thought is, in application program operational process, in real time business datum is stored with daily record data formal output, in order to recovering when database lost data.The output storage of daily record data form is different from the backup of database format, and its system resource taking is close to negligible.On the other hand, when master data base is damaged, although the data in standby database can directly be called, and daily record data need to just can be used through certain treatment step, and these daily record datas have made up the data that database schedule backup mechanism is lost.
For making the application's object, technical scheme and advantage clearer, below in conjunction with drawings and the specific embodiments, the application is described in further detail.
According to the application's embodiment, provide a kind of equipment that database data is recovered.
With reference to figure 1, Fig. 1 is the entire system structural representation that can implement the embodiment of the present application.
On server 110, move an application program 111, application program 111 stores master data base 130 into data in real time.Server 120 has the structure identical with server 110, also in real time data is stored into master data base 130.Master data base 130 backups to standby database 150 every the time interval of one section of setting by the data of master data base 130 by data base update program and equipment 140.In said system, the quantity of server can be not limited to two, can be more mainly with forming cluster, application program on every station server can be identical or different, and application program can be one or more, but application program can store data into master data base 130 to possess the data of database format.In addition, the various piece of an application program can lay respectively on different servers.
The application's equipment can comprise with lower module: daily record modular converter 112, and daily record receiver module 113, log analyzing module 114, rebuilds business data module 115, upgrades business data module 116.Alternatively, above-mentioned module can be positioned on server, for example, on server 110.Log analyzing module 114 can be configured to comprise the first comparing module 114b, rebuilds business data module and can be configured to comprise the second comparing module 115b.Alternatively, module 113 ~ 116 also can not be configured on server 110, and is configured on the standby host of server 110; Daily record modular converter 112 generally can be configured on server 110.When application program 111 operation, daily record modular converter 112 and daily record receiver module 113 be with application program real-time working together, and form calamity for journal file.When master data base is damaged, log analyzing module 114, reconstruction business data module 115, the 116 startup work of renewal business data module, described module can with calamity for volatile data base 160 carry out communication storing, to read, deal with data, described module by the service data updating of the reconstruction being obtained for journal file by calamity to standby database 150.
Below with reference to the principle of work of the modules of Fig. 2 DETAILED DESCRIPTION The present application equipment.Fig. 2 is the module fundamental diagram according to the embodiment of the present application.
During application program 111 operation, produce in real time business datum 201, daily record modular converter 112 is converted to daily record data 202 by business datum 201 in real time, and daily record receiver module 11 3 stores daily record data 202 into calamity for journal file 203.
When master data base breaks down, log analyzing module 114 is the data 204 that possess database format by calamity for the Data Analysis of the setting-up time section in journal file 203, the time period of setting is generally data base update program and equipment 140 backups to master data base 130 time point of standby database 150 for the last time to the time point of master data base 1 30 damages, in order to ensure recovering the complete of data segment, also time period that can setting is set to initial time and for the last time master data base 130 is backuped to the time point of standby database 150 early than data base update program and equipment 140, and (or) end time is later than the time point that master data base 130 is damaged.According to the application's embodiment, initial time is later than early than time point and/or the end time of last backup the time point that master data base is damaged, how long specifically need early and/or evening how long, this for example can need to set according to system, or for example can set in the situation of considering cost.For example, the time point that the regular master data base 130 of database backups to standby database 150 is for the last time 12:55, and master data base is damaged in 12:59, can select the data of recovering the following period to recover: a:12:55 ~ 12:59; B:12:50 ~ 12:59; C:12:55 ~ 13:00; D:12:50 ~ 13:00.
In practice, the parsing time period of above-mentioned selection is generally longer than the time period of data actual loss, so system can adopt unique identifier to get rid of the data that repeat by comparing module.In system, each of data 204 that possesses database format has a unique indications, and each of the data 150 of standby database also has a unique identifier; Log analyzing module can be configured to comprise the first comparing module 114b, it is to possessing the data 204 of database format and the data of standby database 150 are compared, if there are certain data that unique identifier is identical, illustrate that these data Already in standby database 150, need not further process; If it is not identical with the unique identifier of data in any standby database 150 to possess the unique identifier of certain data of data 204 of database format, not these data are described in standby database 1 50, and the first comparing module 114b continues it to process as the data that arrive 205 of resolving.
In practice, multiple servers when operation, can produce calamity separately for journal file, so log analyzing module also runs on multiple servers conventionally concurrently, obtain and resolve the data that obtain.
In the present embodiment, the data 205 that log analyzing module 114 obtains parsing are stored in calamity for volatile data base 160; The data 205n that the log analyzing module of the server that other are parallel also obtains parsing stores calamity into for volatile data base 160.
The log analyzing module of Servers-all all completes after above-mentioned steps, rebuilds business data module and starts to rebuild, and reconstruction procedures is processed by the reconstruction business data module on a station server of selecting.In the present embodiment, select the reconstruction business data module 115 on 110 servers to rebuild.
Rebuilding the different demand data of general foundation carries out.In the present embodiment, rebuild business data module 115 and be configured to comprise sequence and comparing function.The system that time sequencing is had to requirement, can when application program 111 or 112 work of daily record modular converter, be joining day identifier in every data, the data 205 that reconstruction business data module can obtain for the parsing in database 160 interim calamity according to time identifier sort.Rebuild business data module 115 and also can be configured to there is the second comparing module 115b, it is compared with the related data in standby database 150 for the data in volatile data base 160 (through sequence or not through sequence) to calamity, compares wrong calamity and for the data in volatile data base 160, is labeled as " do not rebuild business datum " and treats that other modes process; Comparing errorless data markers is " business datum of reconstruction ".
Upgrade business data module 116 business datum of reconstruction 206 is updated to standby database 150.In order to ensure trackability, the security of data, in the present embodiment, upgrade business data module 116 and be configured to, under situation that the partial data when standby database 1 50 is modified, this partial data before revising be backed up.
The flow process of the application's method is below described with reference to Fig. 3.Fig. 3 is the method flow diagram of implementing the application.
When server application moves, daily record switch process 301, daily record receiving step 302 carry out in real time.
In daily record switch process 301, with predetermined format, convert the business datum distributing and operate in the application program on one or more server to daily record data in real time.
In daily record receiving step 302, by the described daily record data of reception and be stored in one or more calamities in journal file.Alternatively, described one or more calamity can be arranged in one or more home server of application program or one or more long-range calamity for server for journal file.
In analyzing step 303, the calamity in predetermined amount of time resolves to and possesses the data that the data of database format obtain as parsing for the daily record data in journal file.Alternatively, the start time of described predetermined amount of time can early than or equal the time point that database backups to standby database for the last time, and the end time of described predetermined amount of time can be later than or equal the time point that database breaks down; Alternatively, each of data that possesses database format has unique identifier, analyzing step 303 can possess the data of database format and the data of standby database are compared, the data that the different data that possess database format of unique identifier are obtained as parsing by described; Alternatively, the data that analyzing step 303 can obtain parsing store calamity into for volatile data base.
In rebuilding business datum step 304, the data that this method obtains parsing rebuild to obtain the business datum of reconstruction according to pre-defined rule.Alternatively, each business datum in business datum has time identifier, rebuilds business datum step 304 and can to resolving the data that obtain, sort according to described time identifier; Alternatively, rebuilding business datum step 304 and calamity can be compared for the data of the data in volatile data base and standby database, is the business datum of rebuilding for data markers errorless in volatile data base by calamity; It by calamity, for data markers wrong in volatile data base, is the business datum of not rebuilding.
Alternatively, step 303 can be carried out concurrently in multiple servers, and step 304 can be carried out in separate unit server.
Upgrade in business datum step 305, this method arrives standby database by the service data updating of rebuilding.Alternatively, the service data updating of rebuilding, in standby database process, under the situation that the partial data of standby database is modified, is upgraded to business datum step 305 and can this partial data before revising be backed up.
Those skilled in the art should understand, the application's embodiment can be provided as method, system or computer program.Therefore, the application can adopt complete hardware implementation example, implement software example or in conjunction with the form of the embodiment of software and hardware aspect completely.And the application can adopt the form that wherein includes the upper computer program of implementing of computer-usable storage medium (including but not limited to magnetic disk memory, CD-ROM, optical memory etc.) of computer usable program code one or more.
The embodiment that the foregoing is only the application, is not limited to the application, and for a person skilled in the art, the application can have various modifications and variations.All within the application's spirit and principle, any modification of doing, be equal to replacement, improvement etc., within all should being included in the application's claim scope.
Claims (17)
1. a method of database data being recovered, is characterized in that comprising the following steps:
With predetermined format, convert the business datum distributing and operate in the application program on one or more server to daily record data in real time;
Receive described daily record data and be stored in one or more calamities in journal file;
Calamity in predetermined amount of time resolves to and possesses the data that the data of database format obtain as parsing for the daily record data in journal file;
The data that parsing is obtained rebuild to obtain the business datum of reconstruction according to pre-defined rule; And
The service data updating of rebuilding is arrived to standby database.
2. method as claimed in claim 1, wherein, each of data that possesses database format has unique identifier, and wherein, described analyzing step also comprises: by described, possess the data of database format and the data of standby database are compared, the data that the different data that possess database format of unique identifier are obtained as parsing.
3. method as claimed in claim 1, wherein, analyzing step comprises:
The data that parsing is obtained store calamity into for volatile data base.
4. method as claimed in claim 3, wherein, reconstruction procedures comprises:
Calamity is compared for the data of the data in volatile data base and standby database, is the business datum of rebuilding for data markers errorless in volatile data base by calamity; It by calamity, for data markers wrong in volatile data base, is the business datum of not rebuilding.
5. the method as described in claim 1 to 4 any one, wherein, described analyzing step is carried out concurrently in multiple servers, and wherein, described reconstruction procedures is carried out in separate unit server.
6. the method as described in claim 1 to 4 any one, is characterized in that, described one or more calamities are arranged in one or more home server of application program or one or more long-range calamity for server for journal file.
7. the method as described in claim 1 to 4 any one, wherein, the start time of described predetermined amount of time early than or equal the time point that database backups to standby database for the last time, and the end time of described predetermined amount of time is later than or equals the time point that database breaks down.
8. the method as described in claim 1 to 4 any one, wherein, each business datum in business datum has time identifier, and reconstruction procedures also comprises according to described time identifier and sorting to resolving the data that obtain.
9. the method as described in claim 1 to 4 any one, wherein, in standby database process, under the situation that the partial data of standby database is modified, backs up the service data updating of rebuilding to this partial data before revising.
10. equipment database data being recovered, comprising:
Daily record modular converter, it converts with predetermined format the business datum distributing and operate in the application program on one or more server to daily record data in real time;
Daily record receiver module, it receives the daily record data of daily record modular converter output and is stored in one or more calamities in journal file;
Log analyzing module, its calamity in setting-up time section resolves to and possesses the data that the data of database format obtain as parsing for the daily record data in journal file;
Rebuild business data module, its data that parsing is obtained rebuild to obtain the business datum of reconstruction according to pre-defined rule; And
Upgrade business data module, it arrives standby database by the service data updating of rebuilding business data module reconstruction.
11. equipment as claimed in claim 10, wherein, each of data that possesses database format has unique identifier, and wherein, log analyzing module comprises the first comparing module, be configured to possess the data of database format and the data of standby database are compared, the data that the different data that possess database format of unique identifier are obtained as parsing by described.
12. equipment as claimed in claim 10, wherein, the data that log analyzing module is configured to parsing to obtain store calamity into for volatile data base.
13. equipment as claimed in claim 12, wherein, rebuild business data module and comprise:
The second comparing module, is configured to calamity to compare for the data of the data in volatile data base and standby database, is the business datum of rebuilding by calamity for data markers errorless in volatile data base; It to calamity, for data markers wrong in volatile data base, is the business datum of not rebuilding.
14. equipment as described in claim 10 to 13 any one, wherein, log analyzing module works in multiple servers concurrently, and wherein, rebuilds business data module and work in separate unit server.
15. equipment as described in claim 10 to 13 any one, wherein, the start time of described setting-up time section early than or equal the time point that database backups to standby database for the last time, and the end time of described predetermined amount of time is later than or equals the time point that database breaks down.
16. equipment as described in claim 10 to 13 any one, wherein, each business datum in business datum has time identifier, and rebuilds business data module and be also configured to sort to resolving the data that obtain according to described time identifier.
17. equipment as described in claim 10 to 13 any one, wherein, upgrade business data module and are configured to, under situation that the partial data when standby database is modified, this partial data before revising be backed up.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210369540.8A CN103699548B (en) | 2012-09-27 | 2012-09-27 | A kind of method and apparatus being recovered database data by usage log |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210369540.8A CN103699548B (en) | 2012-09-27 | 2012-09-27 | A kind of method and apparatus being recovered database data by usage log |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103699548A true CN103699548A (en) | 2014-04-02 |
| CN103699548B CN103699548B (en) | 2016-12-21 |
Family
ID=50361079
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210369540.8A Active CN103699548B (en) | 2012-09-27 | 2012-09-27 | A kind of method and apparatus being recovered database data by usage log |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103699548B (en) |
Cited By (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104765659A (en) * | 2015-04-30 | 2015-07-08 | 北京奇虎科技有限公司 | Data recovery method and device applied to database |
| CN105045678A (en) * | 2015-07-09 | 2015-11-11 | 小米科技有限责任公司 | Database recovery method and apparatus |
| CN105488389A (en) * | 2014-12-08 | 2016-04-13 | 哈尔滨安天科技股份有限公司 | Update and reduction method and system of honeypot database |
| CN105574020A (en) * | 2014-10-14 | 2016-05-11 | 阿里巴巴集团控股有限公司 | Database operation method and device |
| CN105656706A (en) * | 2014-11-14 | 2016-06-08 | 北京通达无限科技有限公司 | Business data processing method and device |
| CN105677675A (en) * | 2014-11-20 | 2016-06-15 | 阿里巴巴集团控股有限公司 | Business processing method and device |
| CN106021019A (en) * | 2016-05-12 | 2016-10-12 | 广西尊达电子商务有限公司 | Automatic recovery method for databases |
| WO2016180160A1 (en) * | 2015-10-23 | 2016-11-17 | 中兴通讯股份有限公司 | Data snapshot recovery method and apparatus |
| CN106155838A (en) * | 2015-04-24 | 2016-11-23 | 中国移动通信集团河南有限公司 | A kind of database back-up data restoration methods and device |
| CN107408134A (en) * | 2015-03-19 | 2017-11-28 | 华为技术有限公司 | Rebuild the method for the data storage of multi-dimensional database and rebuild server |
| CN108241555A (en) * | 2016-12-26 | 2018-07-03 | 阿里巴巴集团控股有限公司 | A kind of backup of distributed data base, restoration methods, device and server |
| CN111639132A (en) * | 2020-05-29 | 2020-09-08 | 中国联合网络通信集团有限公司 | Log synchronization method and device |
| CN112181722A (en) * | 2020-09-16 | 2021-01-05 | 济南浪潮数据技术有限公司 | Data backup and recovery method, device, equipment and readable storage medium |
| CN112286732A (en) * | 2020-12-02 | 2021-01-29 | 上海英方软件股份有限公司 | Method and system for recovering unsynchronized data to standby machine when database synchronization is abnormal |
| CN118503018A (en) * | 2024-07-17 | 2024-08-16 | 杭州海康威视系统技术有限公司 | Data recovery method, device and system of distributed database and electronic equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20020030223A (en) * | 2000-10-16 | 2002-04-24 | 주식회사 알라딘소프트 | Logging and recovery method for supporting high performance transaction in main memory resident database system |
| CN1975684A (en) * | 2006-12-13 | 2007-06-06 | 天津理工大学 | Distributing real-time data bank fault recovering method capable of supporting serving and recovering simultaneously |
| CN101719165A (en) * | 2010-01-12 | 2010-06-02 | 山东高效能服务器和存储研究院 | Method for realizing high-efficiency rapid backup of database |
-
2012
- 2012-09-27 CN CN201210369540.8A patent/CN103699548B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20020030223A (en) * | 2000-10-16 | 2002-04-24 | 주식회사 알라딘소프트 | Logging and recovery method for supporting high performance transaction in main memory resident database system |
| CN1975684A (en) * | 2006-12-13 | 2007-06-06 | 天津理工大学 | Distributing real-time data bank fault recovering method capable of supporting serving and recovering simultaneously |
| CN101719165A (en) * | 2010-01-12 | 2010-06-02 | 山东高效能服务器和存储研究院 | Method for realizing high-efficiency rapid backup of database |
Non-Patent Citations (2)
| Title |
|---|
| 屈志毅等: "DB2大型数据库容灾备份实时复制系统", 《计算机系统应用》 * |
| 郑阿奇: "SQL Server2000数据库实时备份", 《计算机工程与设计》 * |
Cited By (26)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105574020A (en) * | 2014-10-14 | 2016-05-11 | 阿里巴巴集团控股有限公司 | Database operation method and device |
| CN105574020B (en) * | 2014-10-14 | 2020-02-21 | 阿里巴巴集团控股有限公司 | Database operation method and device |
| CN112003743A (en) * | 2014-11-14 | 2020-11-27 | 北京通达无限科技有限公司 | Service data processing method and device |
| CN105656706A (en) * | 2014-11-14 | 2016-06-08 | 北京通达无限科技有限公司 | Business data processing method and device |
| CN105656706B (en) * | 2014-11-14 | 2020-09-15 | 北京通达无限科技有限公司 | Service data processing method and device |
| CN112003743B (en) * | 2014-11-14 | 2023-04-18 | 北京通达无限科技有限公司 | Service data processing method and device |
| CN105677675A (en) * | 2014-11-20 | 2016-06-15 | 阿里巴巴集团控股有限公司 | Business processing method and device |
| CN105677675B (en) * | 2014-11-20 | 2019-08-27 | 阿里巴巴集团控股有限公司 | Method for processing business and device |
| CN105488389A (en) * | 2014-12-08 | 2016-04-13 | 哈尔滨安天科技股份有限公司 | Update and reduction method and system of honeypot database |
| CN105488389B (en) * | 2014-12-08 | 2018-05-08 | 哈尔滨安天科技股份有限公司 | A kind of renewal in honeypot data storehouse and restoring method and system |
| CN107408134A (en) * | 2015-03-19 | 2017-11-28 | 华为技术有限公司 | Rebuild the method for the data storage of multi-dimensional database and rebuild server |
| CN106155838A (en) * | 2015-04-24 | 2016-11-23 | 中国移动通信集团河南有限公司 | A kind of database back-up data restoration methods and device |
| CN106155838B (en) * | 2015-04-24 | 2019-03-22 | 中国移动通信集团河南有限公司 | A kind of database back-up data restoration methods and device |
| CN104765659A (en) * | 2015-04-30 | 2015-07-08 | 北京奇虎科技有限公司 | Data recovery method and device applied to database |
| CN105045678B (en) * | 2015-07-09 | 2018-10-26 | 小米科技有限责任公司 | Database restoring method and device |
| CN105045678A (en) * | 2015-07-09 | 2015-11-11 | 小米科技有限责任公司 | Database recovery method and apparatus |
| WO2016180160A1 (en) * | 2015-10-23 | 2016-11-17 | 中兴通讯股份有限公司 | Data snapshot recovery method and apparatus |
| CN106021019A (en) * | 2016-05-12 | 2016-10-12 | 广西尊达电子商务有限公司 | Automatic recovery method for databases |
| CN108241555A (en) * | 2016-12-26 | 2018-07-03 | 阿里巴巴集团控股有限公司 | A kind of backup of distributed data base, restoration methods, device and server |
| CN108241555B (en) * | 2016-12-26 | 2022-03-01 | 阿里巴巴集团控股有限公司 | Backup and recovery method and device of distributed database and server |
| CN111639132A (en) * | 2020-05-29 | 2020-09-08 | 中国联合网络通信集团有限公司 | Log synchronization method and device |
| CN111639132B (en) * | 2020-05-29 | 2023-06-06 | 中国联合网络通信集团有限公司 | Log synchronization method and equipment |
| CN112181722A (en) * | 2020-09-16 | 2021-01-05 | 济南浪潮数据技术有限公司 | Data backup and recovery method, device, equipment and readable storage medium |
| CN112286732A (en) * | 2020-12-02 | 2021-01-29 | 上海英方软件股份有限公司 | Method and system for recovering unsynchronized data to standby machine when database synchronization is abnormal |
| CN112286732B (en) * | 2020-12-02 | 2022-04-19 | 上海英方软件股份有限公司 | Method and system for recovering unsynchronized data to standby machine when database synchronization is abnormal |
| CN118503018A (en) * | 2024-07-17 | 2024-08-16 | 杭州海康威视系统技术有限公司 | Data recovery method, device and system of distributed database and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103699548B (en) | 2016-12-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103699548A (en) | Method and equipment for recovering database data by using logs | |
| CN107958057B (en) | Code generation method and device for data migration in heterogeneous database | |
| CN106407356B (en) | Data backup method and device | |
| CN107220142B (en) | Method and device for executing data recovery operation | |
| CN108694195B (en) | Management method and system of distributed data warehouse | |
| CN111124755B (en) | Fault recovery method and device for cluster nodes, electronic equipment and storage medium | |
| CN109656934A (en) | Source oracle database DDL synchronous method and equipment based on log parsing | |
| CN101136783B (en) | Backup, recovery method and apparatus for network management system to configure data | |
| CN107547606B (en) | Data processing method, cluster manager, resource manager and data processing system | |
| CN104331285A (en) | Automatic code generation method and system | |
| CN101167058B (en) | Apparatus, method and system for restoring files | |
| CN105205053A (en) | Method and system for analyzing database incremental logs | |
| CN105224527B (en) | General ETL methods suitable for a variety of purpose table update modes | |
| CN111858146B (en) | Method, apparatus and computer program product for recovering data | |
| CN109144785A (en) | Method and apparatus for Backup Data | |
| CN113420026B (en) | Database table structure changing method, device, equipment and storage medium | |
| CN104657387A (en) | Data query method and device | |
| CN102521073B (en) | Increasing database availability during fault recovery | |
| CN103077019B (en) | A kind of graphical parameter batch maintenance method and device | |
| CN110532123A (en) | The failover method and device of HBase system | |
| CN107179965B (en) | Database recovery method and device | |
| CN111625396A (en) | Backup data verification method, server and storage medium | |
| CN109165175A (en) | Device identification generation method and device | |
| CN108108479A (en) | A kind of database connecting detection method, system, equipment and computer media | |
| CN102148714A (en) | Method and device for upgrading software |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20191204 Address after: P.O. Box 31119, grand exhibition hall, hibiscus street, 802 West Bay Road, Grand Cayman, Cayman Islands Patentee after: Innovative advanced technology Co., Ltd Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Patentee before: Alibaba Group Holding Co., Ltd. |
|
| TR01 | Transfer of patent right |