A data backup method, system and related components of an edge node

Abstract

The application discloses a data backup method and system of an edge node and related components, relates to the field of cloud platforms, and is applied to any edge node in a cluster. The method comprises the following steps: acquiring the network connection state of the edge node and other nodes in the cluster; determining a backup node that provides a spare backup space for the edge node among the other nodes according to the network connection state, and grouping the spare backup spaces of all the backup nodes into a node group backup pool; acquiring a backup strategy corresponding to an application to be backed up in the edge node; determining a backup position according to the backup strategy; the backup position comprises a local backup space, the node group backup pool and / or a cloud backup pool; determining data to be backed up; and classifying and backing up the data to be backed up to the corresponding backup position according to the backup strategy. The distance, backup time and backup data volume of the application of the data to be backed up to different backup positions all have differences in levels, so that the high availability of data backup in the edge node is ensured.

Description

Technical Field

[0001] This invention relates to the field of cloud platforms, and in particular to a data backup method, system, and related components for edge nodes. Background Technology

[0002] With the continuous development of edge computing, more and more users are deploying applications originally deployed in the cloud to the edge to solve problems such as low network bandwidth and high latency between the site and the central cloud. Business continuity is extremely important for application operation and is generally achieved through backup. In the traditional cloud computing model, applications are deployed in the data center, and local data is copied to an off-site backup center through remote replication of the storage system or third-party software. In edge scenarios, business continuity is even more important because the edge environment is harsher than that of the data center, the probability of hardware or software failure is higher, and backup and recovery solutions are more urgent. However, due to the characteristics of edge computing, such as its decentralized nature, unstable network, complex edge scenarios, and non-standardization, the backup methods originally used in data centers are difficult to apply to edge computing.

[0003] Therefore, how to provide a solution to the above-mentioned technical problems is a problem that needs to be solved by those skilled in the art. Summary of the Invention

[0004] In view of this, the purpose of this invention is to provide a data backup method, system, and related components for edge nodes to improve business continuity. The specific solution is as follows:

[0005] A data backup method for edge nodes, applied to any edge node in a cluster, the method comprising:

[0006] Obtain the network connection status between the edge node and other nodes in the cluster;

[0007] Based on the network connection status, a backup node is identified among the other nodes that provides spare backup space for the edge node, and the spare backup space of all the backup nodes is combined into a node group backup pool.

[0008] Obtain the backup strategy corresponding to the application to be backed up within the edge node;

[0009] The backup location is determined according to the backup strategy; the backup location includes the local backup space of the edge node, and / or the node group backup pool, and / or the cloud backup pool of the cluster;

[0010] Determine the data to be backed up corresponding to the application to be backed up;

[0011] According to the backup strategy, the data to be backed up is backed up in stages to the corresponding backup locations.

[0012] Preferably, the process of determining the backup data corresponding to the application to be backed up includes:

[0013] Pause the write operation of the application to be backed up;

[0014] The cached data corresponding to the application to be backed up is refreshed to the hard drive of the edge node;

[0015] All data in the hard drive corresponding to the application to be backed up is identified as the data to be backed up.

[0016] Preferably, before obtaining the backup strategy corresponding to the application to be backed up within the edge node, the method further includes:

[0017] Obtain the estimated space required for the application to be backed up;

[0018] Determine the local backup space to be the same size as the estimated space amount;

[0019] The estimated space and the local backup space are subtracted from the total storage space of the edge node to obtain the amount of free backup space.

[0020] Preferably, the process of backing up the data to be backed up to the corresponding backup locations in a tiered manner according to the backup strategy includes:

[0021] When the backup location includes the node group backup pool, the data to be backed up is evenly backed up to the free backup space of all the backup nodes.

[0022] Preferably, the process of backing up the data to be backed up to the corresponding backup locations in a tiered manner according to the backup strategy includes:

[0023] When the backup location includes the node group backup pool, the data to be backed up is sharded according to the weight of each backup node, and then backed up to the free backup space of the corresponding backup node.

[0024] Preferably, the weight is determined based on the health status of each backup node, the health status including:

[0025] The number of times the backup node is restarted, and / or the network connection status of the backup node, and / or the amount of free backup space of the backup node.

