CN114968656A - Data rollback method, device, equipment and medium - Google Patents
Data rollback method, device, equipment and medium Download PDFInfo
- Publication number
- CN114968656A CN114968656A CN202110193457.9A CN202110193457A CN114968656A CN 114968656 A CN114968656 A CN 114968656A CN 202110193457 A CN202110193457 A CN 202110193457A CN 114968656 A CN114968656 A CN 114968656A
- Authority
- CN
- China
- Prior art keywords
- node
- data
- original
- backup
- rollback
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
- G06F11/1448—Management of the data involved in backup or backup restore
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Abstract
The embodiment of the disclosure relates to a data rollback method, device, equipment and medium, and relates to the field of cloud computing databases. Wherein the method comprises the following steps: acquiring a data rollback request; switching a predetermined backup node into a current master node, and switching an original master node in the stock nodes into a current slave node; and rolling back the data of the stock nodes comprising the current slave node based on the backup data in the current master node. By adopting the technical scheme, one original node can be used as a backup node, when data rollback is needed, the role of the backup node is switched to the main node, and data rollback of all nodes is carried out through backup data, so that rapid data rollback is realized, and the database is prevented from falling into a long-time unavailable state.
Description
Technical Field
The present disclosure relates to the field of database technologies, and in particular, to a data rollback method, apparatus, device, and medium.
Background
To prevent data loss, the database may synchronize data using a multi-copy set architecture.
When the database is used for data recovery, all nodes need to download external backup data and reload the backup data. The external backup data may be subjected to attack and the like to cause unreliable data, so that data recovery fails, and the database may be in an unavailable state. In the prior art, when data recovery fails, external backup data is acquired again to recover, but the data may also fail, and the problem cannot be solved.
Disclosure of Invention
To solve the technical problem or at least partially solve the technical problem, the present disclosure provides a data rollback method, apparatus, device, and medium.
The embodiment of the disclosure provides a data rollback method, which comprises the following steps:
acquiring a data rollback request;
switching a predetermined backup node into a current master node, and switching an original master node in the stock nodes into a current slave node;
and performing data rollback on the inventory nodes including the current slave node based on the backup data in the current master node.
The embodiment of the present disclosure further provides a data rollback apparatus, including:
the request acquisition module is used for acquiring a data rollback request;
the switching module is used for switching a predetermined backup node into a current master node and switching an original master node in the stock nodes into a current slave node;
and the data rollback module is used for performing data rollback on the stock nodes including the current slave node based on the backup data in the current master node.
An embodiment of the present disclosure further provides an electronic device, which includes: a processor; a memory for storing the processor-executable instructions; the processor is used for reading the executable instructions from the memory and executing the instructions to realize the data rollback method provided by the embodiment of the disclosure.
The embodiment of the present disclosure also provides a computer-readable storage medium, which stores a computer program for executing the data rollback method provided by the embodiment of the present disclosure.
Compared with the prior art, the technical scheme provided by the embodiment of the disclosure has the following advantages: the data rollback scheme provided by the embodiment of the disclosure acquires a data rollback request; switching the backup node to be a current main node, and switching an original main node in the stock nodes to be a current slave node; and rolling back the data of the stock nodes comprising the current slave node based on the backup data in the current master node. By adopting the technical scheme, one original node can be used as a backup node, when data rollback is needed, the role of the backup node is switched to the main node, and data rollback of all nodes is carried out through backup data, so that rapid data rollback is realized, and the database is prevented from falling into a long-time unavailable state.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
In order to more clearly illustrate the embodiments or technical solutions in the prior art of the present disclosure, the drawings used in the embodiments or technical solutions in the prior art description will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.
Fig. 1 is a schematic flowchart of a data rollback method according to an embodiment of the present disclosure;
fig. 2 is a schematic flow chart of another data rollback method according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of a data rollback apparatus according to an embodiment of the present disclosure;
fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
Detailed Description
In order that the above objects, features and advantages of the present disclosure may be more clearly understood, aspects of the present disclosure will be further described below. It should be noted that the embodiments and features of the embodiments of the present disclosure may be combined with each other without conflict.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure, but the present disclosure may be practiced otherwise than as described herein; it is to be understood that the embodiments disclosed in the specification are only a few embodiments of the present disclosure, and not all embodiments.
Fig. 1 is a flowchart illustrating a data rollback method according to an embodiment of the present disclosure, where the method may be performed by a data rollback apparatus, where the apparatus may be implemented in software and/or hardware, and may be generally integrated in an electronic device. As shown in fig. 1, the method includes:
The data rollback request is used to perform a request for data recovery of all nodes in the database, and the MongoDB database is taken as an example in the embodiment of the present disclosure. The MongoDB database can adopt a high-availability architecture of a three-node copy set, and three data nodes are located on different physical servers and can automatically synchronize data.
In this embodiment of the present disclosure, before acquiring the data rollback request, the method further includes: acquiring a data recovery request; adding a blank node, and replacing the blank node with a target node, wherein the target node is an original main node, an original slave node or an original hidden node; and performing data recovery on the replaced original main node, original slave node and original hidden node based on the external backup data. When a user discovers a problem or needs to use historical data, a data recovery request can be initiated. The duplicate set of the database can provide three roles, a Hidden (Hidden) node is a data node which does not support access by default in the database, a Primary (Primary) node is a data node which supports read-write requests, a Secondary (Secondary) node is a data node which supports read-only requests, the Primary node and the Secondary node provide services, when the Primary node fails, the system can automatically select a new Primary node, and when the Secondary node is unavailable, a standby node takes over the services, so that the service availability is guaranteed in multiple ways. The original hidden node, the original master node and the original slave node refer to nodes with three roles before data recovery.
A blank node is a data node whose data is empty. The target node is one of an original master node, an original slave node and an original hidden node, and because the original master node and the original slave node support access, when the original master node or the original slave node is used as the target node, a new node needs to be determined again and external access network switching needs to be performed, and the target node is preferably the original hidden node and has the lowest influence on access of a user. And replacing the target node with the blank node, wherein the name of the replaced target node is unchanged, and then the replaced original main node, original slave node and original hidden node can download external backup data, perform data recovery and reconstruct a copy set. The external backup data may be backup data stored in the external device by the database, and the external backup data may include physical backup data, incremental backup data, and the like. For example, when the target node is an original hidden node, the original hidden node is replaced by a blank node to serve as a new original hidden node, and then the original master node, the original slave node and the replaced original hidden node can perform data recovery through external backup data.
In an embodiment of the present disclosure, acquiring a data rollback request includes: and if the data recovery result is detected to be data recovery failure, determining to acquire the data rollback request. The external backup data may be unreliable due to attacks and other reasons, and therefore when it is detected that the data recovery result is data recovery failure, it may be determined that a data rollback request is obtained, and data rollback is triggered. Optionally, when the database is detected to be unavailable or fault information such as data loss sent by the user is received, it is determined that the data recovery result is data recovery failure.
And 102, switching a predetermined backup node to be a current master node, and switching an original master node in the stock nodes to be a current slave node.
The backup node is a node predetermined in the previous data recovery process, and in the embodiment of the present disclosure, the backup node may be an original master node, an original slave node, or an original hidden node. In the embodiment of the present disclosure, before adding a blank node and replacing a target node with the blank node, the method further includes: and determining the target node as a backup node. After the target node is determined to be the backup node, the target node does not participate in data synchronization any more.
Specifically, after the data rollback request is obtained, the backup node may be switched to the current master node and the original master node may be switched to the current slave node by modifying the role information. The stock nodes are nodes included in the database copy set, after the original master node is switched, the stock nodes can include a current slave node, an original slave node and an original hidden node, and one of the stock nodes is obtained by replacing a blank node.
And 103, rolling back data of the stock nodes including the current slave node based on the backup data in the current master node.
The data rollback refers to a behavior of restoring data to a history correct state when data processing is wrong, and in the embodiment of the disclosure, the data is restored to a history state when data restoration fails. The backup data in the current master node is the node data when the data recovery is performed, and the time of the external backup data is different from the time of the external backup data, and the external backup data may be the node data stored at the previous backup time of the data recovery, for example, the external backup data may be the node data stored at the previous day of the data recovery.
Specifically, the data rollback is performed on the stock nodes including the current slave node based on the backup data in the current master node, and the data rollback method includes: and synchronizing the backup data in the current master node to the current slave node, the original slave node and the original hidden node through a consistency protocol. The consistency protocol (Raft protocol), also called data replication protocol, is a protocol for keeping data consistent among nodes in a database replica set. Through a consistency protocol, backup data of the current master node can be synchronized to the current slave node, the original slave node and the original hidden node, namely, the data of all nodes in the database can be correctly restored.
According to the data rollback scheme provided by the embodiment of the disclosure, a data rollback request is acquired; switching the backup node into a current main node, and switching an original main node in the stock nodes into a current slave node; and rolling back the data of the stock nodes comprising the current slave node based on the backup data in the current master node. By adopting the technical scheme, one original node can be used as a backup node, when data rollback is needed, the role of the backup node is switched to the main node, and data rollback of all nodes is carried out through backup data, so that rapid data rollback is realized, and the database is prevented from falling into a long-time unavailable state.
In some embodiments, after performing data recovery on the replaced original master node, original slave node, and original hidden node based on the external backup data, the method may further include: and if the data recovery result is determined to be the data recovery success, deleting the backup node after the set time. The setting time may be preset according to actual conditions, for example, the setting time may be two days. When the data recovery result is that the data recovery is successful, the backup node can be deleted after the set time, and the resource of the backup node is released, so as to save the storage resource.
Fig. 2 is a schematic flow chart of another data rollback method provided in the embodiment of the present disclosure, and the embodiment further optimizes the data rollback method based on the above-described embodiment. As shown in fig. 2, the method includes:
The target node is an original main node, an original slave node or an original hidden node.
And step 203, adding a blank node, and replacing the target node with the blank node.
And 204, performing data recovery on the replaced original main node, original slave node and original hidden node based on the external backup data.
And step 207, switching the predetermined backup node to be the current master node, and switching the original master node in the stock nodes to be the current slave node.
The backup node is an original main node, an original slave node or an original hidden node.
And step 208, rolling back data of the stock nodes comprising the current slave node based on the backup data in the current master node.
The stock nodes comprise a current slave node, an original slave node and an original hidden node, and one of the stock nodes is replaced by a blank node.
Performing data rollback on inventory nodes including the current slave node based on backup data in the current master node may include: and synchronizing the backup data in the current main node to the current slave node, the original slave node and the original hidden node through a data consistency protocol.
And step 209, deleting the backup node after the set time.
In the embodiment of the present disclosure, the montgodb database is taken as an example for explanation, and specifically, a configuration management function of the montgodb can be used to complete node management on a montgodb layer; using a database platform to carry the relation of container nodes of the database service; and through the backup function of the MongoDB, the synchronization between the newly added blank nodes and the stock nodes is realized.
In the scheme, the database is backed up and restored by adding the blank nodes, and the conventional method for restoring all the node data is replaced by adopting a node replacement mode, so that the data on the old nodes can be quickly started for quick rollback when the data restoration encounters an error. Compared with the existing scheme of restoring through external backup data: the scheme is shorter in time consumption, because the backup time is longer along with the increase of data, and can even exceed 24 hours in extreme cases; the scheme is faster in rollback, when data recovery has errors, the data can be recovered by directly using the removed old node as a new main node without performing a backup recovery process, and therefore the user unavailability time is greatly reduced.
The data rollback scheme provided by the embodiment of the present disclosure acquires a data recovery request, determines a target node as a backup node, adds a blank node, and replaces the target node with the blank node, acquires a data rollback request, switches the backup node to a current master node, and switches an original master node in stock nodes to a current slave node if it is detected that a data recovery result is a data recovery failure, and performs data rollback on the stock nodes including the current slave node based on backup data in the current master node; and if the data recovery result is detected to be that the data recovery is successful, deleting the backup node after the set time. By adopting the technical scheme, one original node can be used as a backup node, when data rollback is needed, the role of the backup node is switched to the main node, and the data rollback of all nodes is carried out through the backup data, so that the rapid data rollback is realized, and the database is prevented from being in a long-time unavailable state.
Fig. 3 is a schematic structural diagram of a data rollback apparatus provided in an embodiment of the present disclosure, where the apparatus may be implemented by software and/or hardware, and may be generally integrated in an electronic device. As shown in fig. 3, the apparatus includes:
a request obtaining module 301, configured to obtain a data rollback request;
a switching module 302, configured to switch a predetermined backup node to a current master node, and switch an original master node in the stock nodes to a current slave node;
a data rollback module 303, configured to perform data rollback on the stock nodes including the current slave node based on the backup data in the current master node.
According to the data rollback scheme provided by the embodiment of the disclosure, a data rollback request is acquired; switching the backup node into a current main node, and switching an original main node in the stock nodes into a current slave node; and rolling back the data of the stock nodes comprising the current slave node based on the backup data in the current master node. By adopting the technical scheme, one original node can be used as a backup node, when data rollback is needed, the role of the backup node is switched to the main node, and data rollback of all nodes is carried out through backup data, so that rapid data rollback is realized, and the database is prevented from falling into a long-time unavailable state.
Optionally, the apparatus further includes a data recovery module, specifically configured to: before acquiring the data rollback request, the method further comprises the following steps:
acquiring a data recovery request;
adding a blank node, and replacing a target node with the blank node, wherein the target node is an original main node, an original slave node or an original hidden node;
and performing data recovery on the replaced original main node, the original slave node and the original hidden node based on external backup data.
Optionally, the stock nodes include the current slave node, the original slave node and the original hidden node, and one of the stock nodes is replaced by the blank node.
Optionally, the data rollback module 303 is specifically configured to:
synchronizing backup data in the current master node to the current slave node, the original slave node, and the original hidden node through a consistency protocol.
Optionally, the data recovery module is further configured to: adding blank nodes and replacing the blank nodes with the target nodes,
and determining the target node as a backup node.
Optionally, the apparatus further includes a backup deletion module, specifically configured to: after the replaced original main node, the original slave node and the original hidden node are subjected to data recovery based on external backup data,
and if the data recovery result is determined to be the data recovery success, deleting the backup node after the set time.
Optionally, the request obtaining module 301 is specifically configured to:
and if the data recovery result is detected to be data recovery failure, determining to acquire a data rollback request.
The data rollback device provided by the embodiment of the disclosure can execute the data rollback method provided by any embodiment of the disclosure, and has corresponding functional modules and beneficial effects of the execution method.
Fig. 4 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure. As shown in fig. 4, the electronic device 400 includes one or more processors 401 and memory 402.
The processor 401 may be a Central Processing Unit (CPU) or other form of processing unit having data processing capabilities and/or instruction execution capabilities and may control other components in the electronic device 400 to perform desired functions.
In one example, the electronic device 400 may further include: an input device 403 and an output device 404, which are interconnected by a bus system and/or other form of connection mechanism (not shown).
The input device 403 may also include, for example, a keyboard, a mouse, and the like.
The output device 404 may output various information to the outside, including the determined distance information, direction information, and the like. The output devices 404 may include, for example, a display, speakers, a printer, and a communication network and its connected remote output devices, among others.
Of course, for simplicity, only some of the components of the electronic device 400 relevant to the present disclosure are shown in fig. 4, omitting components such as buses, input/output interfaces, and the like. In addition, electronic device 400 may include any other suitable components depending on the particular application.
In addition to the above-described methods and apparatus, embodiments of the present disclosure may also be a computer program product comprising computer program instructions that, when executed by a processor, cause the processor to perform a data rollback method provided by embodiments of the present disclosure.
The computer program product may write program code for carrying out operations for embodiments of the present disclosure in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server.
Furthermore, embodiments of the present disclosure may also be a computer-readable storage medium having stored thereon a computer program, which, when executed by a processor, causes the processor to perform the data rollback method provided by embodiments of the present disclosure.
The computer-readable storage medium may take any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may include, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element.
The previous description is only for the purpose of describing particular embodiments of the present disclosure, so as to enable those skilled in the art to understand or implement the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A method of data rollback, comprising:
acquiring a data rollback request;
switching a predetermined backup node into a current master node, and switching an original master node in the stock nodes into a current slave node;
and performing data rollback on the inventory nodes including the current slave node based on the backup data in the current master node.
2. The method of claim 1, wherein prior to obtaining the data rollback request, further comprising:
acquiring a data recovery request;
adding a blank node, and replacing a target node with the blank node, wherein the target node is an original main node, an original slave node or an original hidden node;
and performing data recovery on the replaced original main node, the original slave node and the original hidden node based on external backup data.
3. The method of claim 2 wherein said stock nodes include said current slave node, said original slave node and said original hidden node, one of said stock nodes being replaced by said blank node.
4. The method of claim 3, wherein performing a data rollback for the inventory nodes including the current slave node based on backup data in the current master node comprises:
synchronizing backup data in the current master node to the current slave node, the original slave node, and the original hidden node via a coherence protocol.
5. The method of claim 2, wherein adding a blank node and replacing the target node with the blank node is preceded by:
and determining the target node as a backup node.
6. The method of claim 5, wherein after performing data recovery on the replaced original master node, original slave node and original hidden node based on external backup data, the method further comprises:
and if the data recovery result is determined to be the data recovery success, deleting the backup node after the set time.
7. The method of claim 2, wherein obtaining the data rollback request comprises:
and if the data recovery result is detected to be data recovery failure, determining to acquire a data rollback request.
8. A data rollback apparatus, comprising:
the request acquisition module is used for acquiring a data rollback request;
the switching module is used for switching a predetermined backup node into a current master node and switching an original master node in the stock nodes into a current slave node;
and the data rollback module is used for performing data rollback on the stock nodes including the current slave node based on the backup data in the current master node.
9. An electronic device, characterized in that the electronic device comprises:
a processor;
a memory for storing the processor-executable instructions;
the processor is configured to read the executable instructions from the memory and execute the instructions to implement the data rollback method of any one of claims 1-7.
10. A computer-readable storage medium, characterized in that the storage medium stores a computer program for executing the data rollback method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110193457.9A CN114968656A (en) | 2021-02-20 | 2021-02-20 | Data rollback method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110193457.9A CN114968656A (en) | 2021-02-20 | 2021-02-20 | Data rollback method, device, equipment and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114968656A true CN114968656A (en) | 2022-08-30 |
Family
ID=82953914
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110193457.9A Pending CN114968656A (en) | 2021-02-20 | 2021-02-20 | Data rollback method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114968656A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116680256A (en) * | 2023-07-21 | 2023-09-01 | 腾讯科技（深圳）有限公司 | Database node upgrading method and device and computer equipment |
-
2021
- 2021-02-20 CN CN202110193457.9A patent/CN114968656A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116680256A (en) * | 2023-07-21 | 2023-09-01 | 腾讯科技（深圳）有限公司 | Database node upgrading method and device and computer equipment |
| CN116680256B (en) * | 2023-07-21 | 2024-01-09 | 腾讯科技（深圳）有限公司 | Database node upgrading method and device and computer equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200356448A1 (en) | Manifest-based snapshots in distributed computing environments | |
| US9235606B1 (en) | Simplified database/log backup and restore | |
| US20150213100A1 (en) | Data synchronization method and system | |
| US20190129976A1 (en) | Apparatus for controlling synchronization of metadata on network and method for the same | |
| US20130166505A1 (en) | Monitoring replication lag between geographically dispersed sites | |
| WO2017042890A1 (en) | Database system, server device, program, and information processing method | |
| JP6455898B2 (en) | Data replication method, primary data storage controller, apparatus, system, and program | |
| JP5665889B2 (en) | Method and apparatus for backing up subversion repository | |
| WO2023134519A1 (en) | Method and apparatus for synchronously updating metadata in distributed database | |
| US11381641B2 (en) | Granular entry self-healing | |
| US10078558B2 (en) | Database system control method and database system | |
| CN112261164B (en) | Logic clock synchronization method and device and central time service cluster | |
| CN114968656A (en) | Data rollback method, device, equipment and medium | |
| US10169441B2 (en) | Synchronous data replication in a content management system | |
| US20130138999A1 (en) | Computer-readable recording medium, data management method, and storage device | |
| JP6251965B2 (en) | Information system and database recovery method | |
| CN113297134B (en) | Data processing system, data processing method and device, and electronic device | |
| JP7007017B2 (en) | Storage systems, control methods, and programs | |
| CN111522688A (en) | Data backup method and device for distributed system | |
| CN113515574B (en) | Data synchronization method and device | |
| CN111142921A (en) | Software upgrading method and device | |
| JP5244440B2 (en) | Database replication method, database management system and program | |
| KR20130043823A (en) | Distributed storage system for maintaining data consistency based on log, and method for the same | |
| CN111756562B (en) | Cluster takeover method, system and related components | |
| CN116340425A (en) | Data management method, device, medium and computing equipment of MHA (mobile high-definition architecture) |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |