Data backup method, device and equipment and computer storage medium

Abstract

The embodiment of the invention provides a data backup method and device, equipment and a computer storage medium. In the embodiment of the invention, each device in the backup pool forms a chained relationship based on the data backup logic, any device is the main backup device of the previous device and is used for carrying out data backup on the previous device, and the data backup is carried out on the previous device based on the current storage performance and the predicted storage performance of each device. Whether each device can complete the data backup task for the previous device is comprehensively judged, at least one target slave backup device is called for any device whose storage performance does not meet the data backup requirement to assist the device to complete data backup together, the data bearing capacity of each device in a backup pool can be fully utilized, and the data backup efficiency is improved. The data backup pressure of each main backup device in the backup pool is effectively reduced, the safety of the self-bearing service of each device is ensured, and the stability and disaster tolerance of a service system are enhanced.

Description

Technical Field

[0001] This invention belongs to the field of computer technology, and in particular relates to a data backup method, apparatus, device, and computer storage medium. Background Technology

[0002] Data backup is the foundation of disaster recovery. It refers to the process of transferring all or part of the data to other storage media to prevent data loss due to system failure. Typically, in business systems, to ensure the reliability of business operations, a pair of computer devices are set up as backup devices for each other. However, as the data volume of business systems increases, the amount of data to be backed up when the paired computer devices perform data backups also increases significantly. Furthermore, without considering the storage performance of the computer devices themselves, this can lead to excessive data pressure on the computer devices, and may even result in the backup data exceeding the storage capacity of the computer devices, thereby affecting the security and stability of the business system. Summary of the Invention

[0003] This invention provides a data backup method, apparatus, device, and computer storage medium that can fully utilize the data carrying capacity of each device in the backup pool, reduce the data backup pressure of each primary backup device in the backup pool, and ensure the security of the services carried by each device.

[0004] In a first aspect, embodiments of the present invention provide a data backup method, the method comprising: Determine whether each device in the backup pool meets the first condition. The backup pool includes N devices, and each device forms a chain relationship based on data backup logic. Any device in this chain relationship is the primary backup device of the preceding device and is used to perform data backup on the preceding device. The first condition is used to indicate that the current storage performance and future storage performance of the device meet the data backup requirements. In response to the first condition being met by the i-th device in the backup pool, a full backup of the data of the (i-1)-th device is performed on the i-th device, where i and N are positive integers and 2 ≤ i ≤ N; In response to the j-th device in the backup pool not meeting the first condition, at least one target backup device is invoked to assist the j-th device in backing up the data of the (j-1)-th device. The target backup device is a device in the backup pool that has completed a full backup task, where j and N are positive integers and 2 ≤ j ≤ N.

[0005] Secondly, embodiments of the present invention provide a data backup device, the device comprising: The judgment module is used to determine whether each device in the backup pool meets the first condition. The backup pool includes N devices, and each device forms a chain relationship based on data backup logic. Any device in the chain relationship is the primary backup device of the preceding device and is used to perform data backup on the preceding device. The first condition is used to indicate that the current storage performance and future storage performance of the device meet the data backup requirements. The first backup module is used to perform a full backup of the data of the (i-1)th device on the i-th device in response to the i-th device in the backup pool meeting the first condition, where i and N are positive integers and 2≤i≤N; The second backup module is used to respond to the j-th device in the backup pool not meeting the first condition by calling at least one target backup device to assist the j-th device in backing up the data of the (j-1)-th device. The target backup device is a device in the backup pool that has completed a full backup task, where j and N are positive integers and 2≤j≤N.

[0006] Thirdly, embodiments of the present invention provide a computer device, the device comprising: a processor, and a memory storing computer program instructions; the processor reads and executes the computer program instructions to implement any of the above data backup methods.

[0007] Fourthly, embodiments of the present invention provide a computer storage medium storing computer program instructions, which, when executed by a processor, implement any of the above-described data backup methods.

[0008] Fifthly, embodiments of the present invention provide a computer program product in which instructions, when executed by a processor of an electronic device, cause the electronic device to perform any of the aforementioned data backup methods.

[0009] In this embodiment of the invention, the devices in the backup pool form a chain relationship based on data backup logic. Each device is the primary backup device of its predecessor and is used to back up the data of its predecessor. Based on the current storage performance and predicted storage performance of each device, it is comprehensively judged whether each device can complete the data backup task of its predecessor. For any device whose storage performance does not meet the data backup requirements, at least one target backup device is called to assist it in completing the data backup. This can make full use of the data carrying capacity of each device in the backup pool, effectively reduce the data backup pressure of each primary backup device in the backup pool, ensure the security of the business carried by each device, and enhance the stability and disaster recovery capability of the business system. Attached Figure Description

[0010] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments of the present invention will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0011] Figure 1 This is a schematic diagram of the implementation environment of a data backup method provided in an embodiment of the present invention; Figure 2 This is a flowchart of a data backup method provided in an embodiment of the present invention; Figure 3 This is a schematic diagram of an equal-weighted backup provided in an embodiment of the present invention; Figure 4 This is a schematic diagram of a relay backup provided in an embodiment of the present invention; Figure 5 This is a flowchart of batch data backup in a dial-up service scenario provided by an embodiment of the present invention; Figure 6 This is a schematic diagram of a data backup device structure provided in an embodiment of the present invention; Figure 7 This is a schematic diagram of the hardware structure of a computer device provided in an embodiment of the present invention. Detailed Implementation

[0012] The features and exemplary embodiments of various aspects of the present invention will now be described in detail. To make the objectives, technical solutions, and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are merely intended to explain the present invention and not to limit the present invention. For those skilled in the art, the present invention can be practiced without some of these specific details. The following description of the embodiments is merely to provide a better understanding of the present invention by illustrating examples of the invention.

[0013] It should be noted that, in this document, relational terms such as "first" and "second" are used merely 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..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the aforementioned elements.

