CN105630626A - Transaction backup processing method and device - Google Patents
Transaction backup processing method and device Download PDFInfo
- Publication number
- CN105630626A CN105630626A CN201410614050.9A CN201410614050A CN105630626A CN 105630626 A CN105630626 A CN 105630626A CN 201410614050 A CN201410614050 A CN 201410614050A CN 105630626 A CN105630626 A CN 105630626A
- Authority
- CN
- China
- Prior art keywords
- backup
- global transaction
- data base
- deadline
- affairs
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a transaction backup processing method and device, wherein the method comprises the following steps: obtaining the log submission time of a transaction backup on a database DB node included in a global transaction; and performing backup processing of the global transaction according to at least one selected from a group consisting of the log submission time, the predetermined database global backup completion time and the database global transaction log backup deadline. By means of the invention, the problems that the distributed database backup processing scheme in a related technology is complex and low in reliability can be solved; and the backup data reliability is improved.
Description
Technical field
The present invention relates to the communications field, in particular to a kind of affairs backup processing method and device.
Background technology
Traditional data library backup is only suitable for individual data storehouse node and is backed-up, and distributed data base is based especially on the distributed data base of PostgreSQL database exploitation needs new backup scenario be backed-up and ensure reliability and the concordance of data. Existing distributed data library backup and recovery scheme use complexity, reliability not high and are difficult to ensure the concordance of data.
The problem complicated for distributed data base back-up processing scheme in correlation technique, reliability is low, not yet proposes effective solution at present.
Summary of the invention
The invention provides a kind of affairs backup processing method and device, at least to solve the problem that in correlation technique, distributed data base back-up processing scheme is complicated, reliability is low.
According to an aspect of the invention, it is provided a kind of affairs backup processing method, including: obtain the daily record submission time that the affairs on the database D B node that global transaction includes back up; According to described daily record submission time, and in predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline at least one, be backed-up described global transaction processing.
Further, according to described daily record submission time, and predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline, described global transaction is backed-up process and includes: whether the described daily record submission time of the affairs backup judging on the database D B node that global transaction includes all backs up the deadline prior to described predetermined data base's overall situation; When judged result is for being, it is determined that the affairs on DB node included on described global transaction back up successfully.
Further, according to described daily record submission time, and predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline, described global transaction is backed-up process and includes: whether the described daily record submission time of the affairs backup judging on the database D B node that global transaction includes all backs up the deadline prior to described predetermined data base's overall situation; When judged result is no, it is judged that daily record submission time is later than the described daily record submission time of the DB node of described predetermined data base's overall situation backup deadline whether prior to described data base global transaction Log backup deadline; When judged result is for being, described daily record submission time is later than described predetermined data base's overall situation backup deadline, carries out roll forward operation prior to the backup affairs on described data base's global transaction Log backup DB deadline node.
Further, according to described daily record submission time, and predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline, described global transaction is backed-up process and includes: the affairs backup judging on the database D B node that described global transaction includes according to described daily record submission time backs up the deadline or whether data base's global transaction Log backup is all submitted to successfully deadline in described predetermined data base's overall situation; When judged result is no, the backup affairs on described global transaction are carried out rolling back action.
Further, before the daily record submission time of the affairs backup obtained on the database D B node that global transaction includes, also including: send instruction information to DB node-agent, wherein, described instruction information is for indicating described DBAgent that the integrity of described backup affairs is verified.
According to a further aspect in the invention, it is provided that a kind of affairs back-up processing device, including: acquisition module, for obtaining the daily record submission time of the affairs backup on the database D B node that global transaction includes; Back-up processing module, for according to described daily record submission time, and in predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline at least one, be backed-up described global transaction processing.
Further, described back-up processing module includes: the first judging unit, and whether the described daily record submission time for judging the affairs backup on the database D B node that global transaction includes all backs up the deadline prior to described predetermined data base's overall situation; Determine unit, for when judged result is for being, it is determined that the affairs on DB node included on described global transaction back up successfully.
Further, described back-up processing module includes: the second judging unit, and whether the described daily record submission time for judging the affairs backup on the database D B node that global transaction includes all backs up the deadline prior to described predetermined data base's overall situation; 3rd judging unit, for when judged result is no, it is judged that daily record submission time is later than the described daily record submission time of the DB node of described predetermined data base's overall situation backup deadline whether prior to described data base global transaction Log backup deadline; Roll forward operation unit, for when judged result is for being, described daily record submission time is later than described predetermined data base's overall situation backup deadline, carries out roll forward operation prior to the backup affairs on described data base's global transaction Log backup DB deadline node.
Further, described back-up processing module includes: the 4th judging unit, for judging that according to described daily record submission time the affairs on the database D B node that described global transaction includes back up whether described predetermined data base's overall situation backup deadline or data base's global transaction Log backup all submit to successfully deadline; Rolling back action unit, for when judged result is no, carrying out rolling back action to the backup affairs on described global transaction.
Further, described device also includes: correction verification module, and for sending instruction information to DB node-agent, wherein, described instruction information is for indicating described DBAgent that the integrity of described backup affairs is verified.
By the present invention, adopt the daily record submission time of the affairs backup obtained on the database D B node that global transaction includes; According to described daily record submission time, and in predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline at least one, it is backed-up described global transaction processing, solve the problem that in correlation technique, distributed data base back-up processing scheme is complicated, reliability is low, thus improve Backup Data reliability.
Accompanying drawing explanation
Accompanying drawing described herein is used for providing a further understanding of the present invention, constitutes the part of the application, and the schematic description and description of the present invention is used for explaining the present invention, is not intended that inappropriate limitation of the present invention. In the accompanying drawings:
Fig. 1 is the flow chart of affairs backup processing method according to embodiments of the present invention;
Fig. 2 is the block diagram of affairs back-up processing device according to embodiments of the present invention;
Fig. 3 is the block diagram one of affairs back-up processing device according to the preferred embodiment of the invention;
Fig. 4 is the block diagram two of affairs back-up processing device according to the preferred embodiment of the invention;
Fig. 5 is the block diagram three of affairs back-up processing device according to the preferred embodiment of the invention;
Fig. 6 is the block diagram four of affairs back-up processing device according to the preferred embodiment of the invention;
Fig. 7 is the block diagram of affairs back-up processing system architecture according to the preferred embodiment of the invention;
Fig. 8 is that distributed data base backs up flow chart according to the preferred embodiment of the invention;
Fig. 9 is DB node standby schematic diagram according to the preferred embodiment of the invention;
Figure 10 is that distributed data base recovers flow chart according to the preferred embodiment of the invention;
Figure 11 is the schematic diagram of global transaction backup according to the preferred embodiment of the invention.
Detailed description of the invention
Below with reference to accompanying drawing and describe the present invention in detail in conjunction with the embodiments. It should be noted that when not conflicting, the embodiment in the application and the feature in embodiment can be mutually combined.
Providing a kind of affairs backup processing method in the present embodiment, Fig. 1 is the flow chart of affairs backup processing method according to embodiments of the present invention, as it is shown in figure 1, this flow process comprises the steps:
Step S102, obtains the daily record submission time that the affairs on the database D B node that global transaction includes back up;
Step S104, according to this daily record submission time, and in predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline at least one, be backed-up this global transaction processing.
By above-mentioned steps, obtain the daily record submission time that the affairs on the database D B node that global transaction includes back up; According to this daily record submission time, and in predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline at least one, it is backed-up this global transaction processing, solve the problem that in correlation technique, distributed data base back-up processing scheme is complicated, reliability is low, thus improve Backup Data reliability.
In the present embodiment, according to daily record submission time, and predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline, this global transaction is backed-up process can include following preferred embodiment: whether this daily record submission time of the affairs backup judging on the database D B node that global transaction includes all backs up deadline prior to this predetermined data base's overall situation; When judged result is for being, it is determined that the affairs on DB node included on this global transaction back up successfully.
Further, according to this daily record submission time, and predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline, it is backed-up this global transaction processing whether this daily record submission time that may include that the affairs backup judged on the database D B node that global transaction includes all backs up deadline prior to this predetermined data base's overall situation; When judged result is no, it is judged that daily record submission time is later than this daily record submission time of the DB node of this predetermined data base's overall situation backup deadline whether prior to this data base global transaction Log backup deadline; When judged result is for being, this daily record submission time is later than this predetermined data base's overall situation backup deadline, carries out roll forward operation prior to the backup affairs on this data base's global transaction Log backup DB deadline node.
Further, according to this daily record submission time, and predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline, this global transaction is backed-up process can also include: judge the affairs backup on the database D B node that this global transaction includes is whether this predetermined data base's overall situation backup deadline or data base's global transaction Log backup all submit to successfully deadline according to this daily record submission time; When judged result is no, the backup affairs on this global transaction are carried out rolling back action.
As the optional embodiment of one, before the daily record submission time of the affairs backup obtained on the database D B node that global transaction includes, instruction information is sent to DB node-agent, wherein, this instruction information is for indicating this DBAgent that the integrity of these backup affairs is verified, so that it is guaranteed that the integrity of backup affairs, improve reliability.
The embodiment of the present invention additionally provides a kind of affairs back-up processing device, and this device is used for realizing above-described embodiment and preferred implementation, has be carried out repeating no more of explanation. As used below, term " module " can realize the software of predetermined function and/or the combination of hardware. Although the device described by following example preferably realizes with software, but hardware, or the realization of the combination of software and hardware is also likely to and is contemplated.
Fig. 2 is the block diagram of affairs back-up processing device according to embodiments of the present invention, as in figure 2 it is shown, this device includes: acquisition module 22 and back-up processing module 24, below modules is briefly described.
Acquisition module 22, for obtaining the daily record submission time of the affairs backup on the database D B node that global transaction includes;
Back-up processing module 24, for according to this daily record submission time, and in predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline at least one, be backed-up this global transaction processing.
Fig. 3 is the block diagram one of affairs back-up processing device according to the preferred embodiment of the invention, as it is shown on figure 3, this back-up processing module 24 includes:
First judging unit 32, whether this daily record submission time for judging the affairs backup on the database D B node that global transaction includes all backs up deadline prior to this predetermined data base's overall situation;
Determine unit 34, for when judged result is for being, it is determined that the affairs on DB node included on this global transaction back up successfully.
Fig. 4 is the block diagram two of affairs back-up processing device according to the preferred embodiment of the invention, and as shown in Figure 4, this back-up processing module 24 includes:
Second judging unit 42, whether this daily record submission time for judging the affairs backup on the database D B node that global transaction includes all backs up deadline prior to this predetermined data base's overall situation;
3rd judging unit 44, for when judged result is no, it is judged that daily record submission time is later than this daily record submission time of the DB node of this predetermined data base's overall situation backup deadline whether prior to this data base global transaction Log backup deadline;
Roll forward operation unit 46, for when judged result is for being, this daily record submission time is later than this predetermined data base's overall situation backup deadline, carries out roll forward operation prior to the backup affairs on this data base's global transaction Log backup DB deadline node.
Fig. 5 is the block diagram three of affairs back-up processing device according to the preferred embodiment of the invention, as it is shown in figure 5, this back-up processing module 24 includes:
3rd judging unit 52, for judging that according to this daily record submission time the affairs on the database D B node that this global transaction includes back up whether this predetermined data base's overall situation backup deadline or data base's global transaction Log backup all submit to successfully deadline;
Rolling back action unit 54, for when judged result is no, carrying out rolling back action to the backup affairs on this global transaction.
Fig. 6 is the block diagram four of affairs back-up processing device according to the preferred embodiment of the invention, and as shown in Figure 6, this device also includes:
Correction verification module 62, for sending instruction information to DB node-agent, wherein, this instruction information is for indicating this DBAgent that the integrity of these backup affairs is verified.
Below in conjunction with optional embodiment, the embodiment of the present invention is further described.
The embodiment of the present invention, when distributed data base is backed-up, to each DB node Backup Data and journal file respectively, and backs up the active transaction information of distributed data in this time span. Recover the affairs of each DB node when recovering data successively, if then analyze affairs and need, carrying out rollback, if needing to return to last state, then carrying out roll forward operation.
Fig. 7 is the block diagram of affairs back-up processing system architecture according to the preferred embodiment of the invention, Backup and Restore function overall architecture and the position in distributed data base as it is shown in fig. 7, below the function of each module is briefly introduced.
Backup and Restore functional module, is responsible for distributed data base is backed-up, recovering, and the affairs after recovering carry out rollback and latest data before roll.
Distributed transaction GTM, is responsible for application and the release of affairs and the management of current active thing, historical transactions.
DB node, for storing the actual database node of data. This node synchronizes to dispose database broker DBAgent, is responsible for and the communication of Backup and Restore, GTM distributed system function module. And dispose the client backupTool being responsible for Backup and Restore.
Fig. 8 is that distributed data base backs up flow chart according to the preferred embodiment of the invention, as shown in Figure 8, comprises the following steps:
Step S802, backs up each DB node data and daily record, obtains the cluster information needing backup in distributed data base system, and the DBAgent to each DB node needed under the cluster backed up issues backup instruction. DBAgent starts backup tool backupTool. BackupTool starts database of record log serial number (LSN) when starting, then from specifying position to start to replicate data file. The process of backupTool Backup Data is as follows: backupTool starts a background thread copy database log file, this thread monitors journal file always, once journal file changes, just in the copy content changed to the journal file of backupTool self. Owing to data copy may perform the some time, data are recovered to need to use all journal files from backing up when starting to Backup end. Copy data file, reads the data dictionary of DB node database, opens and read data files, once reads one page or multipage according to DB node I/O load situation. When data file copies completes, backupTool stops copy daily record, records this type of backup, LSN when backup starts and terminates.
Step S804, backup global transaction daily record, the i.e. affairs of backup activity, the time span of backup starts to last DB node standby to terminate from first DB node standby, Fig. 9 is DB node standby schematic diagram according to the preferred embodiment of the invention, as it is shown in figure 9, first red line is the time span of this backup in last red line interval. The movable overall separate feature in time span described in the first step is obtained to GTM module.
Step S806, Backup Data lands, and the database file of backup, database log file, active transaction message file are landed to backup target storage device, and record the information such as DB node corresponding to each fileinfo. So far backup procedure terminates.
Figure 10 is that distributed data base recovers flow chart according to the preferred embodiment of the invention, as shown in Figure 10, comprises the following steps:
Step S1002, imports Backup Data, and record when landing according to Backup Data obtains data file, data log files, active transaction message file from alternate device, returns to the DB node of correspondence. And notifying that file content is verified by DBAgent according to record information, it is ensured that file does not unanimously damage.
Step S1004, recovers single-node data, uses and successfully imports and verify normal data and return to DB node.
Step S1006, rollback affairs, global transaction daily record is processed, forces the success of rollback local but overall unsuccessful affairs, and analyze the failed affairs of submission and according to circumstances carry out rollback. Figure 11 is the schematic diagram of global transaction backup according to the preferred embodiment of the invention, and as shown in figure 11, global transaction T1, the affairs on each DB node are all successfully submitted to before the overall situation backs up the deadline, then do not need rolling back action when data pre-restore. Global transaction T2, the affairs on each DB node are all submitted to before the overall situation backs up the deadline, but affairs T2.Node2 submits to unsuccessfully. In this case, it is possible to forced rollback affairs T2.Node1, T2.Node2 and T2.Node3, it is necessary to first check global transaction daily record, if not forcing rollback affairs T2.Node1, T2.Node2 and T2.Node3, then perform to force rollback. Global transaction T3, affairs T3.Node1, T3.Node3 all backed up before the deadline in the overall situation and successfully submit to, but affairs T3.Node2 has backed up moment t0 in the overall situation not yet submits to. Now need to force rollback affairs T3.Node1 and T3.Node3. And for Node2 node, affairs T3.Node2 is likely to by automatic rollback, it is also possible to not by automatic rollback, it is necessary to back up deadline point in conjunction with Node2 and further determine whether to need rollback. After ensureing that affairs T3.Node2 successfully submits in the future, global transaction T3 does not lose, need the change of the every data line according to database journal record, restore performed SQL statement, also will by all SQL statement performed by affairs T3.Node1 and T3.Node3 (potentially including T3.Node2) under submission journal.
Step S1008, before roll, if needing to return to last state, need to roll before further, database journal serial number (LSN) information of record during according to backup, from the next daily record of this serial number of database journal, the change of the every data line according to database journal record, restores performed SQL statement, database rollforward to last state.
Obviously, those skilled in the art should be understood that, each module of the above-mentioned present invention or each step can realize with general calculation element, they can concentrate on single calculation element, or it is distributed on the network that multiple calculation element forms, alternatively, they can realize with the executable program code of calculation element, thus, can be stored in storage device is performed by calculation element, and in some cases, shown or described step can be performed with the order being different from herein, or they are fabricated to respectively each integrated circuit modules, or the multiple modules in them or step are fabricated to single integrated circuit module realize. so, the present invention is not restricted to the combination of any specific hardware and software.
The foregoing is only the preferred embodiments of the present invention, be not limited to the present invention, for a person skilled in the art, the present invention can have various modifications and variations. All within the spirit and principles in the present invention, any amendment of making, equivalent replacement, improvement etc., should be included within protection scope of the present invention.
Claims (10)
1. an affairs backup processing method, it is characterised in that including:
Obtain the daily record submission time that the affairs on the database D B node that global transaction includes back up;
According to described daily record submission time, and in predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline at least one, be backed-up described global transaction processing.
2. method according to claim 1, it is characterised in that according to described daily record submission time, and predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline, be backed-up process to described global transaction and include:
Judge whether the described daily record submission time of the affairs backup on the database D B node that global transaction includes all backs up the deadline prior to described predetermined data base's overall situation;
When judged result is for being, it is determined that the affairs on DB node included on described global transaction back up successfully.
3. method according to claim 1, it is characterised in that according to described daily record submission time, and predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline, be backed-up process to described global transaction and include:
Judge whether the described daily record submission time of the affairs backup on the database D B node that global transaction includes all backs up the deadline prior to described predetermined data base's overall situation;
When judged result is no, it is judged that daily record submission time is later than the described daily record submission time of the DB node of described predetermined data base's overall situation backup deadline whether prior to described data base global transaction Log backup deadline;
When judged result is for being, described daily record submission time is later than described predetermined data base's overall situation backup deadline, carries out roll forward operation prior to the backup affairs on described data base's global transaction Log backup DB deadline node.
4. method according to claim 1, it is characterised in that according to described daily record submission time, and predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline, be backed-up process to described global transaction and include:
Judge the affairs backup on the database D B node that described global transaction includes is whether described predetermined data base's overall situation backup deadline or data base's global transaction Log backup all submit to successfully deadline according to described daily record submission time;
When judged result is no, the backup affairs on described global transaction are carried out rolling back action.
5. method according to claim 1, it is characterised in that before the daily record submission time of the affairs backup obtained on the database D B node that global transaction includes, also include:
Sending instruction information to DB node-agent, wherein, described instruction information is for indicating described DBAgent that the integrity of described backup affairs is verified.
6. an affairs back-up processing device, it is characterised in that including:
Acquisition module, for obtaining the daily record submission time of the affairs backup on the database D B node that global transaction includes;
Back-up processing module, for according to described daily record submission time, and in predetermined data base's overall situation backup deadline and data base global transaction Log backup deadline at least one, be backed-up described global transaction processing.
7. device according to claim 6, it is characterised in that described back-up processing module includes:
First judging unit, whether the described daily record submission time for judging the affairs backup on the database D B node that global transaction includes all backs up the deadline prior to described predetermined data base's overall situation;
Determine unit, for when judged result is for being, it is determined that the affairs on DB node included on described global transaction back up successfully.
8. device according to claim 6, it is characterised in that described back-up processing module includes:
Second judging unit, whether the described daily record submission time for judging the affairs backup on the database D B node that global transaction includes all backs up the deadline prior to described predetermined data base's overall situation;
3rd judging unit, for when judged result is no, it is judged that daily record submission time is later than the described daily record submission time of the DB node of described predetermined data base's overall situation backup deadline whether prior to described data base global transaction Log backup deadline;
Roll forward operation unit, for when judged result is for being, described daily record submission time is later than described predetermined data base's overall situation backup deadline, carries out roll forward operation prior to the backup affairs on described data base's global transaction Log backup DB deadline node.
9. device according to claim 6, it is characterised in that described back-up processing module includes:
4th judging unit, for judging that according to described daily record submission time the affairs on the database D B node that described global transaction includes back up whether described predetermined data base's overall situation backup deadline or data base's global transaction Log backup all submit to successfully deadline;
Rolling back action unit, for when judged result is no, carrying out rolling back action to the backup affairs on described global transaction.
10. device according to claim 6, it is characterised in that described device also includes:
Correction verification module, for sending instruction information to DB node-agent, wherein, described instruction information is for indicating described DBAgent that the integrity of described backup affairs is verified.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410614050.9A CN105630626B (en) | 2014-11-03 | 2014-11-03 | Transaction backup processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410614050.9A CN105630626B (en) | 2014-11-03 | 2014-11-03 | Transaction backup processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105630626A true CN105630626A (en) | 2016-06-01 |
| CN105630626B CN105630626B (en) | 2020-05-05 |
Family
ID=56045601
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410614050.9A Active CN105630626B (en) | 2014-11-03 | 2014-11-03 | Transaction backup processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105630626B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107451013A (en) * | 2017-06-30 | 2017-12-08 | 北京奇虎科技有限公司 | Data reconstruction method, apparatus and system based on distributed system |
| CN109144790A (en) * | 2018-09-30 | 2019-01-04 | 广州鼎甲计算机科技有限公司 | The synthesized backup method and device of MySQL database |
| CN112000521A (en) * | 2020-08-24 | 2020-11-27 | 中国银联股份有限公司 | Full backup method and device for distributed database system and computer readable storage medium |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040225915A1 (en) * | 2003-05-09 | 2004-11-11 | Hewlett-Packard Development Company, L.P. | Minimum latency reinstatement of database transaction locks |
| CN102436490A (en) * | 2010-10-28 | 2012-05-02 | 微软公司 | Versatile in-memory database recovery |
| CN102541694A (en) * | 2012-01-18 | 2012-07-04 | 浪潮(北京)电子信息产业有限公司 | Method and device for database backup |
| CN102662793A (en) * | 2012-03-07 | 2012-09-12 | 江苏引跑网络科技有限公司 | Hot backup and recovery method of distributed database with guarantee of data consistency |
| CN103034739A (en) * | 2012-12-29 | 2013-04-10 | 天津南大通用数据技术有限公司 | Distributed memory system and updating and querying method thereof |
| CN103914485A (en) * | 2013-01-07 | 2014-07-09 | 上海宝信软件股份有限公司 | System and method for remotely collecting, retrieving and displaying application system logs |
-
2014
- 2014-11-03 CN CN201410614050.9A patent/CN105630626B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040225915A1 (en) * | 2003-05-09 | 2004-11-11 | Hewlett-Packard Development Company, L.P. | Minimum latency reinstatement of database transaction locks |
| CN102436490A (en) * | 2010-10-28 | 2012-05-02 | 微软公司 | Versatile in-memory database recovery |
| CN102541694A (en) * | 2012-01-18 | 2012-07-04 | 浪潮(北京)电子信息产业有限公司 | Method and device for database backup |
| CN102662793A (en) * | 2012-03-07 | 2012-09-12 | 江苏引跑网络科技有限公司 | Hot backup and recovery method of distributed database with guarantee of data consistency |
| CN103034739A (en) * | 2012-12-29 | 2013-04-10 | 天津南大通用数据技术有限公司 | Distributed memory system and updating and querying method thereof |
| CN103914485A (en) * | 2013-01-07 | 2014-07-09 | 上海宝信软件股份有限公司 | System and method for remotely collecting, retrieving and displaying application system logs |
Non-Patent Citations (1)
| Title |
|---|
| 张海建 等: "《数据库开发与管理》", 28 February 2014, 清华大学出版社 * |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107451013A (en) * | 2017-06-30 | 2017-12-08 | 北京奇虎科技有限公司 | Data reconstruction method, apparatus and system based on distributed system |
| CN107451013B (en) * | 2017-06-30 | 2020-12-25 | 北京奇虎科技有限公司 | Data recovery method, device and system based on distributed system |
| CN109144790A (en) * | 2018-09-30 | 2019-01-04 | 广州鼎甲计算机科技有限公司 | The synthesized backup method and device of MySQL database |
| CN112000521A (en) * | 2020-08-24 | 2020-11-27 | 中国银联股份有限公司 | Full backup method and device for distributed database system and computer readable storage medium |
| CN112000521B (en) * | 2020-08-24 | 2021-08-27 | 中国银联股份有限公司 | Full backup method and device for distributed database system and computer readable storage medium |
| WO2022041672A1 (en) * | 2020-08-24 | 2022-03-03 | 中国银联股份有限公司 | Full backup method and apparatus for distributed database system, and computer-readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105630626B (en) | 2020-05-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103853837B (en) | Oracle does not stop the table level back-up restoring method of Production database automatically | |
| CN110392120B (en) | Method and device for recovering fault in message pushing process | |
| CN109189860A (en) | A kind of active and standby increment synchronization method of MySQL based on Kubernetes system | |
| CN109491609B (en) | Cache data processing method, device and equipment and readable storage medium | |
| EP1332433B1 (en) | Fault tolerance for computer programs that operate over a communication network | |
| CN110221938A (en) | The method and storage medium of electronic device, block chain common recognition | |
| CN113254425B (en) | Method, apparatus, system, program and storage medium for database transaction retention | |
| WO2017028375A1 (en) | Version upgrading method and system | |
| CN105630626A (en) | Transaction backup processing method and device | |
| CN103973727A (en) | Data synchronizing method and device | |
| CN106815094B (en) | Method and equipment for realizing transaction submission in master-slave synchronization mode | |
| CN113360322A (en) | Method and equipment for recovering data based on backup system | |
| EP4060514A1 (en) | Distributed database system and data disaster backup drilling method | |
| CN102457400B (en) | Method for preventing split brain phenomenon from occurring on distributed replicated block device (DRBD) resource | |
| CN110673982A (en) | Shared mysql database backup and recovery method and device | |
| CN105373549A (en) | Data migration method and device and data node server | |
| WO2018076696A1 (en) | Data synchronization method and out-of-band management device | |
| CN111880947A (en) | Data transmission method and device | |
| CN110825758A (en) | Transaction processing method and device | |
| CN106055433A (en) | Data backup method and device | |
| JP3340431B2 (en) | Database management method | |
| CN115658390A (en) | Container disaster tolerance method, system, device, equipment and computer readable storage medium | |
| CN106648963B (en) | Method and system for recovering synchronous backup of data | |
| CN102929746A (en) | Quick backup and recovery method for lottery sale system | |
| KR20100061983A (en) | Method and system for operating management of real-time replicated database |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220330 Address after: 100176 602, 6 / F, building 6, courtyard 10, KEGU 1st Street, Daxing District, Beijing (Yizhuang group, high-end industrial area, Beijing Pilot Free Trade Zone) Patentee after: Jinzhuan Xinke Co.,Ltd. Address before: 518057 No. 55 South Science and technology road, Shenzhen, Guangdong, Nanshan District Patentee before: ZTE Corp. |