[0026] Preferably, the process of backing up the data to be backed up to the corresponding backup locations in a tiered manner according to the backup strategy includes:

[0027] According to the backup strategy, the data to be backed up is backed up to the corresponding backup locations in a hierarchical manner, with the local backup space having the highest priority, the node group backup pool having the second highest priority, and the cloud backup pool having the lowest priority.

[0028] Accordingly, this application also discloses a data backup system for edge nodes, applicable to any edge node in a cluster, the system comprising:

[0029] The status acquisition module is used to acquire the network connection status between the edge node and other nodes in the cluster.

[0030] The backup pool determination module is used to determine the backup nodes that provide backup services for the edge nodes in the cluster based on the network connection status, and is also used to form a node group backup pool by combining the spare backup space of all the backup nodes.

[0031] The strategy acquisition module is used to acquire the backup strategy corresponding to the application to be backed up within the edge node, and is also used to determine the backup location based on the backup strategy; the backup location includes the local backup space of the edge node, and / or the node group backup pool, and / or the cloud backup pool of the cluster;

[0032] The data determination module is used to determine the data to be backed up corresponding to the application to be backed up.

[0033] The action module is used to back up the data to be backed up to the corresponding backup locations in a tiered manner according to the backup strategy.

[0034] Accordingly, this application also discloses an electronic device, including:

[0035] Memory, used to store computer programs;

[0036] A processor, used to execute the computer program to implement the steps of the data backup system method for edge nodes as described in any of the above.

[0037] Accordingly, this application also discloses a readable storage medium storing a computer program that, when executed by a processor, implements the steps of the edge node data backup system method as described in any of the above claims.

[0038] This application discloses a data backup method for edge nodes. Based on the network topology of the edge nodes and the backup strategy corresponding to the applications in the containers, different backup locations are determined, including local backup space, node group backup pool, and cloud backup pool. The distance, backup time, and backup data volume of the application's data to be backed up to different backup locations are all at different levels. In the context of dispersed edge nodes, unstable networks, complex edge scenarios, and non-standardization, this method ensures high availability of data backup in edge nodes, so that the data at the backup locations can be used to restore the applications of the edge nodes in the future. Attached Figure Description

[0039] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0040] Figure 1 This is a flowchart illustrating the steps of a data backup method for an edge node according to an embodiment of the present invention;

[0041] Figure 2 This is a structural distribution diagram of a backup location in an embodiment of the present invention;

[0042] Figure 3 This is a structural distribution diagram of a data backup system for an edge node according to an embodiment of the present invention;

[0043] Figure 4 This is a structural distribution diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0044] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0045] In traditional cloud computing, applications are deployed in data centers, and local data is copied to an off-site backup center via remote replication from storage systems or third-party software. However, due to the dispersed, unstable network, complex, and non-standardized characteristics of edge computing, traditional data center backup methods are difficult to apply to edge computing.

[0046] This application discloses a data backup method for edge nodes. Based on the network topology of the edge nodes and the backup strategy corresponding to the applications in the containers, different backup locations are determined, including local backup space, node group backup pool, and cloud backup pool. The distance, backup time, and backup data volume of the application's data to be backed up to different backup locations are all at different levels. In the context of dispersed edge nodes, unstable networks, complex edge scenarios, and non-standardization, this method ensures high availability of data backup in edge nodes, so that the data at the backup locations can be used to restore the applications of the edge nodes in the future.

[0047] This invention discloses a data backup method for edge nodes, applicable to any edge node in a cluster. See [link to relevant documentation]. Figure 1 As shown, the method includes:

[0048] S1: Obtain the network connection status between edge nodes and other nodes in the cluster;

[0049] S2: Based on the network connection status, identify the backup nodes that provide spare backup space for the edge nodes among other nodes, and form a node group backup pool by combining the spare backup space of all backup nodes.

