CN103699548B - A kind of method and apparatus being recovered database data by usage log - Google Patents
A kind of method and apparatus being recovered database data by usage log Download PDFInfo
- Publication number
- CN103699548B CN103699548B CN201210369540.8A CN201210369540A CN103699548B CN 103699548 B CN103699548 B CN 103699548B CN 201210369540 A CN201210369540 A CN 201210369540A CN 103699548 B CN103699548 B CN 103699548B
- Authority
- CN
- China
- Prior art keywords
- data
- time
- calamity
- database
- daily record
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 238000011084 recovery Methods 0.000 claims description 3
- 230000007246 mechanism Effects 0.000 abstract description 6
- 238000006243 chemical reaction Methods 0.000 abstract 1
- 230000008569 process Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 4
- 241001269238 Data Species 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000004321 preservation Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012163 sequencing technique Methods 0.000 description 1
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 application relates to a kind of method and apparatus recovered database data by usage log, and it is converted into daily record data the most in a predetermined format by being distributed and operating in the business datum in the application program on one or more server；Receive described daily record data and be stored in one or more calamity in journal file；Calamity in predetermined amount of time is resolved to for the daily record data in journal file the data that the data possessing database format obtain as parsing；Data parsing obtained carry out rebuilding to obtain the business datum rebuild according to pre-defined rule；And by the service data updating of reconstruction to standby database.Owing to daily record conversion and reception are real-time, so when database corruption, the data lost can be recovered after data base's schedule backup mechanism BACKUP TIME point the last time.
Description
Technical field
Present application relates generally to data processing field, particularly relate to a kind of data storage, process and the method recovered and
Equipment.
Background technology
For the system relating to data, it is requisite to properly preserving of data.Such as Taobao's system pair
The preservation of the shopping information of its user, preservation of Alipay system of users accounts information etc., these data are generally held in
In data base, but, when database corruption, will result in the loss of data.
At present, data base's schedule backup mechanism typically can be used to back up data base avoids database corruption to cause
Loss.This mechanism would generally include MDL and standby database, the complete data that MDL storage is real-time, data
The data of MDL are backuped to standby database, when main number every one section of time interval set by library backup program and equipment
When damaging according to storehouse, system just can use standby database.Two data bases be generally of identical complete data form and
Structure, it is possible to the most directly use the data standby database from MDL switching.
But, the time interval of backup is usually a few minutes, several hours, so this backup actions is not to occur in real time
, (as special situation, it is also possible to time interval to be set as the extremely short time, to back up in realtime, but so can consume
A large amount of system resources, so generally not adopting in this way.) so, when MDL damages when, from DB Backup
Data during program and equipment carry out the time point that the time point that backs up damages to MDL for the last time are not backed up
To standby database, this part loss of data, this is the problem that this data base's schedule backup mechanism exists.
Summary of the invention
The main purpose of the application is to provide a kind of method and apparatus being recovered database data by usage log, with
Data base's schedule backup mechanism that solution prior art exists carries out for the last time the time backed up from DB Backup program
Point arrives the data loss problem during the time point that MDL damages, wherein:
An aspect according to the application, it is provided that a kind of method recovering database data, comprises the following steps:
The business datum being distributed and operate in the application program on one or more server is converted into the most in a predetermined format
Daily record data；Receive described daily record data and be stored in one or more calamity in journal file；By the calamity in predetermined amount of time
Daily record data in standby journal file resolves to the data that the data possessing database format obtain as parsing；Parsing is obtained
Data carry out rebuilding obtaining the business datum rebuild according to pre-defined rule；And by the service data updating of reconstruction to standby
Data base.
According to the method for the application detailed description of the invention, also including, each of data possessing database format has
Unique identifier, and wherein, described analyzing step also includes: by the described data possessing database format and standby database
Data compare, using the data possessing database format different for unique identifier as the data that obtain of parsing.
According to the method for the application detailed description of the invention, analyzing step also includes, data parsing obtained store calamity
Standby volatile data base.
According to the method for the application detailed description of the invention, reconstruction procedures also includes, by calamity for the data in volatile data base
Compare with the data of standby database, be the business datum rebuild for data markers errorless in volatile data base by calamity；
It is the business datum do not rebuild for data markers wrong in volatile data base by calamity.
According to the method for the application detailed description of the invention, also include, described analyzing step in multiple servers concurrently
Carry out, and wherein, described reconstruction procedures is carried out in single server.
According to the method for the application detailed description of the invention, also including, the one or more calamity is positioned at for journal file should
With in one or more home server of program or one or more long-range backup & disaster recovery device.
According to the method for the application detailed description of the invention, also include, the time started of described predetermined amount of time early than or etc.
Backup to the time point of standby database for the last time in data base, and the end time of described predetermined amount of time is later than or etc.
In the time point that data base breaks down.
According to the method for the application detailed description of the invention, also including, each business datum in business datum has the time
Identifier, and reconstruction procedures also includes being ranked up resolving the data that obtain according to described time identifier.
According to the method for the application detailed description of the invention, also include, by the service data updating of reconstruction to standby database
During, when the part data of standby database are modified when, these part data before amendment are backed up.
An aspect according to the application, it is provided that a kind of equipment that database data is recovered, including: daily record is changed
Module, it is by distribution and operates in the business datum in the application program on one or more server the most in a predetermined format
It is converted into daily record data；Daily record receiver module, it receives the daily record data of daily record modular converter output and is stored in one or many
Individual calamity is in journal file；Log analyzing module, the calamity set in the time period is resolved by it for the daily record data in journal file
For possessing the data that the data of database format obtain as parsing；Rebuilding business data module, it is by log analyzing module solution
The data that analysis obtains carry out rebuilding to obtain the business datum rebuild according to pre-defined rule；And renewal business data module, its
The service data updating of business data module reconstruction will be rebuild to standby database.
According in the equipment of the embodiment of the present application, each of data possessing database format has unique mark
Symbol, and wherein, log analyzing module includes the first comparing module, be configured to the described data possessing database format and
The data of standby database are compared, and the data possessing database format different for unique identifier are obtained as parsing
Data.
According in the equipment of the embodiment of the present application, the data that log analyzing module is configured to obtain parsing store
Calamity is for volatile data base.
According in the equipment of the embodiment of the present application, rebuild business data module and include that the second comparing module is configured to
Calamity is compared for the data of the data in volatile data base with standby database, by calamity for number errorless in volatile data base
According to the business datum being labeled as reconstruction；It is the business datum do not rebuild to calamity for data markers wrong in volatile data base.
According in the equipment of the embodiment of the present application, log analyzing module works in multiple servers, and its concurrently
In, rebuild business data module and work in single server.
According in the equipment of the embodiment of the present application, also include, the time started of described predetermined amount of time early than or be equal to
Data base backups to the time point of standby database for the last time, and the end time of described predetermined amount of time is later than or is equal to
The time point that data base breaks down.
According in the equipment of the embodiment of the present application, each business datum in business datum has time identifier, and
And reconstruction business data module is further configured to be ranked up resolving the data obtained according to described time identifier.
According in the equipment of the embodiment of the present application, update business data module and be configured to the part when standby database
When data are modified, these part data before amendment are backed up.
Compared with prior art, according to the technical scheme of the application, can be real-time by business datum when application program runs
Ground is converted into daily record data in a predetermined format and exports calamity in journal file, when database corruption, and can be by calamity for daily record
The data parsing of file is the data possessing database format, undergoes reconstruction, and updates to standby database.Due to this method be
Application program is carried out in running in real time, and the time point i.e. carrying out for the last time backing up from DB Backup program and equipment is to master
Time point this method of database corruption is also being carried out, and its final result can recover last from DB Backup program and equipment
Once carry out the business datum during the time point that the time point that backs up damages to MDL.
Accompanying drawing explanation
Accompanying drawing described herein is used for providing further understanding of the present application, constitutes the part of the application, this Shen
Schematic description and description please is used for explaining the application, is not intended that the improper restriction to the application.In the accompanying drawings:
Fig. 1 is the overall system architecture schematic diagram 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 to implement the present processes flow chart.
Detailed description of the invention
The main thought of the application is, in application program running, in real time by business datum with daily record data
Form output storage, in case recovering when database lost data.The output storage of daily record data form and data Coorg
The backup of formula is different, and its system resource taken is close to and is negligible.On the other hand, when MDL damages, although
Data in standby database can directly invoke, and daily record data needs just can use through certain process step,
But these daily record datas compensate for the data lost in data base's schedule backup mechanism.
For making the purpose of the application, technical scheme and advantage clearer, below in conjunction with drawings and the specific embodiments, to this
Application is described in further detail.
According to embodiments herein, it is provided that a kind of equipment that database data is recovered.
It is the overall system architecture schematic diagram that can implement the embodiment of the present application with reference to Fig. 1, Fig. 1.
Running an application program 111 on server 110, application program 111 stores the data to MDL in real time
130.Server 120 has the structure identical with server 110, stores the data to MDL 130 the most in real time.Master data
Data base update program and equipment 140 are passed through every one section of time interval set by the data backup of MDL 130 in storehouse 130
To standby database 150.In said system, the quantity of server can be not limited to two, can be more to form cluster, often
Application program on station server can be identical or different, and application program can be one or more, but application program meeting
Data are stored MDL 130 with the data possessing database format.It addition, the various piece of an application program is permissible
Lay respectively on different servers.
The equipment of the application can include with lower module: daily record modular converter 112, daily record receiver module 113, and daily record resolves
Module 114, rebuilds business data module 115, updates business data module 116.Alternatively, above-mentioned module may be located at server
On, such as on server 110.Log analyzing module 114 can be configured to comprise the first comparing module 114b, rebuilds business datum
Module can be configured to comprise the second comparing module 115b.Alternatively, module 113～116 can not also be arranged in server 110
On, and be arranged on the standby host of server 110；Daily record modular converter 112 typically can be only fitted on server 110.In application
When program 111 is run, daily record modular converter 112 and daily record receiver module 113 are with application program together real time operation, and form calamity
Standby journal file.When MDL damages, log analyzing module 114, reconstruction business data module 115, renewal business datum
Module 116 starts work, and described module can carry out communication to store, to read, to process data with calamity for volatile data base 160, institute
State module by the service data updating of reconstruction that obtained for journal file by calamity to standby database 150.
The operation principle of the modules of the application equipment is described in detail hereinafter with reference to Fig. 2.Fig. 2 is real according to the application
Execute the module fundamental diagram of example.
When application program 111 runs, producing business datum 201 in real time, daily record modular converter 112 is in real time by business datum
201 are converted to daily record data 202, and daily record data 202 is stored calamity for journal file 203 by daily record receiver module 113.
When MDL breaks down, log analyzing module 114 by calamity for journal file 203 sets the time period
Data parsing is the data 204 possessing database format, and the time period of setting is generally data base update program and equipment 140
After once MDL 130 is backuped to the time point that the time point of standby database 150 damages to MDL 130, in order to
Guarantee to recover the complete of data segment, it is also possible to the time period of setting is set to initial time and early than data base update program and sets
The standby 140 last time points that MDL 130 is backuped to standby database 150, and (or) end time is later than
The time point that MDL 130 damages.According to embodiments herein, initial time is early than the time point of last backup
And/or the end time is later than the time point that MDL damages, concrete the most how long need and/or evening how long, this such as can be by
Lighting system needs to set, or such as can set in the situation considering cost.Such as, the regular MDL of data base
130 time points backuping to standby database 150 for the last time are 12:55, and MDL damages in 12:59, then can select
The data recovering the following period are recovered: a:12:55～12:59；B:12:50～12:59；C:12:55～13:00；d:12:
50～13:00.
In practice, the time period that resolves of above-mentioned selection is generally longer than the time period of data actual loss, so system can be adopted
Got rid of the data repeated by comparing module with unique identifier.In system, possess each of data 204 of database format
Having a unique indications, each of the data 150 of standby database also has a unique identifier；Daily record resolves
Module can be configured to comprise the first comparing module 114b, its data 204 and standby database 150 to possessing database format
Data compare, if there is the data that certain unique identifier is identical, the most standby number of this data is described
According in storehouse 150, need not process further；If the unique identifier possessing certain data of the data 204 of database format does not has
Have identical with the unique identifier of the data in any standby database 150, then explanation standby database 150 should not
Data, the first comparing module 114b continues with as resolving the data 205 obtained.
In practice, when multiple servers runs, respective calamity can be produced for journal file, so log analyzing module is usual
Run on multiple servers the most concurrently, it is thus achieved that resolve the data obtained.
In the present embodiment, the data 205 that parsing is obtained by log analyzing module 114 are stored in calamity for volatile data base 160；
Data 205n that parsing obtains also are stored calamity for volatile data base 160 by the log analyzing module of other parallel servers.
After the log analyzing module of Servers-all all completes above-mentioned steps, rebuild business data module and proceed by weight
Building, reconstruction procedures is processed by the reconstruction business data module on the station server selected.In the present embodiment, select 110
Reconstruction business data module 115 on server is rebuild.
Rebuild and typically carry out according to different demand datas.In the present embodiment, rebuild business data module 115 and be configured to
Comprise sequence and data comparison function.The system requiring time sequencing, can be at application program 111 or daily record modular converter
Being joining day identifier in every data during 112 work, rebuilding business data module can be according to time identifier to interim calamity
The data 205 that parsing in standby data base 160 obtains are ranked up.Reconstruction business data module 115 may be additionally configured to be had
Second comparing module 115b, its to calamity in volatile data base 160 data (through sequence or through sequence) with standby
Related data in data base 150 is compared, and the wrong calamity of comparison is then labeled as " not for the data in volatile data base 160
The business datum rebuild " treat that other modes process；The errorless data markers of comparison is " business datum of reconstruction ".
Update business data module 116 and the business datum 206 of reconstruction is updated standby database 150.In order to ensure number
According to trackability, safety, in the present embodiment, update business data module 116 be configured to when the portion of standby database 150
When divided data is modified, these part data before amendment are backed up.
The flow process of the application method is described hereinafter with reference to Fig. 3.Fig. 3 is to implement the present processes flow chart.
When server application runs, daily record switch process 301, daily record receiving step 302 are carried out in real time.
In daily record switch process 301, will be distributed and operate in the industry in the application program on one or more server
Business data are converted into daily record data the most in a predetermined format.
In daily record receiving step 302, by described for reception daily record data and be stored in one or more calamity for journal file
In.Alternatively, the one or more calamity for journal file may be located at application program one or more home server or
In one or more long-range backup & disaster recovery device of person.
In analyzing step 303, the calamity in predetermined amount of time is resolved to for the daily record data in journal file and possesses number
The data obtained as parsing according to the data of library format.Alternatively, the time started of described predetermined amount of time can early than or etc.
Backup to the time point of standby database in data base for the last time, and the end time of described predetermined amount of time can be later than
Or it is equal to the time point that data base breaks down；Alternatively, each of data possessing database format has unique mark
Symbol, the data of the described data possessing database format and standby database can be compared by analyzing step 303, by unique
What identifier was different possesses the data that the data of database format obtain as parsing；Alternatively, analyzing step 303 can will solve
The data that analysis obtains store calamity for volatile data base.
Rebuilding in business datum step 304, the data that parsing is obtained by this method according to pre-defined rule carry out rebuilding with
Obtain the business datum rebuild.Alternatively, each business datum in business datum has time identifier, rebuilds business datum
Step 304 can be ranked up resolving the data obtained according to described time identifier；Alternatively, business datum step is rebuild
Calamity can be compared, by calamity in volatile data base by 304 for the data of the data in volatile data base with standby database
Errorless data markers is the business datum rebuild；It is the business do not rebuild for data markers wrong in volatile data base by calamity
Data.
Alternatively, step 303 can be carried out in multiple servers concurrently, and, step 304 can be in separate unit service
Device is carried out.
Update in business datum step 305, this method by the service data updating rebuild to standby database.Alternatively,
During the service data updating of reconstruction to standby database, when the part data of standby database are modified when,
Update business datum step 305 can these part data before amendment be backed up.
Those skilled in the art are it should be appreciated that embodiments herein can be provided as method, system or computer program
Product.Therefore, the reality in terms of the application can use complete hardware embodiment, complete software implementation or combine software and hardware
Execute the form of example.And, the application can use at one or more computers wherein including computer usable program code
The upper computer program product implemented of usable storage medium (including but not limited to disk memory, CD-ROM, optical memory etc.)
The form of product.
The foregoing is only embodiments herein, be not limited to the application, for those skilled in the art
For Yuan, the application can have various modifications and variations.All within spirit herein and principle, any amendment of being made,
Equivalent, improvement etc., within the scope of should be included in claims hereof.
Claims (17)
1. the method that database data is recovered, it is characterised in that comprise the following steps:
The business datum being distributed and operate in the application program on one or more server is turned the most in a predetermined format
Change daily record data into；
Receive described daily record data and be stored in one or more calamity in journal file；
Calamity in predetermined amount of time is resolved to for the daily record data in journal file and possesses the data of database format as solution
The data that analysis obtains；
Data parsing obtained carry out rebuilding to obtain the business datum rebuild according to pre-defined rule；And
By the service data updating of reconstruction to standby database.
2. method as claimed in claim 1, wherein, each of data possessing database format has unique identifier, and
Wherein, described analyzing step also includes: the data of the described data possessing database format and standby database compared,
The data that the data possessing database format different for unique identifier are obtained as parsing.
3. method as claimed in claim 1, wherein, analyzing step includes:
Data parsing obtained store calamity for volatile data base.
4. method as claimed in claim 3, wherein, reconstruction procedures includes:
Calamity is compared for the data of the data in volatile data base with standby database, by calamity for errorless in volatile data base
Data markers be rebuild business datum；It is the business number do not rebuild for data markers wrong in volatile data base by calamity
According to.
5. the method as described in any one of Claims 1-4, wherein, described analyzing step is entered in multiple servers concurrently
OK, and wherein, described reconstruction procedures is carried out in single server.
6. the method as described in any one of Claims 1-4, it is characterised in that the one or more calamity is for journal file position
In one or more home server or one or more long-range backup & disaster recovery device of application program.
7. the method as described in any one of Claims 1-4, wherein, the time started of described predetermined amount of time early than or be equal to
Data base backups to the time point of standby database for the last time, and the end time of described predetermined amount of time is later than or is equal to
The time point that data base breaks down.
8. the method as described in any one of Claims 1-4, wherein, each business datum in business datum has time mark
Know symbol, and reconstruction procedures also includes being ranked up resolving the data obtained according to described time identifier.
9. the method as described in any one of Claims 1-4, wherein, by the service data updating of reconstruction to standby database mistake
These part data before amendment, when the part data of standby database are modified when, are backed up by Cheng Zhong.
10. equipment database data recovered, including:
Daily record modular converter, it is by distribution and to operate in the business datum in the application program on one or more server real-time
Ground is converted into daily record data in a predetermined format；
Daily record receiver module, it receives the daily record data of daily record modular converter output and is stored in one or more calamity for daily record literary composition
In part；
Log analyzing module, the calamity set in the time period is resolved to by it for the daily record data in journal file possesses data Coorg
The data that the data of formula obtain as parsing；
Rebuilding business data module, the data that parsing is obtained by it carry out rebuilding to obtain the business number rebuild according to pre-defined rule
According to；And
Updating business data module, it will rebuild the service data updating of business data module reconstruction to standby database.
11. equipment as claimed in claim 10, wherein, each of data possessing database format has unique mark
Symbol, and wherein, log analyzing module includes the first comparing module, be configured to the described data possessing database format and
The data of standby database are compared, and the data possessing database format different for unique identifier are obtained as parsing
Data.
12. equipment as claimed in claim 10, wherein, the data that log analyzing module is configured to obtain parsing store
Calamity is for volatile data base.
13. equipment as claimed in claim 12, wherein, rebuild business data module and include:
Second comparing module, is configured to compare calamity for the data of the data in volatile data base with standby database,
It is the business datum rebuild for data markers errorless in volatile data base by calamity；To calamity for data wrong in volatile data base
It is labeled as the business datum do not rebuild.
14. equipment as described in any one of claim 10 to 13, wherein, log analyzing module works in multiple stage service concurrently
Device, and wherein, rebuild business data module and work in single server.
15. equipment as described in any one of claim 10 to 13, wherein, described set the time period time started early than or etc.
Backup to the time point of standby database for the last time in data base, and the end time of described predetermined amount of time is later than or etc.
In the time point that data base breaks down.
16. equipment as described in any one of claim 10 to 13, wherein, each business datum in business datum has the time
Identifier, and rebuild business data module and be further configured to arrange resolving the data that obtain according to described time identifier
Sequence.
17. equipment as described in any one of claim 10 to 13, wherein, update business data module and are configured to when standby number
When being modified according to the part data in storehouse, these part data before amendment are 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 CN103699548A (en) | 2014-04-02 |
| CN103699548B true 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) |
Families Citing this family (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105574020B (en) * | 2014-10-14 | 2020-02-21 | 阿里巴巴集团控股有限公司 | Database operation method and device |
| CN105656706B (en) * | 2014-11-14 | 2020-09-15 | 北京通达无限科技有限公司 | Service data processing method and device |
| CN105677675B (en) * | 2014-11-20 | 2019-08-27 | 阿里巴巴集团控股有限公司 | Method for processing business and device |
| CN105488389B (en) * | 2014-12-08 | 2018-05-08 | 哈尔滨安天科技股份有限公司 | A kind of renewal in honeypot data storehouse and restoring method and system |
| WO2016146019A1 (en) * | 2015-03-19 | 2016-09-22 | Huawei Technologies Co., Ltd. | Method and restructuring server for restructuring data stores of a multi-dimensional database |
| CN106155838B (en) * | 2015-04-24 | 2019-03-22 | 中国移动通信集团河南有限公司 | A kind of database backup data recovery method 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 |
| CN106610876B (en) * | 2015-10-23 | 2020-11-03 | 中兴通讯股份有限公司 | Data snapshot recovery method and device |
| CN106021019A (en) * | 2016-05-12 | 2016-10-12 | 广西尊达电子商务有限公司 | Automatic recovery method for databases |
| CN108241555B (en) * | 2016-12-26 | 2022-03-01 | 阿里巴巴集团控股有限公司 | Backup and recovery method and device of distributed database and server |
| CN111639132B (en) * | 2020-05-29 | 2023-06-06 | 中国联合网络通信集团有限公司 | Log synchronization method and device |
| CN112181722A (en) * | 2020-09-16 | 2021-01-05 | 济南浪潮数据技术有限公司 | Data backup and recovery method, device, equipment and readable storage medium |
| CN112286732B (en) * | 2020-12-02 | 2022-04-19 | 上海英方软件股份有限公司 | Method and system for recovering unsynchronized data to standby machine when database synchronization is abnormal |
| CN115904803A (en) * | 2022-11-01 | 2023-04-04 | 云南省地矿测绘院有限公司 | Remote one-way synchronous backup method for data |
| CN115862208A (en) * | 2022-11-30 | 2023-03-28 | 广州广电运通智能科技有限公司 | Business processing method, device and storage medium of rail transit gate software |
| CN118503018B (en) * | 2024-07-17 | 2024-12-06 | 杭州海康威视系统技术有限公司 | Data recovery method, device, system and electronic equipment for distributed database |
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大型数据库容灾备份实时复制系统;屈志毅等;《计算机系统应用》;20120330;第21卷(第3期);第198-201页 * |
| SQL Server2000数据库实时备份;郑阿奇;《计算机工程与设计》;20060131;第27卷(第1期);第126-128页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103699548A (en) | 2014-04-02 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103699548B (en) | A kind of method and apparatus being recovered database data by usage log | |
| CN101542445B (en) | Apparatus and methods of a zero single point of failure load balancer | |
| US10481978B2 (en) | Optimal slice encoding strategies within a dispersed storage unit | |
| US8473515B2 (en) | Multi-tenancy in database namespace | |
| CN108228814B (en) | Data synchronization method and device | |
| US9270546B2 (en) | Systems and/or methods for on-demand repository bootstrapping at runtime in a scalable, distributed multi-tenant environment | |
| CN103744906A (en) | System, method and device for data synchronization | |
| CN102622427A (en) | Method and system for read-write splitting database | |
| CN104718533A (en) | Robust hardware fault management system, method and framework for enterprise devices | |
| US11789832B1 (en) | Retrying failed write operations in a distributed storage network | |
| US10394630B2 (en) | Estimating relative data importance in a dispersed storage network | |
| US20220311757A1 (en) | Cross-regional replication of keys | |
| CN110555150B (en) | Data monitoring method, device, equipment and storage medium | |
| CN107122362A (en) | Cloud database resource extends the method and system with service extension | |
| US10387252B2 (en) | Synchronously storing data in a plurality of dispersed storage networks | |
| CN104484167A (en) | Task processing method and device | |
| CN107368569B (en) | Data difference comparison method and device, storage medium and processor | |
| CN113312209B (en) | Data hot standby method, device, server and storage medium | |
| CN113760469A (en) | Distributed computing method and device | |
| US9430440B2 (en) | Environment construction apparatus and method, environment registration apparatus and method, environment switching apparatus and method | |
| CN104809033B (en) | A kind of backup method and system | |
| CN114528155B (en) | Disaster recovery method, platform, system, computer equipment and storage medium | |
| CN111522832A (en) | Big data real-time updating method, system, equipment and storage medium | |
| CN104462344A (en) | Processing method and device for constructing ETL system on target server | |
| US10122795B2 (en) | Consistency level driven data storage in a dispersed storage network |
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 | ||
| 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. |