[0014] To address the problems of existing technologies, embodiments of the present invention provide a data backup method, apparatus, device, and computer storage medium that can fully utilize the data carrying capacity of each device in the backup pool, effectively reduce the data backup pressure on each primary backup device in the backup pool, and enhance the stability and disaster recovery capabilities of the business system. The following detailed description of this solution is provided in conjunction with the accompanying drawings.

[0015] Figure 1 This is a schematic diagram illustrating the implementation environment of a data backup method provided in an embodiment of the present invention. For example... Figure 1 As shown, in one embodiment, this solution can be deployed in a backup pool 101, which may include N devices 102, each of which has data storage capabilities, where N is a positive integer. In this embodiment, the devices 102 form a chain relationship based on data backup logic, where each device in the chain is the primary backup device of the preceding device, used to back up data from that preceding device. Figure 1 As shown, the second device in the backup pool is the primary backup device of the first device, the third device is the primary backup device of the second device, and taking the m-th device as an example, the m-th device is the primary backup device of the (m-1)-th device. Similarly, the first device is the primary backup device of the N-th device. In one embodiment, each device in the backup pool can correspond to N-2 slave backup devices. That is, for any device, all devices in the backup pool other than that device and its corresponding primary backup device can serve as slave backup devices for that device. Slave backup devices can be used to share the data backup pressure of the primary backup device and work together with the primary backup device to complete the data backup task. Figure 1 As shown, devices 3 through N in the backup pool are slave backup devices of device 1; devices 4 through N and device 1 are slave backup devices of device 2; and devices 2 through N-1 are slave backup devices of device N. In this embodiment of the invention, the traditional pairing of devices for mutual backup is extended into a chained backup. All devices in the backup pool can form a chain based on the master-slave relationship. In this chained relationship, there are N-2 slave backup devices that assist the master backup device in sharing the data backup pressure, which can effectively reduce the backup pressure on the master backup device, improve the utilization efficiency of devices in the entire backup pool, and improve the availability and disaster recovery capabilities of the business system.

[0016] In one embodiment, the aforementioned device 102 may be a portable computer, desktop computer, server, etc. For example, the server may be a BRAS (Broadband Remote Access Server), a standalone physical server, a server cluster consisting of multiple physical servers, or a cloud server providing cloud services, network services, big data, and other cloud computing services. This embodiment of the invention does not limit the specific type of server. In one embodiment, the devices 102 in the backup pool and the user terminal may be connected via wired or wireless communication. For example, any device 102 may receive a data backup request from the user terminal and, in response to the request, transmit the data to other devices in the backup pool 101 to complete the data backup. For example, the computer device 102 may also send the data backup result to the user terminal. In one embodiment, the backup pool 101 may further include a management device, which may be used to instruct each device 102 to perform data backup. For example, the control device can instruct each device 102 to perform data backup based on data backup instructions sent by the user terminal or at a first preset frequency. It can also obtain the data backup results of each device 102 and send the data backup results to the user terminal. This embodiment of the invention does not limit the scope of the invention. The first preset frequency can be set by the developers.

[0017] Figure 2 This is a flowchart of a data backup method provided in an embodiment of the present invention. This method can be applied to the above-mentioned... Figure 1 The implementation environment shown is as follows: Figure 2 As shown, the method may include the following steps: S201. Determine whether each device in the backup pool meets the first condition. The backup pool includes N devices, and each device forms a chain relationship based on data backup logic. Any device in the chain relationship is the primary backup device of the preceding device and is used to perform data backup on the preceding device. The first condition is used to indicate that the current storage performance and future storage performance of the device meet the data backup requirements.

[0018] S202. In response to the first condition being met by the i-th device in the backup pool, a full backup of the data of the (i-1)-th device is performed on the i-th device, where i and N are positive integers and 2 ≤ i ≤ N.

[0019] S203. In response to the j-th device in the backup pool not meeting the first condition, at least one target backup device is invoked to assist the j-th device in backing up the data of the (j-1)-th device. The target backup device is a device in the backup pool that has completed a full backup task, where j and N are positive integers and 2≤j≤N.

[0020] In this embodiment of the invention, the devices in the backup pool form a chain relationship based on data backup logic. Each device is the primary backup device of its predecessor and is used to back up the data of its predecessor. Based on the current storage performance and predicted storage performance of each device, it is comprehensively judged whether each device can complete the data backup task of its predecessor. For any device whose storage performance does not meet the data backup requirements, at least one target backup device is called to assist it in completing the data backup. This can make full use of the data carrying capacity of each device in the backup pool, effectively reduce the data backup pressure of each primary backup device in the backup pool, ensure the security of the business carried by each device, and enhance the stability and disaster recovery capability of the business system.

[0021] In one embodiment, the above method can be executed by any device in the implementation environment. The device can be a computer device, a BRAS device, or a device with BRAS device control functions. This embodiment of the invention does not limit this. In this embodiment of the invention, only a computer device is used as the execution subject to describe the specific implementation of the above steps.

[0022] In step S201, the computer device determines whether each device in the backup pool meets the first condition.

[0023] In one embodiment, the computer device can receive a data backup request and, in response to the request, determine whether the storage performance of each device in the backup pool meets the data backup requirements. The data backup request can be sent by a user terminal or any computer device, or by any device in the backup pool. For example, a failure in any device in the backup pool can trigger a data backup request to be sent to that computer device. This embodiment does not limit which device sends the data backup request. In one embodiment, the data backup request can instruct data backup to be performed on one or more devices in the backup pool. For example, the data backup request can carry device identifiers of one or more devices to be backed up. These device identifiers can be used to uniquely identify a device in the backup pool. This embodiment does not limit the number of devices performing data backup; in this embodiment, data backup is performed on all devices in the backup pool.