[0050] Understandably, a cluster includes edge nodes and other nodes. Based on the network connection status of the edge nodes and other nodes, nodes that can provide spare backup space for the edge nodes are selected as backup nodes. The conditions for determining backup nodes may include direct connection to the edge nodes and / or connection distance to the edge nodes not exceeding the preset network link length. Under these conditions, different edge nodes correspond to different backup nodes, and the specific correspondence between edge nodes and backup nodes needs to be recorded internally. Alternatively, the condition for determining backup nodes may be that they belong to the same sub-cluster as the edge nodes. In this case, for all nodes in a sub-cluster, the backup node for each node can be directly determined from all nodes in its sub-cluster, or other nodes in the sub-cluster besides the current node can be directly used as the backup node for that node. The determination of backup nodes is simpler and more direct.

[0051] S3: Obtain the backup strategy corresponding to the application to be backed up within the edge node;

[0052] S4: Determine the backup location based on the backup strategy; the backup location includes the local backup space of the edge node, and / or the node group backup pool, and / or the cloud backup pool of the cluster;

[0053] Specifically, the backup strategy for applications to be backed up within edge nodes is determined by configuration parameters, and there are several scenarios. Common backup strategies include high, medium, and low reliability options. In a high-reliability backup strategy, backup locations include local backup space, node group backup pool, and cloud backup pool. In a medium-reliability backup strategy, backup locations include local backup space and node group backup pool. In a low-reliability backup strategy, backup locations only include local backup space, and a backup copy is allocated to each backup location during backup. Besides these scenarios, backup strategies can also be pre-configured according to actual needs, which will not be elaborated here.

[0054] S5: Determine the data to be backed up for the application to be backed up;

[0055] Specifically, the steps include:

[0056] Pause write operations on the application to be backed up;

[0057] The cached data of the application to be backed up is refreshed to the hard drive of the edge node;

[0058] All data on the hard drive corresponding to the application to be backed up is identified as the data to be backed up.

[0059] It is understandable that when determining the data to be backed up, write operations need to be paused and cached data needs to be written to disk; otherwise, inconsistencies in the backup data may occur.

[0060] S6: According to the backup strategy, back up the data to be backed up in stages to the corresponding backup locations.

[0061] Specifically, the backup process includes compressing the data to be backed up beforehand, and using concurrent mode for file copying to improve efficiency. It's important to note that when the backup location includes a node group backup pool, the process of allocating the data to the node group backup pool typically involves fragmenting the data and distributing it to the corresponding available backup space within the node group backup pool.

[0062] Furthermore, step S6 may specifically include:

[0063] Based on the backup strategy, data to be backed up is tiered and backed up to the corresponding backup locations, with the local backup space having the highest priority, the node group backup pool having the second highest priority, and the cloud backup pool having the lowest priority.

[0064] It is understandable that the priority of backup locations can be set to other orders; there are no restrictions here. If a backup location appears in the priority list but is not included in the backup policy, it can be skipped.

[0065] Understandably, during tiered backups, the data to be backed up is typically sent to the highest priority backup location. Then, the backup data from the highest priority backup location is distributed to the next lower priority backup location, and so on. However, if the network connection between a backup location and the backup location of the next higher priority is lost, the backup process may not follow the priority rules. Alternatively, the backup data can be forwarded to the appropriate backup location via other nodes with uninterrupted connections, as long as the data to be backed up arrives at the backup location accurately and completely.

[0066] Furthermore, in this embodiment, the application to be backed up within the edge node is typically an application deployed in a container on the edge node. The data of the application to be backed up in the container includes metadata and business data. The metadata is directly backed up to the cloud backup pool, while the business data is used as the data to be backed up using the data backup method in this embodiment. In the edge scenario, the business data is usually stored in a data volume mounted on the application to be backed up in the container. The data volume corresponds to a file system directory on the edge node.

[0067] Furthermore, the backup and recovery of metadata in the cloud backup pool are both achieved by calling the Kubernetes API (Application Programming Interface). This allows the metadata corresponding to the application to be backed up to be allocated to the cloud backup pool. During recovery, the metadata backup data in the cloud backup pool is read and then the resource is reapplied in Kubernetes to restore the container application.

[0068] Furthermore, a Kubernetes daemon set is deployed on the edge node to perform the actions in steps S5 and S6 of this embodiment. It can also complete the subsequent acquisition, decompression and restoration of backup data at the backup location. During restoration, backup data is generally obtained from the backup location with the highest priority. If the backup data is incomplete, incorrect or non-existent, the corresponding backup data can be obtained from the backup location with the next lower priority until the complete backup data location is obtained.

