Data Backup System and Method for Comprehensive Monitoring SaaS Service Platform

Abstract

The present invention discloses a data backup system and method for a comprehensive monitoring SaaS service platform, relating to the technical field of data backup. When the backup distribution unit allocates a cloud server for data backup corresponding to the monitoring data of each parameter object according to its backup cycle, multiple cloud servers to be currently backed up are screened out by analyzing the current states of each cloud server. Combining the data capacity of the data to be backed up, the optimal backup data volume is planned, and each cloud server backs up a part of the data. Multiple redundant backup cloud servers are selected for it from other cloud servers. On the one hand, the risk of data loss due to the downtime of a certain cloud server can be avoided, and the advantages of distributed backup storage are retained. On the other hand, the number of cloud servers to which the monitoring data of each parameter object is backed up and redundantly backed up is reasonably planned, making data backup more intelligent.

Description

Technical Field

[0001] The present invention relates to the technical field of data backup, and particularly to a data backup system and method for a comprehensive monitoring SaaS service platform. Background Art

[0002] Data backup refers to the process of copying all or part of a data set from the hard disk or array of an application host to other storage media to prevent data loss caused by operational errors or system failures in the system. Data backup is the basis of disaster recovery, which can protect the security of data and improve the continuous availability of data;

[0003] A comprehensive monitoring SaaS service platform refers to a software-as-a-service platform that provides all-round monitoring services based on the cloud computing model. Such platforms can help users monitor the performance and running status of various resources such as their networks, application programs, servers, databases, and storage to ensure the stability, security, and high availability of the system;

[0004] In a current comprehensive monitoring SaaS service platform, the data obtained by helping users monitor is stored in a distributed backup manner, and the data is backed up to multiple servers at the same time. In this way, even if a certain server crashes, the data stored on other servers can be used for data recovery, which greatly increases the security of data backup. However, there is no reasonable plan for how many servers the data should be backed up to, and the backed-up data does not combine the needs of users. All data is backed up at the same frequency, which will undoubtedly waste the transmission resources of the platform and result in low efficiency and lack of intelligence in data backup;

[0005] To solve the above problems, the present invention proposes a solution. Summary of the Invention

[0006] The purpose of the present invention is to provide a data backup system and method for a comprehensive monitoring SaaS service platform to solve the problems in the prior art that when using a distributed backup storage method and backing up data to multiple servers at the same time, there is no reasonable plan for how many servers the data should be backed up to, and the backed-up data does not combine the needs of users. All data is backed up at the same frequency, which will undoubtedly waste the transmission resources of the platform and result in low efficiency and lack of intelligence in data backup;

[0007] The purpose of the present invention can be achieved through the following technical solutions:

[0008] A data backup system for a comprehensive monitoring SaaS service platform includes:

[0009] Monitoring service module, which is used to provide monitoring services to authorized users. For one authorized user, the monitoring service module collects in real time the monitoring data of the parameter objects of all hardware devices and virtual devices belonging to this authorized user;

[0010] Monitoring data storage module, which is used to permanently store the monitoring data of the parameter objects of all hardware devices and virtual devices belonging to all authorized users;

[0011] For each authorized user, a backup planning module is used to plan the backup of the monitoring data of the parameter objects of all hardware devices and virtual devices belonging to it. The backup planning module includes a backup extraction unit and a backup distribution unit;

[0012] For any one authorized user, the backup extraction unit extracts from the monitoring data storage module the monitoring data of the parameter objects of the corresponding hardware device or virtual device stored during the corresponding backup period according to the backup period specified by this authorized user for the parameter object of each hardware device or virtual device belonging to it, and transmits it to the backup distribution unit;

[0013] For one hardware device belonging to one authorized user, after the backup distribution unit receives the monitoring data of the hardware parameters of this hardware device stored in the monitoring data storage module during the current backup period, it generates a preliminary backup policy for this authorized user based on the hardware parameters of this hardware device during the current backup period according to the preset distribution generation rule.

[0014] Furthermore, for each authorized user, the backup period specified by the corresponding authorized user for the parameter object of each hardware device and virtual device belonging to it is stored in the backup extraction unit.

[0015] Data backup method for an integrated monitoring SaaS service platform, including the following steps:

[0016] Step 1: For each authorized user, collect in real time the monitoring data of the parameter objects of all hardware devices and virtual devices belonging to each authorized user and store it;

[0017] Step 2: For each authorized user, extract the monitoring data of the parameter objects of the corresponding hardware device or virtual device collected during the backup period according to the backup period specified by this authorized user for the parameter object of each hardware device or virtual device belonging to it;

[0018] Step 3: For each authorized user, based on the monitoring data of the parameter objects of each hardware device or virtual device belonging to the user in the currently collected backup cycle, analyze the backup evaluation indicators of all cloud servers specifically set up for data backup by the service platform in the current backup cycle, and generate a preliminary backup strategy for each authorized user in the current backup cycle based on the parameter objects of each hardware device or virtual device belonging to the user according to the preset allocation generation rules;

[0019] Step 4: For each authorized user, based on the preliminary backup strategy of the parameter objects of each hardware device or virtual device belonging to the user in the current backup cycle, transmit the monitoring data of the corresponding parameter objects collected in the current backup cycle to the corresponding cloud server for storage backup.

[0020] Advantages of the present invention:

[0021] (1) By setting up a monitoring service module, the present invention can collect the monitoring data of the parameter objects of all hardware devices and virtual devices belonging to each authorized user in real time. For any authorized user, the backup extraction unit extracts the monitoring data of the parameter objects of the corresponding hardware device or virtual device stored in the corresponding backup cycle from the monitoring data storage module according to the backup cycle specified by the authorized user for the parameter objects of each hardware device or virtual device belonging to the user. Then, the backup allocation unit allocates the cloud servers used for data backup to the monitoring data of the parameter objects corresponding to each backup cycle for each parameter object. In this way, for different parameter objects of different devices, the monitoring data is backed up at different frequencies according to the user's needs, avoiding excessive waste of the platform's transmission resources during the backup process, improving the efficiency of data backup, and making data backup more intelligent;

[0022] (2) When the backup distribution unit of the present invention allocates monitoring data of parameter objects corresponding to each backup cycle to a cloud server for data backup corresponding to each backup cycle, the current states of each cloud server are evaluated by analyzing the machine load, packet loss rate, network latency, and data transmission rate of each cloud server at the current moment, and multiple cloud servers for current pre-backup are selected. Combining the data capacity of the pre-backup data, the optimal backup data volume is planned for the selected multiple cloud servers. For the partial data backed up by each cloud server, multiple redundant backup cloud servers are selected for it from other cloud servers. In this way, on the one hand, the data backed up to each cloud server is re-segmented and backed up in multiple other cloud servers, which can avoid the risk of data loss due to the downtime of a certain cloud server and retain the advantages of distributed backup storage. On the other hand, the number of cloud servers to which the monitoring data of each parameter object is backed up and redundantly backed up is reasonably planned, making data backup more intelligent. Brief Description of the Drawings

[0023] The present invention will be further described below with reference to the accompanying drawings.

[0024] Figure 1 is the system block diagram of the present invention;

[0025] Figure 2 is the method flow chart of the present invention. Detailed Embodiments

[0026] The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0027] As Figure 1 、 2 shown, a data backup system and method for a comprehensive monitoring SaaS service platform include a monitoring service module, a monitoring data storage module, and a planning backup module;

[0028] The monitoring service module is used to provide monitoring services to authorized users. For an authorized user, the monitoring service module collects monitoring data of parameter objects of all hardware devices and virtual devices belonging to the authorized user in real time and generates service monitoring data of the authorized user based on it;

[0029] The hardware device refers to a physical host that provides resources such as computing, network, and storage for cloud host instances. The virtual device refers to a virtual machine instance running on the physical host, which has an independent IP address, can access the public network, and run application services. The authorized user refers to a user who has been trusted and authorized by the service platform to log in;

[0030] The parameter object of a hardware device includes the physical host name, platform name, physical machine IP, device status, CPU usage rate, memory usage rate, broadband upload and download, packet reception count, and creation time. Here, it should be noted that the platform name included in the hardware device parameter object refers to the name of the platform that provides the rental service of this hardware device;

[0031] The parameter object of a virtual device includes the virtual device name, platform name, elastic IP, change device status, CPU usage rate, memory usage rate, disk usage rate, IPV4 address, MAC address, cluster, CPU architecture, creation time, etc. Here, it should be noted that the platform name included in the virtual device parameter object refers to the name of the platform that provides the rental service of the physical host on which it runs;