[0024] In this embodiment of the invention, a computer device can determine whether the storage performance of the device meets the data backup requirements by judging whether the device meets a first condition. In one embodiment, a state factor k and a predicted state factor k can be constructed. 预测The storage performance of a device is quantified. A state factor indicates the current storage performance of the device, and a predicted state factor indicates the predicted storage performance of the device over a future target time period. In this embodiment, the computer device can determine the state factor and predicted state factor of each device, and based on the values ​​of these factors, determine whether each device meets the first condition. This first condition can be set by the developer, and this embodiment does not limit its implementation. In this embodiment, by constructing state factors and predicted state factors, the storage performance of a device is quantified, thereby simplifying the device storage performance determination process and improving the efficiency of the computer device's determination.

[0025] In one embodiment, the determination process in step S201 above may include the following steps: Step 1: The computer equipment determines the state factors of each device based on the current operating data of each device.

[0026] The current operating data includes at least the current egress utilization, current memory utilization, and current CPU (Central Processing Unit) utilization. In one embodiment, the computer device can obtain the device's operating data through a network management module. For example, the computer device can send a data acquisition request to the network management module, indicating that it needs to acquire operating data for one or more devices. In response to receiving the data acquisition request, the network management module acquires the current egress utilization, current memory utilization, and current CPU utilization for one or more devices. Of course, the operating data may also include other data items, and this embodiment of the invention does not limit this. In this embodiment of the invention, determining the state factor based on multiple actual operating data of the device can ensure the accuracy of device performance quantification.

[0027] In this embodiment of the invention, if the current egress utilization, current memory utilization, and current CPU utilization of the device are all less than a first reference value, then the current storage performance of the device is determined to be good, and the state factor k of the device is set to 1; if any one of the current egress utilization, current memory utilization, and current CPU utilization of the device is greater than the first reference value, then the current storage performance of the device is determined to be poor, and the state factor k of the device is set to 0. The first reference value can be set by the developer; in this embodiment of the invention, the first reference value is described as 50%.

[0028] Step 2: The computer equipment determines the predicted state factor of each device based on the predicted operating data of each device within the target time period in the future.

[0029] The predicted runtime data includes at least predicted peak egress utilization, predicted peak memory utilization, and predicted peak CPU utilization. This target time period can be set by the developers, for example, it could be the next hour.

[0030] In one embodiment, the predicted operating data is obtained from a performance prediction model used to predict the operating data of the device within any future time period. This performance prediction model can be a model built on a convolutional neural network, trained iteratively multiple times using training data, enabling it to predict the device's operating status within future time periods.

[0031] In one embodiment, a computer device can iteratively train the performance prediction model based on the historical operating data of each device in the backup pool, the correspondence between the historical operating data and time, and operating environment data. The historical operating data includes at least egress utilization, memory utilization, CPU utilization, and peak user data, while the operating environment data includes at least one of weather data, seasonal data, holiday data, and public event data. For example, the computer device can obtain the historical operating data and operating environment data of each device in the backup pool through a network management module. For instance, the network management module can sample the operating data of each device in the backup pool at a second preset frequency, i.e., obtain the egress utilization, memory utilization, CPU utilization, user data, etc., of each device at the current moment, and store them as historical operating data for subsequent data retrieval. The second preset frequency is set by the developers; for example, it can be set to sample data every 5 minutes. In one embodiment, the computer device can construct multiple training datasets based on the historical operating data of each device, the correspondence between the historical operating data and time, and operating environment data, and apply these training datasets to iteratively train the performance prediction model. For example, a computer device can input training data into the performance prediction model, which predicts the device's operating data at a certain point in time. The computer device obtains the error value between the operating data predicted by the performance prediction model and the actual operating data of the device at that point in time, and updates the parameters of the performance prediction model based on the error value. The computer device can perform multiple rounds of iterative training on the performance prediction model until the error value of the output result of the performance prediction model meets a preset condition, thus obtaining a trained performance model. The preset condition can be set by the developer, and this embodiment of the invention does not limit the number of rounds of model iterative training or the specific process of iterative training.

[0032] In one embodiment, a computer device can obtain the predicted operating data of each device through the trained performance prediction model. For example, the performance prediction model can output the predicted operating data of the devices at a third preset frequency, wherein the third preset frequency can be set by the developer, and this embodiment of the invention does not limit this. For instance, the performance prediction model can output results once per hour to obtain the predicted peak utilization rate of the output, the predicted peak utilization rate of memory, and the predicted peak utilization rate of CPU within the next hour.

[0033] In this embodiment of the invention, training data is constructed using historical operating data and operating environment data of each device in the backup pool. The training data has high authenticity and accuracy, resulting in a high accuracy performance prediction model, which in turn improves the accuracy of subsequent device performance judgments.

[0034] In this embodiment of the invention, if the predicted egress utilization, predicted memory utilization, and predicted CPU utilization of the device are all less than the first reference value, then the predicted storage performance of the device is determined to be good, and the predicted state factor k of the device is determined to be... 预测 The value is 1; if any one of the predicted egress utilization, predicted memory utilization, or predicted CPU utilization of the device is greater than this first reference value, then the predicted storage performance of the device is determined to be poor, and the predicted state factor k of the device is set to 1. 预测 The value is 0.

[0035] Step 3: The computer equipment matches the state factors and predicted state factors of each device with the first condition to determine whether each device meets the first condition.

[0036] In this embodiment of the invention, the first condition can be set as the device's state factor k and the predicted state factor k. 预测 The values ​​of both are 1. If the device's state factor k and the predicted state factor k are both 1... 预测 If both the current state factor k and the predicted state factor k are 1, satisfying the first condition, then the current storage performance and predicted storage performance of the device are both good, and the device meets the data backup requirements. 预测 If at least one of the values ​​is not 1, then at least one of the current storage performance or predicted storage performance of the device is poor, and the device does not meet the data backup requirements.