[0069] This application discloses a data backup method for edge nodes. Based on the network topology of the edge nodes and the backup strategy corresponding to the applications in the containers, different backup locations are determined, including local backup space, node group backup pool, and cloud backup pool. The distance, backup time, and backup data volume of the application's data to be backed up to different backup locations are all at different levels. In the context of dispersed edge nodes, unstable networks, complex edge scenarios, and non-standardization, this method ensures high availability of data backup in edge nodes, so that the data at the backup locations can be used to restore the applications of the edge nodes in the future.

[0070] This invention discloses a specific data backup method for edge nodes. Compared with the previous embodiment, this embodiment further explains and optimizes the technical solution.

[0071] Specifically, before obtaining the backup policy corresponding to the application to be backed up within the edge node, the following steps are also included:

[0072] Get the estimated space required for the application to be backed up;

[0073] Determine the same amount of local backup space as the estimated amount;

[0074] Subtract the estimated space and local backup space from the total storage space of the edge nodes to obtain the amount of free backup space.

[0075] It is understandable that the total storage space of an edge node can be divided into several parts: application storage space provided to applications, local backup space, and spare backup space. The application storage space includes at least the estimated storage space of the application to be backed up, and its size is the estimated space amount. The local backup space is the same size as the application storage space. The remaining space of the total storage space can be used for spare backup space, so as to form a node group backup pool of another edge node with the spare backup space of other nodes.

[0076] by Figure 2 For example, the condition for determining a backup node is that it belongs to the same sub-cluster as the edge node. In this case, the logical architecture of the backup pool in each node is as follows: Figure 2 As shown in the image.

[0077] In some specific embodiments, depending on different space configurations, the data to be backed up can be evenly distributed to the available backup spaces in the node group backup pool, or the data to be backed up can be distributed to different available spaces according to weight.

[0078] During the even distribution, the process of backing up the data to be backed up to the corresponding backup locations according to the backup strategy includes:

[0079] When the backup location includes the node group backup pool, the data to be backed up is evenly backed up to the available backup space of all backup nodes.

[0080] When allocating data based on weights, the process of backing up the data to be backed up to the corresponding backup locations according to the backup strategy includes:

[0081] When the backup location includes a node group backup pool, the data to be backed up is sharded according to the weight of each backup node, and then backed up to the corresponding spare backup space of each backup node.

[0082] Furthermore, the weights are determined based on the health status of each backup node, which includes:

[0083] The number of times the backup node has been restarted, and / or the network connection status of the backup node, and / or the amount of free backup space on the backup node.

[0084] Understandably, for backup nodes, the more times they restart, the worse their health status. The better their network connection, the larger their storage space, and the greater their backup capacity. In addition to these factors, health status can also be determined based on factors such as network bandwidth ratio and configuration model. Then, backup nodes with better health status can be assigned higher weights to ensure that more backup data is routed to these nodes, thereby improving the reliability of the backup data and business continuity.

[0085] Accordingly, this application also discloses a data backup system for edge nodes, applicable to any edge node in the cluster, see [link to relevant documentation]. Figure 3 As shown, the system includes:

[0086] Status acquisition module 1 is used to acquire the network connection status between the edge node and other nodes in the cluster;

[0087] Backup pool determination module 2 is used to determine the backup node in the cluster that provides backup services for the edge node according to the network connection status, and is also used to form a node group backup pool by combining the spare backup space of all the backup nodes.

[0088] The strategy acquisition module 3 is used to acquire the backup strategy corresponding to the application to be backed up within the edge node, and is also used to determine the backup location based on the backup strategy; the backup location includes the local backup space of the edge node, and / or the node group backup pool, and / or the cloud backup pool of the cluster;

[0089] Data determination module 4 is used to determine the data to be backed up corresponding to the application to be backed up;

[0090] Action module 5 is used to back up the data to be backed up to the corresponding backup location in a hierarchical manner according to the backup strategy.

