CN111444043A - Data backup method, device, node, system and medium - Google Patents
Data backup method, device, node, system and medium Download PDFInfo
- Publication number
- CN111444043A CN111444043A CN202010231310.XA CN202010231310A CN111444043A CN 111444043 A CN111444043 A CN 111444043A CN 202010231310 A CN202010231310 A CN 202010231310A CN 111444043 A CN111444043 A CN 111444043A
- Authority
- CN
- China
- Prior art keywords
- edge
- data
- computing node
- edge computing
- block
- 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
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000004590 computer program Methods 0.000 claims description 12
- 238000004364 calculation method Methods 0.000 claims description 10
- 230000004048 modification Effects 0.000 claims description 6
- 238000012986 modification Methods 0.000 claims description 6
- 238000004422 calculation algorithm Methods 0.000 claims description 4
- 230000001419 dependent effect Effects 0.000 claims description 2
- 238000011084 recovery Methods 0.000 abstract description 20
- 230000008569 process Effects 0.000 description 8
- 238000010586 diagram Methods 0.000 description 7
- 230000009471 action Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 101100018928 Drosophila melanogaster InR gene Proteins 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- MKXZASYAUGDDCJ-NJAFHUGGSA-N dextromethorphan Chemical compound C([C@@H]12)CCC[C@]11CCN(C)[C@H]2CC2=CC=C(OC)C=C21 MKXZASYAUGDDCJ-NJAFHUGGSA-N 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000012546 transfer Methods 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/1458—Management of the backup or restore process
- G06F11/1464—Management of the backup or restore process for networked environments
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention discloses a data backup method, a data backup device, a data backup node, a data backup system and a data backup medium. The data backup method applied to the edge computing node comprises the following steps: acquiring data to be backed up; splitting data to be backed up to obtain at least one block of data; storing at least one block of data in an edge device corresponding to an edge computing node; and sending at least one block data to at least one other edge computing node adjacent to the edge computing node for the at least one other edge computing node to store the at least one block data in an edge device corresponding to the at least one other edge computing node. According to the data backup method, device, node, system and medium provided by the embodiment of the invention, the data is backed up to the edge equipment corresponding to other edge computing nodes, but not to the shared cloud or the private cloud, so that the backup speed of edge computing and the disaster recovery efficiency can be improved.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a data backup method, apparatus, node, system, and medium.
Background
Disaster recovery backup is to establish and maintain a backup storage system, and separate data backup to ensure the capability of data to resist disastrous events.
At present, a common disaster recovery backup method is cloud backup. The cloud backup refers to that data is stored on a public cloud or a private cloud in a cloud storage mode.
For edge computing, disaster recovery can be performed though cloud backup. However, the backup is slow and the disaster recovery efficiency is low due to the limitation of network bandwidth.
Disclosure of Invention
Embodiments of the present invention provide a data backup method, apparatus, node, system, and medium, which can improve backup speed of edge calculation and disaster recovery efficiency.
In a first aspect, an embodiment of the present invention provides a data backup method applied to an edge computing node, where the method includes:
acquiring data to be backed up;
splitting data to be backed up to obtain at least one block of data;
storing at least one block of data in an edge device corresponding to an edge computing node;
and sending at least one block data to at least one other edge computing node adjacent to the edge computing node for the at least one other edge computing node to store the at least one block data in an edge device corresponding to the at least one other edge computing node.
In a second aspect, an embodiment of the present invention provides a data backup apparatus applied to an edge computing node, including:
the acquisition module is used for acquiring data to be backed up;
the splitting module is used for splitting the data to be backed up to obtain at least one block of data;
the storage module is used for storing at least one piece of block data in the edge equipment corresponding to the edge computing node;
the sending module is used for sending at least one piece of block data to at least one other edge computing node adjacent to the edge computing node, so that the at least one piece of block data is stored in the edge device corresponding to the at least one other edge computing node by the at least one other edge computing node.
In a third aspect, an embodiment of the present invention provides an edge computing node, including: a memory, a processor, and a computer program stored on the memory and executable on the processor;
the processor implements the data backup method provided by the first aspect of the embodiment of the present invention when executing the computer program.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements the data backup method provided in the first aspect of the embodiment of the present invention.
In a fifth aspect, an embodiment of the present invention provides a data backup system, including at least one edge computing node provided in the third aspect of the embodiment of the present invention and a dependent edge computing node corresponding to each edge computing node;
and the subordinate edge computing node is used for backing up the edge computing node corresponding to the subordinate edge computing node.
According to the data backup method, the data backup device, the data backup nodes, the data backup system and the data backup media, data are backed up to the edge devices corresponding to other edge computing nodes, and are not backed up to the common cloud or the private cloud, so that the backup speed of edge computing can be increased; in addition, when disaster recovery is performed, backup data can be acquired from edge devices corresponding to other edge computing nodes, and disaster recovery efficiency can be improved without the need of a shared cloud or a private cloud.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments of the present invention will be briefly described below, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic flowchart of a data backup method applied to an edge computing node according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a data backup apparatus applied to an edge computing node according to an embodiment of the present invention;
FIG. 3 is a schematic structural diagram of a computing device according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a data backup system according to an embodiment of the present invention.
Detailed Description
Features and exemplary embodiments of various aspects of the present invention will be described in detail below, and in order to make objects, technical solutions and advantages of the present invention more apparent, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not to be construed as limiting the invention. It will be apparent to one skilled in the art that the present invention may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present invention by illustrating examples of the present invention.
It is noted that, herein, 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 … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Edge computing refers to an open platform integrating network, computing, storage and application core capabilities at one side close to an object or a data source to provide nearest-end services nearby. The application program is initiated at the edge side, so that a faster network service response is generated, and the basic requirements of the industry in the aspects of real-time business, application intelligence, safety, privacy protection and the like are met.
For edge computing, disaster recovery can be performed though cloud backup. However, the backup is slow and the disaster recovery efficiency is low due to the limitation of network bandwidth. For example, when one edge computing node performs data backup or disaster recovery, other edge computing nodes perform data backup or disaster recovery, and at this time, the data backup or disaster recovery is limited by network bandwidth, the backup speed is slow, the disaster recovery speed is also slow, and the disaster recovery efficiency is low.
Based on this, embodiments of the present invention provide a data backup method, apparatus, node, system, and medium. First, a data backup method provided by an embodiment of the present invention is described in detail below.
Fig. 1 is a schematic flowchart of a data backup method applied to an edge computing node according to an embodiment of the present invention. The data backup method applied to the edge computing node can comprise the following steps:
s101: and acquiring data to be backed up.
S102: and splitting the data to be backed up to obtain at least one block of data.
S103: and storing at least one block of data in the edge device corresponding to the edge computing node.
S104: and sending at least one block data to at least one other edge computing node adjacent to the edge computing node for the at least one other edge computing node to store the at least one block data in an edge device corresponding to the at least one other edge computing node.
For example, assume that the backup data is split into two block data, block data 1 and block data 2, respectively. The current edge compute node is edge compute node 1.
First, the edge computing node 1 stores block data 1 and block data 2 in the edge device corresponding to the edge computing node 1. For example, block data 1 is stored in the edge device 1 corresponding to the edge computing node 1, and block data 2 is stored in the edge device 3 corresponding to the edge computing node 1.
The edge computing node 1 transmits block data 1 to the edge computing node 2 and the edge computing node 3 adjacent to the edge computing node 1, and transmits block data 2 to the edge computing node 2 and the edge computing node 4 adjacent to the edge computing node 1.
The edge computing node 2 stores block data 1 in the edge device corresponding to the edge computing node 2. For example, it is stored in the edge device 2 corresponding to the edge computing node 2.
The edge computing node 3 stores block data 1 in the edge device corresponding to the edge computing node 3. For example, in the edge device 2 corresponding to the edge computing node 3.
The edge computing node 2 stores the block data 2 in the edge device corresponding to the edge computing node 2. For example, in the edge device 4 corresponding to the edge computing node 2.
The edge computing node 4 stores the block data 2 in the edge device corresponding to the edge computing node 4. For example, in the edge device 5 corresponding to the edge computing node 4.
According to the data backup method provided by the embodiment of the invention, the data is backed up to the edge devices corresponding to other edge computing nodes, but not to the common cloud or the private cloud, so that the backup speed of the edge computing can be increased; in addition, when disaster recovery is performed, backup data can be acquired from edge devices corresponding to other edge computing nodes, backup data does not need to be acquired from a common cloud or a private cloud, and disaster recovery efficiency can be improved.
In some possible implementations of the embodiment of the present invention, the data to be backed up may be split according to the size of the preset data block to obtain at least one block data.
The disk block is typically 512 bytes, so the predetermined data block size may be an integral multiple of 512 bytes. If the block is too large, the data processing time on a single node may be too long, and if the block is too small, the addressing and communication overhead may be increased. Therefore, the data block size may be set to 32M.
For example, assume that the data to be backed up is 60M, and the preset data block size is 32M. The data to be backed up is split into two block data, one block data including the data of the first 32M (0-32M) of the data to be backed up, and the other block data including the data of the last 28M (32M-60M) of the data to be backed up.
It is understood that the size of the last block data may be less than the preset block size.
In some possible implementations of the embodiment of the present invention, to save the storage space, the block data may also be compressed to save the occupation of the storage space. In the embodiment of the invention, the bzip format is adopted to compress the block data.
In some possible implementations of the embodiment of the present invention, a globally unique identification information (such as a block data number) may be set for each block data, so as to distinguish the block data.
In some possible implementations of the embodiment of the present invention, the block data may be stored in the edge device corresponding to the edge computing node based on a load balancing algorithm.
For example, edge compute node 1 corresponds to 5 edge devices. The 5 edge devices are edge device 1, edge device 2, edge device 3, edge device 4 and edge device 5, respectively.
Edge device 1, edge device 2, edge device 3, and edge device 4 currently have block data stored.
When there is more block data to store, the block data may be stored in the edge device 5.
In some possible implementations of the embodiment of the present invention, other edge computing nodes may also be based on a load balancing algorithm when storing block data.
In some possible implementations of the embodiments of the present invention, the number of block data blocks may be set according to the requirements of a user. Of course, the number of block data blocks may also be fixed, such as 6. Excessive backups not only take up storage space, but also increase addressing overhead and maintenance costs.
In some possible implementations of embodiments of the invention, when block data in an edge device is not available, one block data may be copied from another edge device and stored in the edge device to ensure the number of block data.
In some possible implementations of the embodiment of the present invention, an edge computing node may receive storage information sent by other edge computing nodes, where the storage information includes identification information of an edge device that stores block data; generating a directory tree of the data to be backed up based on the identification information, wherein the directory tree is recorded with storage position information of the block data; the directory tree is stored.
Illustratively, assume a 60M video.data.cfg.bz2 file under path "mec:// controller: port/dir-a/dir-b/dir-c/".
The file is split into two blocks of data.
Block data 1, 0-32M, blk _ 10373825; where blk _10373825 is the global number of block data 1.
Block data 2, 32M-60M, blk _ 10373826; where blk _10373826 is the global number of block data 2.
The block data 1 is stored in the edge device 1 corresponding to the edge computing node (i.e., edge computing node 1), the edge device 2 corresponding to the edge computing node 2, and the edge device 2 corresponding to the edge computing node 3.
The block data 2 is stored in the edge device 3 corresponding to the edge computing node, the edge device 4 corresponding to the edge computing node 2, and the edge device 5 corresponding to the edge computing node 4.
The edge computing node 2 transmits identification information of the edge device 2 storing the block data 1 and identification information of the edge device 4 storing the block data 2 to the edge computing node 1.
The edge computing node 3 transmits identification information of the edge device 2 storing the block data 1 to the edge computing node 1.
The edge computing node 4 transmits identification information of the edge device 5 storing the block data 2 to the edge computing node 1.
After receiving the identification information of the edge device storing each block data sent by each edge computing node, the edge computing node 1 generates a directory tree of the data to be backed up. The directory tree is generated as follows:
mec://controller:port/dir-a/dir-b/dir-c/vidio.data.cfg.bz2
0-32M，blk_10373825[node1，platform_2-node2，platform_3-node2]
32M-60M，blk_10373826[node3，platform_2-node4，platform_4-node5]
wherein, nodeX represents the edge device X corresponding to the edge computing node, and platform _ i-nodej represents the edge device j corresponding to the edge computing node i.
The purpose of the directory tree is to provide a fast index of the backed-up files, with the backup data being accessible through paths in the directory tree.
And recording the metadata information of each block data index list and file on the directory tree. Metadata information includes, but is not limited to: rights information and size information, etc.
In some possible implementations of the embodiments of the present invention, the directory tree and the metadata information may be stored in an index manner of a memory database, that is, the directory tree is stored in a memory of an edge computing node, so as to accelerate the index efficiency of block data, thereby improving the data recovery speed and efficiency.
In some possible implementations of the embodiment of the present invention, the directory tree may be stored in a disk of the edge computing node in a separate storage manner, so as to implement the reconstruction of the directory tree after a memory failure or a machine restart.
In some possible implementations of embodiments of the invention, the directory tree and metadata information may be stored in disk in json format. An example of storing directory trees and metadata information in json format is as follows:
in some possible implementations of embodiments of the invention, the directory tree may follow the user to different edge compute nodes.
When a user wants to modify a certain piece of data, firstly logging in a certain edge computing node, determining whether the block of data is stored in the edge equipment corresponding to the edge computing node according to a directory tree, if the block of data is stored in the edge equipment corresponding to the edge computing node, acquiring the block of data from the edge equipment, and after the block of data is modified, storing the modified block of data according to the directory tree; and if the data of the block is not stored in the edge device corresponding to the edge computing node, acquiring the data of the block from the edge devices corresponding to other edge computing nodes, and storing the modified data of the block according to the directory tree after the data of the block is modified.
Illustratively, the block data 0-32M, blk _10373825 described above is taken as an example.
The user wants to modify the block data whose identification information is blk _10373825, and logs in the edge computing node 2.
And according to the directory tree, determining that the data block is stored in the edge device 2 corresponding to the edge computing node 2, and acquiring the data block from the edge device 2 corresponding to the edge computing node 2.
After the data block is modified, the modified data block is stored in the edge device 1 corresponding to the edge computing node 1, the edge device 2 corresponding to the edge computing node 2, and the edge device 2 corresponding to the edge computing node 3 according to the directory tree.
Assume that the user logs in to the edge compute node 4. And according to the directory tree, determining that the block data is not stored in the edge device corresponding to the edge computing node 4, and acquiring the block data from the edge device 1 corresponding to the edge computing node 1, the edge device 2 corresponding to the edge computing node 2 or the edge device 2 corresponding to the edge computing node 3.
After the data block is modified, the modified data block is stored in the edge device 1 corresponding to the edge computing node 1, the edge device 2 corresponding to the edge computing node 2, and the edge device 2 corresponding to the edge computing node 3 according to the directory tree.
In some possible implementations of the embodiment of the present invention, when the block data is not stored in the edge device corresponding to the edge computing node, the block data may be acquired from the edge device corresponding to the edge computing node closest to the edge computing node.
Illustratively, the block data 0-32M, blk _10373825 described above is also taken as an example.
The user wants to modify the block data whose identification information is blk _10373825, and logs in the edge computing node 4.
And determining that the block data is not stored in the edge device corresponding to the edge computing node 4 according to the directory tree.
Assume that the edge calculation node closest to the edge calculation node 4 is the edge calculation node 3.
The block data is acquired from the edge device 2 corresponding to the edge computing node 3.
After the data block is modified, the modified data block is stored in the edge device 1 corresponding to the edge computing node 1, the edge device 2 corresponding to the edge computing node 2, and the edge device 2 corresponding to the edge computing node 3 according to the directory tree.
According to the data backup method provided by the embodiment of the invention, when a certain piece of data is modified, when the piece of data is stored in the edge device corresponding to the edge computing node logged in by the user, the piece of data can be directly acquired from the edge device corresponding to the edge computing node logged in by the user, when the piece of data is not stored in the edge device corresponding to the edge computing node logged in by the user, the piece of data can be acquired from the edge device corresponding to the edge computing node closest to the edge computing node logged in by the user, the piece of data does not need to be acquired from a common cloud or a private cloud, and the data modification efficiency can be improved.
Corresponding to the above method embodiment, the embodiment of the present invention further provides a data backup apparatus applied to the edge computing node. As shown in fig. 2, fig. 2 is a schematic structural diagram of a data backup apparatus applied to an edge computing node according to an embodiment of the present invention. The data backup device applied to the edge computing node may include:
an obtaining module 201, configured to obtain data to be backed up;
the splitting module 202 is configured to split data to be backed up to obtain at least one block of data;
the storage module 203 is configured to store at least one block of data in an edge device corresponding to the edge computing node.
A sending module 204, configured to send at least one block of data to at least one other edge computing node adjacent to the edge computing node, so that the at least one other edge computing node stores the at least one block of data in an edge device corresponding to the at least one other edge computing node.
In some possible implementations of the embodiment of the present invention, the storage module 203 may be specifically configured to:
and storing at least one block of data in the edge device corresponding to the edge computing node based on a load balancing algorithm.
In some possible implementations of the embodiment of the present invention, the data backup apparatus applied to the edge computing node provided in the embodiment of the present invention may further include:
the receiving module is used for receiving storage information sent by at least one other edge computing node, wherein the storage information comprises identification information of an edge device for storing at least one piece of block data;
the generating module is used for generating a directory tree of the data to be backed up based on the identification information; the directory tree records at least one piece of storage position information of the block data;
the storage module 203 may further be configured to store a directory tree.
In some possible implementations of the embodiment of the present invention, the storage module 203 may be specifically configured to:
storing the directory tree in a memory of the edge compute node, and/or,
and storing the directory tree in a disk of the edge computing node.
In some possible implementations of the embodiments of the present invention, the receiving module may be further configured to:
receiving a modification request of a user for target block data in at least one block data;
the obtaining module 201 may further be configured to:
if the target block data is stored in the edge equipment corresponding to the edge calculation node according to the directory tree, acquiring the target block data from the edge equipment corresponding to the edge calculation node;
the storage module 203 may further be configured to:
and storing the modified target block data according to the directory tree.
In some possible implementations of the embodiment of the present invention, the obtaining module 201 may further be configured to:
and if the target block data is not stored in the edge equipment corresponding to the edge calculation node according to the directory tree, acquiring the target block data from the edge equipment corresponding to other edge calculation nodes.
In some possible implementations of the embodiment of the present invention, the obtaining module 201 may be specifically configured to:
and acquiring target block data from edge equipment corresponding to other edge computing nodes closest to the edge computing node.
For the embodiment of the data backup apparatus applied to the edge computing node in the embodiment of the present invention, since it is basically similar to the embodiment of the data backup method applied to the edge computing node in the embodiment of the present invention, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the embodiment of the data backup method applied to the edge computing node in the embodiment of the present invention. The embodiments of the present invention are not described herein in detail.
According to the data backup device provided by the embodiment of the invention, the data is backed up to the edge equipment corresponding to other edge computing nodes, but not to the shared cloud or the private cloud, so that the backup speed of edge computing can be increased; in addition, when disaster recovery is performed, backup data can be acquired from edge devices corresponding to other edge computing nodes, backup data does not need to be acquired from a common cloud or a private cloud, and disaster recovery efficiency can be improved
Fig. 3 is a schematic structural diagram of a computing device according to an embodiment of the present invention. As shown in fig. 3, computing device 300 includes an input device 301, an input interface 302, a central processor 303, a memory 304, an output interface 305, and an output device 306. The input interface 302, the central processing unit 303, the memory 304, and the output interface 305 are connected to each other through a bus 310, and the input device 301 and the output device 306 are connected to the bus 310 through the input interface 302 and the output interface 305, respectively, and further connected to other components of the computing device 300.
Specifically, the input device 301 receives input information from the outside and transmits the input information to the central processor 303 through the input interface 302; central processor 303 processes the input information based on computer-executable instructions stored in memory 304 to generate output information, stores the output information temporarily or permanently in memory 304, and then transmits the output information to output device 306 through output interface 305; output device 306 outputs the output information external to computing device 300 for use by the user.
That is, the computing device shown in fig. 3 may also be implemented as an edge computing node, which may include: a memory storing a computer program; and a processor, which can implement the data backup method provided by the embodiment of the present invention when executing the computer program.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium; when being executed by a processor, the computer program realizes each process of the data backup method embodiment provided by the embodiment of the invention, can achieve the same technical effect, and is not repeated herein to avoid repetition. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
An embodiment of the present invention further provides a data backup system, as shown in fig. 4. Fig. 4 is a schematic structural diagram of a data backup system according to an embodiment of the present invention. The data backup system comprises at least one edge computing node and a subordinate edge computing node corresponding to each edge computing node. And the subordinate edge computing nodes are used for backing up the edge computing nodes corresponding to the subordinate edge computing nodes.
FIG. 4 shows N edge compute nodes, which are respectively edge compute node 1, edge compute nodes 2, … …, and edge compute node N.N.N.the slave edge compute nodes are respectively slave edge compute node 1, slave edge compute node 2, … …, slave edge compute node N.edge compute node i corresponds to slave edge compute node i, i ∈ N.
Wherein, edge computing node 1 corresponds to X edge devices, edge computing node 2 corresponds to Y edge devices, … …, and edge computing node N corresponds to Z edge devices.
In some possible implementations of the embodiment of the present invention, the slave edge computing node i may periodically obtain a mirror copy from the edge computing node i, and recover data through the mirror copy.
When the edge computing node fails, the slave edge computing node corresponding to the failed edge computing node is started.
Illustratively, assuming that edge compute node 2 fails, the slave edge compute node 2 is enabled.
The data backup system provided by the embodiment of the invention can prevent the data loss of the edge computing node.
The following describes a data backup method provided in an embodiment of the present invention with reference to a data backup system.
When a user logs in the edge computing node 1 to backup data, the data to be backed up is firstly split into block data. Assume splitting into first block data and second block data.
The first block data is stored in the edge device 1 of the edge computing node 1, the edge device 2 of the edge computing node 2, and the edge device 2 corresponding to the edge computing node 3.
The second block data is stored in the edge device 3 of the edge computing node 1, the edge device 4 of the edge computing node 2, and the edge device 5 corresponding to the edge computing node 4.
And the memory and the disk of the edge computing node 1 store the directory tree corresponding to the data to be backed up.
When the user logs in the edge computing node 1 again to modify the first block data, the first block data is obtained from the edge device 1 of the edge computing node 1.
And after the first block data is modified, storing the modified first block data in the edge device 1 corresponding to the edge computing node 1, the edge device 2 corresponding to the edge computing node 2 and the edge device 2 corresponding to the edge computing node 3.
When a user logs in the edge computing node 4 to modify the first block data, the first block data is acquired from the edge device 2 of the edge computing node 3 closest to the edge computing node 4.
And after the first block data is modified, storing the modified first block data in the edge device 1 corresponding to the edge computing node 1, the edge device 2 corresponding to the edge computing node 2 and the edge device 2 corresponding to the edge computing node 3.
The slave edge computing node i periodically obtains a mirror image copy from the edge computing node i. When the edge computing node fails, the slave edge computing node corresponding to the failed edge computing node works.
It is to be understood that the invention is not limited to the specific arrangements and instrumentality described above and shown in the drawings. A detailed description of known methods is omitted herein for the sake of brevity. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present invention are not limited to the specific steps described and illustrated, and those skilled in the art can make various changes, modifications and additions or change the order between the steps after comprehending the spirit of the present invention.
The functional blocks shown in the above-described structural block diagrams may be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an Application Specific Integrated Circuit (ASIC), suitable firmware, plug-in, function card, or the like. When implemented in software, the elements of the invention are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine-readable medium or transmitted by a data signal carried in a carrier wave over a transmission medium or a communication link. A "machine-readable medium" may include any medium that can store or transfer information. Examples of a machine-readable medium include electronic circuits, semiconductor memory devices, ROM, flash memory, Erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, Radio Frequency (RF) links, and so forth. The code segments may be downloaded via computer networks such as the internet, intranet, etc.
It should also be noted that the exemplary embodiments mentioned in this patent describe some methods or systems based on a series of steps or devices. However, the present invention is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, may be performed in an order different from the order in the embodiments, or may be performed simultaneously.
As described above, only the specific embodiments of the present invention are provided, and it can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the module and the unit described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. It should be understood that the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the present invention, and these modifications or substitutions should be covered within the scope of the present invention.
Claims (11)
1. A data backup method is characterized in that the method is applied to an edge computing node; the method comprises the following steps:
acquiring data to be backed up;
splitting the data to be backed up to obtain at least one block of data;
storing the at least one block of data in an edge device corresponding to the edge computing node;
sending the at least one block data to at least one other edge computing node adjacent to the edge computing node for the at least one other edge computing node to store the at least one block data in an edge device corresponding to the at least one other edge computing node.
2. The method of claim 1, wherein storing the at least one block of data in an edge device corresponding to the edge computing node comprises:
and storing the at least one block of data in the edge device corresponding to the edge computing node based on a load balancing algorithm.
3. The method of claim 2, further comprising:
receiving storage information sent by the at least one other edge computing node, wherein the storage information comprises identification information of an edge device storing the at least one block of data;
generating a directory tree of the data to be backed up based on the identification information; the directory tree records storage position information of the at least one block data;
and storing the directory tree.
4. The method of claim 3, wherein storing the directory tree comprises:
storing the directory tree in a memory of the edge compute node, and/or,
and storing the directory tree in a disk of the edge computing node.
5. The method of claim 3, further comprising:
receiving a user modification request for target block data in the at least one block data;
if the target block data is stored in the edge device corresponding to the edge calculation node according to the directory tree, acquiring the target block data from the edge device corresponding to the edge calculation node;
and storing the modified target block data according to the directory tree.
6. The method of claim 5, further comprising:
and if the target block data is not stored in the edge equipment corresponding to the edge computing node according to the directory tree, acquiring the target block data from the edge equipment corresponding to the other edge computing nodes.
7. The method according to claim 6, wherein the obtaining the target block data from the edge devices corresponding to the other edge computing nodes comprises:
and acquiring the target block data from the edge devices corresponding to other edge computing nodes which are closest to the edge computing node.
8. A data backup device is characterized in that the device is applied to an edge computing node; the device comprises:
the acquisition module is used for acquiring data to be backed up;
the splitting module is used for splitting the data to be backed up to obtain at least one block of data;
the storage module is used for storing the at least one piece of block data in the edge device corresponding to the edge computing node;
a sending module, configured to send the at least one block of data to at least one other edge computing node adjacent to the edge computing node, so that the at least one other edge computing node stores the at least one block of data in an edge device corresponding to the at least one other edge computing node.
9. An edge compute node, the edge compute node comprising: a memory, a processor, and a computer program stored on the memory and executable on the processor;
the processor, when executing the computer program, implements the data backup method of any of claims 1 to 7.
10. A computer-readable storage medium, having stored thereon a computer program which, when executed by a processor, implements a data backup method according to any one of claims 1 to 7.
11. A data backup system, the system comprising: at least one edge compute node according to claim 9 and a dependent edge compute node corresponding to each of said edge compute nodes;
and the subordinate edge computing node is used for backing up the edge computing node corresponding to the subordinate edge computing node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010231310.XA CN111444043A (en) | 2020-03-27 | 2020-03-27 | Data backup method, device, node, system and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010231310.XA CN111444043A (en) | 2020-03-27 | 2020-03-27 | Data backup method, device, node, system and medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111444043A true CN111444043A (en) | 2020-07-24 |
Family
ID=71651323
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010231310.XA Pending CN111444043A (en) | 2020-03-27 | 2020-03-27 | Data backup method, device, node, system and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111444043A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111752764A (en) * | 2020-08-31 | 2020-10-09 | 湖南康通电子股份有限公司 | Data distribution method and system |
| CN113190378A (en) * | 2020-12-31 | 2021-07-30 | 华数云科技有限公司 | Edge cloud disaster recovery method based on distributed cloud platform |
| CN113676510A (en) * | 2021-07-13 | 2021-11-19 | 阿里巴巴新加坡控股有限公司 | Cloud storage method, system, equipment and storage medium |
| CN114401183A (en) * | 2022-01-17 | 2022-04-26 | 杭州瑞网广通信息技术有限公司 | Edge cloud disaster recovery system, method and device based on distributed cloud platform |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110055161A1 (en) * | 2009-09-01 | 2011-03-03 | Andrew Wolfe | Cloud Data Backup Storage |
| CN104639661A (en) * | 2015-03-13 | 2015-05-20 | 华存数据信息技术有限公司 | Distributed storage system and storing and reading method for files |
| CN108268209A (en) * | 2016-12-31 | 2018-07-10 | 深圳市优朋普乐传媒发展有限公司 | Date storage method and CDN system in a kind of CDN system |
| CN109271283A (en) * | 2018-09-06 | 2019-01-25 | 北京云测信息技术有限公司 | A kind of data back up method based on block chain |
| CN109726037A (en) * | 2017-10-27 | 2019-05-07 | 伊姆西Ip控股有限责任公司 | Method, equipment and computer program product for Backup Data |
| CN109902114A (en) * | 2019-01-24 | 2019-06-18 | 中国平安人寿保险股份有限公司 | ES company-data multiplexing method, system, computer installation and storage medium |
| CN110515770A (en) * | 2019-08-16 | 2019-11-29 | 苏州浪潮智能科技有限公司 | A kind of cloud backup method of data, device, equipment and storage medium |
-
2020
- 2020-03-27 CN CN202010231310.XA patent/CN111444043A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110055161A1 (en) * | 2009-09-01 | 2011-03-03 | Andrew Wolfe | Cloud Data Backup Storage |
| CN104639661A (en) * | 2015-03-13 | 2015-05-20 | 华存数据信息技术有限公司 | Distributed storage system and storing and reading method for files |
| CN108268209A (en) * | 2016-12-31 | 2018-07-10 | 深圳市优朋普乐传媒发展有限公司 | Date storage method and CDN system in a kind of CDN system |
| CN109726037A (en) * | 2017-10-27 | 2019-05-07 | 伊姆西Ip控股有限责任公司 | Method, equipment and computer program product for Backup Data |
| CN109271283A (en) * | 2018-09-06 | 2019-01-25 | 北京云测信息技术有限公司 | A kind of data back up method based on block chain |
| CN109902114A (en) * | 2019-01-24 | 2019-06-18 | 中国平安人寿保险股份有限公司 | ES company-data multiplexing method, system, computer installation and storage medium |
| CN110515770A (en) * | 2019-08-16 | 2019-11-29 | 苏州浪潮智能科技有限公司 | A kind of cloud backup method of data, device, equipment and storage medium |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111752764A (en) * | 2020-08-31 | 2020-10-09 | 湖南康通电子股份有限公司 | Data distribution method and system |
| CN113190378A (en) * | 2020-12-31 | 2021-07-30 | 华数云科技有限公司 | Edge cloud disaster recovery method based on distributed cloud platform |
| CN113190378B (en) * | 2020-12-31 | 2024-04-02 | 华数云科技有限公司 | Edge cloud disaster recovery method based on distributed cloud platform |
| CN113676510A (en) * | 2021-07-13 | 2021-11-19 | 阿里巴巴新加坡控股有限公司 | Cloud storage method, system, equipment and storage medium |
| CN114401183A (en) * | 2022-01-17 | 2022-04-26 | 杭州瑞网广通信息技术有限公司 | Edge cloud disaster recovery system, method and device based on distributed cloud platform |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111444043A (en) | Data backup method, device, node, system and medium | |
| CN109492013B (en) | Data processing method, device and system applied to database cluster | |
| US20160203054A1 (en) | Disk group based backup | |
| US9836361B2 (en) | Data replicating system, data replicating method, node device, management device and computer readable medium | |
| US11736371B2 (en) | Heartbeat information sending method and apparatus, and heartbeat sending node | |
| CN107992537B (en) | Service attribute transmission method, device, computer equipment and storage medium | |
| WO2014084922A1 (en) | High availability for cloud servers | |
| CN104182294A (en) | Method and device for backing up and recovering file | |
| US20060136903A1 (en) | Peer to peer backup and recovery | |
| JP6700308B2 (en) | Data copy method and device | |
| US20190227710A1 (en) | Incremental data restoration method and apparatus | |
| CN112925759B (en) | Data file processing method and device, storage medium and electronic device | |
| CN111651424B (en) | Data processing method, device, data node and storage medium | |
| CN110825562A (en) | Data backup method, device, system and storage medium | |
| CN114138732A (en) | Data processing method and device | |
| CN115658390A (en) | Container disaster tolerance method, system, device, equipment and computer readable storage medium | |
| US20210240350A1 (en) | Method, device, and computer program product for recovering based on reverse differential recovery | |
| CN111404737B (en) | Disaster recovery processing method and related device | |
| CN106951443B (en) | Method, equipment and system for synchronizing copies based on distributed system | |
| CN107623705B (en) | Storage mode upgrading method, device and system based on video cloud storage system | |
| CN110798358B (en) | Distributed service identification method and device, computer readable medium and electronic equipment | |
| CN113630317B (en) | Data transmission method and device, nonvolatile storage medium and electronic device | |
| CN116795587A (en) | Backup method and device of cloud host, electronic equipment and storage medium | |
| CN112015520B (en) | Data uploading system and method | |
| CN114281600A (en) | Disaster recovery backup and recovery method, device, equipment and storage medium |
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: 20200724 |