[0037] In this embodiment of the invention, by first determining whether the storage performance of each device in the backup pool meets the data backup requirements, and then executing subsequent data backup steps based on the storage performance of the devices, it is possible to avoid excessive data pressure on the devices after completing the main backup task, which could affect the operation of the business systems they support.

[0038] In step S202, in response to the first condition being met by the i-th device in the backup pool, the computer device performs a full backup of the data of the (i-1)-th device on the i-th device.

[0039] Where i is a positive integer, 2≤i≤N.

[0040] In one embodiment, the computer device determines that the current storage performance and future storage performance of the i-th device both meet the data backup requirements, and performs a full backup of the data of the (i-1)-th device on the i-th device. The data of the (i-1)-th device may include multiple user data sets, each containing user entries, sessions, IP (Internet Protocol) addresses, etc. Taking a backup pool where all devices are BRAS devices as an example, a backup channel can be established between the i-th device and the (i-1)-th device to transmit the data to be backed up. Of course, the computer device can also perform data backup in other ways, and this embodiment of the invention does not limit this method.

[0041] In this embodiment of the invention, for a device whose storage performance meets the data backup requirements, performing a full data backup can fully utilize the device's storage performance and ensure the completion of the data backup task.

[0042] In step S203, in response to the fact that the j-th device in the backup pool does not meet the first condition, the computer device calls at least one target from the backup device to assist the j-th device in backing up the data of the (j-1)-th device.

[0043] Where j is a positive integer, 2≤j≤N. The target backup device is a device in the backup pool that has completed a full backup task, that is, the target backup device is a device in the backup pool that has completed a primary backup task.

[0044] In one embodiment, the computer device identifies at least one target from a backup device, and the process of backing up data includes the following steps.

[0045] Step 1: In response to the fact that device j does not meet the first condition, the computer device backs up part of the data of device j-1 based on the performance limit of device j.

[0046] The device's performance limit is used to indicate the maximum amount of data the device can currently back up. In one embodiment, this maximum data amount can be determined based on the maximum value among six performance metrics: current egress utilization, current memory utilization, current CPU utilization, predicted peak egress utilization, predicted peak memory utilization, and predicted peak CPU utilization. For example, the maximum value among these six performance metrics is defined as Q, and the maximum amount of data the device can currently back up is defined as P. The computer device compares Q with a second reference value. If Q is less than the second reference value, the maximum data amount P is equal to the difference between the second reference value and Q; if Q is greater than the second reference value, the maximum data amount P is determined to be 0, meaning the device has reached its performance limit and cannot perform data backup. The second reference value is set by the developers, and this embodiment of the invention does not limit its setting.

[0047] In this embodiment of the invention, for devices that do not meet the first condition, data backup is performed according to the device's performance limit, which can prevent the backup data from exceeding the device's capacity limit and avoid excessive data backup pressure on the device.

[0048] Step 2: The computer equipment adds a backup tag to the j-1 device.

[0049] In this embodiment of the invention, the computer device can add a "pending backup" tag to devices that have not completed all data backups. In one embodiment, the computer device can poll each device in the backup pool in ascending order of their serial numbers to determine whether there is a device in the backup pool carrying the "pending backup" tag, that is, to determine whether each device in the backup pool has completed data backup. In this embodiment of the invention, by adding a "pending backup" tag, the completion of the current data backup task can be accurately and efficiently determined, avoiding data loss.

[0050] Step 3: The computer equipment identifies at least one target from the backup device in the backup pool.

[0051] In this embodiment of the invention, the computer device can identify devices in the backup pool that have completed all tasks as candidate backup devices and determine whether each candidate backup device meets the first condition. In one embodiment, the computer device can filter each candidate backup device based on its state factor and predicted state factor. For example, the computer device can poll each candidate backup device in ascending order of its serial number, match the state factor and predicted state factor of each candidate backup device with the first condition, and determine whether each candidate backup device meets the first condition. The process by which the computer device determines whether a candidate backup device meets the first condition is the same as the process in step S201 described above, and will not be repeated here. In response to the existence of a candidate backup device that meets the first condition, the computer device identifies the candidate backup device that meets the condition as the target backup device.

[0052] In one embodiment, in response to the absence of a candidate backup device satisfying the first condition, the computer device determines the candidate backup device that satisfies the second condition as the target backup device. The second condition indicates that the device's current storage performance meets the data backup requirements. This second condition can be set by the developer; for example, it can be set to a state factor k of 1 and a predicted state factor k... 预测 The value of is 0. In one embodiment, in response to each candidate backup device not meeting the first condition, the computer device re-polles each candidate backup device in ascending order of sequence number to select the candidate backup device that meets the second condition as the target backup device. The process by which the computer device determines whether a candidate backup device meets the second condition is the same as the process in step 201 above, and will not be described in detail here.

[0053] In this embodiment of the invention, by determining the target backup device based on device performance, low-load devices in the backup pool can be fully utilized, allowing low-load devices to share more of the data backup pressure and improving the stability of the operation of each device in the backup pool.

[0054] Step 4: The computer device backs up the remaining data of the j-1th device from the backup device at least once.

[0055] In embodiments of the present invention, the implementation of backing up remaining data from the backup device for at least one target includes any of the following: Implementation Method 1: In response to the at least one target backup device satisfying the first condition, the computer device performs an equal-weighted backup of the remaining data on the at least one target backup device. This equal-weighted backup is also known as an average backup. In one embodiment, the computer device may divide the remaining data into multiple equal parts based on the number of target backup devices, rounding down, with the remainder data going into the last part; the computer device may back up each part of the data separately on each of the target backup devices.