[0091] Based on the network topology of the edge nodes and the backup strategy corresponding to the application in the container, this application determines different backup locations, including local backup space, node group backup pool, and cloud backup pool. The distance, backup time, and backup data volume of the application's data to be backed up to different backup locations are all at different levels. In the context of scattered edge nodes, unstable networks, complex edge scenarios, and non-standardization, this ensures high availability of data backup in edge nodes, so that the data in the backup locations can be used to restore the application of the edge nodes in the future.

[0092] Understandably, a cluster includes edge nodes and other nodes. Based on the network connection status of the edge nodes and other nodes, nodes that can provide spare backup space for the edge nodes are selected as backup nodes. The conditions for determining backup nodes may include direct connection to the edge nodes and / or connection distance to the edge nodes not exceeding the preset network link length. Under these conditions, different edge nodes correspond to different backup nodes, and the specific correspondence between edge nodes and backup nodes needs to be recorded internally. Alternatively, the condition for determining backup nodes may be that they belong to the same sub-cluster as the edge nodes. In this case, for all nodes in a sub-cluster, the backup node for each node can be directly determined from all nodes in its sub-cluster, or other nodes in the sub-cluster besides the current node can be directly used as the backup node for that node. The determination of backup nodes is simpler and more direct.

[0093] Specifically, the backup strategy for applications to be backed up within edge nodes is determined by configuration parameters, and there are several scenarios. Common backup strategies include high, medium, and low reliability options. In a high-reliability backup strategy, backup locations include local backup space, node group backup pool, and cloud backup pool. In a medium-reliability backup strategy, backup locations include local backup space and node group backup pool. In a low-reliability backup strategy, backup locations only include local backup space, and a backup copy is allocated to each backup location during backup. Besides these scenarios, backup strategies can also be pre-configured according to actual needs, which will not be elaborated here.

[0094] Specifically, the backup process includes compressing the data to be backed up beforehand, and using concurrent mode for file copying to improve efficiency. It's important to note that when the backup location includes a node group backup pool, the process of allocating the data to the node group backup pool typically involves fragmenting the data and distributing it to the corresponding available backup space within the node group backup pool.

[0095] In some specific embodiments, the process of determining the backup data corresponding to the application to be backed up includes:

[0096] Pause the write operation of the application to be backed up;

[0097] The cached data corresponding to the application to be backed up is refreshed to the hard drive of the edge node;

[0098] All data in the hard drive corresponding to the application to be backed up is identified as the data to be backed up.

[0099] In some specific embodiments, before the policy acquisition module 3 acquires the backup policy corresponding to the application to be backed up within the edge node, it further includes:

[0100] Obtain the estimated space required for the application to be backed up;

[0101] Determine the local backup space to be the same size as the estimated space amount;

[0102] The estimated space and the local backup space are subtracted from the total storage space of the edge node to obtain the amount of free backup space.

[0103] In some specific embodiments, the process of backing up the data to be backed up to the corresponding backup locations in a tiered manner according to the backup strategy includes:

[0104] When the backup location includes the node group backup pool, the data to be backed up is evenly backed up to the free backup space of all the backup nodes.

[0105] In some specific embodiments, the process of backing up the data to be backed up to the corresponding backup locations in a tiered manner according to the backup strategy includes:

[0106] When the backup location includes the node group backup pool, the data to be backed up is sharded according to the weight of each backup node, and then backed up to the free backup space of the corresponding backup node.

[0107] In some specific embodiments, the weights are determined based on the health status of each backup node, the health status including:

[0108] The number of times the backup node is restarted, and / or the network connection status of the backup node, and / or the amount of free backup space of the backup node.

[0109] In some specific embodiments, the process of backing up the data to be backed up to the corresponding backup locations in a tiered manner according to the backup strategy includes:

[0110] According to the backup strategy, the data to be backed up is backed up to the corresponding backup locations in a hierarchical manner, with the local backup space having the highest priority, the node group backup pool having the second highest priority, and the cloud backup pool having the lowest priority.

[0111] It is understandable that the priority of backup locations can be set to other orders; there are no restrictions here. If a backup location appears in the priority list but is not included in the backup policy, it can be skipped.