[0032] The monitoring data of the parameter object of a hardware device or virtual device refers to its monitoring value;

[0033] The monitoring service module transmits the service monitoring data of all authorized users generated at the current moment collected to the monitoring data storage module;

[0034] The monitoring data storage module is used to store the service monitoring data of all authorized users. After receiving the service monitoring data of all authorized users transmitted by the monitoring service module at the current moment, it permanently stores them;

[0035] The planning backup module is used to securely transmit the service monitoring data of all authorized users received to the cloud backup storage center for backup. The planning backup module includes a backup extraction unit, a backup distribution unit, and a backup transmission unit;

[0036] For each authorized user, the backup extraction unit stores the backup period specified by the corresponding authorized user for each parameter object of its hardware device and virtual device. In an embodiment of the present invention, the time length of the backup period can be 1 second, 1 minute, 10 minutes, 1 hour, 12 hours, 1 day, 3 days, 7 days, 1 month, half a year, 1 year, and 3 years;

[0037] For any authorized user, the backup extraction unit extracts the monitoring data of the parameter objects of the corresponding hardware device or virtual device stored during the corresponding backup period from the monitoring data storage module according to the backup period specified by the authorized user for each parameter object of its affiliated hardware device or virtual device, and transmits it to the backup distribution unit;

[0038] Taking a parameter object of a hardware device of an authorized user as an example, after receiving the monitoring data of the parameter object of this hardware device stored in the monitoring data storage module during the current backup period, the backup distribution unit generates a preliminary backup policy of this authorized user based on this parameter object of this hardware device for the previous backup period according to the preset distribution generation rule. It should be noted that the backup period here refers to the backup period specified by this authorized user for this parameter object of this hardware device;

[0039] The specific distribution rule for distributing the monitoring data of this hardware device's hardware parameters stored in the monitoring data storage module during the current backup period is as follows:

[0040] S11: Mark all cloud servers specially set up for data backup by the service platform as A1, A2,..., Aa in sequence, where a≥1;

[0041] S12: Calculate and obtain the backup evaluation index D1 of cloud server A1 according to the preset first calculation rule. The specific calculation rule is as follows:

[0042] S121: Obtain the machine loads B1, B2, and B3 of cloud server A1 at the current moment within the past P1, P2, and P3 times;

[0043] Obtain the packet loss rate B4, network delay B5 of cloud server A1 at the current moment, and the data transmission rates B6, B7, and B8 within the past P1, P2, and P3 times. The P1, P2, and P3 are respectively the preset first, second, and third backtracking time thresholds. Preferably, the values of P1, P2, and P3 are 5, 10, and 15 minutes;

[0044] S12: Calculate and obtain the machine load index C1 of cloud server A1 during the current backup period using the formula C1=(B1 + B2 + B3) / 3;

[0045] Using the formula Calculate and obtain the transmission capacity index C2 of cloud server A1 during the current backup period. The ɑ1 and ɑ2 are respectively the preset first and second adjustment factors, and the Bmean is the data transmission rate with the middle value among the data transmission rates B6, B7, and B8;

[0046] S123: Using the formula Calculate and obtain the backup evaluation metric D1 of cloud server A1 for the current backup period, where β1 and β2 are respectively the preset first and second evaluation proportion factors, Baver is the machine load among B1, B2, and B3 with the middle value in terms of size, that is, Baver is the machine load among B1, B2, and B3 that is greater than Bmin and less than Bmax, and Bmin and Bmax are respectively the minimum and maximum values among the machine loads B1, B2, and B3;

[0047] It should be noted here that the backup evaluation metric is defined artificially and is used to refer to the evaluation index obtained based on the load and transmission capabilities of the cloud server during the current backup period;

[0048] S13: Calculate and obtain the backup evaluation metrics D1, D2,..., Da of cloud servers A1, A2,..., Aa in sequence according to S12;

[0049] S14: Calculate and obtain the pre-allocated data volume G1 of the pre-backup cloud server and the number H1 of pre-backup redundant servers for the current backup period belonging to this authorized user based on this hardware device and this hardware parameter according to the preset second calculation rule, specifically as follows:

[0050] S141: Obtain the number E1 of backup evaluation metrics less than or equal to P4 from the backup evaluation metrics D1, D2,..., Da, where P4 is the evaluation metric comparison threshold for preset screening and allocation of cloud servers;

[0051] S142: Obtain the data capacity size F1 of the monitoring data of this hardware device and this hardware parameter stored in the monitoring data storage module for the current backup period received by the backup allocation unit;

[0052] S143: Use the formula to calculate and obtain the pre-allocated data volume G1 of the pre-backup cloud server for the current backup period belonging to this authorized user based on this hardware device and this hardware parameter;

[0053] At the same time, based on the inequality calculate the value of x, round down the value of x, and re-calibrate the rounded result as the number H1 of pre-backup redundant servers for the current backup period belonging to this authorized user based on this hardware device and this hardware parameter. P5 is the preset redundant server screening data capacity threshold, and here P5 is greater than G1 to ensure that the value of x and the value of E1 differ by at least 1;

[0054] S15: Sort the backup evaluation metrics D1, D2,..., Da in ascending order and re-calibrate them as I1, I2,..., Ia;

[0055] S16: Store the current backup period into the monitoring data storage module. Cut the monitoring data of this hardware device and this hardware parameter into E1 backup monitoring data. After the cutting is completed, bind the E1 backup monitoring data and the cloud servers corresponding to the backup evaluation metrics I1, I2, ..., IE1 according to the pre-set backup binding rules to obtain E1 backup data packets. The backup binding rules are as follows:

[0056] Based on any one of the E1 backup monitoring data, bind it to the cloud server corresponding to any one of the backup evaluation metrics I1, I2, ..., IE1 to obtain a backup data packet. It should be noted that the cloud servers bound to each backup monitoring data are different from each other;

[0057] S17: Based on the E1 backup data packets, bind them according to the pre-set redundant backup binding rules to obtain H1 redundant component backup data packets for each backup data packet, specifically as follows:

[0058] S171: Take one backup data packet as an example, re-label the backup monitoring data carried in this backup data packet as J1, and re-label the cloud server as K1;

[0059] S172: Equally divide the backup monitoring data J1 into H1 redundant component backup data, and then bind these H1 redundant component backup data to the cloud servers corresponding to the backup evaluation metrics I1, I2, ..., IE1 except for the cloud server K1 according to the pre-set component binding rules to obtain H1 redundant component backup data packets based on this backup data packet. The pre-set component binding rules are as follows:

[0060] Based on any one of the H1 redundant component backup data, bind it to the cloud server corresponding to any one of the backup evaluation metrics I1, I2, ..., IE1. The cloud server bound here does not include the cloud server K1, and obtain a redundant component backup data packet. Based on this, obtain H1 redundant component backup data packets;

[0061] S173: According to S171 to S172, based on the E1 backup data packets, obtain H1 redundant component backup data packets for each backup data packet;

[0062] S18: Merge them according to the pre-set merging rules to obtain redundant component data packets based on the cloud servers L1, L2, ..., LL, specifically as follows:

[0063] S181: Based on the H1 redundant component backup data packets of each backup data in the E1 backup data packets, obtain all the cloud servers included therein, and label them as L1, L2, ..., LL in sequence, where L ≥ 1;

[0064] The cloud servers L1, L2, ..., LL here are deduplicated and are all different cloud servers;

[0065] S182: Based on the H1 redundant component backup data packets of each backup data in the E1 backup data packets, obtain all the redundant component backup data bound to the cloud server L1 therein, merge them to obtain redundant component data, and bind the redundant component data to the cloud server L1 to obtain a redundant component data packet based on the cloud server L1;

[0066] S183: Calculate in sequence according to S181 to S182 to obtain redundant component data packets based on the cloud servers L1, L2, ..., LL;

[0067] The current moment in S12 refers to the moment when the backup allocation unit receives the monitoring data of this hardware device and this hardware parameter stored in the monitoring data storage module during the current backup cycle;

[0068] The backup allocation unit generates a preliminary backup policy for this authorized user based on this hardware device and this hardware parameter during the current backup cycle according to the E1 backup data packets of this authorized user based on this hardware device and this hardware parameter and the redundant component data packets based on the cloud servers L1, L2, ..., LL, and transmits it to the backup transmission unit;

