CN105630626B - Transaction backup processing method and device - Google Patents
Transaction backup processing method and device Download PDFInfo
- Publication number
- CN105630626B CN105630626B CN201410614050.9A CN201410614050A CN105630626B CN 105630626 B CN105630626 B CN 105630626B CN 201410614050 A CN201410614050 A CN 201410614050A CN 105630626 B CN105630626 B CN 105630626B
- Authority
- CN
- China
- Prior art keywords
- backup
- transaction
- log
- global
- database
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a transaction backup processing method and a device, wherein the method comprises the following steps: acquiring the log submission time of the transaction backup on a database DB node included in the global transaction; and carrying out backup processing on the global transaction according to the log submitting time, at least one of preset database global backup finishing time and database global transaction log backup deadline. The invention solves the problems of complex backup processing scheme and low reliability of the distributed database in the related technology, thereby improving the reliability of backup data.
Description
Technical Field
The present invention relates to the field of communications, and in particular, to a transaction backup processing method and apparatus.
Background
The traditional database backup is only suitable for a single database node to backup, and the distributed database, especially the distributed database developed based on the open source database, needs a new backup scheme to backup and ensures the reliability and consistency of data. The existing distributed database backup and recovery scheme is complex to use, low in reliability and difficult to guarantee the consistency of data.
Aiming at the problems of complex backup processing scheme and low reliability of the distributed database in the related technology, no effective solution is provided at present.
Disclosure of Invention
The invention provides a transaction backup processing method and device, which at least solve the problems of complex backup processing scheme and low reliability of a distributed database in the related technology.
According to an aspect of the present invention, there is provided a transaction backup processing method, including: acquiring the log submission time of the transaction backup on a database DB node included in the global transaction; and carrying out backup processing on the global transaction according to the log submitting time and at least one of preset database global backup finishing time and database global transaction log backup deadline.
Further, according to the log submitting time, the preset database global backup finishing time and the preset database global transaction log backup deadline, performing backup processing on the global transaction comprises: judging whether the log submission time of the transaction backup on the database DB node included in the global transaction is prior to the preset database global backup completion time; and if the judgment result is yes, determining that the transaction backup on the DB node included on the global transaction is successful.
Further, according to the log submitting time, the preset database global backup finishing time and the preset database global transaction log backup deadline, performing backup processing on the global transaction comprises: judging whether the log submission time of the transaction backup on the database DB node included in the global transaction is prior to the preset database global backup completion time; under the condition that the judgment result is negative, judging whether the log submitting time of the DB node with the log submitting time later than the preset database global backup finishing time is earlier than the database global transaction log backup deadline; and if so, performing forward rolling operation on the backup transaction on the DB node before the backup deadline of the database global transaction log, wherein the commit time of the log is later than the preset database global backup completion time.
Further, according to the log submitting time, the preset database global backup finishing time and the preset database global transaction log backup deadline, performing backup processing on the global transaction comprises: judging whether the transaction backups on the database DB nodes included in the global transaction are successfully submitted at the preset database global backup completion time or the database global transaction log backup deadline according to the log submission time; and under the condition that the judgment result is negative, performing rollback operation on the backup transaction on the global transaction.
Further, before obtaining the log commit time of the transaction backup on the database DB node included in the global transaction, the method further includes: and sending indication information to a DB node agent, wherein the indication information is used for indicating the DB node agent to check the integrity of the backup transaction.
According to another aspect of the present invention, there is provided a transaction backup processing apparatus, including: the acquisition module is used for acquiring the log submission time of the transaction backup on the DB node of the database included in the global transaction; and the backup processing module is used for carrying out backup processing on the global transaction according to the log submitting time and at least one of preset database global backup finishing time and database global transaction log backup deadline.
Further, the backup processing module includes: the first judgment unit is used for judging whether the log submission time of the transaction backup on the database DB node included in the global transaction is prior to the preset database global backup completion time; and the determining unit is used for determining that the transaction backup on the DB node included in the global transaction is successful under the condition that the judgment result is yes.
Further, the backup processing module includes: the second judging unit is used for judging whether the log submitting time of the transaction backups on the database DB nodes included in the global transaction is prior to the preset database global backup finishing time; a third judging unit, configured to, if the judgment result is negative, judge whether the log commit time of the DB node whose log commit time is later than the predetermined database global backup completion time is earlier than the database global transaction log backup deadline; and the forward rolling operation unit is used for performing forward rolling operation on the backup transaction on the DB node before the backup deadline of the database global transaction log if the judgment result is yes, wherein the log submitting time is later than the preset database global backup finishing time.
Further, the backup processing module includes: a fourth judging unit, configured to judge, according to the log submission time, whether the transaction backup on the database DB node included in the global transaction is successfully submitted at the predetermined database global backup completion time or the database global transaction log backup deadline; and the rollback operation unit is used for performing rollback operation on the backup transaction on the global transaction under the condition that the judgment result is negative.
Further, the apparatus further comprises: and the checking module is used for sending indication information to a DB node agent, wherein the indication information is used for indicating the DB node agent to check the integrity of the backup transaction.
By the method, the log submission time of the transaction backup on the DB node of the database included in the global transaction is acquired; and performing backup processing on the global transaction according to the log submitting time and at least one of the preset database global backup finishing time and the database global transaction log backup deadline, so that the problems of complex distributed database backup processing scheme and low reliability in the related technology are solved, and the reliability of backup data is improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
FIG. 1 is a flow diagram of a transaction backup processing method according to an embodiment of the invention;
FIG. 2 is a block diagram of a transaction backup processing device according to an embodiment of the invention;
FIG. 3 is a block diagram one of a transaction backup processing device in accordance with a preferred embodiment of the present invention;
FIG. 4 is a block diagram two of a transaction backup processing device in accordance with a preferred embodiment of the present invention;
FIG. 5 is a block diagram three of a transaction backup processing device in accordance with a preferred embodiment of the present invention;
FIG. 6 is a block diagram four of a transaction backup processing device in accordance with a preferred embodiment of the present invention;
FIG. 7 is a block diagram of a transactional backup processing system architecture in accordance with a preferred embodiment of the present invention;
FIG. 8 is a flow diagram of a distributed database backup in accordance with a preferred embodiment of the present invention;
FIG. 9 is a diagram of a DB node backup in accordance with a preferred embodiment of the present invention;
FIG. 10 is a flow diagram of a distributed database recovery in accordance with a preferred embodiment of the present invention;
FIG. 11 is a diagram of a global transaction backup in accordance with a preferred embodiment of the present invention.
Detailed Description
The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
In this embodiment, a transaction backup processing method is provided, and fig. 1 is a flowchart of the transaction backup processing method according to an embodiment of the present invention, as shown in fig. 1, the flowchart includes the following steps:
step S102, obtaining the log submission time of the transaction backup on the DB node of the database included in the global transaction;
step S104, according to the log submitting time, at least one of the preset database global backup finishing time and the database global transaction log backup deadline, the global transaction is backed up.
Through the steps, the log submission time of the transaction backup on the DB node of the database included in the global transaction is obtained; according to the log submitting time, at least one of the preset database global backup finishing time and the database global transaction log backup deadline, the global transaction is backed up, the problems of complex distributed database backup processing scheme and low reliability in the related technology are solved, and the backup data reliability is improved.
In this embodiment, according to the log submitting time, the predetermined database global backup completing time and the database global transaction log backup deadline, performing backup processing on the global transaction may include the following preferred embodiments: judging whether the log submission time of the transaction backup on the database DB node included in the global transaction is prior to the preset database global backup completion time; and if the judgment result is yes, determining that the transaction backup on the DB node included on the global transaction is successful.
Further, according to the log commit time, the predetermined database global backup completion time and the predetermined database global transaction log backup deadline, performing backup processing on the global transaction may include: judging whether the log submission time of the transaction backup on the database DB node included in the global transaction is prior to the preset database global backup completion time; under the condition that the judgment result is negative, judging whether the log submitting time of the DB node with the log submitting time later than the preset database global backup finishing time is earlier than the database global transaction log backup deadline; and if so, performing forward rolling operation on the backup transaction on the DB node prior to the backup deadline of the database global transaction log, wherein the commit time of the log is later than the preset database global backup completion time.
Further, according to the log commit time, the predetermined database global backup completion time and the predetermined database global transaction log backup deadline, performing backup processing on the global transaction may further include: judging whether the transaction backups on the database DB nodes included in the global transaction are successfully submitted at the preset database global backup completion time or the database global transaction log backup deadline according to the log submission time; and under the condition that the judgment result is negative, performing rollback operation on the backup transaction on the global transaction.
As an optional implementation manner, before obtaining the log commit time of the transaction backup on the DB node included in the global transaction, sending indication information to the DB node proxy, where the indication information is used to indicate the DB node proxy to check the integrity of the backup transaction, so as to ensure the integrity of the backup transaction and improve the reliability.
The embodiment of the present invention further provides a transaction backup processing apparatus, which is used to implement the foregoing embodiments and preferred embodiments, and the description of the apparatus is omitted here. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Fig. 2 is a block diagram of a transaction backup processing device according to an embodiment of the present invention, as shown in fig. 2, the device including: an acquisition module 22 and a backup processing module 24, each of which is briefly described below.
An obtaining module 22, configured to obtain a log commit time of a transaction backup on a database DB node included in the global transaction;
and the backup processing module 24 is configured to perform backup processing on the global transaction according to the log submitting time, and at least one of a predetermined database global backup completing time and a predetermined database global transaction log backup deadline.
Fig. 3 is a block diagram one of a transaction backup processing device according to a preferred embodiment of the present invention, and as shown in fig. 3, the backup processing module 24 includes:
a first judging unit 32, configured to judge whether the log commit times of the transaction backups on the database DB nodes included in the global transaction all precede the predetermined database global backup completion time;
and a determining unit 34, configured to determine that the transaction backup on the DB node included in the global transaction is successful if the determination result is yes.
Fig. 4 is a block diagram ii of the transaction backup processing device according to the preferred embodiment of the present invention, and as shown in fig. 4, the backup processing module 24 includes:
a second judging unit 42, configured to judge whether the log commit times of the transaction backups on the database DB nodes included in the global transaction all precede the predetermined database global backup completion time;
a third judging unit 44, configured to, in a case that a judgment result is negative, judge whether the log commit time of the DB node whose log commit time is later than the predetermined database global backup completion time is earlier than the database global transaction log backup deadline;
and a rolling-forward operation unit 46, configured to, if the determination result is yes, perform rolling-forward operation on the backup transaction on the DB node before the backup transaction on the database global transaction log backup deadline, the log commit time being later than the predetermined database global backup completion time.
Fig. 5 is a block diagram three of a transaction backup processing device according to a preferred embodiment of the present invention, and as shown in fig. 5, the backup processing module 24 includes:
a third determining unit 52, configured to determine, according to the log submission time, whether the transaction backup on the database DB node included in the global transaction is successfully submitted at the predetermined database global backup completion time or the database global transaction log backup deadline;
and a rollback operation unit 54, configured to perform a rollback operation on the backup transaction on the global transaction if the determination result is negative.
Fig. 6 is a fourth block diagram of the transaction backup processing device according to the preferred embodiment of the present invention, as shown in fig. 6, the device further includes:
a checking module 62, configured to send indication information to the DB node proxy, where the indication information is used to instruct the DB node proxy to check the integrity of the backup transaction.
Examples of the present invention are further described below in conjunction with the alternative embodiments.
When the embodiment of the invention backups the distributed database, the data and the log file are respectively backed up for each DB node, and the activity transaction information of the distributed data in the time span is backed up. And when the data is recovered, the affairs of each DB node are sequentially recovered, the affairs are analyzed again, if necessary, the rolling back is carried out, and if the affairs need to be recovered to the latest state, the rolling-forward operation is carried out again.
Fig. 7 is a block diagram of the architecture of the transaction backup processing system according to the preferred embodiment of the present invention, and the overall architecture and location of the backup recovery function in the distributed database are shown in fig. 7, and the functions of the modules are briefly described below.
And the backup recovery function module is responsible for backing up and recovering the distributed database, rolling back the recovered transaction and rolling forward the latest data.
The distributed transaction GTM is responsible for applying and releasing the transaction, and managing the current activity and historical transaction.
A DB node for storing an actual database node of data. The node synchronously deploys a database agent DB node agent which is responsible for communication with distributed system function modules such as backup recovery, GTM and the like. And deploying the client backup tool responsible for backup recovery.
Fig. 8 is a flowchart of a distributed database backup according to a preferred embodiment of the present invention, as shown in fig. 8, including the following steps:
step S802, backuping each DB node data and log, obtaining cluster information needing to be backed up in the distributed database system, and issuing a backup instruction to a DB node agent of each DB node under the cluster needing to be backed up. The DB node proxy starts the backup tool. When backing tool starts, the database Log Serial Number (LSN) is recorded, and then the data file is copied from the specified position. The process of backing up tool data is as follows: the backup tool starts a background thread to copy the database log file, the thread monitors the log file all the time, and once the log file changes, the changed content is copied to the own log file of the backup tool. Since data copying may be performed for a long time, data restoration requires all log files from the start of backup to the end of backup. Copying the data file, reading the data dictionary of the DB node database, opening and reading the data file, and reading one or more pages at a time according to the IO load condition of the DB node. When the data file is copied, the backup tool stops copying the log, and records the backup type, the LSN when the backup is started and ended.
Step S804, a global transaction log, that is, a transaction of a backup activity is backed up, a time span of the backup is from a first DB node backup start to a last DB node backup end, fig. 9 is a DB node backup schematic diagram according to the preferred embodiment of the present invention, as shown in fig. 9, a time span from a first red line to a last red line is the time span of the backup. Global transaction information for activities within the time span described in the first step is obtained to the GTM module.
Step S806, landing the backup data, landing the backed-up database file, database log file, and active transaction information file to the backup target storage device, and recording information such as the DB node corresponding to each file information. This concludes the backup process.
FIG. 10 is a flow chart of distributed database recovery according to the preferred embodiment of the present invention, as shown in FIG. 10, including the following steps:
step S1002, importing backup data, acquiring data files, data log files and activity transaction information files from backup equipment according to records when the backup data falls to the ground, and restoring the data files, the data log files and the activity transaction information files to corresponding DB nodes. And informing the DB node agent to check the file content according to the record information, and ensuring that the file is consistent and not damaged.
Step S1004, the single-node data is recovered, and the data which is successfully imported and checked to be normal is recovered to the DB node.
Step S1006, rolling back the transaction, processing the global transaction log, forcing to roll back the transaction which is locally successful but globally unsuccessful, and analyzing the transaction which fails to submit to roll back according to the situation. FIG. 11 is a diagram of a global transaction backup according to the preferred embodiment of the present invention, as shown in FIG. 11, global transaction T1, where the transaction on each DB node is successfully committed before the completion time of the global backup, and no rollback operation is required for data pre-recovery. Global transaction T2, the transaction on each DB node commits before the global backup completion time, but transaction T2.node2 commits failed. In this case, it may be necessary to check the global transaction log after the transactions t2.node1, t2.node2, and t2.node3 are forced to be rolled back, and if there is no forced rolling transaction t2.node1, t2.node2, and t2.node3, then perform the forced rolling back. Global transaction T3, transaction T3.node1, transaction T3.node3 both submitted successfully before the global backup completion time, but transaction T3.node2 did not submit yet at global backup completion time T0. At this point, transactions t3.node1 and t3.node3 need to be forced to roll back. For Node2 Node, transaction t3.Node2 may or may not have been rolled back automatically, and needs to further determine whether rolling back is needed by combining Node2 backup completion time point. In order to ensure that the global transaction T3 is not lost after the future transaction T3.node2 is successfully committed, the executed SQL statements need to be restored according to the change of each line of data recorded in the database log, and all the SQL statements executed by the transactions T3.node1 and T3.node3 (possibly including T3.node2) need to be recorded in the commit order.
Step S1008, rolling forward, if it is necessary to restore the database to the latest state, further rolling forward, starting from the next log of the serial number of the database log according to the database Log Serial Number (LSN) information recorded during backup, restoring the executed SQL statement according to the change of each row of data recorded by the database log, and rolling forward the database to the latest state.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (8)
1. A transaction backup processing method, comprising:
acquiring the log submission time of the transaction backup on a database DB node included in the global transaction;
according to the log submitting time and at least one of the preset database global backup finishing time and the preset database global transaction log backup deadline, carrying out backup processing on the global transaction, wherein the backup processing comprises the following steps: judging whether the log submission time of the transaction backup on the database DB node included in the global transaction is prior to the preset database global backup completion time; under the condition that the judgment result is negative, judging whether the log submitting time of the DB node with the log submitting time later than the preset database global backup finishing time is earlier than the database global transaction log backup deadline; and if so, performing forward rolling operation on the backup transaction on the DB node before the backup deadline of the database global transaction log, wherein the commit time of the log is later than the preset database global backup completion time.
2. The method of claim 1, wherein performing backup processing on the global transaction according to the log commit time, the predetermined database global backup completion time and the database global transaction log backup deadline comprises:
judging whether the log submission time of the transaction backup on the database DB node included in the global transaction is prior to the preset database global backup completion time;
and if the judgment result is yes, determining that the transaction backup on the DB node included on the global transaction is successful.
3. The method of claim 1, wherein performing backup processing on the global transaction according to the log commit time, the predetermined database global backup completion time and the database global transaction log backup deadline comprises:
judging whether the transaction backups on the database DB nodes included in the global transaction are successfully submitted at the preset database global backup completion time or the database global transaction log backup deadline according to the log submission time;
and under the condition that the judgment result is negative, performing rollback operation on the backup transaction on the global transaction.
4. The method of claim 1, prior to obtaining a log commit time for a transaction backup on a database DB node that the global transaction comprises, further comprising:
and sending indication information to a DB node agent, wherein the indication information is used for indicating the DB node agent to check the integrity of the backup transaction.
5. A transaction backup processing apparatus, comprising:
the acquisition module is used for acquiring the log submission time of the transaction backup on the DB node of the database included in the global transaction;
the backup processing module is used for performing backup processing on the global transaction according to the log submitting time and at least one of preset database global backup finishing time and database global transaction log backup deadline, and comprises the following steps: the second judging unit is used for judging whether the log submitting time of the transaction backups on the database DB nodes included in the global transaction is prior to the preset database global backup finishing time; a third judging unit, configured to, if the judgment result is negative, judge whether the log commit time of the DB node whose log commit time is later than the predetermined database global backup completion time is earlier than the database global transaction log backup deadline; and the forward rolling operation unit is used for performing forward rolling operation on the backup transaction on the DB node before the backup deadline of the database global transaction log if the judgment result is yes, wherein the log submitting time is later than the preset database global backup finishing time.
6. The apparatus of claim 5, wherein the backup processing module comprises:
the first judgment unit is used for judging whether the log submission time of the transaction backup on the database DB node included in the global transaction is prior to the preset database global backup completion time;
and the determining unit is used for determining that the transaction backup on the DB node included in the global transaction is successful under the condition that the judgment result is yes.
7. The apparatus of claim 5, wherein the backup processing module comprises:
a fourth judging unit, configured to judge, according to the log submission time, whether the transaction backup on the database DB node included in the global transaction is successfully submitted at the predetermined database global backup completion time or the database global transaction log backup deadline;
and the rollback operation unit is used for performing rollback operation on the backup transaction on the global transaction under the condition that the judgment result is negative.
8. The apparatus of claim 5, further comprising:
and the checking module is used for sending indication information to the DB node agent, wherein the indication information is used for indicating the DB node agent to check the integrity of the backup transaction.
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 CN105630626A (en) | 2016-06-01 |
| CN105630626B true 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) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| CN112000521B (en) * | 2020-08-24 | 2021-08-27 | 中国银联股份有限公司 | Full backup method and device for distributed database system and computer readable storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102662793A (en) * | 2012-03-07 | 2012-09-12 | 江苏引跑网络科技有限公司 | Hot backup and recovery method of distributed database with guarantee of data consistency |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7100076B2 (en) * | 2003-05-09 | 2006-08-29 | Hewlett-Packard Development Company, L.P. | Minimum latency reinstatement of database transaction locks |
| US10430298B2 (en) * | 2010-10-28 | 2019-10-01 | Microsoft Technology Licensing, Llc | Versatile in-memory database recovery using logical log records |
| CN102541694B (en) * | 2012-01-18 | 2015-05-13 | 浪潮(北京)电子信息产业有限公司 | Method and device for database backup |
| CN103034739A (en) * | 2012-12-29 | 2013-04-10 | 天津南大通用数据技术有限公司 | Distributed memory system and updating and querying method thereof |
| CN103914485B (en) * | 2013-01-07 | 2017-05-03 | 上海宝信软件股份有限公司 | 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 (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102662793A (en) * | 2012-03-07 | 2012-09-12 | 江苏引跑网络科技有限公司 | Hot backup and recovery method of distributed database with guarantee of data consistency |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105630626A (en) | 2016-06-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105718570B (en) | Data migration method and device for database | |
| US9372908B2 (en) | Merging an out of synchronization indicator and a change recording indicator in response to a failure in consistency group formation | |
| US7386752B1 (en) | Using asset dependencies to identify the recovery set and optionally automate and/or optimize the recovery | |
| US20060095478A1 (en) | Consistent reintegration a failed primary instance | |
| JP2007310701A (en) | Database system, storage device, initial duplication method, and log application method | |
| CN109086425B (en) | Data processing method and device for database | |
| 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 | |
| CN110825562B (en) | Data backup method, device, system and storage medium | |
| CN113254425B (en) | Method, apparatus, system, program and storage medium for database transaction retention | |
| WO2017028375A1 (en) | Version upgrading method and system | |
| EP3163447B1 (en) | Data replication method, device and system | |
| CN105630626B (en) | Transaction backup processing method and device | |
| EP4060514A1 (en) | Distributed database system and data disaster backup drilling method | |
| CN110543413A (en) | Business system testing method, device, equipment and storage medium | |
| US10296517B1 (en) | Taking a back-up software agnostic consistent backup during asynchronous replication | |
| US9619506B2 (en) | Method and system to avoid deadlocks during a log recovery | |
| US9015116B2 (en) | Consistent replication of transactional updates | |
| CN111290885B (en) | Multi-computer two-stage data backup and hierarchical recovery method for Mars detection | |
| CN111427718B (en) | File backup method, file recovery method and file recovery device | |
| CN110389713B (en) | Data synchronization method, apparatus and computer readable medium | |
| CN112860492B (en) | Automatic regression testing method and system suitable for core system | |
| CN117271206A (en) | Database recovery method and device based on time point and distributed database system | |
| CN118277157A (en) | Database backup method, platform and related equipment | |
| CN117271204A (en) | Database recovery method, device, electronic equipment and storage medium |
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. |