[0112] Understandably, during tiered backups, the data to be backed up is typically sent to the highest priority backup location. Then, the backup data from the highest priority backup location is distributed to the next lower priority backup location, and so on. However, if the network connection between a backup location and the backup location of the next higher priority is lost, the backup process may not follow the priority rules. Alternatively, the backup data can be forwarded to the appropriate backup location via other nodes with uninterrupted connections, as long as the data to be backed up arrives at the backup location accurately and completely.

[0113] This application also discloses an electronic device, see [link to relevant documentation] Figure 4 As shown, it includes a processor 11 and a memory 12; wherein, when the processor 11 executes the computer program stored in the memory 12, it performs the following steps:

[0114] Obtain the network connection status between the edge node and other nodes in the cluster;

[0115] Based on the network connection status, a backup node is identified among the other nodes that provides spare backup space for the edge node, and the spare backup space of all the backup nodes is combined into a node group backup pool.

[0116] Obtain the backup strategy corresponding to the application to be backed up within the edge node;

[0117] The backup location is determined according to the backup strategy; the backup location includes the local backup space of the edge node, and / or the node group backup pool, and / or the cloud backup pool of the cluster;

[0118] Determine the backup data corresponding to the application to be backed up;

[0119] According to the backup strategy, the data to be backed up is backed up in stages to the corresponding backup locations.

[0120] Based on the network topology of the edge nodes and the backup strategy corresponding to the application in the container, this application determines different backup locations, including local backup space, node group backup pool, and cloud backup pool. The distance, backup time, and backup data volume of the application's data to be backed up to different backup locations are all at different levels. In the context of scattered edge nodes, unstable networks, complex edge scenarios, and non-standardization, this ensures high availability of data backup in edge nodes, so that the data in the backup locations can be used to restore the application of the edge nodes in the future.

[0121] In some specific embodiments, when the processor 11 executes the computer subroutine stored in the memory 12, it may specifically implement the following steps:

[0122] Pause the write operation of the application to be backed up;

[0123] The cached data corresponding to the application to be backed up is refreshed to the hard drive of the edge node;

[0124] All data in the hard drive corresponding to the application to be backed up is identified as the data to be backed up.

[0125] In some specific embodiments, when the processor 11 executes the computer subroutine stored in the memory 12, it may specifically implement the following steps:

[0126] Obtain the estimated space required for the application to be backed up;

[0127] Determine the local backup space to be the same size as the estimated space amount;

[0128] The estimated space and the local backup space are subtracted from the total storage space of the edge node to obtain the amount of free backup space.

[0129] In some specific embodiments, when the processor 11 executes the computer subroutine stored in the memory 12, it may specifically implement the following steps:

[0130] When the backup location includes the node group backup pool, the data to be backed up is evenly backed up to the free backup space of all the backup nodes.

[0131] In some specific embodiments, when the processor 11 executes the computer subroutine stored in the memory 12, it may specifically implement the following steps:

[0132] When the backup location includes the node group backup pool, the data to be backed up is sharded according to the weight of each backup node, and then backed up to the free backup space of the corresponding backup node.

[0133] In some specific embodiments, the weights are determined based on the health status of each backup node, the health status including:

[0134] The number of times the backup node is restarted, and / or the network connection status of the backup node, and / or the amount of free backup space of the backup node.

[0135] In some specific embodiments, when the processor 11 executes the computer subroutine stored in the memory 12, it may specifically implement the following steps:

[0136] According to the backup strategy, the data to be backed up is backed up to the corresponding backup locations in a hierarchical manner, with the local backup space having the highest priority, the node group backup pool having the second highest priority, and the cloud backup pool having the lowest priority.

[0137] Furthermore, the electronic device in this embodiment may also include:

[0138] Input interface 13 is used to acquire computer programs imported from external sources and save the acquired computer programs to the memory 12. It can also be used to acquire various instructions and parameters transmitted from external terminal devices and transmit them to the processor 11 so that the processor 11 can perform corresponding processing using the aforementioned instructions and parameters. In this embodiment, the input interface 13 may specifically include, but is not limited to, a USB interface, a serial interface, a voice input interface, a fingerprint input interface, a hard disk read interface, etc.

[0139] Output interface 14 is used to output various data generated by processor 11 to connected terminal devices, so that other terminal devices connected to output interface 14 can obtain various data generated by processor 11. In this embodiment, output interface 14 may specifically include, but is not limited to, USB interface, serial interface, etc.

