CN101122924A - Logic log generation method, database backup/ restoration method and system - Google Patents
Logic log generation method, database backup/ restoration method and system Download PDFInfo
- Publication number
- CN101122924A CN101122924A CNA2007101642227A CN200710164222A CN101122924A CN 101122924 A CN101122924 A CN 101122924A CN A2007101642227 A CNA2007101642227 A CN A2007101642227A CN 200710164222 A CN200710164222 A CN 200710164222A CN 101122924 A CN101122924 A CN 101122924A
- Authority
- CN
- China
- Prior art keywords
- logic log
- backup
- data
- operand
- logic
- 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
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a logical log generating method, which comprises: Acquiring the operation description included in the request of database operation; Generating a logical log comprising the only identified tag and the operation type tag of the operation object in accordance with the operation description; Wherein the operation type tag comprises a delete operation type tag or an overwriting operation type tag. Utilizing the logical log generating method, the invention also provides a database backup method and a database recovery method based on the logical log generating method. If the method provided in by the invention is used for physical backup of a database, the database can receive other operation requests, and physical backup data can be completely recovered when the database is recovered.
Description
Technical field
The present invention relates to computer realm, relate in particular to a kind of logic log generation method and DB Backup method, restoration methods and database backup system.
Background technology
Along with the continuous development of computer technology, Database Backup becomes an important means of preserving database information, and data base management system (DBMS) is exactly the system that is used for managing the lot of data database data.Used DB Backup method comprises that mainly physical backup and logic log back up two kinds at present.
Physical backup is that the memory contents with certain time point data base copies on a plurality of memory devices such as tape, the disk and preserves the process of getting up, and it is the basic means that adopts in the DB Backup.If adopt physical backup separately, must forbid in backup procedure that then the user is to access of database, be that database should be in closed condition during the physical backup, having the user to align in the backed up data storehouse else if in the physical backup process conducts interviews, for example this visit is revised the event memory in the storage space, the last modification result of the storage space that had then backed up before modification time point does not obtain backup, and this time physical backup has only backed up the modification result of the storage space that backs up after the modification time point.As seen, need the blocking operation request in the prior art physical backup process, it is the new operation requests that the physical backup process can be blocked the user, speech is known on the contrary, and each physical backup must be avoided the operation requests time, under the service request situation to the long-time continuous of database, the time interval of twice physical backup can need very long, further can cause DB Backup untimely, when database breaks down, lose a large amount of useful datas easily; If the physical backup time interval is shorter, then cause system to back up continually, new operation requests constantly is obstructed.
Daily record is the file that is used for writing down at every turn the accessing operation of database.When logic log backup is meant database conducted interviews, the process record of the database of this time visit in logic log, and is stored this logic log.As seen, the logic log backup is the change procedure of the storage space of backup database.Description major part to operation in the existing logic log is directly to describe, therefore when repeating a certain logic log, if twice operation describe in operand the base state difference or operand is different can make that the result of repeatedly actuating logic daily record is inconsistent.For example: certain logarithm according to the storehouse to operate in that operation in the logic log describes may be " value of data A is increased by 5 ", then during restore database, repeatedly repeat this operation after, the data value in the back data field is always than preceding once big 5.As seen, the base state Different Effects operating result repeatedly of operand; Again for example: certain logarithm is described as according to the operation in the logic log of operating in storehouse that " revising attribute type is the record that A and property value equal 1, and its property value is modified as 2; Revising attribute type is the record that A and property value equal 2, its property value is modified as 3 "; then during restore database; describe when the data field re-executed this operation; owing to during executable operations be that this property value that A and property value equal in 1 the record is modified as 2 for the first time; therefore; the second time is during executable operations with attribute type according to aforesaid operations, with respect to operation for the first time, the range of the operand that comprises has been described in " attribute type is the record that A and property value equal 2 " this operation, then for the second time after the executable operations, can be initial attribute type that A and property value equal 1 record also to belong to attribute type be that A and property value equal in 3 the set.As seen, for same logic log, the operand difference that comprises is described in the operation of this logic log also influences the repeatedly operating result of actuating logic daily record.
If adopt the logic log backup method that database is backed up separately, must all note all historical logic daily records during each backup, cause the backed up data amount excessive like this storage space of database, and when restore database, it is too big to recover delay, hinders system effectiveness.
For solving the defective of above-mentioned independent employing logic log backup, the DB Backup method of existing a kind of physical backup and logic log backup combination, specific implementation method is: use the physical backup method regularly database to be backed up, after each physical backup deadline point database is carried out the logic log backup.Be that logic log execution result before each physical backup start time point all is embodied in the physical backup, be embodied in the logic log backup to the logic log execution result between the time period before physical backup begins next time after the physical backup deadline point.Logic log this method only need back up this physical backup deadline point when each physical backup after need not to back up all historical logic daily records.But when adopting this method to carry out DB Backup, the physical backup process still needs the blocking operation request, even otherwise in the physical backup process, carried out the logic log backup, but during restore database, can't recover correct data according to the physical backup result of mistake.
For example, in the database two data: A=10 and B=10 are arranged when supposing certain physical backup startup, in the physical backup process, as the intact data A of physical backup and also do not begin the t1 sometime of Backup Data B, if the operation requests that database is carried out comprises the operation requests that operation is described as " currency of all data in the database is all increased by 5 ", then data A in database this moment and the value of data B all become 15, if the t2 (beginning of t2＞t1) physical backup data B sometime, the value of data B was 15 after then physical backup was finished, and since the value of data A when database root carries out corresponding operating according to the aforesaid operations request, backed up and finished, the result of therefore last physical backup is: A=10, B=15.And being described as in the record of the logic log in the physical backup process: the value of all data in the database is all increased by 5, therefore, when restore database, can be according to the result " A=10; B=15 " and the above-mentioned logic log of physical backup, data in the database are reverted to " A=5, B=10 ".Perhaps, if with the A=10 as a result of physical backup, B=15 " be operand; re-execute the logic log that is described as " value of all data in the database is all increased by 5 "; after then carrying out once this logic log, the database data that recovers is: A=15, B=20.As seen, in existing physical backup and the logic log backup combined method, the physical backup process still needs the blocking operation request.
In sum, the inventor finds that data base management system (DBMS) does not allow to receive new operation requests in the existing process of database being carried out physical backup.
Summary of the invention
The embodiment of the invention provides a kind of logic log generation method and DB Backup method, restoration methods and database backup system, can't receive the problem of new operation requests in order to data base management system (DBMS) in the physical backup process that exists in the solution prior art.
The embodiment of the invention provides a kind of logic log generation method, comprising:
Obtaining the operation that comprises in the operation requests that database is operated describes;
According to described operation the logic log that generation comprises the unique definite sign and the action type sign of operand is described; Wherein, described action type sign comprises deletion action type identification or overlapping operation type identification; When described action type was designated the overlapping operation type identification, described logic log also comprised the cover data of operand being carried out overlapping operation.
Adopt above-mentioned logic log generation method, the embodiment of the invention also provides a kind of DB Backup method, comprising:
New physical backup is carried out in the data field;
The logic log of record backs up under first catalogue before starting constantly to described new physical backup after starting last physical backup constantly; Logic log after starting described new physical backup constantly backs up under second catalogue.
In addition, the embodiment of the invention also provides a kind of database recovery method, is applied to adopting above-mentioned DB Backup method backed up data storehouse to recover, and this method comprises:
Use the data of physical backup to recover described physical backup startup moment data field data before;
Carry out the logic log that described physical backup starts back backup constantly.
In addition, the embodiment of the invention also provides a kind of database backup system, comprising: logic log generation module, physical backup module, logic log backup module and data field, wherein:
The logic log generation module, the operation that is used for comprising according to the operation requests that database is operated is described, and generates to comprise unique definite sign of operand and comprise the logic log that action type is designated overlapping operation type identification or deletion action type identification;
The physical backup module is used for carrying out physical backup according to the data that the physical backup trigger condition is stored described data field;
The logic log backup module is used for the logic log that the logic log generation module generates is backed up in realtime; And the logic log before starting described physical backup constantly and the described physical backup logic log after starting constantly backs up respectively;
The data field is used for store database data.
In the DB Backup method that the embodiment of the invention provides, physical backup is carried out in the data field; To be recorded as logic log to the operation requests that database is operated and the logic log that generates will be backed up in realtime;
During the record logic log, the operation that comprises according to the operation requests that database is operated is earlier described to generate and is comprised unique definite sign of operand and the logic log that action type is designated overlapping operation type identification or deletion action type identification; During the backup logic log, logic log is shunted backup, be specially: the logic log of record backs up under first catalogue before starting constantly to this physical backup after starting last physical backup constantly; Logic log after starting this physical backup constantly backs up under second catalogue.Can be achieved as follows beneficial effect when therefore, adopting the method embodiment logarithm institute library backup:
1, logic log can be noted the everything of database in the physical backup process of database, realization is backed up in realtime to database, the no longer blocking operation request of physical backup process has realized the requirement of DB Backup process non-interrupting service, has improved the backup efficient of system;
2, do not need to back up all historical logic daily records during backup logic, and only need start constantly according to physical backup, backing up last physical backup starts constantly to the logic log between this physical backup startup constantly, greatly reduced the backup amount of logic log, shorten the BACKUP TIME of system, improved the backup efficient of system once more.
The DB Backup method that adopts the embodiment of the invention to provide when database is recovered, uses the data of physical backup to recover physical backup startup moment data field data before; Carrying out the logic log that backs up after physical backup starts constantly gets final product.Because in the logic log of backup, operation that all operations request that database is operated comprises is described and is all converted overlapping operation type that operand represents with unique fixing sign to or the operation of deletion action type is described, therefore, the actuating logic daily record can bring following beneficial effect in the restore database process:
1, can make database in the physical backup process, receive new operation requests, and can improve the accuracy and the reliability of DB Backup and database recovery;
2, the database recovery process does not need the historical logic daily record of reforming all, has reduced the release time of database, has improved database recovery efficient.
Description of drawings
The process flow diagram of backing up in realtime of logic log after a physical backup starts in the DB Backup method that Fig. 1 provides for the embodiment of the invention;
A kind of database backup system structural representation that Fig. 2 provides for the embodiment of the invention.
Embodiment
The embodiment of the invention provides a kind of logic log generation method, during with this method formation logic daily record, obtains the operation that operation requests that database is operated comprises earlier and describes; According to this operation the logic log that generation comprises the unique definite sign and the action type sign of operand is described then.In addition, can also comprise the cover data of operand being carried out overlapping operation when the formation logic daily record.The method that adopts the embodiment of the invention to provide, the operating result that can realize operand after the repeatedly actuating logic daily record has nothing to do with the number of times of actuating logic daily record.
In the process of above-mentioned formation logic daily record, convert the description of the operation in the origin operation request to that operand is represented with unique definite sign, that action type is designated overlapping operation type identification or deletion action type identification operation and describe.
The generation method of the logic log that the embodiment of the invention is provided below in conjunction with object lesson is described in detail.
At first, for satisfying all identical requirement of operand when the actuating logic daily record repeatedly, carry out following operation and describe conversion: will operate the operand that relates at every turn and use the unique and immutable sign of scope of expression to represent respectively.Preferably, because the address of the access unit in the database or the sign (ID) of access unit are a kind of unique and changeless signs, therefore the operand that can use the ID of the address of minimum access unit in database storing space or access unit to represent this operation description to comprise is described for each operation.For example: the operation requests of delete list data may relate to the deletion of record in several data fields, then operates when describing conversion, and the ID of access unit that can deleted record is corresponding represents corresponding operand.
Secondly, for the base state that satisfies operand does not influence the requirement of operating result, carry out following action type conversion: will operate the action type that description comprises and convert overlapping operation type or deletion action type to.After carrying out this action type conversion, to same operand, be to cover or delete when repeating logic log with the existing content of the content in the description of the operation after the conversion to operand, therefore no matter with this logic log operation how many times, all consistent with operation result once to the operating result of operand.
As shown in table 1 below, the sign (ID) of a memory block is Chunk10 in database embryonic stage of tentation data storehouse, this memory block Chunk10 is divided into 10 storage cells, each storage cell is represented with Slot, if the sign of each storage cell is represented with XMID, and establish each memory block and only deposit same tables of data, record of each storage cell Slot corresponding stored.Each Slot comprises main storage available action type identification among header information district SoltHead and the data field SoltData:SoltHead; SoltData is used for storaging user data.Suppose that the data length of storing among the SoltData is 8, and the data of storing among each SoltData comprise attribute-bit (attributeID) and numerical value (value) two parts, deposit the corresponding attributeID of value value, deposit the value value for back 4 for wherein preceding 4.
Table 1
| Chunk 10 | |||
| XMID | SlotID | SoltHead | SoltData |
| 1001 | 01 | 0 | 00000000 |
| 1002 | 02 | 0 | 00000000 |
| 1003 | 03 | 0 | 00000000 |
| 1004 | 04 | 0 | 00000000 |
| 1005 | 05 | 0 | 00000000 |
| 1006 | 06 | 0 | 00000000 |
| 1007 | 07 | 0 | 00000000 |
| 1008 | 08 | 0 | 00000000 |
| 1009 | 09 | 0 | 00000000 |
| 1010 | 10 | 0 | 00000000 |
When data base management system (DBMS) receives a operation requests about Chunk10, the operand of this operation requests may be the content of the several Slot among the Chunk10, therefore can describe the operand that comprises by first conversion operations, each Slot that relates to be described in operation use its corresponding XMID to represent.And then will operate and describe the action type comprise and be converted to and cover or the deletion action type.Logic log record format after conversion operations is described is: " XMID+OperateType+SlotData ".Wherein, XMID represents (SlotID is the ID of Slot corresponding among this Chunk) by two SlotID of two ChunkID+.OperateType is the action type sign, SoltHead corresponding to the memory block, this sign comprises deletion action type identification and overlapping operation type identification two classes: the deletion action type identification is corresponding to the unused state mark of SoltHead, and the overlapping operation type identification is corresponding to the user mode mark of SoltHead.For example, if the user mode mark of the SoltHead of memory block comprises " 0 " and " 1 " two kinds, wherein SoltHead represents the not use of this storage unit for " 0 ", SoltHead represents that for " 1 " this storage unit has been used to store data, then OperateType can be set it according to two big generic operation types and can value be " 0 " and " 1 ", " 0 " expression deletion action type, " 1 " expression overlapping operation type, promptly the OperateType value is the data field content of the Slot of this logic log indication of " 0 " expression deletion; The OperateType value is that " 1 " expression uses the SlotData of record in this logic log to cover the data of the data field of corresponding Slot.
Wherein, the corresponding deletion action of deletion action type identification, corresponding all the other the non-deletion actions such as operation, renewal operation and incremental update operation that increase of overlapping operation type identification.
The logic log recording method that for example two kinds of different action types is identified is elaborated below: for explaining conveniently, the operand of establishing all operation requests all is memory block Chunk10:
1, OperateType is overlapping operation type identification (a non-deletion action type identification):
A, increase recording operation:
For example: establish current C hunk10 and be in the state shown in the table 1, data base management system (DBMS) has received the operation requests that an operation is described as " increase record { attributeID=0001; value=0011} ", then determine this operation earlier and describe the operand that comprises, the memory unit address according to this operand writes down logic log again.For example described record to be increased to SlotID among the Chunk10 and be 01 data field, be 1001 then to preceding 4 of logic log that should operation requests, the 5th is designated as 1 expression overlapping operation type, final logic log can be designated as: 1001100010011, expression is that the SoltHead of 01 Slot uses 1 to cover to SlotID, and the SlotData data of this storage unit correspondence are covered with 00010011; Wherein, by order from left to right, preceding 4 " 1001 " expression is 01 corresponding unique identification XMID with SlotID, and the 5th " 1 " expression action type is overlapping operation, and the concrete numerical value that back 8 bit representations cover is " 00010011 ".The subsequent data base management system receives again that an operation is described as " increase record { attributeID=0002; value=0012} " and operation is described as the operation requests of " increase write down { attributeID=0003; value=0010} ", suppose that operand that these two operations are described to comprise is that SlotID is 02 and 03 data field among the Chunk10, then logic log can be designated as: 1002100020012 and 1003100030010, expression is that the SoltHead of 02 Slot uses 1 to cover to SlotID, and the SlotData data of this storage unit correspondence are covered with 00020012, and be that the SoltHead of 03 Slot uses 1 to cover to SlotID, and the SlotData data of this storage unit correspondence are covered with 00030010.It is as shown in table 2 to increase behind back two records the store status of memory block Chunk10:
Table 2
| Chunk 10 | |||
| XMID | SlotID | SoltHead | SoltData |
| 1001 | 01 | 1 | 00010011 |
| 1002 | 02 | 1 | 00020012 |
| 1003 | 03 | 1 | 00030010 |
| 1004 | 04 | 0 | 00000000 |
| 1005 | 05 | 0 | 00000000 |
| 1006 | 06 | 0 | 00000000 |
| 1007 | 07 | 0 | 00000000 |
| 1008 | 08 | 0 | 00000000 |
| 1009 | 09 | 0 | 00000000 |
| 1010 | 10 | 0 | 00000000 |
B, renewal recording operation:
For example: when Chunk10 is in state shown in the table 2, data base management system (DBMS) has received the operation requests that an operation is described as " attributeID of the Slot of the record correspondence of all attributeID 〉=0002 is updated to 0001 ", when then writing logic log, need find out this operation earlier and describe all operations object that comprises, in this example, operand is that SlotID is two storage cells of 02 and 03, then preceding 4 of logic log are designated as 1002 and 1003 respectively, the 5th of logic log is designated as 1 (overlapping operation), logic log under the final entry is: 1002100010012 and 1003100010010, expression is that the SoltHead of 02 Slot uses 1 to cover to SlotID, and the SlotData data of this storage unit correspondence are covered with 00010012, and be that the SoltHead of 03 Slot uses 1 to cover to SlotID, and the SlotData data of this storage unit correspondence are covered with 00010010, the Chunk10 store status after the covering is as shown in table 3:
Table 3
| Chunk 10 | |||
| XMID | SlotID | SoltHead | SoltData |
| 1001 | 01 | 1 | 00010011 |
| 1002 | 02 | 1 | 00010012 |
| 1003 | 03 | 1 | 00010010 |
| 1004 | 04 | 0 | 00000000 |
| 1005 | 05 | 0 | 00000000 |
| 1006 | 06 | 0 | 00000000 |
| 1007 | 07 | 0 | 00000000 |
| 1008 | 08 | 0 | 00000000 |
| 1009 | 09 | 0 | 00000000 |
| 1010 | 10 | 0 | 00000000 |
C, incremental update operation:
For example: when Chunk10 is in state shown in the table 3, data base management system (DBMS) has received the operation requests that an operation is described as " the last place value that with attributeID is the value of 0001 record correspondence all increases by 1 ", before then writing logic log, determining operand earlier is that SlotID is 01, three storage cells of 02 and 03, preceding 4 that write down logic log then are respectively 1001,1002 and 1003, the 5th of logic log all is designated as 1 (overlapping operation), logic log under the final entry is: 1001100010012,1002100010013 and 1003100010011, after carrying out this operation requests, the Chunk10 store status is as shown in table 4:
Table 4
| Chunk 10 | |||
| XMID | SlotID | SoltHead | SoltData |
| 1001 | 01 | 1 | 00010012 |
| 1002 | 02 | 1 | 00010013 |
| 1003 | 03 | 1 | 00010011 |
| 1004 | 04 | 0 | 00000000 |
| 1005 | 05 | 0 | 00000000 |
| 1006 | 06 | 0 | 00000000 |
| 1007 | 07 | 0 | 00000000 |
| 1008 | 08 | 0 | 00000000 |
| 1009 | 09 | 0 | 00000000 |
| 1010 | 10 | 0 | 00000000 |
2, OperateType is the deletion action type identification:
For example: when Chunk10 is in state shown in the table 3, data base management system (DBMS) has received the operation requests that an operation is described as " be with attributeID 0001 record deletion ", before then writing logic log, determining operand earlier is that SlotID is 01, three storage cells of 02 and 03, can write down logic log then is: 1001000000000,1002000000000 and 1003000000000.Wherein, the 5th of logic log is recorded as the data field content deletion (release) of 0 expression with corresponding stored unit, write logic log after database carry out this operation, the operating result of Chunk10 is as shown in table 5:
Table 5
| Chunk 10 | |||
| XMID | SlotID | SoltHead | SoltData |
| 1001 | 01 | 0 | 00000000 |
| 1002 | 02 | 0 | 00000000 |
| 1003 | 03 | 0 | 00000000 |
| 1004 | 04 | 0 | 00000000 |
| 1005 | 05 | 0 | 00000000 |
| 1006 | 06 | 0 | 00000000 |
| 1007 | 07 | 0 | 00000000 |
| 1008 | 08 | 0 | 00000000 |
| 1009 | 09 | 0 | 00000000 |
| 1010 | 10 | 0 | 00000000 |
More than in two kinds of action types, for deletion action, because OperateType is the data field content deletion of 0 expression with corresponding stored unit, when therefore writing logic log, the value that need not to set SlotData wherein is 00000000, i.e. the corresponding logic log of deletion action description also can be recorded as:
" SlotData of XMID+OperateType+ arbitrary value " or " XMID+OperateType ".If with the memory block of correspondence is operand this two kinds of logic logs that rerun, the user mode sign that when then operating all is the XMID that will write down in the logic log is changed to unused state mark value (for example according to OperateType=0 SoltHead being changed to 0), then with the data field content deletion of the storage cell of this XMID correspondence, the operating result of last memory block is consistent, operating result all with logic log in SlotData it doesn't matter, therefore for deletion action, need recording operation object address sign and deletion action type identification in the logic log at least.
For OperateType is the logic log of overlapping operation type identification, because corresponding to non-deletion action, therefore the logic log of overlapping operation also can be recorded as: " XMID+OperateType (arbitrary value that the deletion action type identification is outer)+SlotData ", for example, if the deletion action type identification is set at 0, when then writing down the logic log of non-deletion action request correspondence, OperateType in the logic log can be designated as the value that any permission of non-0 is set, be overlapping operation (non-deletion action) with the operation requests of representing this logic log record.When reruning logic log " XMID+OperateType (deletion action type identification outer arbitrary value)+SlotData ", but regulation is changed to 1 with the SoltHead of the slot of XMID correspondence.
In sum, corresponding to certain bar operation requests, logic log can be recorded as standard mode: " XMID+OperateType+SlotData ", wherein, OperateType can be set to two kinds of values according to action type, and the physical record mode described content of face of seing before no longer repeats.In addition to the above methods, deletion action represented in record when also but regulation OperateType is a certain value during logic log, for non-deletion action request, OperateType can be recorded as the arbitrary value different with non-deletion action, when reruning this logic log, if the deletion action value of the value of OperateType correspondence for setting, then no matter how many SlotData behind the OperateType is, all the SoltHead value with the storage cell of XMID correspondence in this logic log is changed to the non-working condition ident value, and deletes the storage area data of the storage cell of this XMID correspondence; If the value of OperateType correspondence is not the deletion action value of setting, then no matter how many values of OperateType is, all the SoltHead value with the storage cell of XMID correspondence in this logic log is changed to the user mode ident value, and the SlotData data that write down in this logic log is covered the storage area data of the storage cell of former XMID correspondence.
Therefore for deletion action, even the logic log after the conversion of repeatedly reruning, operating result all is the data deletion with the corresponding stored district, and the number of times that operating result and logic log rerun is irrelevant;
For non-deletion action because the logic log after the conversion has used overlapping operation, even so logic log repeatedly rerun and also can not change corresponding storage cell data, the operating result of operand all is the SlotData value that writes down in the logic log.
Based on above-mentioned logic log generation method, the invention provides a kind of DB Backup method, this method comprises:
Use logic log generation method provided by the invention will be written as logic log, and the logic log that generates is backed up in realtime the operation requests that database is operated; Carry out physical backup according to the data that the data field backup request data memory area of regular initiation (or the user initiates) is stored.Wherein, when carrying out the logic log backup, the logic log of backup backs up logic log backup after this physical backup startup constantly and this physical backup logic log before respectively as this physical backup logic log before between starting the last physical backup startup moment to this physical backup constantly.
During concrete enforcement, the logic log that (before physical backup starts constantly next time) after this physical backup startup constantly generates is backed up in realtime to second catalogue; When physical backup end each time, the logic log that last physical backup can be started the record between starting constantly to this physical backup constantly back up under first catalogue.
Figure 1 shows that a physical backup starts the real time backup method process flow diagram of logic log afterwards, comprising:
S101: receive the data field backup request, under logic log unloading to the three catalogues of storing under current second catalogue.
Wherein, during unloading, directly use the logic log of storing under current second catalogue to cover content under former the 3rd catalogue.
S102: the logic log that is stored in buffer zone in this data field physical backup process is backed up in realtime to described second catalogue.
Wherein, if carry out in the physical backup process data field, data base management system (DBMS) has received new operation requests, then according to the logic log backup method that provides previously, translation look-aside part is described in the operation that this operation requests is comprised to be logic log and to be stored in the buffer zone, behind the EO of this operation requests correspondence, the logic log that backs up in the buffer zone is backed up in realtime to described second catalogue.
S103: judged whether data field Backup end request,, then continued to carry out S104, carried out S102 otherwise return if having.
S104: the last physical backup of storing under current the 3rd catalogue is started the logic log unloading of record between the moment to this physical backup startup moment to described first catalogue.
S105: the logic log of buffer zone is backed up in realtime to second catalogue, and continue to carry out S106.
S106: judge whether new data field backup request,, then return and carry out S101, carry out S105 otherwise return if having.
Wherein, among the above-mentioned steps S101-S104, before the Backup end of data field, use the 3rd catalogue to back up this physical backup and start the logic log that is stored in before constantly under second catalogue, and be stored in before directly not starting this physical backup constantly that logic log under second catalogue backs up to the former of first catalogue because: if this physical backup failure, logic log before then this physical backup under unloading to the three catalogues can being started constantly simply returns under second catalogue, waits for the arrival of data field backup request next time.Otherwise, if the logic log that is stored under second catalogue before directly starting this physical backup constantly in step S101 backs up under first catalogue, if this data field backup failure then needs to recover the mass data of storing under first catalogue; Perhaps, because the memory capacity of first catalogue is limited, before starting this physical backup constantly, be stored in logic log under second catalogue and backed up to for first catalogue following time, can cover the partial content that backs up under former first catalogue, cause can not this physical backup point start-up time of complete recovery before content under first catalogue.
Preferably, the logic log in the physical backup process that backups under second catalogue and this physical backup can be finished logic log afterwards backs up respectively.For example: can in logic log, create a LogOld catalogue in advance, a LogDirty catalogue, a Log catalogue, when carrying out certain physical backup, the logic log before this physical backup startup constantly (the promptly last physical backup that completes successfully is constantly to the logic log between this physical backup startup constantly) is backuped under the LogOld catalogue; Logic log in the physical backup process is backed up in realtime under the LogDirty catalogue; Logic log after finishing physical backup is constantly backed up in realtime under the Log catalogue.Like this, can easily the logic log in the physical backup process further be done backup separately or supply all the other to manipulate, can further reduce the backup amount when backing up separately simultaneously.
In the DB Backup method that the embodiment of the invention provides, with before each physical backup, in the physical backup process and the logic log of physical backup after finishing carried out backing up in realtime of logic log, therefore, can both be backed up in realtime to all operations of database; In addition, the logic log in the entire database backup procedure backs up does not need to back up all historical logic daily records, only needs the logic log of record in the duration of twice physical backup interval, backup front and back to get final product.As seen this kind DB Backup method greatly reduces logic log backup amount, also no longer needs to carry out all historical logic daily records during corresponding restore database.In addition, in the DB Backup method that the embodiment of the invention provides, because the operation that will comprise the operation requests that database is operated description converts operand to and represents with unique definite sign, action type is designated the operation of covering or deletion action type identification and describes, therefore, even corresponding operation is described in the operation of repeatedly carrying out after the conversion, operating result all is identical, thereby when restore database, can be operand with certain physical backup result, carry out the logic log that writes down with method provided by the invention in this time physical backup process, can complete and correct restore database.As seen, use logic log backup method provided by the invention, the physical backup process no longer needs the blocking operation request.
Corresponding to the DB Backup method that the embodiment of the invention provides, the embodiment of the invention also provides a kind of database recovery method, and this method comprises: use the data of physical backup to recover physical backup startup moment data field data before; With the data field data that recover is that operand is carried out the logic log that physical backup starts back backup constantly.
If during to the data library backup after physical backup starts constantly, logic log after the logic log of physical backup process and physical backup finished backs up respectively, carry out physical backup in the then above-mentioned database recovery method and start constantly the logic log of backup afterwards, comprising:
1), carries out the logic log that backs up in the physical backup process;
2), carry out the logic log that backs up after physical backup is finished.
Below convenient for statement, be example with certain physical backup process and the restoration methods of aforementioned memory block Chunk10, the database recovery method that the embodiment of the invention is provided is elaborated.
For example: certain physical backup starts the data mode of the memory block Chunk10 that needs backup constantly shown in the table 2 of front, if it is t1 that physical backup starts constantly, be located at the t2 (t2＞t1) constantly in the physical backup process, data base management system (DBMS) has received the new operation requests (establish whole physical backup process data base management system and received only this time operation newly) that an operation is described as " attributeID of the record correspondence of all attributeID 〉=0002 is updated to 0001 ", suppose t2 constantly physical backup to have finished SlotID among the Chunk10 be the backup of data in 02 the storage cell, but also do not begin to back up SlotID and be the data in 03 the storage cell, after then physical backup was finished, the physical backup result of Chunk10 was as shown in table 6:
Table 6
| Chunk 10 | |||
| XMID | SlotID | SoltHead | SoltData |
| 1001 | 01 | 1 | 00010011 |
| 1002 | 02 | 1 | 00020012 |
| 1003 | 03 | 1 | 00010010 |
| 1004 | 04 | 0 | 00000000 |
| 1005 | 05 | 0 | 00000000 |
| 1006 | 06 | 0 | 00000000 |
| 1007 | 07 | 0 | 00000000 |
| 1008 | 08 | 0 | 00000000 |
| 1009 | 09 | 0 | 00000000 |
| 1010 | 10 | 0 | 00000000 |
As seen, do not have in the physical backup process backup down SlotID be the data of the change after the SlotData data executable operations of 02 Slot correspondence.
According to the logic log generation method that the embodiment of the invention provides, the pairing logic log of operation of t2 data base management system (DBMS) reception constantly is designated as according to the standard recording mode: 1002100010012 and 1003100010010.Therefore, when the database recovery method that adopts the embodiment of the invention to provide is recovered the data of t1 memory block Chunk10 after the moment, at first adopt the data of physical backup to recover the data shown in the table 6, carry out the logic log 1002100010012 and 1003100010010 of backup then, as can be known: after the actuating logic daily record, the SlotData data that to SlotID among the Chunk10 are 02 Slot correspondence cover with 00010012, therefore, become 00010012 after wrong physical backup data 00020012 are capped in the data field of this storage cell; The SlotData data that to SlotID are 03 Slot correspondence cover with 00010010, because the data consistent in this storage cell before covering and after covering, therefore, the data after the covering also are correct database manipulation results.Chunk10 data mode after the covering is as shown in table 7:
Table 7
| Chunk 10 | |||
| XMID | SlotID | SoltHead | SoltData |
| 1001 | 01 | 1 | 00010011 |
| 1002 | 02 | 1 | 00010012 |
| 1003 | 03 | 1 | 00010010 |
| 1004 | 04 | 0 | 00000000 |
| 1005 | 05 | 0 | 00000000 |
| 1006 | 06 | 0 | 00000000 |
| 1007 | 07 | 0 | 00000000 |
| 1008 | 08 | 0 | 00000000 |
| 1009 | 09 | 0 | 00000000 |
| 1010 | 10 | 0 | 00000000 |
In the above-mentioned database recovery method, because the data that recover with physical backup are operand, re-executed the logic log of backup in the logic log backup, the data of each storage cell of writing down in the logic log have been covered the data of the corresponding stored unit that physical backup recovers respectively, made the database data that recovers accurately and reliably.
Figure 2 shows that a kind of Database Systems that the embodiment of the invention provides, this system comprises: logic log generation module 21, physical backup module 22, logic log backup module 23 and data field 24, wherein:
Logic log generation module 21, describe according to the operation that the operation requests that database is operated comprises, the operation that the operation requests that receives is comprised is described and is converted cover type that operand represents with unique and changeless sign to or the operation of deletion type is described, and generates the respective logic daily record.
Physical backup module 22 is carried out physical backup according to the physical backup trigger condition to the data of storage in the data field 24.
Logic log backup module 23 is backed up in realtime to the logic log that logic log generation module 21 generates; And the logic log before starting physical backup constantly and start constantly after logic log back up respectively.
Data field 24 is used for store database data.
The technique scheme that provides by the embodiment of the invention, can back up in realtime to the data in data database data district, and no longer need the blocking operation request in the process of physical backup, when restore database, the logic log of backup can be repeated the data of the storage in the corresponding data district that recovers accurately and reliably.
Obviously, those skilled in the art can carry out various changes and modification to the present invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (11)
1. a logic log generation method is characterized in that, comprising:
Obtaining the operation that comprises in the operation requests that database is operated describes;
According to described operation the logic log that generation comprises the unique definite sign and the action type sign of operand is described; Wherein, described action type sign comprises deletion action type identification or overlapping operation type identification; When described action type was designated the overlapping operation type identification, described logic log also comprised the cover data of operand being carried out overlapping operation.
2. the method for claim 1 is characterized in that, and is described according to operating the logic log that the description generation comprises the unique definite sign and the action type sign of operand, comprising:
The operation of obtaining described change, make operation after the conversion comprise unique definite sign and action type sign that the operand that comprises is described in operation before the conversion in describing; Perhaps the operation after the conversion is described and is also comprised the cover data of operand being carried out overlapping operation;
According to the operation after the conversion the described logic log of generation is described.
3. method as claimed in claim 1 or 2 is characterized in that, described operand unique determines to be designated the address of the minimum access unit in database storing space, perhaps
Described operand unique determines to be designated the sign of the minimum access unit in database storing space.
4. the method for claim 1 is characterized in that, described logic log comprises first field and second field; Described first field is unique definite sign of described operand, and described second field is described action type sign; Perhaps
Described logic log comprises first field, second field and the 3rd field; Described first field is unique definite sign of described operand, and described second field is described action type sign, and described the 3rd field is described cover data of overlapping operation being carried out overlapping operation.
5. a DB Backup method is characterized in that, comprising:
New physical backup is carried out in the data field;
The logic log of record backs up under first catalogue before starting constantly to described new physical backup after starting last physical backup constantly; Logic log after starting described new physical backup constantly backs up under second catalogue;
Wherein, described logic log comprises the unique definite sign and the action type sign of operand; Described action type sign comprises deletion action type identification or overlapping operation type identification; Perhaps, described logic log also comprises the cover data of operand being carried out overlapping operation.
6. method as claimed in claim 5, it is characterized in that, after described logic log after starting new physical backup constantly backed up under second catalogue, when the data field backup request that receives once more database, described DB Backup method was further comprising the steps of:
Under logic log unloading to the three catalogues of storing under current second catalogue;
In the physical backup process of described data field once more, the logic log that is stored in buffer zone is backed up in realtime to described second catalogue;
After receiving data field Backup end request, with the logic log unloading of storing under described the 3rd catalogue to described first catalogue;
Before receiving next time the data field backup request, the logic log that is stored in buffer zone is backed up in realtime to described second catalogue.
7. method as claimed in claim 5 is characterized in that, also comprises:
Logic log after logic log in the described new physical backup process and described new physical backup finished backs up respectively.
8. a database recovery method is characterized in that, comprising:
Use the data of physical backup to recover described physical backup startup moment data field data before;
Carry out the logic log that described physical backup starts back backup constantly;
Wherein, described logic log comprises the unique definite sign and the action type sign of operand; Described action type sign comprises deletion action type identification or overlapping operation type identification; Perhaps, described logic log also comprises the cover data of operand being carried out overlapping operation;
The logic log that described this time physical backup starts back backup constantly comprises logic log in this time physical backup process and this time physical backup logic log after finishing.
9. method as claimed in claim 8 is characterized in that, described execution physical backup starts the logic log of back backup constantly, comprising:
According to operand that comprises in the described logic log and action type, the data of described operand correspondence are operated.
10. method as claimed in claim 9 is characterized in that, and is described according to operand that comprises in the described logic log and action type, and the data of described operand correspondence are operated, and specifically comprises:
When described action type is the deletion action type, delete the data of described operand correspondence;
When described action type is the overlapping operation type, cover the data of described operand correspondence with the cover data that operand is carried out overlapping operation that comprises in the described logic log.
11. a database backup system is characterized in that, comprising: logic log generation module, physical backup module, logic log backup module and data field, wherein:
The logic log generation module, the operation that is used for comprising according to the operation requests that database is operated is described, and generates to comprise unique definite sign of operand and comprise the logic log that action type is designated overlapping operation type identification or deletion action type identification;
The physical backup module is used for carrying out physical backup according to the data that the physical backup trigger condition is stored described data field;
The logic log backup module is used for the logic log that the logic log generation module generates is backed up in realtime; And the logic log before starting described physical backup constantly and the described physical backup logic log after starting constantly backs up respectively;
The data field is used for store database data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2007101642227A CN100498796C (en) | 2007-09-30 | 2007-09-30 | Logic log generation method, database backup/ restoration method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2007101642227A CN100498796C (en) | 2007-09-30 | 2007-09-30 | Logic log generation method, database backup/ restoration method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101122924A true CN101122924A (en) | 2008-02-13 |
| CN100498796C CN100498796C (en) | 2009-06-10 |
Family
ID=39085258
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2007101642227A Active CN100498796C (en) | 2007-09-30 | 2007-09-30 | Logic log generation method, database backup/ restoration method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100498796C (en) |
Cited By (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101370032B (en) * | 2008-09-09 | 2011-08-10 | 中兴通讯股份有限公司 | Modification log maintenance method and apparatus for data synchronization |
| CN101667181B (en) * | 2008-09-05 | 2011-12-21 | 华为技术有限公司 | Method, device and system for data disaster tolerance |
| CN102929771A (en) * | 2012-09-28 | 2013-02-13 | 用友软件股份有限公司 | Log recording device and log recording method |
| CN103049355A (en) * | 2012-12-25 | 2013-04-17 | 华为技术有限公司 | Method and equipment for database system recovery |
| CN103885855A (en) * | 2012-12-20 | 2014-06-25 | 航天信息股份有限公司 | Data backup and recovery method and data backup and recovery device |
| CN103942117A (en) * | 2013-01-21 | 2014-07-23 | 中国移动通信集团河南有限公司 | Data backup method, device and system |
| CN104169981A (en) * | 2012-03-09 | 2014-11-26 | 日本电气英富醍株式会社 | Pos device |
| CN104239167A (en) * | 2014-09-25 | 2014-12-24 | 珠海市君天电子科技有限公司 | Backup method and backup device for database as well as electronic equipment |
| CN104239476A (en) * | 2014-09-04 | 2014-12-24 | 上海天脉聚源文化传媒有限公司 | Method, device and system for synchronizing databases |
| CN104809033A (en) * | 2014-01-27 | 2015-07-29 | 中国移动通信集团河南有限公司 | Backup method and system |
| CN104881336A (en) * | 2015-05-22 | 2015-09-02 | 北京奇虎科技有限公司 | Data backup method and device |
| CN107665219A (en) * | 2016-07-28 | 2018-02-06 | 华为技术有限公司 | A kind of blog management method and device |
| CN110868428A (en) * | 2019-12-06 | 2020-03-06 | 吉林建筑大学 | Computer network safety early warning device |
| CN112650725A (en) * | 2020-12-30 | 2021-04-13 | 四川效率源信息安全技术股份有限公司 | Method for recovering DM8 database log file |
| WO2021077967A1 (en) * | 2019-10-21 | 2021-04-29 | 华为技术有限公司 | Network device management method, apparatus, and system |
| CN112740198A (en) * | 2018-09-24 | 2021-04-30 | 易享信息技术有限公司 | System and method for early removal of tombstone records in a database |
-
2007
- 2007-09-30 CN CNB2007101642227A patent/CN100498796C/en active Active
Cited By (22)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101667181B (en) * | 2008-09-05 | 2011-12-21 | 华为技术有限公司 | Method, device and system for data disaster tolerance |
| CN101370032B (en) * | 2008-09-09 | 2011-08-10 | 中兴通讯股份有限公司 | Modification log maintenance method and apparatus for data synchronization |
| US9129275B2 (en) | 2012-03-09 | 2015-09-08 | Nec Platforms, Ltd. | POS device |
| CN104169981A (en) * | 2012-03-09 | 2014-11-26 | 日本电气英富醍株式会社 | Pos device |
| CN104169981B (en) * | 2012-03-09 | 2016-08-24 | Nec平台株式会社 | POS terminal |
| CN102929771A (en) * | 2012-09-28 | 2013-02-13 | 用友软件股份有限公司 | Log recording device and log recording method |
| CN102929771B (en) * | 2012-09-28 | 2015-12-02 | 用友网络科技股份有限公司 | Log recording apparatus and log recording method |
| CN103885855A (en) * | 2012-12-20 | 2014-06-25 | 航天信息股份有限公司 | Data backup and recovery method and data backup and recovery device |
| CN103049355A (en) * | 2012-12-25 | 2013-04-17 | 华为技术有限公司 | Method and equipment for database system recovery |
| CN103049355B (en) * | 2012-12-25 | 2015-06-17 | 华为技术有限公司 | Method and equipment for database system recovery |
| CN103942117A (en) * | 2013-01-21 | 2014-07-23 | 中国移动通信集团河南有限公司 | Data backup method, device and system |
| CN103942117B (en) * | 2013-01-21 | 2018-03-23 | 中国移动通信集团河南有限公司 | A kind of data back up method, apparatus and system |
| CN104809033A (en) * | 2014-01-27 | 2015-07-29 | 中国移动通信集团河南有限公司 | Backup method and system |
| CN104809033B (en) * | 2014-01-27 | 2018-09-07 | 中国移动通信集团河南有限公司 | A kind of backup method and system |
| CN104239476A (en) * | 2014-09-04 | 2014-12-24 | 上海天脉聚源文化传媒有限公司 | Method, device and system for synchronizing databases |
| CN104239167A (en) * | 2014-09-25 | 2014-12-24 | 珠海市君天电子科技有限公司 | Backup method and backup device for database as well as electronic equipment |
| CN104881336A (en) * | 2015-05-22 | 2015-09-02 | 北京奇虎科技有限公司 | Data backup method and device |
| CN107665219A (en) * | 2016-07-28 | 2018-02-06 | 华为技术有限公司 | A kind of blog management method and device |
| CN112740198A (en) * | 2018-09-24 | 2021-04-30 | 易享信息技术有限公司 | System and method for early removal of tombstone records in a database |
| WO2021077967A1 (en) * | 2019-10-21 | 2021-04-29 | 华为技术有限公司 | Network device management method, apparatus, and system |
| CN110868428A (en) * | 2019-12-06 | 2020-03-06 | 吉林建筑大学 | Computer network safety early warning device |
| CN112650725A (en) * | 2020-12-30 | 2021-04-13 | 四川效率源信息安全技术股份有限公司 | Method for recovering DM8 database log file |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100498796C (en) | 2009-06-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100498796C (en) | Logic log generation method, database backup/ restoration method and system | |
| CN1331063C (en) | On-line data backup method based on data volume snapshot | |
| CN103577121B (en) | A kind of highly reliable linear file access method based on Nand Flash | |
| US7774565B2 (en) | Methods and apparatus for point in time data access and recovery | |
| CN104040481B (en) | Method and system for merging, storing and retrieving incremental backup data | |
| US8060713B1 (en) | Consolidating snapshots in a continuous data protection system using journaling | |
| CN101515276B (en) | Method for write operation of file data, and recovery method and recovery system for file data | |
| US7363540B2 (en) | Transaction-safe FAT file system improvements | |
| US7107294B2 (en) | Method and apparatus for interrupting updates to a database to provide read-only access | |
| US8250033B1 (en) | Replication of a data set using differential snapshots | |
| CN106021016A (en) | Virtual point in time access between snapshots | |
| US7698319B2 (en) | Database system management method, database system, database device, and backup program | |
| CN100430902C (en) | Distributing real-time data bank fault recovering method capable of supporting serving and recovering simultaneously | |
| CN103744936A (en) | Multi-version concurrency control method in database and database system | |
| CN102591982A (en) | Method and system of performing incremental sql server database backups | |
| CN103197988A (en) | Data backup and recovery method, device and database system | |
| CN103617277A (en) | Method for restoring data table content deleted mistakenly | |
| CN103544110A (en) | Block-level continuous data protection method based on solid-state disc | |
| CN104166605A (en) | Data backup method and system based on incremental data files | |
| CN104516959A (en) | Method and device for managing database logs | |
| CN106104515A (en) | Utilize File system design and the fault recovery method of nonvolatile memory | |
| CN104750755A (en) | Method and system for recovering data after switching between main database and standby database | |
| CN101937378B (en) | Method for carrying out back-up protection on data of storage equipment and computer system | |
| CN102479118A (en) | Incremental backup method for data blocks | |
| CN102024021A (en) | Method for logging metadata in logical file system |
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: 20201116 Address after: No.1 Yingpan Road, Zhaiji village, Wangting Town, Xiangcheng District, Suzhou City, Jiangsu Province Patentee after: Suzhou Gonghu precision manufacturing industry development Co.,Ltd. Address before: Unit 2414-2416, main building, no.371, Wushan Road, Tianhe District, Guangzhou City, Guangdong Province Patentee before: GUANGDONG GAOHANG INTELLECTUAL PROPERTY OPERATION Co.,Ltd. Effective date of registration: 20201116 Address after: Unit 2414-2416, main building, no.371, Wushan Road, Tianhe District, Guangzhou City, Guangdong Province Patentee after: GUANGDONG GAOHANG INTELLECTUAL PROPERTY OPERATION Co.,Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd. |
|
| TR01 | Transfer of patent right |