[0056] Taking the example of data that needs to be backed up as user data of multiple users, in order to facilitate data utilization, computer devices store data at the user level. For example, a user's table entries, sessions, IP addresses, and other information are considered as one user data. Figure 3 This is a schematic diagram of an equal-weighted backup provided in an embodiment of the present invention, such as... Figure 3 As shown, device 302, as the primary backup device of device 301, has backed up a portion of the data in device 301 according to its performance limit. Devices 303, 304, and 305 are target backup devices that meet the first condition. Devices 303, 304, and 305 perform equal-weighted backups of the remaining data in device 301. For example, the remaining data includes user data for 212 users. The user data for these 212 users is evenly distributed across the three devices. Rounding down to the nearest integer gives 70, with a remainder of 2, device 303 backs up the user data for 70 users, device 304 backs up the user data for 70 users, and device 305, which has the largest sequence number among the three target backup devices, backs up the user data for 72 users. It should be noted that in this embodiment of the invention, only the backup of the remaining data to the target backup device with the largest sequence number is taken as an example. In some embodiments, the remaining data can also be backed up to any target backup device. This embodiment of the invention does not limit this.

[0057] Implementation Method 2: In response to the fact that at least one target backup device meets the second condition, the computer device sequentially backs up the remaining data in each of the target backup devices at the maximum performance level.

[0058] Relay backup means that the remaining data is backed up sequentially from the backup device on each target. Figure 4 This is a schematic diagram of a relay backup provided by an embodiment of the present invention, as shown below. Figure 4As shown, device 402, acting as the primary backup device for device 401, has already backed up a portion of the data in device 401 according to its performance limit. Devices 403, 404, and 405 are target backup devices that meet the second condition, and they will relay the backup of the remaining data in device 401. For example, the computer devices can relay the backup of the remaining data in ascending order of their serial numbers, according to the performance limit of each target backup device. For instance, the remaining data includes user data for 15 users; device 403's performance limit is for storing 10 users' data, device 404's is for storing 6 users' data, and device 405's is for storing 7 users' data. The computer device first performs data backup in device 403, which has the smallest serial number. It backs up 10 user data entries according to the performance limit, leaving 5 user data entries remaining. Then, it performs data backup in device 404, which has a performance limit of storing 6 user data entries. Since this is greater than the amount of remaining user data, it backs up the remaining 5 user data entries in device 404. Finally, the computer device determines that the remaining data has been backed up completely, and device 405 does not need to perform data backup.

[0059] In one embodiment, there may also be situations where the remaining data exceeds the performance limits of each target from the backup device. Figure 4 For example, if the remaining data includes user data for 40 users, the computer device first performs data backup in device 403 with the smallest serial number, backing up 10 users' data according to the performance limit, leaving 30 users' data; then it performs data backup in device 404, backing up 6 users' data according to the performance limit, leaving 24 users' data; finally, it performs data backup in device 405, backing up 7 users' data according to the performance limit, leaving 17 users' data. In other words, each target cannot complete the backup of the remaining data from the backup device.

[0060] In one embodiment, the computer device can start an aging timer on the target backup device that has completed relay backup in terms of performance. This aging timer indicates that the device should no longer perform data backups. In another embodiment, for the target backup device that has completed relay backup in terms of performance (i.e., a target backup device without data storage space), the computer device can start the aging timer before the predicted time point to indicate that the target backup device should no longer perform data backups. In one embodiment, the predicted time point can be the time point when the device reaches its performance limit, and this predicted time point can be output by the aforementioned performance prediction model. For example, the performance prediction model can predict the time point when any one of the device's predicted egress utilization, predicted memory utilization, or predicted CPU utilization exceeds a first reference value, as the predicted time point. This embodiment of the invention does not limit the process by which the performance prediction model outputs the predicted time point. For example, if a performance prediction model starts predicting device operation for the next hour at 13:00, and obtains predictions that the peak utilization of the egress port will be greater than the first reference value at 13:15, the peak utilization of memory will be greater than the first reference value at 13:35, and the peak utilization of CPU will be less than the first reference value, then the predicted time point T for the device to reach its performance limit is 13:15. In this embodiment of the invention, by introducing this predicted time point to determine whether to continue data backup on the device, and promptly activating the aging timer to stop data backup, excessive data pressure on the device can be avoided, ensuring that the device protects itself and the security of the business systems it supports while performing data backup.

[0061] Step 5: The computer equipment retrieves the data backup results.

[0062] In one embodiment, in response to the at least one target completing the remaining data backup from the backup device, the computer device removes the pending backup mark from the (j-1)th device. The computer device may poll each device in the backup pool to determine whether there are still devices carrying the pending backup mark, i.e., whether there are still devices that have not completed data backup. If there are devices that have not completed data backup, the computer device performs data backup on each of these devices in ascending order of their serial numbers, i.e., executes steps three and four above. After the data backup is completed, the pending backup mark is removed.

[0063] In one embodiment, the computer device requests capacity expansion in response to the at least one target failing to complete the backup of the remaining data from the backup device. For example, the computer device may send a prompt message to the user terminal, which can be used to instruct the expansion of the devices in the backup pool. In one embodiment, the computer device may also output a list of devices that have not completed data backup and a list of remaining data to prompt the user to complete the backup of the remaining data in the list as soon as possible to avoid data loss.

[0064] In the technical solution provided in this embodiment of the invention, the devices in the backup pool form a chain relationship based on data backup logic. Each device is the primary backup device of its predecessor and is used to perform data backup on its predecessor. Based on the current storage performance and predicted storage performance of each device, it is comprehensively judged whether each device can complete the data backup task of its predecessor. For any device whose storage performance does not meet the data backup requirements, at least one target backup device is called to assist it in completing the data backup. This can make full use of the data carrying capacity of each device in the backup pool, effectively reduce the data backup pressure of each primary backup device in the backup pool, ensure the security of the business carried by each device, and enhance the stability and disaster recovery capability of the business system.