[0140] The communication unit 15 is used to establish a remote communication connection between the electronic device and the external server, so that the electronic device can mount the image file to the external server. In this embodiment, the communication unit 15 may specifically include, but is not limited to, a remote communication unit based on wireless communication technology or wired communication technology.

[0141] Keyboard 16 is used to acquire various parameter data or commands input by the user through real-time keystrokes.

[0142] Display 17 is used to display relevant information about the data backup process in real time, so that users can understand the current data backup status in a timely manner.

[0143] Mouse 18 can be used to assist users in inputting data and simplify user operations.

[0144] Furthermore, embodiments of this application also disclose a readable storage medium, which includes random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage medium known in the art. The readable storage medium stores a computer program, which, when executed by a processor, performs the following steps:

[0145] Obtain the network connection status between the edge node and other nodes in the cluster;

[0146] Based on the network connection status, a backup node is identified among the other nodes that provides spare backup space for the edge node, and the spare backup space of all the backup nodes is combined into a node group backup pool.

[0147] Obtain the backup strategy corresponding to the application to be backed up within the edge node;

[0148] The backup location is determined according to the backup strategy; the backup location includes the local backup space of the edge node, and / or the node group backup pool, and / or the cloud backup pool of the cluster;

[0149] Determine the data to be backed up corresponding to the application to be backed up;

[0150] According to the backup strategy, the data to be backed up is backed up in stages to the corresponding backup locations.

[0151] Based on the network topology of the edge nodes and the backup strategy corresponding to the application in the container, this application determines different backup locations, including local backup space, node group backup pool, and cloud backup pool. The distance, backup time, and backup data volume of the application's data to be backed up to different backup locations are all at different levels. In the context of scattered edge nodes, unstable networks, complex edge scenarios, and non-standardization, this ensures high availability of data backup in edge nodes, so that the data in the backup locations can be used to restore the application of the edge nodes in the future.

[0152] In some specific embodiments, when the computer subroutine stored in the readable storage medium is executed by a processor, the following steps can be implemented:

[0153] Pause the write operation of the application to be backed up;

[0154] The cached data corresponding to the application to be backed up is refreshed to the hard drive of the edge node;

[0155] All data in the hard drive corresponding to the application to be backed up is identified as the data to be backed up.

[0156] In some specific embodiments, when the computer subroutine stored in the readable storage medium is executed by a processor, the following steps can be implemented:

[0157] Obtain the estimated space required for the application to be backed up;

[0158] Determine the local backup space to be the same size as the estimated space amount;

[0159] The estimated space and the local backup space are subtracted from the total storage space of the edge node to obtain the amount of free backup space.

[0160] In some specific embodiments, when the computer subroutine stored in the readable storage medium is executed by a processor, the following steps can be implemented:

[0161] When the backup location includes the node group backup pool, the data to be backed up is evenly backed up to the free backup space of all the backup nodes.

[0162] In some specific embodiments, when the computer subroutine stored in the readable storage medium is executed by a processor, the following steps can be implemented:

[0163] When the backup location includes the node group backup pool, the data to be backed up is sharded according to the weight of each backup node, and then backed up to the free backup space of the corresponding backup node.

[0164] In some specific embodiments, the weights are determined based on the health status of each backup node, the health status including:

[0165] The number of times the backup node is restarted, and / or the network connection status of the backup node, and / or the amount of free backup space of the backup node.

[0166] In some specific embodiments, when the computer subroutine stored in the readable storage medium is executed by a processor, the following steps can be implemented:

[0167] According to the backup strategy, the data to be backed up is backed up to the corresponding backup locations in a hierarchical manner, with the local backup space having the highest priority, the node group backup pool having the second highest priority, and the cloud backup pool having the lowest priority.

