Data backup method and device, equipment, storage medium and program product
By using historical load information to determine idle periods and perform data backup in the cloud computing operation and maintenance platform, the problems of inefficient data backup and interruption of business processes are solved, and the backup efficiency and platform reliability are improved.
Patent Information
- Application Number
- CN202411658634.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-19
- Publication Date
- 2025-04-25
AI Technical Summary
Traditional data backup methods are inefficient, which can easily interrupt the business process of the cloud computing operation and maintenance platform, and cannot meet the needs of business continuity, reducing the reliability of the cloud computing operation and maintenance platform.
By obtaining historical load information for each period, the idle period set is determined, and the target data is grouped based on data priority. If the amount of data to be backed up reaches a preset threshold, the backup period is determined from the idle period set, and data backup is performed during the backup period.
It improves the efficiency of data backup, reduces the impact on the business process of the cloud computing operation and maintenance platform, and improves the reliability of the cloud computing operation and maintenance platform.
Smart Images

Figure CN119883723A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of data backup, and in particular to a data backup method, device, equipment, storage medium and program product. Background Art
[0002] In cloud computing operation and maintenance platforms, data backup is usually required to ensure data security and business continuity. However, traditional manual backup or scheduled incremental backup is not only inefficient, but also easily interrupts business processes and cannot meet the business continuity requirements of cloud computing operation and maintenance platforms, resulting in the inability to advance business processes on cloud computing operation and maintenance platforms normally, reducing the reliability of cloud computing operation and maintenance platforms. Summary of the invention
[0003] In view of this, the present invention provides a data backup method, device, equipment, storage medium and program product to solve the problem of low data backup efficiency and reduced reliability of cloud computing operation and maintenance platform.
[0004] In a first aspect, the present invention provides a data backup method, the method comprising:
[0005] Obtaining historical load information corresponding to each time period, and determining an idle time period set based on the historical load information corresponding to each time period and a preset load value;
[0006] Based on the data priority, the target data is grouped to obtain multiple groups of data to be backed up; the multiple groups of data to be backed up correspond to different data priorities;
[0007] If the amount of data to be backed up reaches a preset threshold, a backup period is determined from the idle period set;
[0008] During the backup period, the data to be backed up is backed up.
[0009] In an optional implementation, determining the idle time period set based on historical load information and preset load values corresponding to each time period includes:
[0010] The period in which the corresponding historical load information is less than the preset load value is determined as an idle period;
[0011] The idle time periods are summarized and aggregated to obtain an idle time period set.
[0012] In an optional implementation, determining a backup period from a set of idle periods includes:
[0013] Based on the amount of data to be backed up, determine the target backup duration corresponding to the data to be backed up;
[0014] An idle period in the idle period set whose duration is longer than the target backup duration is determined as the backup period.
[0015] In an optional embodiment, the method further includes:
[0016] If there are multiple sets of data to be backed up whose data volumes reach a preset threshold, then based on the data volumes of the multiple sets of data to be backed up, respectively determine the backup durations of the multiple sets of data to be backed up;
[0017] The shortest backup duration among multiple backup durations is determined as the target backup duration.
[0018] In an optional embodiment, the method further includes:
[0019] If there is no idle period with a duration longer than the target backup duration in the idle period set, the data to be backed up is divided into multiple data blocks to be backed up based on the preset data volume;
[0020] An idle period in the idle period set whose duration is greater than the backup duration corresponding to the preset data volume is determined as a backup period.
[0021] In an optional implementation, backing up the data to be backed up during the backup period includes:
[0022] At the beginning of the backup period, obtain the current load information corresponding to the backup period;
[0023] If the current load information corresponding to the backup period is less than the preset load value, the data to be backed up is backed up.
[0024] In a second aspect, the present invention provides a data backup device, the device comprising:
[0025] An idle period set determination module, used to obtain historical load information corresponding to each period in the backup cycle, and determine an idle period set based on the historical load information corresponding to each period;
[0026] The module for acquiring data to be backed up is used to group the target data based on the data priority to obtain multiple groups of data to be backed up; the multiple groups of data to be backed up correspond to different data priorities respectively;
[0027] A backup period determination module, used to determine a backup period from an idle period set if the amount of data to be backed up reaches a preset threshold;
[0028] The data backup module is used to back up the data to be backed up within the backup period.
[0029] In a third aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the data backup method of the first aspect or any corresponding embodiment thereof by executing the computer instructions.
[0030] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the data backup method of the first aspect or any corresponding embodiment thereof.
[0031] In a fifth aspect, the present invention provides a computer program product, comprising computer instructions for causing a computer to execute the data backup method of the first aspect or any corresponding embodiment thereof.
[0032] The data backup method provided by the embodiment of the present invention determines a set of idle time periods based on historical load information and preset load values corresponding to each time period, determines a backup time period from the set of idle time periods when the amount of data to be backed up reaches a preset threshold, and backs up the data to be backed up within the backup time period, thereby performing data backup in the idle time period, improving the efficiency of data backup, and at the same time reducing the impact on the business processes of the cloud computing operation and maintenance platform, thereby improving the reliability of the cloud computing operation and maintenance platform. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] In order to more clearly illustrate the specific implementation methods of the present invention or the technical solutions in the prior art, the drawings required for use in the specific implementation methods or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some implementation methods of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0034] Figure 1 is a flow chart of a data backup method according to an embodiment of the present invention;
[0035] Figure 2 is a flow chart of another data backup method according to an embodiment of the present invention;
[0036] Figure 3 is a flow chart of another data backup method according to an embodiment of the present invention;
[0037] Figure 4 is a flow chart of yet another data backup method according to an embodiment of the present invention;
[0038] Figure 5 is a structural block diagram of a data backup device according to an embodiment of the present invention;
[0039] Figure 6 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION
[0040] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.
[0041] In cloud computing operation and maintenance platforms, data backup is usually required to ensure data security and business continuity. However, traditional manual backup or scheduled incremental backup is not only inefficient, but also easily interrupts business processes and cannot meet the business continuity requirements of cloud computing operation and maintenance platforms, resulting in the inability to advance business processes on cloud computing operation and maintenance platforms normally, reducing the reliability of cloud computing operation and maintenance platforms.
[0042] Based on this, an embodiment of the present invention provides a data backup method, which obtains historical load information corresponding to each time period, and determines an idle time period set based on the historical load information corresponding to each time period and the preset load value; groups the target data based on the data priority to obtain multiple groups of data to be backed up; the multiple groups of data to be backed up correspond to different data priorities; if the data volume of the data to be backed up reaches the preset threshold, the backup time period is determined from the idle time period set; and the data to be backed up is backed up during the backup time period. In this way, the idle time period set is determined based on the historical load information and the preset load value corresponding to each time period, and the backup time period is determined from the idle time period set when the data volume of the data to be backed up reaches the preset threshold, and the data to be backed up is backed up during the backup time period, thereby performing data backup during the idle time period, improving the efficiency of data backup, and at the same time reducing the impact on the business process of the cloud computing operation and maintenance platform, and improving the reliability of the cloud computing operation and maintenance platform.
[0043] According to an embodiment of the present invention, a data backup method embodiment is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.
[0044] In this embodiment, a receipt backup method is provided, which can be used in the above-mentioned cloud computing operation and maintenance platform. Figure 1 is a flow chart of a data backup method according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:
[0045] Step S101, obtaining historical load information corresponding to each time period, and determining an idle time period set based on the historical load information corresponding to each time period and a preset load value.
[0046] In an embodiment of the present invention, historical load information corresponding to each time period in a statistical period is obtained. Among them, any duration such as a day, a week, and a business process processing cycle can be used as a statistical period. A statistical period is divided into multiple time periods, and the duration of each time period is the unit statistical duration, such as one hour. The historical load information is the load information corresponding to each time period in one or more past statistical periods. The load information is used to measure the data processing volume or load utilization of the cloud computing operation and maintenance platform in the corresponding time period; the load information may include information such as CPU load utilization, memory utilization, and platform access volume.
[0047] In the embodiment of the present invention, the preset load value is used to define the load threshold corresponding to the idle period. Each of the multiple information included in the load information has a corresponding preset load value; only when all the information in the load information meets the limit of the preset load value can a period be determined as an idle period.
[0048] In the embodiment of the present invention, the determined multiple idle time periods are collected to obtain an idle time period set.
[0049] Step S102: grouping the target data based on the data priority to obtain multiple groups of data to be backed up.
[0050] In the embodiment of the present invention, the target data is the data that needs to be backed up in the cloud computing operation and maintenance platform; the multiple groups of data to be backed up correspond to different data priorities. For different data types, the data priorities are also different; according to the data priority, the target data is grouped, and the target data with the same data priority is grouped into one group, so as to obtain multiple groups of data to be backed up.
[0051] In an optional implementation, each data type corresponds to a different data priority, and among the multiple groups of data to be backed up obtained by grouping, each group of data to be backed up corresponds to a different data type, thereby achieving refined grouping. When backing up data, it can be backed up separately according to the data type.
[0052] In an optional implementation, different data types may correspond to the same data priority, and each of the multiple groups of data to be backed up obtained by grouping may contain data of multiple data types, thereby backing up data of multiple data types simultaneously.
[0053] In an optional implementation, data priority can be determined according to the data importance of different data types. The data importance is judged based on the impact of each data type on the operation of the cloud computing operation and maintenance platform, the difficulty of data regeneration, etc., so as to determine the data priority corresponding to each data type.
[0054] Step S103: if the amount of data to be backed up reaches a preset threshold, a backup period is determined from the idle period set.
[0055] In the embodiment of the present invention, if the amount of data to be backed up reaches a preset threshold, the backup of the data to be backed up can be started at this time, and an idle period that can meet the backup requirements of the data to be backed up is determined from the idle period set and is determined as the backup period. Among them, meeting the requirements of the data to be backed up means that the backup of the data to be backed up can be completed within the period.
[0056] In an optional implementation, the modified data is recorded in the log from the last backup to the current time, and the data volume is calculated, so as to obtain the data volume of each group of data to be backed up.
[0057] In an optional embodiment, if there are multiple groups of data to be backed up, whether the data volume of the data to be backed up with the highest data priority reaches a preset threshold is used as a criterion for determining whether to start the backup of the data to be backed up; at the same time, if the data volume of the data to be backed up with the highest data priority reaches the preset threshold, it is determined whether the data volume of the data to be backed up with other data priorities reaches the preset threshold, and the backup of the other data to be backed up whose data volume reaches the preset threshold is started.
[0058] Step S104: backing up the data to be backed up within the backup period.
[0059] In the embodiment of the present invention, after the backup period is determined, when the backup period is reached, the data to be backed up is backed up, so that the business process of the cloud computing operation and maintenance platform is not affected while the data backup is completed.
[0060] The data backup method provided by the embodiment of the present invention obtains the historical load information corresponding to each time period, and determines the idle time period set based on the historical load information corresponding to each time period and the preset load value; groups the target data based on the data priority to obtain multiple groups of data to be backed up; the multiple groups of data to be backed up correspond to different data priorities; if the data volume of the data to be backed up reaches the preset threshold, the backup time period is determined from the idle time period set; and the data to be backed up is backed up within the backup time period. In this way, the idle time period set is determined based on the historical load information and the preset load value corresponding to each time period, and the backup time period is determined from the idle time period set when the data volume of the data to be backed up reaches the preset threshold, and the data to be backed up is backed up within the backup time period, so that data backup is performed in the idle time period, the efficiency of data backup is improved, and at the same time, the impact on the business process of the cloud computing operation and maintenance platform is reduced, and the reliability of the cloud computing operation and maintenance platform is improved.
[0061] In this embodiment, a receipt backup method is provided, which can be used in the above-mentioned cloud computing operation and maintenance platform. Figure 2 is a flow chart of another data backup method according to an embodiment of the present invention. Figure 2 As shown, the process includes the following steps:
[0062] Step S201, obtaining historical load information corresponding to each time period, and determining an idle time period set based on the historical load information corresponding to each time period and a preset load value.
[0063] Specifically, step S201 includes:
[0064] Step S2011, determining a time period in which the corresponding historical load information is less than a preset load value as an idle time period.
[0065] In the embodiment of the present invention, the period when the corresponding historical load information is less than the preset load value is determined as the idle period. If the historical load information contains multiple information, when each information is less than the corresponding preset load value, the period is determined as the idle period.
[0066] Step S2012, summarize and aggregate the idle time periods to obtain an idle time period set.
[0067] In the embodiment of the present invention, the idle time periods obtained are summarized, and the idle time periods that are continuous in time are aggregated to obtain a complete idle time period, and the aggregated idle time periods are summarized to obtain an idle time period set. For example, the idle time periods obtained in step S2011 are T1, T2, and T3, where T1 and T2 are continuous in time, and T1 and T2 are aggregated into a new idle time period T, and the start time corresponding to the new idle time period T is the start time of T1, and the end time is the end time of T2, and the idle time period set obtained thereby includes two idle time periods, namely T and T3.
[0068] In an optional implementation, in order to avoid the preset load value from placing too strict restrictions on the idle period, resulting in the idle period being too short and unable to meet the backup requirements, the duration required for a full backup of data within a statistical period is calculated, and a minimum backup duration is determined based on the duration and a preset ratio. If the maximum duration of the idle period in the obtained idle period set is less than the shortest backup duration, it indicates that the duration of the idle period in the obtained idle period set is too short. Therefore, the preset load value is readjusted, the threshold corresponding to the preset load value is increased, and the idle period set is redetermined based on this.
[0069] Step S202: group the target data based on the data priority to obtain multiple groups of data to be backed up. Figure 1 Step S102 of the illustrated embodiment will not be described in detail here.
[0070] Step S203: If the amount of data to be backed up reaches a preset threshold, a backup period is determined from the idle period set. Figure 1 Step S103 of the illustrated embodiment will not be described in detail here.
[0071] Step S204: Back up the data to be backed up during the backup period. Figure 1 Step S104 of the illustrated embodiment will not be described in detail here.
[0072] In this embodiment, a receipt backup method is provided, which can be used in the above-mentioned cloud computing operation and maintenance platform. Figure 3 is a flow chart of another data backup method according to an embodiment of the present invention. Figure 3 As shown, the process includes the following steps:
[0073] Step S301, obtain the historical load information corresponding to each time period, and determine the idle time period set based on the historical load information corresponding to each time period and the preset load value. Figure 1 Step S101 of the illustrated embodiment will not be described in detail here.
[0074] Step S302: group the target data based on the data priority to obtain multiple groups of data to be backed up. Figure 1 Step S102 of the illustrated embodiment will not be described in detail here.
[0075] Step S303: if the amount of data to be backed up reaches a preset threshold, a backup period is determined from the idle period set.
[0076] Specifically, step S303 includes:
[0077] Step S3031: Determine a target backup duration corresponding to the data to be backed up based on the amount of data to be backed up.
[0078] In the embodiment of the present invention, the backup time required to back up the data to be backed up is calculated based on the data volume of the data to be backed up and the speed of backing up the data, so as to obtain the target backup duration corresponding to the data to be backed up.
[0079] In an optional implementation, if there are multiple groups of data to be backed up whose data volume reaches a preset threshold, the backup durations of the multiple groups of data to be backed up are determined separately based on the data volume of the multiple groups of data to be backed up; then, the backup duration with the shortest duration among the multiple backup durations is determined as the target backup duration.
[0080] Step S3032: determine the idle time periods in the idle time period set whose duration is longer than the target backup duration as backup time periods.
[0081] In the embodiment of the present invention, in order to ensure that data backup can be completed within an idle period, an idle period in the idle period set whose duration is greater than the target backup duration is determined as a backup period.
[0082] In an optional implementation, if there is no idle period in the idle period set whose duration is greater than the target backup duration, in order to ensure that data backup can proceed normally, the data to be backed up is divided into multiple data blocks to be backed up based on a preset data volume; then, the idle period in the idle period set whose duration is greater than the backup duration corresponding to the preset data volume is determined as the backup period.
[0083] In an optional implementation, the data to be backed up may be split according to the data type in the data to be backed up to obtain multiple data blocks, and the backup period may be determined according to the data volume of the obtained data blocks. If the backup period cannot be obtained after splitting according to the data type, each data block may be split again according to the preset data volume to obtain the backup period.
[0084] In an optional implementation, the preset data volume may be a preset size of a data block. When all data backup cannot be completed within an idle period, the data to be backed up is divided into multiple data blocks to be backed up according to the preset data volume.
[0085] In an optional implementation, the data to be backed up may be divided into a plurality of data blocks to be backed up with equal data volumes according to the current data volume of the data to be backed up, for example, divided into two data blocks to be backed up with equal data volumes, and the target backup duration corresponding to the split data blocks to be backed up is compared with the duration of the idle time period in the idle time period set to determine the backup time period. If there is still no idle time period that meets the backup requirements after one split, splitting is performed again until a backup time period is determined from the idle time period set.
[0086] In an optional implementation, the backup data volume that can be satisfied by the shortest idle period in the idle period set can also be used as the preset data volume, and the data to be backed up can be divided into multiple data blocks to be backed up. Specifically, the idle period with the shortest duration, the speed of backing up data, and the duration of the idle period are determined from the idle period set, and the backup data volume that can be satisfied by the idle period is determined, and the backup data volume is used as the preset data volume. In this case, all idle periods in the idle period set can be used as backup periods.
[0087] In an optional implementation, the amount of backup data that can be satisfied by the idle periods in the idle period set can be taken as the preset data amount in sequence, and the data to be backed up can be split in sequence to obtain data blocks to be backed up, so that data backup can be performed in each idle period in the idle period set.
[0088] Step S304: Back up the data to be backed up during the backup period. Figure 1 Step S104 of the illustrated embodiment will not be described in detail here.
[0089] In this embodiment, a receipt backup method is provided, which can be used in the above-mentioned cloud computing operation and maintenance platform. Figure 4 FIG. 1 is a flow chart of another data backup method according to an embodiment of the present invention. Figure 4 As shown, the process includes the following steps:
[0090] Step S401, obtain the historical load information corresponding to each time period, and determine the idle time period set based on the historical load information corresponding to each time period and the preset load value. Figure 1 Step S101 of the illustrated embodiment will not be described in detail here.
[0091] Step S402: group the target data based on the data priority to obtain multiple groups of data to be backed up. Figure 1 Step S102 of the illustrated embodiment will not be described in detail here.
[0092] Step S403: If the amount of data to be backed up reaches a preset threshold, a backup period is determined from the idle period set. Figure 1 Step S103 of the illustrated embodiment will not be described in detail here.
[0093] Step S404: backing up the data to be backed up within the backup period.
[0094] Specifically, step S404 includes:
[0095] Step S4041, when the backup period starts, obtain the current load information corresponding to the backup period.
[0096] In the embodiment of the present invention, when the backup period starts, that is, when the current time reaches the start time of the backup period, the load information at the current time is acquired to obtain the current load information corresponding to the backup period.
[0097] Step S4042: if the current load information corresponding to the backup period is less than the preset load value, the data to be backed up is backed up.
[0098] In the embodiment of the present invention, if the current load information corresponding to the backup period is less than the preset load value, it indicates that the cloud computing operation and maintenance platform is in an idle state or the current business process occupies a low load and memory, and the current data backup will not affect the normal business process, so the backup data is backed up at this time. Repeat the above steps until all the backup data are backed up, thereby completing the data backup.
[0099] In the present embodiment, a data backup device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.
[0100] This embodiment provides a data backup device, such as Figure 5 As shown, including:
[0101] The idle period set determination module 501 is used to obtain the historical load information corresponding to each period in the backup cycle, and determine the idle period set based on the historical load information corresponding to each period;
[0102] The to-be-backed-up data acquisition module 502 is used to group the target data based on the data priority to obtain multiple groups of to-be-backed-up data; the multiple groups of to-be-backed-up data correspond to different data priorities respectively;
[0103] The backup period determination module 503 is used to determine a backup period from the idle period set if the amount of data to be backed up reaches a preset threshold;
[0104] The data backup module 504 is used to back up the data to be backed up within the backup period.
[0105] In an optional implementation, the idle period set determining module 501 includes:
[0106] An idle period determination unit, configured to determine a period when the corresponding historical load information is less than a preset load value as an idle period;
[0107] The idle time period aggregation unit is used to summarize and aggregate the idle time periods to obtain an idle time period set.
[0108] In an optional implementation, the to-be-backed-up data acquisition module 502 includes:
[0109] A target backup duration determining unit, configured to determine a target backup duration corresponding to the data to be backed up based on the amount of data to be backed up;
[0110] The backup period determination unit is used to determine an idle period in the idle period set whose duration is greater than the target backup duration as a backup period.
[0111] In an optional implementation, the to-be-backed-up data acquisition module 502 further includes:
[0112] A backup duration determination unit, configured to determine the backup durations of the multiple groups of data to be backed up respectively based on the data volumes of the multiple groups of data to be backed up if there are multiple groups of data to be backed up whose data volumes reach a preset threshold;
[0113] The target backup duration determining unit is further configured to determine the smallest backup duration among the multiple backup durations as the target backup duration.
[0114] In an optional implementation, the to-be-backed-up data acquisition module 502 further includes:
[0115] The data to be backed up splitting unit is used to divide the data to be backed up into a plurality of data blocks to be backed up based on a preset data volume if there is no idle period with a duration longer than the target backup duration in the idle period set;
[0116] The backup period determination unit is further used to determine an idle period in the idle period set whose duration is greater than the backup duration corresponding to the preset data volume as a backup period.
[0117] In an optional implementation, the data backup module 504 includes:
[0118] A current load information acquisition unit, used to acquire the current load information corresponding to the backup period when the backup period starts;
[0119] The data backup unit is used to back up the data to be backed up if the current load information corresponding to the backup period is less than a preset load value.
[0120] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.
[0121] The data backup device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.
[0122] The embodiment of the present invention also provides a computer device having the above Figure 5 The data backup device shown.
[0123] See also Figure 6 , Figure 6 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 6 As shown, the computer device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 6 A processor 10 is taken as an example.
[0124] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.
[0125] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.
[0126] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0127] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.
[0128] The computer device further comprises a communication interface 30 for the computer device to communicate with other devices or a communication network.
[0129] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.
[0130] A part of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the existence of computer program instructions in computer-readable media includes, but is not limited to, source files, executable files, installation package files, etc., and accordingly, the way in which computer program instructions are executed by a computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium accessible to the computer.
[0131] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the present invention.
Claims
1. A data backup method, characterized in that: The method comprises: Acquire historical load information corresponding to each time period, and determine an idle time period set based on the historical load information corresponding to each time period and a preset load value; Based on the data priority, the target data is grouped to obtain multiple groups of data to be backed up; the multiple groups of data to be backed up correspond to different data priorities respectively; If the amount of the data to be backed up reaches a preset threshold, determining a backup period from the idle period set; The data to be backed up is backed up during the backup period.
2. The method according to claim 1, characterized in that The determining of the idle time period set based on the historical load information and the preset load value corresponding to each time period includes: Determine a period of time when the corresponding historical load information is less than the preset load value as an idle period; The idle time periods are summarized and aggregated to obtain the idle time period set.
3. The method according to claim 1, characterized in that The step of determining a backup period from the idle period set includes: Based on the data volume of the data to be backed up, determining a target backup duration corresponding to the data to be backed up; An idle period in the idle period set whose duration is longer than the target backup duration is determined as the backup period.
4. The method according to claim 3, characterized in that The method further comprises: If there are multiple groups of data to be backed up whose data volumes reach the preset threshold, then based on the data volumes of the multiple groups of data to be backed up, respectively determine the backup durations of the multiple groups of data to be backed up; The smallest backup duration among the multiple backup durations is determined as the target backup duration.
5. The method according to claim 3, characterized in that: The method further comprises: If there is no idle period with a duration longer than the target backup duration in the idle period set, dividing the data to be backed up into a plurality of data blocks to be backed up based on a preset data volume; An idle period in the idle period set whose duration is greater than the backup duration corresponding to the preset data volume is determined as the backup period.
6. The method according to claim 1, characterized in that Backing up the data to be backed up within the backup period includes: When the backup period starts, obtaining current load information corresponding to the backup period; If the current load information corresponding to the backup period is less than the preset load value, the data to be backed up is backed up.
7. A data backup device, characterized in that: The device comprises: An idle period set determination module, used to obtain historical load information corresponding to each period in the backup cycle, and determine an idle period set based on the historical load information corresponding to each period; The module for acquiring data to be backed up is used to group the target data based on the data priority to obtain multiple groups of data to be backed up; the multiple groups of data to be backed up correspond to different data priorities respectively; A backup period determination module, configured to determine a backup period from the idle period set if the amount of the data to be backed up reaches a preset threshold; The data backup module is used to back up the data to be backed up within the backup period.
8. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the data backup method according to any one of claims 1 to 6 by executing the computer instructions.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the data backup method according to any one of claims 1 to 6.
10. A computer program product, characterized in that The method comprises computer instructions, wherein the computer instructions are used to cause a computer to execute the data backup method according to any one of claims 1 to 6.