[0065] In one embodiment, the technical solution provided by this invention can be applied to dial-up service scenarios. Each device in the backup pool is a BRAS device, meaning the backup pool includes a first BRAS device to an Nth BRAS device. After a user terminal establishes a PPPoE (Point-to-Point Protocol Over Ethernet) dial-up session with the BRAS device, the BRAS device generates and stores user data. In the initial batch data backup scenario during hot standby, i.e., when devices in the backup pool need to be upgraded, cutoverdone, restarted, or a large number of users need to come back online, the data backup method provided by this invention can be applied to achieve batch data backup. Of course, the above data backup method can also be applied to the implementation backup scenario during hot standby, i.e., when small, sporadic data backups are performed in real time after the business system is running stably. Figure 5 This is a flowchart of batch data backup in a dial-up service scenario provided by an embodiment of the present invention. Figure 5 Taking this as an example, we will explain the process of batch data backup in dial-up service scenarios.

[0066] S501: The computer equipment determines whether the primary backup device corresponding to each BRAS device in the backup pool meets the first condition. This determination process is the same as the process in step S201 above, and will not be repeated here. If it meets the condition, proceed to step S502; if it does not meet the condition, proceed to step S503.

[0067] S502. For the primary backup device that meets the first condition, perform a full backup of the data of its corresponding BRAS device on the primary backup device. After the data backup is completed, proceed to step S513.

[0068] S503. For primary backup devices that do not meet the first condition, back up the data of their corresponding BRAS devices according to the performance limit, and add a "to be backed up" mark to BRAS devices with remaining data that have not been backed up.

[0069] S504. Determine the BRAS device with the smallest sequence number that has been marked, and determine whether its corresponding slave backup devices meet the first condition. If they do, proceed to step S505; otherwise, proceed to step S507. For example, if the first BRAS device, the fifth BRAS device, and the twelfth BRAS device are all marked, then start backing up the remaining data from the first BRAS device with the smallest sequence number. After the data backup of the first BRAS device is completed, the mark of the first BRAS device waiting to be backed up is removed. The remaining fifth BRAS devices and twelfth BRAS devices carry the mark of waiting to be backed up, and then start backing up the remaining data from the fifth BRAS device with the smallest sequence number, and so on.

[0070] S505. If the target backup device meets the first condition, back up the remaining data of its corresponding BRAS device on an average basis, and remove the pending backup mark of the BRAS device.

[0071] S506. Determine if there are any BRAS devices carrying the backup tag. If so, proceed to step S504; if not, proceed to step S513.

[0072] S507. Determine whether there is a target backup device that meets the second condition among the backup devices corresponding to the BRAS device with the smallest sequence number. If it exists, proceed to step S508; if it does not exist, proceed to step S512.

[0073] S508. For target backup devices that meet the second condition, back up the remaining data of their corresponding BRAS devices in ascending order of serial number, based on the maximum performance limit of the devices, and start the aging timer to age up the target backup devices.

[0074] S509. Determine whether the BRAS device with the smallest sequence number has completed data backup. If yes, proceed to step S510; otherwise, proceed to step S512.

[0075] S510, Remove the pending backup marker for this BRAS.

[0076] S511. Determine whether there are still BRAS devices carrying the backup tag. If yes, proceed to step S507; otherwise, proceed to step S513.

[0077] S512, if it is determined that data backup cannot be completed, output a list of BRAS devices marked as to be backed up, as well as the remaining data to be backed up, send an expansion notification, and the process ends.

[0078] S513, Batch data backup complete.

[0079] The technical solution provided by this invention expands the traditional backup method of pairing devices to a chain-like backup structure formed by multiple devices. The primary and secondary backup relationships between devices in the backup pool constitute a chain. Compared to the traditional method of two devices backing up each other, the expanded chain-like backup structure theoretically provides n-1 backup devices for each device, significantly improving the availability and disaster recovery capabilities of the business system, effectively reducing the backup pressure on the primary backup devices, and improving the utilization efficiency of the entire backup pool. When performing data backup, this invention fully considers the current and future storage performance of each backup device and proposes a method for quantifying and predicting device storage status. Specifically, it quantifies the device's storage status using device egress utilization, CPU utilization, and memory utilization; and trains a performance prediction model using historical device operating data combined with external factors such as weather, seasons, and public events to obtain the device's storage performance within a future target time period. By quantifying and simplifying the complex device status into simple indicators, the status determination process is streamlined, and the backup decision-making efficiency of the entire backup pool is improved. In this embodiment of the invention, by sharing the data backup pressure among backup devices and introducing an aging timer, it is possible to maximize disaster recovery backup while effectively preventing the backup devices' own business operations from being affected, thereby improving the stability of the devices in the entire backup pool.

[0080] All of the above-mentioned optional technical solutions can be combined in any way to form the optional embodiments of this application, and will not be described in detail here.

[0081] Figure 6 This is a schematic diagram of a data backup device provided in an embodiment of the present invention. Figure 6 As shown, the device may include a judgment module 601, a first backup module 602, and a second backup module 603.

[0082] The judgment module 601 is used to determine whether each device in the backup pool meets the first condition. The backup pool includes N devices, and each device forms a chain relationship based on data backup logic. Any device in the chain relationship is the primary backup device of the preceding device and is used to perform data backup on the preceding device. The first condition is used to indicate that the current storage performance and future storage performance of the device meet the data backup requirements. The first backup module 602 is used to perform a full backup of the data of the (i-1)th device on the i-th device in response to the i-th device in the backup pool meeting the first condition, where i and N are positive integers and 2≤i≤N; The second backup module 603 is used to respond to the j-th device in the backup pool not meeting the first condition by calling at least one target backup device to assist the j-th device in backing up the data of the (j-1)-th device. The target backup device is a device in the backup pool that has completed a full backup task, where j and N are positive integers and 2≤j≤N.

[0083] In one embodiment, the determination module 601 includes: The determination submodule is used to determine the status factor and predicted status factor of each device. The status factor is used to indicate the current storage performance of the device, and the predicted status factor is used to indicate the predicted storage performance of the device in a future target time period. The judgment submodule is used to determine whether each device meets the first condition based on the values ​​of the state factor and the predicted state factor.

