CN113157492A - Backup method, recovery method and backup system of distributed database - Google Patents
Backup method, recovery method and backup system of distributed database Download PDFInfo
- Publication number
- CN113157492A CN113157492A CN202110371639.0A CN202110371639A CN113157492A CN 113157492 A CN113157492 A CN 113157492A CN 202110371639 A CN202110371639 A CN 202110371639A CN 113157492 A CN113157492 A CN 113157492A
- Authority
- CN
- China
- Prior art keywords
- backup
- node
- module
- relationship
- nodes
- 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
- 238000011084 recovery Methods 0.000 title claims abstract description 69
- 238000000034 method Methods 0.000 title claims abstract description 46
- 230000008859 change Effects 0.000 claims abstract description 33
- 230000003247 decreasing effect Effects 0.000 claims description 5
- 230000000750 progressive effect Effects 0.000 claims description 5
- 238000012545 processing Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000008602 contraction Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Quality & Reliability (AREA)
- Computing Systems (AREA)
- Data Mining & Analysis (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a backup method, a recovery method and a backup system of a distributed database, wherein the backup method comprises the following steps: acquiring node information of a distributed database cluster; analyzing the node change condition according to the node information; if a new node is added, adding the new node in the backup relationship; if the nodes are reduced, deleting the reduced nodes in the backup relation; sending a backup request to a node according to the backup relation; and receiving the backup data returned by the node. During backup, the change condition of the current node is judged by analyzing the node information, the current backup relation is established, a backup request is sent to the corresponding node according to the backup relation so as to obtain backup data, and the backup relation and the backup data are generated.
Description
Technical Field
The invention relates to the technical field of distributed databases, in particular to a backup method, a recovery method and a backup system of a distributed database.
Background
The data in the distributed database are respectively stored in different local databases, run on different hosts and are connected through a communication network, and an application program can perform transparent operation on the distributed database. A distributed database is a unified whole logically, and is stored on different nodes physically, and an application program can access the database distributed at different geographic positions through network connection.
The distributed database usually performs data backup through an interface, backup data are mostly stored by taking a data node as a unit, and when the data of the distributed database are restored, corresponding backup data acquired from a backup system are required to be reversely restored to the data node of the distributed memory database according to a restoration condition and a restoration time point. But the distributed database has the function of elastic expansion and contraction, and nodes or processing capacity can be increased or decreased elastically. For the change of the nodes and the host thereof caused by elastic expansion, the existing backup system of the distributed database does not carry out synchronous adjustment. Manual intervention is needed, database backup and recovery configuration are adjusted according to the change condition of the adjusted host or distributed data nodes, and backup processing or recovery processing is carried out again. Whole adjustment process needs artifical the intervention, and the operation is too much and comparatively complicated, and efficiency is lower, has increased the maloperation probability simultaneously, and data is lost easily.
Disclosure of Invention
Aiming at the technical problems in the prior art, the invention provides a backup method, a recovery method and a backup system of a distributed database, so as to adapt to node changes caused by elastic expansion of the distributed database and prevent data loss.
The invention discloses a backup method of a distributed database, which comprises the following steps: acquiring node information of a distributed database cluster; analyzing the node change condition according to the node information; if a new node is added, adding the new node in the backup relationship; if the nodes are reduced, deleting the reduced nodes in the backup relation; sending a backup request to a node according to the backup relation; and receiving the backup data returned by the node.
Preferably, the method for generating backup data by the node includes:
setting a time stamp for the backup relation and the backup data, wherein the backup request comprises the time stamp of the last backup; the node returns the backup data generated between the timestamp and the backup request time.
Preferably, the backup method of the present invention further includes a data backup method of node change:
the node information comprises node change time, and the backup request comprises a timestamp of the last backup and the node change time;
the node returns the backup data generated between the timestamp and the node change time.
The invention also provides a method for recovering the backup data, which comprises the following steps:
step 401: acquiring node information of a distributed database cluster;
step 402: analyzing the node change condition according to the node information;
if a new node is added, go to step 404: according to the relation to be backed up, sending the backup data to be restored to the corresponding node for restoration;
if the number of nodes is decreased, go to step 405: deleting the reduced nodes in the backup relationship to obtain a second backup relationship, and executing step 407;
step 407: and redistributing the backup data to be restored to the nodes of the second backup relationship.
Preferably, if a new node and a reduced node are added at the same time, step 408 is executed: deleting the reduced nodes in the backup relation, obtaining a second backup relation, and sending the backup data to be restored to the corresponding nodes for restoration according to the second backup relation;
step 409: and adding a new node in the second backup relationship, obtaining a third backup relationship, and redistributing the backup data of the reduced node into the new node or the node of the third backup relationship.
Preferably, the recovery method of the present invention further includes a step-by-step recovery method: according to the recovery request, acquiring a request time point and a backup before the request time point; and sequentially restoring the backups according to the sequence of the backup time.
The invention also provides a backup system for realizing the backup method, which comprises an acquisition module, a backup analysis module, a backup relation module and a backup module;
the acquisition module is used for acquiring node information of the distributed database cluster;
the backup analysis module analyzes the node change condition according to the node information; if a new node is added, the new node is added in the backup relationship through the backup relationship module; if the nodes are reduced, deleting the reduced nodes in the backup relationship through the backup relationship module;
and the backup module is used for sending a backup request to the node according to the backup relation and receiving backup data returned by the node.
Preferably, the backup system further comprises a recovery analysis module, a first recovery module, a second recovery module and a reallocation module, wherein the acquisition module acquires node information of the distributed database cluster when receiving a backup recovery request; the recovery analysis module is used for analyzing the node change condition according to the node information; when a new node is added, the first recovery module sends the backup data to be recovered to the corresponding node for recovery according to the corresponding backup relation of the backup data to be recovered; when the nodes are reduced, the second recovery module deletes the reduced nodes in the backup relationship to obtain a second backup relationship; the reallocation module is used for reallocating the backup data to be restored to the nodes of the second backup relation.
Preferably, the backup system further comprises a third restore module,
when a new node and a reduced node are added at the same time, deleting the reduced node in the backup relationship through a third recovery module to obtain a second backup relationship, and sending the backup data to be recovered to the corresponding node for recovery according to the second backup relationship;
adding a new node in the second backup relationship to obtain a third backup relationship;
and redistributing the backup data of the reduced nodes into the new node or the nodes of the third backup relationship through a redistributing module.
Preferably, the backup system further comprises a progressive restoration module,
the step-by-step recovery module is used for acquiring the recovery request time and the backup before the request time point, and sequentially sending the backup, the recovery request time and the node information to the recovery analysis module according to the sequence of the backup time.
Compared with the prior art, the invention has the beneficial effects that: during backup, the change condition of the current node is judged by analyzing the node information, the current backup relation is established, a backup request is sent to the corresponding node according to the backup relation so as to obtain backup data, and the backup relation and the backup data are generated.
Drawings
FIG. 1 is a flow chart of a distributed database backup method of the present invention;
FIG. 2 is a flow chart of a distributed database recovery method of the present invention;
FIG. 3 is a logical block diagram of the backup system of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be obtained by a person skilled in the art without any inventive step based on the embodiments of the present invention, are within the scope of the present invention.
The invention is described in further detail below with reference to the attached drawing figures:
a backup method of a distributed database, as shown in fig. 1, the backup method includes:
step 101: and acquiring node information of the distributed database cluster. Node information may be obtained from a distributed database management system, and may include node name, host name, node IP, port.
Step 102: and analyzing the node change condition according to the node information. The node information which is backed up last time can be compared and judged with the current node information.
If a new node is added, go to step 103: a backup relationship is established with the new node, i.e. the new node is added in the backup relationship, step 105 is executed.
If the number of nodes is decreased, go to step 104: the backup relationship of the reduced node is deleted, i.e. the reduced node is deleted in the backup relationship, step 105 is performed. In the elastic scaling mechanism, the data migration of the nodes to the reserved nodes is reduced, so that the data loss is avoided.
If the node remains unchanged, go to step 105.
If a new node and a reduced node are added at the same time, the new node is added in the backup relationship, and the reduced node is deleted at the same time, and step 105 is executed.
Step 105: and sending a backup request to the node according to the backup relation.
Step 106: and receiving the backup data returned by the node. And after backup, generating a backup relation and backup data, wherein the backup relation is used for describing the relation between the backup data and the nodes. Backup data may include, but is not limited to, redo logs and archive logs. The distributed database may be a distributed in-memory database.
During backup, the change condition of the current node is judged by analyzing the node information, the current backup relation is established, a backup request is sent to the corresponding node according to the backup relation so as to obtain backup data, and the backup relation and the backup data are generated.
The method for generating the backup data by the node comprises the following steps:
step 201: and setting a time stamp for the backup relation and the backup data, wherein the backup request comprises the time stamp of the last backup. The last backup refers to the backup with the backup time earlier than the current time and the backup time closest to the current time or the backup request time.
Step 201: the node returns the backup data generated between the timestamp and the backup request time.
Through time-phased backup, the data volume of each backup is reduced, and repeated backup of data is avoided.
The backup method of the present invention may further include a data backup method of node change:
step 301: the node information comprises node change time, and the backup request comprises a timestamp of the last backup and the node change time.
Step 302: the node returns the backup data generated between the timestamp and the node change time.
And the change time of the nodes is backed up, so that the data loss in the elastic expansion is avoided.
The present invention further provides a recovery method of a distributed database, as shown in fig. 2, the recovery method includes:
step 401: and acquiring node information of the distributed database cluster.
Step 402: and analyzing the node change condition according to the node information.
If a new node is added, go to step 404: and sending the backup data to be restored to the corresponding node for restoration according to the corresponding backup relationship of the backup data to be restored, namely restoring the backup data according to the backup relationship.
If the number of nodes is decreased, go to step 405: the reduced nodes are deleted in the backup relationship to obtain a second backup relationship, and step 407 is executed. It should be noted that the second backup relationship after the deletion of the reduced node should not overwrite the original backup relationship.
Step 407: and redistributing the backup data into the nodes of the two backup relations. But not limited to this, according to the second backup relationship, the backup data to be restored may also be sent to the corresponding node for restoration, and the backup data of the reduced node is redistributed to the nodes of the second backup relationship, so as to reduce the calculation amount of redistribution.
If the new node and the reduced node are added at the same time, go to step 408: and deleting the backup relation of the reduced nodes, obtaining a second backup relation, and sending the backup data to be restored to the corresponding nodes for restoration according to the second backup relation. Step 409: adding a new node in the second backup relationship to obtain a third backup relationship; and redistributing the backup data of the reduced nodes into the new node or the nodes of the third backup relation. But not limited to, the reduced nodes and new nodes may be deleted and added in the backup relationship to obtain a third backup relationship, and then the backup data to be restored is redistributed to the third backup relationship.
When the distributed database cluster is elastically stretched, data recovery is carried out according to the corresponding backup relation, data loss in the recovery process is prevented, manual intervention is avoided, and data recovery efficiency is improved.
The recovery method of the present invention may further include a step-by-step recovery method: acquiring a request time point and backups before the request time point according to the recovery request; and sequentially restoring the backups according to the sequence of the backup time. The method of progressive restoration corresponds to the method of generating backup data by the node, i.e. each backup contains backup data of backup time and last backup time.
The present invention further provides a system for implementing the above backup method, as shown in fig. 3, including an obtaining module 1, a backup analyzing module 2, a backup relation module 3, and a backup module 4; the acquisition module 1 is configured to acquire node information of the distributed database cluster 31; the backup analysis module 2 analyzes the change condition of the node 32 according to the node information; if a new node is added, the new node is added in the backup relationship through the backup relationship module 3; if the nodes are reduced, deleting the reduced nodes in the backup relationship through the backup relationship module 3; the backup module 4 is configured to send a backup request to a node according to the backup relationship, and receive backup data returned by the node.
The backup system of the invention also comprises a recovery analysis module 11, a first recovery module 12, a second recovery module 13 and a redistribution module 14, wherein the acquisition module 1 acquires the node information of the distributed database cluster 31 when receiving a backup recovery request; the recovery analysis module 11 is configured to analyze a change condition of the node 32 according to the node information; when a new node is added, the first recovery module 12 sends the backup data to be recovered to the corresponding node for recovery according to the corresponding backup relationship of the backup data to be recovered; when the nodes are reduced, the second recovery module 13 deletes the reduced nodes in the backup relationship to obtain a second backup relationship; the reallocation module 14 is configured to reallocate the backup data to be restored to the node in the second backup relationship.
When a new node and a reduced node are added at the same time, the reduced node is deleted in the backup relationship through the third recovery module 15 to obtain a second backup relationship, and the backup data to be recovered is sent to the corresponding node for recovery according to the second backup relationship; adding a new node in the second backup relationship to obtain a third backup relationship; the backup data of the reduced node is redistributed by the redistribution module 14 to the new node or the node of the third backup relationship.
The system of the present invention may further include a progressive recovery module 21, where the progressive recovery module 21 is configured to obtain the request recovery time and the backup before the request time, and sequentially send the backup, the recovery request time, and the node information to the recovery analysis module 11 according to the sequence of the backup time. The backup comprises a backup relation and backup data, and the sequence of the backup time refers to the sequence of time, namely, the backup generated firstly, the backup recovered firstly, the backup generated secondly and the backup recovered secondly.
Examples
First, data backup after node change of distributed database
Take a three-host three-node (one node per host) distributed memory database cluster a as an example.
1. The backup system B starts and points to the cluster A, acquires the service address (192.168.1.100) and the port (10000) of the cluster A from the distributed database client, and establishes connection with the cluster A.
2. The backup system B sends a request to the service port of the cluster A, and the cluster A returns the current node information as shown in the following table:
| serial number | Host name | Host address | Node | Backup port | |
| 1 | H01 | 192.168.1.101 | db01 | 10001 | |
| 2 | H02 | 192.168.1.102 | db02 | 10002 | |
| 3 | H03 | 192.168.1.103 | db03 | 10003 |
3. The backup system B respectively establishes connection with the backup port of each data node, the backup system B sends a request backup request to each node in parallel, the node sends the filing log and the redo log which are not backed up locally to the backup system B in real time after receiving the backup request, and the backup system B backs up the file in a local backup file after successfully receiving the file. Wherein the backup files are separated by data nodes and identified.
4. The cluster a needs to improve the processing performance, and the number of hosts is extended to 5, and the number of nodes is extended to 5, and still one data node is provided for each host. And the cluster A synchronously records the data node expansion time and the expanded data node information.
| Serial number | Host name | Host address | Node | Backup port | |
| 1 | H01 | 192.168.1.101 | db01 | 10001 | |
| 2 | H02 | 192.168.1.102 | db02 | 10002 | |
| 3 | H03 | 192.168.1.103 | db03 | 10003 | |
| 4 | H04 | 192.168.1.104 | db04 | 10004 | |
| 5 | H05 | 192.168.1.105 | db05 | 10005 |
5. Before requesting backup data, the backup system B acquires the current host and node information from the service port of the distributed memory database, and finds out that 2 nodes are newly added. And the backup system B continuously requests backup data from the original 3 data nodes, establishes connection with the backup port of the newly added node, sends a request for the backup data to acquire the backup data, and stores the backup data and the backup relation.
6. Cluster a needs to release one host, reduce the number of hosts to 4, delete the 5 th node, and change the number of data nodes to 4. And the cluster A synchronously records the data node expansion time and the expanded data node information.
| Serial number | Host name | Host address | Node | Backup port | |
| 1 | H01 | 192.168.1.101 | db01 | 10001 | |
| 2 | H02 | 192.168.1.102 | db02 | 10002 | |
| 3 | H03 | 192.168.1.103 | db03 | 10003 | |
| 4 | H04 | 192.168.1.104 | db04 | 10004 |
7. When the backup system B requests the backup again, one less node is found. And the backup system B continuously sends backup requests to the 4 nodes which are still reserved, and simultaneously sends a request for backup data to the deleted data node (but no data is returned), and the backup system B deletes the backup connection with the 5 th node in the backup relation and does not send the backup requests any more. The backup for the 5 th node is still saved in backup system B.
Secondly, recovering distributed memory database data
And (3) recovery purpose: and restoring the data of the distributed database to the state of the time point T1.
1. The current distributed memory database is reduced, the node db03 is deleted, and 2 nodes are reserved: db01, db 02.
2. The data recovery function of the backup system is initiated specifying the cluster that needs to be recovered and the point in time of recovery T1. According to the time point T1, the backup system finds that there are 3 data nodes at T1: db01, db02, and db 03.
3. The backup system acquires the latest archive log of the 3 data nodes before T1, and the backup generation time is T2. The archive log and the redo log backed up by the recovery T2 are redistributed to 2 nodes, and are recovered to the time of T2 by utilizing the archive log and the redo log.
4. The backup system acquires all redo logs generated by the 3 data nodes within the time T2 and the time T1 and redistributes the redo logs to the 2 nodes, and the T2 restores the 2 data nodes to the time T1 according to the redo logs.
The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes will occur to 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 (10)
1. A backup method of a distributed database, the backup method comprising:
acquiring node information of a distributed database cluster;
analyzing the node change condition according to the node information;
if a new node is added, adding the new node in the backup relationship;
if the nodes are reduced, deleting the reduced nodes in the backup relation;
sending a backup request to a node according to the backup relation;
and receiving the backup data returned by the node.
2. The backup method according to claim 1, wherein the method for the node to generate backup data comprises:
setting a time stamp for the backup relation and the backup data, wherein the backup request comprises the time stamp of the last backup;
the node returns the backup data generated between the timestamp and the backup request time.
3. The backup method of claim 2, further comprising a data backup method of node change:
the node information comprises node change time, and the backup request comprises a timestamp of the last backup and the node change time;
the node returns the backup data generated between the timestamp and the node change time.
4. A recovery method for a distributed database, the recovery method comprising:
step 401: acquiring node information of a distributed database cluster;
step 402: analyzing the node change condition according to the node information;
if a new node is added, go to step 404: according to the backup relation, sending the backup data to be restored to the corresponding node for restoration;
if the number of nodes is decreased, go to step 405: deleting the reduced nodes in the backup relationship to obtain a second backup relationship, and executing step 407;
step 407: and redistributing the backup data to be restored to the nodes of the second backup relationship.
5. The recovery method according to claim 4, wherein if the new node and the reduced node are added at the same time, step 408 is executed: deleting the reduced nodes in the backup relation, obtaining a second backup relation, and sending the backup data to be restored to the corresponding nodes for restoration according to the second backup relation;
step 409: and adding a new node in the second backup relationship, obtaining a third backup relationship, and redistributing the backup data of the reduced node into the new node or the node of the third backup relationship.
6. The recovery method of claim 4, further comprising a step-by-step recovery method:
according to the recovery request, acquiring a request time point and a backup before the request time point;
and sequentially restoring the backups according to the sequence of the backup time.
7. A backup system for implementing the backup method according to any one of claims 1 to 3, comprising an acquisition module, a backup resolution module, a backup relationship module and a backup module;
the acquisition module is used for acquiring node information of the distributed database cluster;
the backup analysis module analyzes the node change condition according to the node information; if a new node is added, the new node is added in the backup relationship through the backup relationship module; if the nodes are reduced, deleting the reduced nodes in the backup relationship through the backup relationship module;
and the backup module is used for sending a backup request to the node according to the backup relation and receiving backup data returned by the node.
8. The backup system of claim 7, further comprising a restore resolution module, a first restore module, a second restore module, and a reallocation module,
the acquisition module acquires node information of the distributed database cluster when receiving a backup recovery request;
the recovery analysis module is used for analyzing the node change condition according to the node information;
when a new node is added, the first recovery module sends the backup data to be recovered to the corresponding node for recovery according to the corresponding backup relation of the backup data to be recovered;
when the nodes are reduced, the second recovery module deletes the reduced nodes in the backup relationship to obtain a second backup relationship;
the reallocation module is used for reallocating the backup data to be restored to the nodes of the second backup relation.
9. The backup system of claim 8, further comprising a third restore module,
when a new node and a reduced node are added at the same time, deleting the reduced node in the backup relationship through a third recovery module to obtain a second backup relationship, and sending the backup data to be recovered to the corresponding node for recovery according to the second backup relationship;
adding a new node in the second backup relationship to obtain a third backup relationship;
and redistributing the backup data of the reduced nodes into the new node or the nodes of the third backup relationship through a redistributing module.
10. The backup system of claim 8, further comprising a progressive restore module,
the step-by-step recovery module is used for acquiring the recovery request time and the backup before the request time, and sequentially sending the backup, the recovery request time and the node information to the recovery analysis module according to the sequence of the backup time.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110371639.0A CN113157492A (en) | 2021-04-07 | 2021-04-07 | Backup method, recovery method and backup system of distributed database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110371639.0A CN113157492A (en) | 2021-04-07 | 2021-04-07 | Backup method, recovery method and backup system of distributed database |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113157492A true CN113157492A (en) | 2021-07-23 |
Family
ID=76888528
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110371639.0A Pending CN113157492A (en) | 2021-04-07 | 2021-04-07 | Backup method, recovery method and backup system of distributed database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113157492A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1567237A (en) * | 2003-06-09 | 2005-01-19 | 浪潮电子信息产业股份有限公司 | Method for constructing high-available distributed memory system |
| CN102693324A (en) * | 2012-01-09 | 2012-09-26 | 西安电子科技大学 | Distributed database synchronization system, synchronization method and node management method |
| CN105009513A (en) * | 2013-12-03 | 2015-10-28 | 华为技术有限公司 | Method for updating node device in distributed system, node device and distributed system |
| US20180300206A1 (en) * | 2017-04-17 | 2018-10-18 | EMC IP Holding Company LLC | Method and system for data backup and restoration in cluster system |
| CN108984341A (en) * | 2018-06-16 | 2018-12-11 | 温州职业技术学院 | A kind of data reconstruction method and system based on distributed memory system |
| US20210026740A1 (en) * | 2018-09-30 | 2021-01-28 | Tencent Technology (Shenzhen) Company Ltd | Data backup method, storage medium, and computing device |
-
2021
- 2021-04-07 CN CN202110371639.0A patent/CN113157492A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1567237A (en) * | 2003-06-09 | 2005-01-19 | 浪潮电子信息产业股份有限公司 | Method for constructing high-available distributed memory system |
| CN102693324A (en) * | 2012-01-09 | 2012-09-26 | 西安电子科技大学 | Distributed database synchronization system, synchronization method and node management method |
| CN105009513A (en) * | 2013-12-03 | 2015-10-28 | 华为技术有限公司 | Method for updating node device in distributed system, node device and distributed system |
| US20180300206A1 (en) * | 2017-04-17 | 2018-10-18 | EMC IP Holding Company LLC | Method and system for data backup and restoration in cluster system |
| CN108984341A (en) * | 2018-06-16 | 2018-12-11 | 温州职业技术学院 | A kind of data reconstruction method and system based on distributed memory system |
| US20210026740A1 (en) * | 2018-09-30 | 2021-01-28 | Tencent Technology (Shenzhen) Company Ltd | Data backup method, storage medium, and computing device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11468015B2 (en) | Storage and synchronization of metadata in a distributed storage system | |
| CN106610876B (en) | Data snapshot recovery method and device | |
| US20210004181A1 (en) | Global de-duplication of virtual disks in a storage platform | |
| US9767177B1 (en) | System and method for optimizing data recovery in a parallel database | |
| EP1277113B1 (en) | Method and apparatus utilizing application dependency information in performing a backup service in a computer system | |
| US11593332B1 (en) | Destination file copying and error handling | |
| CN111444043A (en) | Data backup method, device, node, system and medium | |
| CN113064760B (en) | Database synthesis backup method and device, computer equipment and storage medium | |
| CN102184218B (en) | Repeated data delete method based on causal relationship | |
| CN111581017A (en) | Backup and recovery system and method for modern application | |
| CN109753381B (en) | Continuous data protection method based on object storage | |
| US11243925B2 (en) | Verification microservice for deployment of controller and worker nodes for verification paths | |
| CN113157492A (en) | Backup method, recovery method and backup system of distributed database | |
| CN110457163B (en) | Data recovery method and device for distributed block storage and storage medium | |
| US11593218B1 (en) | Source file copying and error handling | |
| US12038947B2 (en) | Destination file copying | |
| CN112346907B (en) | Data backup recovery method and system based on heterogeneous object storage | |
| CN108429813B (en) | Disaster recovery method, system and terminal for cloud storage service | |
| CN112364105A (en) | Collection file management method and system based on Redis | |
| CN112650628A (en) | High-availability and expandable data deduplication method | |
| CN112035296A (en) | Backup method for minimum change of incremental backup | |
| CN104580498A (en) | Self-adaptive cloud management platform | |
| CN110413449B (en) | Metadata backup and recovery method based on file storage system | |
| US20230109105A1 (en) | Source file copying | |
| CN115858238A (en) | Method and related device for recovering database cluster |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210723 |