[0168] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0169] The above provides a detailed description of the data backup method, system, and related components for edge nodes provided by the present invention. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A data backup method for edge nodes, characterized in that, Applied to any edge node in the cluster, the method includes: Obtain the network connection status between the edge node and other nodes in the cluster; Based on the network connection status, a backup node is identified among the other nodes that provides spare backup space for the edge node, and the spare backup space of all the backup nodes is combined into a node group backup pool. Obtain the backup strategy corresponding to the application to be backed up within the edge node; The backup location is determined according to the backup strategy; the backup location includes the local backup space of the edge node, and / or the node group backup pool, and / or the cloud backup pool of the cluster; when the backup location includes the node group backup pool, the data to be backed up is fragmented and distributed to the corresponding spare backup spaces of the node group backup pool. Determine the data to be backed up corresponding to the application to be backed up; According to the backup strategy, the data to be backed up is backed up in stages to the corresponding backup locations; Before obtaining the backup strategy corresponding to the application to be backed up within the edge node, the process also includes: Obtain the estimated space required for the application to be backed up; Determine the local backup space to be the same size as the estimated space amount; The estimated space and the local backup space are subtracted from the total storage space of the edge node to obtain the amount of free backup space. The process of backing up the data to be backed up to the corresponding backup locations in a tiered manner according to the backup strategy includes: According to the backup strategy, the data to be backed up is backed up to the corresponding backup locations in a hierarchical manner, with the local backup space having the highest priority, the node group backup pool having the second highest priority, and the cloud backup pool having the lowest priority.

2. The data backup method according to claim 1, characterized in that, The process of determining the backup data corresponding to the application to be backed up includes: Pause the write operation of the application to be backed up; The cached data corresponding to the application to be backed up is refreshed to the hard drive of the edge node; All data in the hard drive corresponding to the application to be backed up is identified as the data to be backed up.

3. The data backup method according to claim 1, characterized in that, The process of backing up the data to be backed up to the corresponding backup locations in a tiered manner according to the backup strategy includes: When the backup location includes the node group backup pool, the data to be backed up is evenly backed up to the free backup space of all the backup nodes.

4. The data backup method according to claim 1, characterized in that, The process of backing up the data to be backed up to the corresponding backup locations in a tiered manner according to the backup strategy includes: When the backup location includes the node group backup pool, the data to be backed up is sharded according to the weight of each backup node, and then backed up to the free backup space of the corresponding backup node.

5. The data backup method according to claim 4, characterized in that, The weights are determined based on the health status of each backup node, and the health status includes: The number of times the backup node is restarted, and / or the network connection status of the backup node, and / or the amount of free backup space of the backup node.

6. A data backup system for edge nodes, characterized in that, This system, applicable to any edge node in a cluster, includes: The status acquisition module is used to acquire the network connection status between the edge node and other nodes in the cluster. The backup pool determination module is used to determine the backup nodes that provide backup services for the edge nodes in the cluster based on the network connection status, and is also used to form a node group backup pool by combining the spare backup space of all the backup nodes. The strategy acquisition module is used to acquire the backup strategy corresponding to the application to be backed up within the edge node, and is also used to determine the backup location based on the backup strategy; the backup location includes the local backup space of the edge node, and / or the node group backup pool, and / or the cloud backup pool of the cluster; when the backup location includes the node group backup pool, the data to be backed up is fragmented and distributed to each available backup space corresponding to the node group backup pool. The data determination module is used to determine the data to be backed up corresponding to the application to be backed up. An action module is used to back up the data to be backed up to the corresponding backup locations in a tiered manner according to the backup strategy. Before obtaining the backup strategy corresponding to the application to be backed up within the edge node, the process also includes: Obtain the estimated space required for the application to be backed up; Determine the local backup space to be the same size as the estimated space amount; The estimated space and the local backup space are subtracted from the total storage space of the edge node to obtain the amount of free backup space. The process of backing up the data to be backed up to the corresponding backup locations in a tiered manner according to the backup strategy includes: According to the backup strategy, the data to be backed up is backed up to the corresponding backup locations in a hierarchical manner, with the local backup space having the highest priority, the node group backup pool having the second highest priority, and the cloud backup pool having the lowest priority.

7. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the data backup system method for an edge node as described in any one of claims 1 to 5 when executing the computer program.

8. A readable storage medium, characterized in that, The readable storage medium stores a computer program that, when executed by a processor, implements the steps of the data backup system method for edge nodes as described in any one of claims 1 to 5.

Images