[0069] The IP addresses of all cloud servers are pre-stored in the backup transmission unit. After receiving the preliminary backup policy for this authorized user based on this hardware device and this hardware parameter during the current backup cycle transmitted by the backup allocation unit, the backup transmission unit transmits the monitoring data of this hardware device and this hardware parameter stored in the monitoring data storage module during the current backup cycle according to the preset transmission rules, specifically as follows:

[0070] SS1: For a backup data packet carried in the preliminary backup policy for this authorized user based on this hardware device and this hardware parameter during the current backup cycle, obtain the cloud server carried in the backup data packet, obtain the IP address of the cloud server, and transmit the backup monitoring data bound to the cloud server carried in the backup data packet to the cloud server for backup storage;

[0071] SS2: For a redundant component data packet carried in the preliminary backup policy for this authorized user based on this hardware device and this hardware parameter during the current backup cycle, obtain the cloud server carried in the redundant component data packet, obtain the IP address of the cloud server, and transmit the redundant component data bound to the cloud server carried in the redundant component data packet to the cloud server for backup storage;

[0072] Based on the above SS1 and SS2, all backup data packets carried in the preliminary backup policy of the authorized user belonging to the current backup period based on the hardware parameters of the hardware device and the redundant component data packets carrying backup monitoring data or redundant component data are transmitted to the corresponding cloud server for backup storage.

[0073] In the description of the specification, the description referring to terms such as "one embodiment", "example", "specific example", etc. means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in a suitable manner in any one or more embodiments or examples.

[0074] The above content is only an example and illustration of the present invention. Those skilled in the art of the present technology can make various modifications or supplements to the described specific embodiments or use similar methods for substitution, as long as they do not deviate from the invention or exceed the scope defined by the claims of the present invention, they should fall within the protection scope of the present invention.

[0075] The above has described in detail one embodiment of the present invention, but the content described is only the preferred embodiment of the present invention and cannot be considered as limiting the scope of implementation of the present invention. All equivalent changes and improvements made according to the scope of the application of the present invention should still fall within the scope covered by the patent of the present invention.

Claims

1. A data backup system for a comprehensive monitoring SaaS service platform, characterized in that, Including: A monitoring service module, which is used to provide a monitoring service to authorized users. For an authorized user, the monitoring service module collects in real time the monitoring data of the parameter objects of all the hardware devices and virtual devices belonging to the authorized user. A monitoring data storage module, which is used to permanently store the monitoring data of the parameter objects of all the hardware devices and virtual devices belonging to all authorized users. For each authorized user, a backup planning module is used to plan the backup of the monitoring data of the parameter objects of all the hardware devices and virtual devices belonging to the user. The backup planning module includes a backup extraction unit and a backup allocation unit. For any authorized user, the backup extraction unit extracts from the monitoring data storage module the monitoring data of the parameter objects of the corresponding hardware device or virtual device stored during the corresponding backup period according to the backup period specified by the authorized user for the parameter object of each hardware device or virtual device belonging to the user, and transmits it to the backup allocation unit. For a hardware device belonging to an authorized user, after the backup allocation unit receives the monitoring data of the hardware parameters of the hardware device stored in the monitoring data storage module during the current backup period, it generates a preliminary backup policy for the authorized user based on the hardware parameters of the hardware device during the current backup period according to a preset allocation generation rule. The specific generation method is as follows: S11: Mark all the cloud servers specially set up for data backup on the service platform as A1, A2,..., Aa, where a≥1. S12: Calculate and obtain the backup evaluation indicators D1, D2,..., Da of all the cloud servers A1, A2,..., Aa according to a preset first calculation rule. S13: Calculate and obtain the pre-allocated data volume G1 of the preliminary backup cloud server and the number H1 of the preliminary backup redundant servers for the authorized user based on the hardware parameters of the hardware device during the current backup period according to a preset second calculation rule. S14: Sort the backup evaluation indicators D1, D2,..., Da in ascending order and re-calibrate them as I1, I2,..., Ia. S15: Cut the monitoring data of the hardware parameters of the hardware device stored in the monitoring data storage module during the current backup period into E1 backup monitoring data. After cutting, bind the E1 backup monitoring data and the cloud servers corresponding to the backup evaluation indicators I1, I2,..., IE1 according to a preset backup binding rule to obtain E1 backup data packets. S16: Based on the E1 backup data packets, bind H1 redundant component backup data packets for each backup data packet according to a preset redundant backup binding rule. S17: Merge the redundant component data packets of each cloud server that have been de-duplicated according to a preset merging rule.