[0084] In one embodiment, the determining submodule is used for: Based on the current operating data of each device, the status factors of each device are determined. The current operating data includes at least the current egress utilization, current memory utilization, and current CPU utilization. Based on the predicted operating data of each device within the target time period in the future, the predicted state factor of each device is determined. The predicted operating data includes at least the predicted peak utilization rate of the egress port, the predicted peak utilization rate of the memory, and the predicted peak utilization rate of the CPU.

[0085] In one embodiment, the device further includes: The training module is used to iteratively train the performance prediction model based on the historical operating data of each device in the backup pool, the correspondence between the historical operating data and time, and the operating environment data. The historical operating data includes at least the outgoing flow utilization, memory utilization, CPU utilization, and peak user data. The operating environment data includes at least one of the following: weather data, seasonal data, holiday data, and public event data. The acquisition module is used to acquire the predicted operating data of each device through the trained performance prediction model.

[0086] In one embodiment, the second backup module 603 includes: The first backup submodule is used to back up part of the data of the (j-1)th device based on the performance limit of the jth device in response to the jth device not meeting the first condition. The device identifies a submodule that determines the at least one target from the backup device within the backup pool; The second backup submodule backs up the remaining data of the j-1th device from the backup device at least once.

[0087] In one embodiment, the second backup submodule includes: The first determining unit is used to determine the devices in the backup pool that have completed all tasks as candidate backup devices; The judgment unit is used to determine whether each candidate backup device meets the first condition; The second determining unit is configured to determine the candidate backup device that satisfies the first condition as the target backup device in response to the existence of a candidate backup device that satisfies the first condition. The third determining unit is configured to determine the candidate backup device that satisfies the second condition as the target backup device in response to the absence of a candidate backup device that satisfies the first condition, wherein the second condition is used to indicate that the current storage performance of the device meets the data backup requirements.

[0088] In one embodiment, the second backup submodule includes: A first backup subunit is configured to, in response to the at least one target backup device satisfying the first condition, back up the remaining data equally weighted in the at least one target backup device; The second backup subunit is configured to, in response to the at least one target backup device satisfying the second condition, sequentially back up the remaining data in each of the target backup devices at the maximum performance level.

[0089] In one embodiment, the first backup subunit is used for: Based on the target number of backup devices, the remaining data is divided into multiple parts in a round-down manner, and the remaining data is assigned to the last part. Back up each copy of the data from the backup device for each target separately.

[0090] In one embodiment, the device further includes: The aging module is used to start an aging timer from the backup device to indicate that the device will no longer perform data backups after the target has completed the relay backup in terms of performance.

[0091] In one embodiment, the device further includes: The tag adding module is used to add a tag for relay backup to the j-1 device.

[0092] In one embodiment, the device further includes: A marker removal module is used to remove the backup-to-be-repaired marker in response to the at least one target completing the backup of the remaining data from the backup device. The request module is used to request device expansion in response to the failure of at least one target to complete the backup of the remaining data from the backup device.

[0093] The data backup device provided in this embodiment of the invention forms a chain relationship between various devices in the backup pool based on data backup logic. Each device is the primary backup device for the preceding device and is used to back up the data of the preceding device. Based on the current storage performance and predicted storage performance of each device, it is comprehensively judged whether each device can complete the data backup task for the preceding device. For any device whose storage performance does not meet the data backup requirements, at least one target backup device is invoked to assist it in completing the data backup. This can make full use of the data carrying capacity of each device in the backup pool, effectively reduce the data backup pressure of each primary backup device in the backup pool, ensure the security of the business carried by each device, and enhance the stability and disaster recovery capability of the business system.

[0094] Figure 7 This is a schematic diagram of the hardware structure of a computer device provided in an embodiment of the present invention.

[0095] The computer device may include a processor 701 and a memory 702 storing computer program instructions.

[0096] Specifically, the processor 701 may include a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of the present invention.

[0097] Memory 702 may include mass storage for data or instructions. For example, and not limitingly, memory 702 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. In one instance, memory 702 may include removable or non-removable (or fixed) media, or memory 702 may be non-volatile solid-state memory. Memory 702 may be internal or external to the integrated gateway disaster recovery device.

[0098] In one example, memory 702 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Thus, typically, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of this disclosure.

[0099] The processor 701 reads and executes computer program instructions stored in the memory 702 to achieve... Figure 2 The data backup method in the illustrated embodiment.

[0100] In one example, the computer device may also include a communication interface 703 and a bus 704. Wherein, as... Figure 7 As shown, the processor 701, memory 702, and communication interface 703 are connected through bus 704 and complete communication with each other.

[0101] The communication interface 703 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of the present invention.

[0102] Bus 704 includes hardware, software, or both, that couples components of an online data traffic metering device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 704 may include one or more buses. While specific buses are described and illustrated in embodiments of the invention, the invention contemplates any suitable bus or interconnect.

[0103] This computer device can comprehensively assess the data backup capabilities of the primary and backup devices based on their current and predicted storage performance before performing data backup. It also incorporates at least one target device to collaboratively complete the data backup process, thereby achieving a combined approach. Figure 2 and Figure 6 The data backup method and apparatus described.

[0104] Furthermore, in conjunction with the data backup methods described in the above embodiments, this invention can be implemented using a computer storage medium. This computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the data backup methods described in the above embodiments.

[0105] It should be clarified that the present invention is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present invention is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of the present invention.

[0106] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this invention are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried in a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, read-only memory (ROM), flash memory, erasable read-only memory (EROM), floppy disks, compact disc read-only memory (CD-ROM), optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0107] It should also be noted that the exemplary embodiments mentioned in this invention describe methods or systems based on a series of steps or apparatus. However, this invention is not limited to the order of the steps described above; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0108] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0109] The above description is merely a specific embodiment of the present invention. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in the present invention, and these modifications or substitutions should all be covered within the protection scope of the present invention.

Claims

1. A data backup method characterized by, The method comprises: determining whether each device in a backup pool meets a first condition, the backup pool comprising N devices, each device forming a chain relationship based on data backup logic, any device in the chain relationship being a primary backup device of a previous device for data backup of the previous device, the first condition indicating that the current storage performance and future storage performance of the device meet data backup requirements; in response to the ith device in the backup pool meeting the first condition, performing full backup of data of the i-1th device by the ith device, wherein i and N are positive integers, and 2≤i≤N; in response to the jth device in the backup pool not meeting the first condition, calling at least one target backup device to assist the jth device in backing up data of the j-1th device, the target backup device being a device in the backup pool that has completed full backup, wherein j and N are positive integers, and 2≤j≤N.

2. The method of claim 1, wherein, The method comprises: determining a state factor and a predicted state factor of each device, the state factor indicating the current storage performance of the device, and the predicted state factor indicating the predicted storage performance of the device in a future target time period; based on the values of the state factor and the predicted state factor, determining whether each device meets the first condition.

3. The method of claim 2, wherein, The method comprises: based on current running data of each device, determining the state factor of each device, the current running data comprising at least current outlet utilization, current memory utilization, and current CPU utilization; based on predicted running data of each device in a future target time period, determining the predicted state factor of each device, the predicted running data comprising at least predicted peak outlet utilization, predicted peak memory utilization, and predicted peak CPU utilization.

4. The method of claim 3, wherein, The predicted running data is obtained by a performance prediction model for predicting running data of a device in any future time period; Before determining the predicted state factor of each device based on the predicted running data of each device in a future target time period, the method further comprises: based on historical running data of each device in the backup pool, a correspondence between the historical running data and time, and running environment data, iteratively training the performance prediction model, the historical running data comprising at least outlet utilization, memory utilization, CPU utilization, and peak user data, and the running environment data comprising at least one of weather data, seasonal data, holiday data, and public event data; obtaining the predicted running data of each device by the trained performance prediction model.

5. The method of claim 1, wherein, The method comprises: in response to the jth device not satisfying the first condition, backing up part of data of the j-1th device based on an upper limit of performance of the jth device; determining the at least one target slave backup device in the backup pool; backing up remaining data of the j-1th device in the at least one target slave backup device.

6. The method of claim 5, wherein, The determining the at least one target slave backup device in the backup pool comprises: determining a device in the backup pool that has completed a full backup task as a candidate slave backup device; judging whether each candidate slave backup device satisfies the first condition; in response to the candidate slave backup device satisfying the first condition, determining the candidate slave backup device satisfying the first condition as the target slave backup device; in response to the candidate slave backup device not satisfying the first condition, determining the candidate slave backup device satisfying a second condition as the target slave backup device, the second condition being used to indicate that a current storage performance of a device satisfies a data backup requirement.

7. The method of claim 6, wherein, The backing up the remaining data of the j-1th device in the at least one target slave backup device comprises: in response to the at least one target slave backup device satisfying the first condition, equally weighting backing up the remaining data in the at least one target slave backup device; in response to the at least one target slave backup device satisfying the second condition, successively backing up the remaining data in each target slave backup device at an upper limit of performance.

8. The method of claim 7, wherein, The equally weighting backing up the remaining data in the at least one target slave backup device comprises: based on a number of the target slave backup devices, equally dividing the remaining data into multiple parts in an integer form, and a remainder part of data being included in a last part; respectively backing up each part of data in each target slave backup device.

9. The method of claim 7, wherein, After the successively backing up the remaining data in each target slave backup device at the upper limit of performance in response to the at least one target slave backup device satisfying the second condition, the method further comprises: starting an aging timer in the target slave backup device that has completed relay backup at the upper limit of performance, the aging timer being used to indicate that a device no longer performs data backup.

10. The method of claim 5, wherein, After the backing up part of data of the j-1th device based on the upper limit of performance of the jth device in response to the jth device not satisfying the first condition, the method further comprises: adding a to-be-relay-backed-up mark to the j-1th device.

11. The method of claim 10, wherein, After the backing up the remaining data of the j-1th device in the at least one target slave backup device, the method further comprises: in response to the at least one target slave backup device completing the remaining data backup, eliminating the to-be-relay-backed-up mark; in response to the at least one target slave backup device failing to complete the remaining data backup, requesting device expansion.

12. A data backup apparatus characterized by comprising: The apparatus comprises: A judging module is configured to judge whether each device in a backup pool satisfies a first condition, the backup pool comprising N devices, each device forming a chained relationship based on data backup logic, any device in the chained relationship being a master backup device of a previous device, and being configured to perform data backup on the previous device, the first condition indicating that a current storage performance and a future storage performance of the device both satisfy a data backup requirement; A first backup module is configured to, in response to an ith device in the backup pool satisfying the first condition, perform full backup of data of an (i-1)th device by the ith device, wherein i and N are positive integers, and 2≤i≤N; A second backup module is configured to, in response to a jth device in the backup pool not satisfying the first condition, call at least one target slave backup device to assist the jth device in performing backup of data of a (j-1)th device, the target slave backup device being a device in the backup pool that has completed a full backup task, wherein j and N are positive integers, and 2≤j≤N.

13. A data backup apparatus characterized by comprising: The device comprises a processor and a memory storing computer program instructions, and the processor reads and executes the computer program instructions to implement the data backup method according to any one of claims 1-11.

14. A computer-readable storage medium, characterized in that, The computer storage medium stores computer program instructions, and the computer program instructions are executed by a processor to implement the data backup method according to any one of claims 1-11.

15. A computer program product, characterised in that, The instructions in the computer program product are executed by a processor of an electronic device to enable the electronic device to perform the data backup method according to any one of claims 1-11.

Images