2. The data backup system for the comprehensive monitoring SaaS service platform according to claim 1, characterized in that, In the above S12, the preset first calculation rule for calculating and obtaining the backup evaluation indicator D1 of the cloud server A1 is as follows: S121: Obtain the machine loads B1, B2, and B3 of the cloud server A1 at the past times P1, P2, and P3 at the current moment. Obtain the packet loss rate B4 and network latency B5 of cloud server A1 at the current moment, as well as the data transmission rates B6, B7, and B8 within the past P1, P2, and P3 time periods, where P1, P2, and P3 are the preset first, second, and third retrospective time thresholds respectively; S122: Calculate and obtain the machine load index C1 of cloud server A1 in the current backup period using the formula C1 = (B1 + B2 + B3) / 3; Using the formula calculate and obtain the transmission capacity index C2 of the cloud server in the current backup period, where ɑ1 and ɑ2 are respectively preset first and second adjustment factors, and Bmean is the data transmission rate among the data transmission rates B6, B7, and B8 whose median size is in the middle; S123: Use the formula to calculate and obtain the backup evaluation metric D1 of cloud server A1 for the current backup period. The β1 and β2 are respectively the preset first and second evaluation ratio factors, and the Baver is the machine load among the machine loads B1, B2, and B3 that has the middle value in terms of magnitude.

3. The data backup system for the comprehensive monitoring SaaS service platform according to claim 1, characterized in that, For the said S13, the preset second calculation rule for calculating and obtaining the pre-allocated data volume G1 of the pre-backup cloud server and the number H1 of pre-backup redundant servers of this authorized user based on this hardware device and this hardware parameter in the current backup period is as follows: S131: Obtain the number E1 of backup evaluation metrics less than or equal to P4 from the backup evaluation metrics D1, D2,..., Da, where P4 is the evaluation metric comparison threshold for preset screening and allocation of cloud servers; S132: Obtain the data capacity size F1 of the monitoring data of this hardware device and this hardware parameter stored in the monitoring data storage module received by the backup allocation unit in the current backup period; S133: Use the formula to calculate and obtain the pre-allocated data volume G1 of the pre-backup cloud server of the authorized user for the current backup period based on the hardware device and the hardware parameter. At the same time, based on the inequality calculate and obtain the value of x, round down the value of x, and re-calibrate the rounding result as the number H1 of the backup redundant servers belonging to the authorized user based on the hardware device and the hardware parameters during the current backup period. The P5 is a preset redundant server screening data capacity threshold.

4. The data backup system for the comprehensive monitoring SaaS service platform according to claim 1, characterized in that For the said S16, the preset redundancy binding rule for binding H1 redundant component backup data packets for each backup data packet is as follows: S161: Based on one backup data packet among the E1 backup data packets, re-label the backup monitoring data carried in this backup data packet as J1 and the cloud server as K1; S162: Equally divide the backup monitoring data J1 into H1 redundant component backup data, and then bind these H1 redundant component backup data and the other cloud servers except the cloud server K1 corresponding to the backup evaluation metrics I1, I2,..., IE1 according to the preset component binding rule to obtain H1 redundant component backup data packets based on this backup data packet; S163: According to S161 to S162, based on the E1 backup data packets, obtain H1 redundant component backup data packets for each backup data packet.

5. The data backup system and method for the comprehensive monitoring SaaS service platform according to claim 1, characterized in that, The preset merging rule is as follows: S171: Based on the H1 redundant component backup data packets of each backup data among the E1 backup data packets, obtain all the cloud servers included therein, and label them as L1, L2,..., LL in sequence, where L ≥ 1; S172: Obtain all the redundant component backup data bound to the cloud server L1, merge them to obtain redundant component data, and bind this redundant component data and the cloud server L1 to obtain a redundant component data packet based on the cloud server L1; S173: Calculate and obtain the redundant component data packets based on the cloud servers L1, L2,..., LL in sequence according to S171 to S172.

Images