A data backup method, device, equipment, medium and product

Abstract

The application provides a data backup method, device, equipment, medium and product, and relates to the technical field of data storage. The method comprises the following steps: receiving a backup plan sent by a database; creating a backup task according to the backup plan, and obtaining backup task requirements required for executing the backup task; sending the backup task requirements to a scheduling engine; receiving resource instance information sent by the scheduling engine; generating a backup instruction according to the resource instance information; and sending the backup task and the backup instruction to a backup server, so that the backup server executes the backup task according to the backup instruction. The data backup method of the application introduces a scheduler in a data backup system, automatically receives a backup plan, creates a backup task, obtains and allocates resource instance information, and generates a backup instruction. Users no longer need to manage complex hardware and network resources by themselves, and do not need to deploy and maintain a backup service, thereby reducing the cost of data backup.

Description

Technical Field

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

[0002] Data backup refers to copying and storing important data to other physical or cloud storage media so that it can be recovered and used in the event of data loss, corruption, or catastrophic events. Its main purpose is to protect the integrity and availability of data, ensuring that businesses or individuals can quickly resume normal operations after an unexpected event and avoid losses caused by data loss.

[0003] In existing technologies, data backup methods typically employ a resource-based service model. Under this model, users need to subscribe to and manage the necessary hardware and network resources, such as virtual machines, storage resources, and dedicated lines. Users can choose to build their own backup service or subscribe to backup services provided by third-party providers. In the self-built model, users need to deploy the backup service themselves and may need to subscribe to dedicated lines for data transmission, which requires a higher level of technical expertise. In the third-party service model, although users do not need to build their own backup service, they still need to pay for the performance specifications of the backup resources and may need to subscribe to dedicated lines to ensure the security and efficiency of data transmission.

[0004] However, existing technologies suffer from high costs, primarily because users need to order and maintain substantial hardware and network resources. In the self-built model, users must order virtual machines, storage resources, and dedicated lines, all of which are costly to maintain. Furthermore, users require significant technical expertise to deploy and manage backup services, increasing labor costs. In the third-party service model, while users don't need to build their own backup systems, they still need to pay for the performance specifications of the backup resources, essentially ordering a dedicated backup server. Simultaneously, to ensure data transmission security and efficiency, users may need to order dedicated lines, further increasing costs. Regardless of the model, users face substantial long-term expenses, making data backup costly. Summary of the Invention

[0005] This application provides a data backup method, apparatus, device, medium, and product to solve the problem of high cost in existing data backup methods.

[0006] In a first aspect, this application provides a data backup method, which is applied to the scheduler of a data backup system. The data backup system further includes a server, a database, a scheduling engine, and a backup server. The method comprises:

[0007] Receive a backup plan sent by the database; wherein the backup plan is created by the server according to user requirements and sent to the database, and the backup plan is used to define the backup time and backup content instruction set for data backup;

[0008] According to the backup plan, a backup task is created, and the backup task requirements required to execute the backup task are obtained; wherein, the backup task is a set of steps to implement the backup plan;

[0009] The backup task request is sent to the scheduling engine, so that the scheduling engine generates resource instance information based on the backup task request; wherein, the resource instance information is the configuration information of the backup resources required by the backup task request;

[0010] Receive resource instance information sent by the scheduling engine;

[0011] Based on the resource instance information, a backup instruction is generated; wherein, the backup instruction refers to the instruction of the backup server to execute the backup task;

[0012] The backup task and the backup instruction are sent to the backup server so that the backup server executes the backup task according to the backup instruction.

[0013] In one possible design, creating a backup task according to the backup plan includes:

[0014] Obtain the data priority, recovery time after damage, backup time, backup frequency, and storage capacity requirements in the backup plan;

[0015] The backup strategy for the backup task is obtained by selecting a strategy based on the data priority and the recovery time after damage; wherein, the data priority refers to the importance level of different data in the backup data;

[0016] The backup task's time schedule is obtained by performing time planning based on the backup time and the backup frequency; wherein, the backup time refers to the specific time of the data backup operation, and the backup frequency refers to the execution interval of the data backup operation;

[0017] Based on the storage capacity requirements and the preset budget constraints, a storage medium is selected to obtain the storage scheme for the backup task; wherein, the storage capacity requirements refer to the total amount of storage space required to store the backup data;

[0018] The system is configured according to the backup strategy and the time schedule to obtain the implementation technology of the backup task;

[0019] The backup task is created based on the storage scheme and the implementation technology described.

[0020] In one possible design, generating backup instructions based on the resource instance information includes:

[0021] Obtain the elastic address and software configuration from the resource instance information;

[0022] Based on the software configuration, a software deployment instruction is generated; wherein, the software deployment instruction is used to deploy and start the preset backup software on the backup server;

[0023] The software deployment instruction is sent to the backup server via the elastic address, so that the backup server deploys and starts the backup software according to the software deployment instruction;

[0024] Receive deployment completion instruction and software start instruction sent by the backup server; wherein, the deployment completion instruction is used to indicate that the backup software deployment is complete, and the software start instruction is used to indicate that the backup software is started;

[0025] The backup instruction is generated based on the deployment completion instruction and the software startup instruction.

[0026] In one possible design, after sending the backup task and the backup instructions to the backup server, the method further includes:

[0027] Upon receiving a backup completion instruction from the backup server, a release instruction is generated; wherein, the release instruction is used to instruct the backup engine to release the backup resources;

[0028] Send the release command to the backup engine to cause the backup engine to release the backup resources;

[0029] Collect log information for data backup;

[0030] The log information is sent to the database so that the database stores the log information.

[0031] Secondly, this application provides a data backup method, which is applied to the scheduling engine of a data backup system. The data backup system further includes a server, a database, a scheduler, and a backup server. The method includes:

[0032] Receive backup task requests sent by the scheduler;

[0033] Based on the backup task requirements, generate resource instance information;

[0034] The resource instance information is sent to the scheduler, so that the scheduler generates a backup instruction based on the resource instance information, and sends the backup instruction and the backup task to the backup server, so that the backup server executes the backup task according to the backup instruction.

[0035] In one possible design, generating resource instance information based on the backup task requirements includes:

[0036] Obtain the backup data attributes from the backup task requirements;

[0037] The backup data attributes are matched with a plurality of preset backup resource instances to obtain a first resource instance that matches the backup data attributes.

[0038] Configure the resources for the first resource instance to obtain the resource instance information.

[0039] In one possible design, after sending the resource instance information to the scheduler, the method further includes:

[0040] Upon receiving a release command from the scheduler, the backup resource is released.

[0041] Thirdly, this application provides a data backup system, including: a server, a database, a scheduler, a scheduling engine, and a backup server;

[0042] The scheduler is used to implement the data backup method described in any of the first aspects;

[0043] The scheduling engine is used to implement the data backup method described in any of the second aspects;

[0044] The server is used to create backup plans;

[0045] The database is used to store the backup plan and log information;

[0046] The backup server is used to perform backup tasks.

[0047] Fourthly, this application provides a data backup device, which is applied to the scheduler of a data backup system. The data backup system further includes a server, a database, a scheduling engine, and a backup server. The device comprises:

[0048] The first receiving module is used to receive the backup plan sent by the database; wherein the backup plan is created by the server according to user requirements and sent to the database, and the backup plan is used to define the backup time and backup content instruction set of the data backup;

[0049] A creation module is used to create backup tasks according to the backup plan and obtain the backup task requirements required to execute the backup tasks; wherein, the backup task is a set of steps to implement the backup plan;

[0050] The first sending module is used to send the backup task requirement to the scheduling engine, so that the scheduling engine generates resource instance information according to the backup task requirement; wherein, the resource instance information is the configuration information of the backup resources required by the backup task requirement;

[0051] The second receiving module is used to receive resource instance information sent by the scheduling engine;

[0052] The instruction generation module is used to generate backup instructions based on the resource instance information; wherein, the backup instructions refer to the instructions of the backup server to execute the backup task;

[0053] The second sending module is used to send the backup task and the backup instruction to the backup server, so that the backup server executes the backup task according to the backup instruction.

[0054] In one possible design, the creation module includes:

[0055] The first acquisition unit is used to acquire the data priority, recovery time after damage, backup time, backup frequency and storage capacity requirements in the backup plan;

[0056] The strategy selection unit is used to select a strategy based on the data priority and the recovery time after damage to obtain the backup strategy of the backup task; wherein, the data priority refers to the importance level of different data in the backup data;

[0057] A time planning unit is used to perform time planning based on the backup time and the backup frequency to obtain the time schedule of the backup task; wherein, the backup time refers to the specific time of the data backup operation, and the backup frequency refers to the execution interval of the data backup operation;

[0058] The media selection unit is used to select a storage medium based on the storage capacity requirement and the preset budget limit to obtain a storage scheme for the backup task; wherein, the storage capacity requirement refers to the total amount of storage space required to store the backup data;

[0059] The system configuration unit is used to configure the system according to the backup strategy and the time schedule to obtain the implementation technology of the backup task;

[0060] The task creation unit is used to create the backup task according to the storage scheme and the implementation technology.

[0061] In one possible design, the instruction generation module includes:

[0062] The second acquisition unit is used to acquire the elastic address and software configuration from the resource instance information;

[0063] A software deployment unit is used to generate software deployment instructions based on the software configuration; wherein the software deployment instructions are used to deploy and start the preset backup software on the backup server;

[0064] The sending unit is configured to send the software deployment instruction to the backup server via the elastic address, so that the backup server deploys and starts the backup software according to the software deployment instruction;

[0065] The receiving unit is configured to receive a deployment completion instruction and a software startup instruction sent by the backup server; wherein the deployment completion instruction is used to indicate that the backup software deployment is complete, and the software startup instruction is used to indicate that the backup software is started.

[0066] The instruction generation unit is used to generate the backup instruction based on the deployment completion instruction and the software startup instruction.

[0067] In one possible design, the data backup device further includes:

[0068] A release instruction generation module is used to generate a release instruction when a backup completion instruction is received from the backup server; wherein the release instruction is used to instruct the backup engine to release the backup resources;

[0069] The fourth sending module is used to send the release command to the backup engine so that the backup engine releases the backup resources;

[0070] The data acquisition module is used to collect log information from data backup.

[0071] The fifth sending module is used to send the log information to the database so that the database stores the log information.

[0072] Fifthly, this application provides a data backup device, which is applied to the scheduling engine of a data backup system. The data backup system further includes a server, a database, a scheduler, and a backup server. The device comprises:

[0073] The third receiving module is used to receive the backup task request sent by the scheduler;

[0074] The information generation module is used to generate resource instance information according to the backup task requirements;

[0075] The third sending module is used to send the resource instance information to the scheduler, so that the scheduler generates a backup instruction based on the resource instance information, and sends the backup instruction and the backup task to the backup server, so that the backup server executes the backup task according to the backup instruction.

[0076] In one possible design, the information generation module includes:

[0077] The third acquisition unit is used to acquire the backup data attributes in the backup task requirements;

[0078] A matching unit is used to match the backup data attributes with a plurality of preset backup resource instances to obtain a first resource instance that matches the backup data attributes.

[0079] The resource configuration unit is used to configure resources for the first resource instance and obtain the resource instance information.

[0080] In one possible design, the data backup device further includes:

[0081] The resource release module is used to release the backup resources when it receives a release command sent by the scheduler.

[0082] Sixthly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0083] The memory stores computer-executed instructions;

[0084] When the processor executes the computer execution instructions stored in the memory, it is used to implement the data backup method as described in any of the first aspects, or to implement the data backup method as described in any of the second aspects.

[0085] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the data backup method as described in any of the first aspects, or to implement the data backup method as described in any of the second aspects.

[0086] Fifthly, this application provides a computer program product, including a computer program, which, when executed by a processor, is used to implement the data backup method as described in any of the first aspects, or to implement the data backup method as described in any of the second aspects.

[0087] This application provides a data backup method, apparatus, device, medium, and product. The method includes: receiving a backup plan sent by a database; wherein the backup plan is created by the server according to user needs and sent to the database, and the backup plan is used to define a set of instructions for data backup time and backup content; creating a backup task according to the backup plan and obtaining backup task requirements required to execute the backup task; wherein the backup task is a set of steps to implement the backup plan; sending the backup task requirements to a scheduling engine, so that the scheduling engine generates resource instance information according to the backup task requirements; wherein the resource instance information is configuration information of backup resources required by the backup task requirements; receiving the resource instance information sent by the scheduling engine; generating a backup instruction according to the resource instance information; wherein the backup instruction is an instruction for the backup server to execute the backup task; sending the backup task and the backup instruction to the backup server, so that the backup server executes the backup task according to the backup instruction. This data backup method, through automated scheduling and resource management processes, reduces the burden on users in ordering and managing hardware and network resources during data backup, and reduces the technical requirements on users. Meanwhile, by dynamically generating and allocating resource instance information, the efficiency of resource utilization is optimized, resource waste is avoided, and the overall operating cost of data backup is reduced. Attached Figure Description

[0088] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0089] Figure 1 This is a schematic diagram illustrating an application scenario of the data backup method provided in the embodiments of this application;

[0090] Figure 2 Flowchart of the data backup method provided in the embodiments of this application Figure 1 ;

[0091] Figure 3 Flowchart of the data backup method provided in the embodiments of this application Figure 2 ;

[0092] Figure 4 Flowchart of the data backup method provided in the embodiments of this application Figure 3 ;

[0093] Figure 5Flowchart of the data backup method provided in the embodiments of this application Figure 4 ;

[0094] Figure 6 A timing diagram of the data backup method provided in the embodiments of this application;

[0095] Figure 7 Schematic diagram of the data backup device provided in the embodiments of this application Figure 1 ;

[0096] Figure 8 Schematic diagram of the data backup device provided in the embodiments of this application Figure 2 ;

[0097] Figure 9 Schematic diagram of the data backup device provided in the embodiments of this application Figure 3 ;

[0098] Figure 10 Schematic diagram of the data backup device provided in the embodiments of this application Figure 4 ;

[0099] Figure 11 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0100] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0101] In the embodiments of this application, the terms "first" and "second" are used to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" do not necessarily imply difference. It should be noted that in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner. In the embodiments of this application, "at least one" refers to one or more, and "more than one" refers to two or more.

[0102] It should be noted that the phrase "at...time" in the embodiments of this application can refer to the instant at which a certain situation occurs, or to a period of time after the occurrence of a certain situation; the embodiments of this application do not specifically limit this. Furthermore, the data backup method provided in the embodiments of this application is merely an example, and data backup methods may include more or fewer elements.

[0103] To facilitate a clear description of the technical solutions in the embodiments of this application, some terms and technologies involved in the embodiments of this application will be briefly introduced below:

[0104] The scheduling engine is an intelligent orchestration and scheduling system that receives the computing and network resource requirements from the backup task scheduling module. By connecting to the cloud provider's cloud management platform and network controller, it automatically opens and configures the required computing and network resources to support the execution of backup tasks, and is responsible for releasing and reclaiming these resources after the tasks are completed.

[0105] Resource instances refer to the instantiation information of specific computing and network resources configured by the scheduling engine in a data backup system to perform backup tasks. These include elastic addresses, storage media, and software configurations. These resource instances are used to support the deployment of backup servers and the execution of backup tasks.

[0106] Backup strategy: This refers to a series of measures and methods established to ensure data security, recovery, and continuous operation. It includes determining the scope of data to be backed up, backup frequency, storage location, and recovery strategy. Common backup strategies include full backup, incremental backup, and differential backup.

[0107] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the invention as detailed in the appended claims.

[0108] The technical solution of the present invention will be described in detail below with reference to specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the present invention will now be described with reference to the accompanying drawings.

[0109] To clearly understand the technical solution of this application, the solutions of existing technologies will first be described in detail. Data backup refers to copying and storing important data to other media or locations so that it can be recovered in case the original data is lost, damaged, or destroyed. The need for data backup stems from a variety of real-world problems, including hardware failures, software errors, software attacks, human error, and natural disasters, which may lead to the permanent loss or unavailability of data. By regularly backing up data, individuals and organizations can ensure that they can quickly recover data in the event of unforeseen events, maintaining business continuity and data integrity. Therefore, data backup is necessary.

[0110] Currently, data backup methods typically employ a resource-based service model. In this model, users need to order and manage the necessary hardware and network resources, such as virtual machines, storage resources, and dedicated lines. Users can choose to build their own backup service or subscribe to a third-party service provider. In the self-built model, users must order virtual machines, storage resources, and dedicated lines, all of which have high maintenance costs. Furthermore, users need significant technical skills to deploy and manage the backup service, increasing labor costs. In the third-party service model, while users don't need to build their own, they still need to pay for the performance specifications of the backup resources, essentially subscribing to a dedicated backup server. Additionally, to ensure data transmission security and efficiency, users may need to subscribe to dedicated lines, further increasing costs. Regardless of the model, users face high long-term expenses, making data backup costly. Therefore, current data backup methods suffer from high costs.

[0111] Therefore, addressing the high cost of existing data backup methods, this research found that to solve this problem, it's necessary to reduce users' hardware and network resource investment costs while ensuring the completion of data backup tasks: ① To ensure the completion of user data backup tasks, a port needs to be set up, through which users can input the type and format of the data to be backed up. ② After the data backup task is created, the resources required for the data backup task can be scheduled through a scheduling module. ③ Based on the needs of the data backup task, different data backup strategies can be compared, and a cost-effective backup strategy can be selected.

[0112] Specifically:

[0113] A network port can be configured, allowing users to set parameters such as the size, format, and type of data to be backed up. The data backup system then creates a data backup task based on these parameters and automatically schedules the necessary resources to execute the task.

[0114] The data backup method in this embodiment receives a backup plan from the database through a scheduler, creates a backup task based on the plan, and obtains the backup task requirements. Then, the requirements are sent to the scheduling engine to generate resource instance information, and a backup instruction is generated upon receiving this information. Finally, the backup task and instruction are sent to the backup server for execution. Users only need to input the data backup plan; there is no need to order and manage backup hardware and network resources, thus achieving automation and efficient scheduling of the data backup process and reducing the cost of data backup.

[0115] Based on the above-mentioned inventive discovery, the technical solution of this application is proposed.

[0116] The following describes the application scenarios of the data backup method provided in the embodiments of the present invention. Figure 1 This is a schematic diagram illustrating an application scenario of the data backup method provided in this application embodiment. For example... Figure 1 As shown, this application scenario includes a server 101, a database 102, a scheduler 103, a scheduling engine 104, and a backup server 105. The server 101 creates a backup plan based on user requirements and sends the backup plan to the database 102. The database 102 sends the backup plan to the scheduler 103. The scheduler 103 creates a backup task based on the backup plan and obtains the backup task requirements needed to execute the backup task. The scheduler 103 sends the backup task requirements to the scheduling engine 104. The scheduling engine 104 generates resource instance information based on the backup task requirements and sends the resource instance information to the scheduler 103. The scheduler 103 generates a backup instruction based on the resource instance information and sends the backup instruction and backup task to the backup server 105. The backup server 105 executes the backup task according to the backup instruction.

[0117] The embodiments of the present invention will now be described with reference to the accompanying drawings.

[0118] Figure 2 Flowchart of the data backup method provided in the embodiments of this application Figure 1 .like Figure 2 As shown, in this embodiment, the execution entity of this invention is a scheduler. Therefore, the data backup method provided in this embodiment includes the following steps:

[0119] S201. Receive the backup plan sent by the database; wherein, the backup plan is created by the server according to the user's needs and sent to the database, and the backup plan is used to define the backup time and backup content instruction set of the data backup.

[0120] Specifically, a communication interface can be set up in the data backup system to receive backup plans sent by the database. This interface allows data transfer between the database and the scheduler. The server generates a backup plan based on user requirements and sends the plan to the database through this interface, which then passes it to the scheduler. This design automates the transmission of backup plans, reduces the need for manual intervention, improves the efficiency and accuracy of the data backup process, and ensures that backup tasks are executed according to the user-specified time and content requirements.

[0121] S202. Based on the backup plan, create a backup task and obtain the backup task requirements needed to execute the backup task; wherein, a backup task is a set of steps to implement the backup plan.

[0122] Specifically, a task generation module can be designed within the scheduler to create backup tasks based on the backup plan. This module parses the received backup plan, identifies the instruction set including backup time and content, and transforms it into specific backup steps. Simultaneously, the task generation module analyzes the resources and conditions required for each task step, forming a backup task requirements list. This design enables automatic conversion from an abstract backup plan to concrete executable tasks, ensuring efficient scheduling of backup tasks and rational allocation of resources, thereby improving the overall system efficiency and reliability.

[0123] S203. Send the backup task request to the scheduling engine so that the scheduling engine can generate resource instance information based on the backup task request; wherein, the resource instance information is the configuration information of the backup resources required by the backup task request.

[0124] Specifically, sending backup task requests to the scheduling engine can be achieved by establishing a communication protocol between the scheduler and the scheduling engine. The scheduler sends the parsed backup task requests to the scheduling engine via this protocol. Upon receiving the requests, the scheduling engine analyzes the required backup resource types, quantities, and configuration parameters based on the requests, and generates corresponding resource instance information. This design enables automatic matching of backup task requests and resource configurations, ensuring that backup tasks receive appropriate resource support, optimizing resource utilization, reducing the possibility of human configuration errors, and improving the reliability and efficiency of backup operations.

[0125] S204. Receive resource instance information sent by the scheduling engine.

[0126] Specifically, a receiving module can be set up in the scheduler to receive resource instance information sent by the scheduling engine. This module is responsible for monitoring the communication channel from the scheduling engine. When the scheduling engine generates and sends resource instance information, the receiving module captures and receives this information. This design ensures that the scheduler can obtain the resource configuration data provided by the scheduling engine in a timely manner, thus making full preparations for the execution of backup tasks. This mechanism improves the response speed and coordination of the data backup process, ensures that backup tasks can be carried out smoothly in a suitable resource environment, and improves the overall efficiency and stability of the system.

[0127] S205. Generate backup instructions based on resource instance information; where backup instructions refer to instructions given by the backup server to perform backup tasks.

[0128] Specifically, generating backup instructions based on resource instance information can be achieved by designing an instruction generation module within the scheduler. This module receives the resource instance information, parses the specific configuration and availability of the resources, and, combined with the requirements of the backup task, generates a corresponding set of backup instructions. These instructions guide the backup server on how to execute the specific backup task. This design automates the conversion from resource configuration to execution instructions, ensuring that the backup server can accurately and efficiently execute backup tasks, reducing the possibility of human intervention and errors, and improving the reliability of backup operations and the overall automation level of the system.

[0129] S206. Send the backup task and backup instructions to the backup server so that the backup server can execute the backup task according to the backup instructions.

[0130] Specifically, sending backup tasks and instructions to the backup server can be achieved by establishing a reliable communication channel between the scheduler and the backup server. The scheduler packages the generated backup tasks and corresponding backup instructions and transmits them to the backup server through this communication channel. After receiving this information, the backup server parses the instructions and executes the specific backup tasks accordingly. This design ensures that backup tasks and instructions are accurately delivered to the backup server, reducing delays and errors in information transmission, improving the accuracy and efficiency of backup task execution, and thus enhancing the overall reliability and automation of the data backup system.

[0131] This embodiment provides a data backup method, which includes: receiving a backup plan sent by a database; wherein the backup plan is created by the server according to user needs and sent to the database, and the backup plan is used to define the backup time and backup content instruction set for data backup; creating a backup task according to the backup plan, and obtaining the backup task requirements required to execute the backup task; wherein the backup task is a set of steps to implement the backup plan; sending the backup task requirements to a scheduling engine, so that the scheduling engine generates resource instance information according to the backup task requirements; wherein the resource instance information is the configuration information of the backup resources required by the backup task requirements; receiving the resource instance information sent by the scheduling engine; generating a backup instruction according to the resource instance information; wherein the backup instruction is an instruction for the backup server to execute the backup task; and sending the backup task and the backup instruction to the backup server, so that the backup server executes the backup task according to the backup instruction. This data backup method achieves the following technical effects: by automatically receiving the backup plan, creating the backup task, generating resource instance information and backup instructions, and sending these instructions to the backup server for execution, it reduces the user's direct management needs of hardware and network resources and lowers the requirements for the user's technical capabilities. Meanwhile, by optimizing resource allocation and task scheduling, the system can effectively utilize existing resources and avoid unnecessary waste. This reduces maintenance costs and reliance on additional resources such as dedicated lines, thereby lowering the overall cost of data backup.

[0132] In one possible design, S202, based on the backup plan, creates a backup task, including:

[0133] S2021. Obtain the data priority, recovery time after damage, backup time, backup frequency and storage capacity requirements in the backup plan.

[0134] Specifically, the backup plan instruction set sent by the server can be parsed to obtain the data priority, recovery time after damage, backup time, backup frequency, and storage capacity requirements in the backup plan. This design can accurately identify and classify different user needs for data backup, ensuring that the creation of backup tasks fully considers the importance of data, recovery timeliness, and reasonable resource allocation, thereby improving the efficiency and reliability of data backup.

[0135] S2022. Select a strategy based on data priority and recovery time after damage to obtain the backup strategy for the backup task; where data priority refers to the importance level of different data in the backup data.

[0136] Specifically, the backup strategy for a backup task is selected based on data priority and recovery time after corruption. This strategy can be achieved through a preset strategy selection algorithm. This algorithm automatically matches the most suitable backup strategy based on data priority and expected recovery time, such as incremental backup, differential backup, or full backup. This design optimizes the use of backup resources, ensures that critical data can be recovered in the shortest possible time, reduces unnecessary data redundancy and storage costs, and improves the overall efficiency and responsiveness of the backup system.

[0137] S2023. Based on the backup time and backup frequency, perform time planning to obtain the time schedule for backup tasks; where backup time refers to the specific time of data backup operation, and backup frequency refers to the execution interval of data backup operation.

[0138] Specifically, time planning based on backup time and frequency allows for the scheduling of backup tasks. This scheduling algorithm automatically generates an optimized timetable based on the user-specified backup time and frequency, ensuring that backup tasks execute within the specified time intervals while avoiding conflicts with other system tasks. This design improves the planning and predictability of backup operations, ensuring that data backups are completed within appropriate time windows, thereby reducing the impact on system performance and meeting users' time requirements for data protection.

[0139] S2024. Select storage media based on storage capacity requirements and preset budget constraints to obtain a storage plan for the backup task; where storage capacity requirements refer to the total amount of storage space required to store backup data.

[0140] Specifically, the storage solution for backup tasks is determined by selecting storage media based on storage capacity requirements and preset budget constraints. This decision-making algorithm automatically selects the most suitable storage media based on the user's storage capacity needs and budget limitations. This design optimizes the allocation of storage resources, ensuring that data backup needs are met while controlling costs, thus improving the economics and sustainability of the backup system.

[0141] S2025. Configure the system according to the backup strategy and schedule to obtain the backup task implementation technology.

[0142] Specifically, the system configuration based on backup strategies and schedules allows the backup tasks to be executed through a configuration management module. This module automatically adjusts the backup system's parameter settings, including network bandwidth allocation, processing priority, and storage paths, based on the selected backup strategy and schedule to ensure the smooth execution of backup tasks. This design enables the backup system to dynamically adapt to different backup needs and time requirements, improving the execution efficiency of backup tasks and the utilization of system resources, while reducing the possibility of human configuration errors.

[0143] S2026. Based on the storage scheme and implementation technology, create a backup task.

[0144] Specifically, based on the storage solution and implementation technology, backup tasks can be created through a task generation module. This module, combining the selected storage solution and specific implementation technology, automatically generates a detailed backup task configuration file, including task parameters, execution steps, and required resources. This design ensures that the backup task configuration matches system resources and technical capabilities, thereby improving the execution efficiency and reliability of the backup task and ensuring the smooth progress of the data backup process and data security.

[0145] The technical advantages of this solution in this embodiment are as follows: By acquiring data priority, recovery time after damage, backup time, backup frequency, and storage capacity requirements from the backup plan, the system can accurately identify and classify users' backup needs. Subsequently, through strategy selection, time planning, and storage scheme formulation, the system can rationally allocate resources and control costs while meeting user needs. Finally, through system configuration and backup task creation, efficient scheduling and execution of backup tasks are achieved. This series of steps ensures the reliability and economy of the data backup process, improves the system's responsiveness and resource utilization, and meets users' diverse data protection needs.

[0146] In one possible design, S205 generates backup instructions based on resource instance information, including:

[0147] S2051. Obtain the elastic address and software configuration from the resource instance information.

[0148] Specifically, obtaining the elastic addresses and software configurations from resource instance information can be achieved through the information interface provided by the scheduling engine. This interface can dynamically allocate and transfer the elastic addresses and software environment configurations required for backup tasks. This design ensures that the backup server can flexibly adapt to different network environments and software requirements, thereby achieving efficient backup software deployment and startup. This dynamic configuration capability improves the resource utilization efficiency and response speed of the backup system, enhancing the system's flexibility and scalability.

[0149] S2052. Generate software deployment instructions based on the software configuration; wherein, the software deployment instructions are used to deploy and start the preset backup software on the backup server.

[0150] Specifically, based on the software configuration, generating software deployment instructions can be achieved by parsing the software configuration parameters contained in the resource instance information. These parameters define specific configuration requirements such as the backup software version, dependencies, and installation path. The generated software deployment instructions can automatically guide the backup server to install and configure the software. This design ensures that the backup software can be deployed accurately on the backup server, reducing the possibility of human configuration errors, improving the automation and reliability of the deployment process, thereby speeding up the preparation time of backup tasks and improving overall system efficiency.

[0151] S2053. Send software deployment instructions to the backup server via the elastic address, so that the backup server can deploy and start the backup software according to the software deployment instructions.

[0152] Specifically, sending software deployment instructions to the backup server via elastic addresses can be achieved through network communication protocols. The elastic address provides dynamic network location information for the backup server, enabling the scheduler to accurately deliver the deployment instructions to the target server. This design leverages the dynamic allocation characteristics of elastic addresses to ensure the accessibility and connection stability of the backup server in different network environments, thereby achieving automated deployment and startup of backup software. This approach improves the system's flexibility and adaptability, supporting efficient backup operations in cloud environments or other dynamic network environments.

[0153] S2054. Receive the deployment completion instruction and software startup instruction sent by the backup server; wherein, the deployment completion instruction is used to indicate that the backup software deployment is complete, and the software startup instruction is used to indicate that the backup software is started.

[0154] Specifically, receiving deployment completion and software startup commands from the backup server can be achieved by establishing a reliable communication channel, typically using message queues or network protocols to receive feedback signals from the backup server. These signals include deployment completion and software startup commands, used to confirm the successful deployment and startup of the backup software, respectively. This design provides an automated feedback mechanism, enabling the scheduler to monitor the deployment and startup status of the backup software in real time, thereby ensuring the smooth execution of backup tasks. This mechanism improves system reliability and controllability, reduces the need for manual intervention, and accelerates the backup process.

[0155] S2055. Generate backup instructions based on deployment completion instructions and software startup instructions.

[0156] Specifically, based on the deployment completion and software startup instructions, backup instructions are generated by parsing and verifying the instruction signals received from the backup server. Once the scheduler confirms receipt of these instructions, it automatically generates specific backup instructions according to predefined backup task requirements and strategies. These instructions contain the parameters and steps required to perform the backup operation. This design ensures that backup operations are performed only after the backup software has been correctly deployed and started, thereby improving the accuracy and efficiency of the backup process. This method reduces the possibility of human error, optimizes the backup task execution flow, and enhances the reliability of data protection.

[0157] The technical advantages of this solution in this embodiment are as follows: By acquiring the elastic address and software configuration from the resource instance information, the system can flexibly adapt to different network environments and software requirements, automatically generate and send software deployment instructions, ensuring that the backup server accurately deploys and starts the required software. This automated process reduces the problems of manual intervention and configuration errors, improving the response speed and resource utilization efficiency of the backup system. Furthermore, real-time reception and processing of feedback instructions from the backup server further enhances the system's reliability and controllability, ensuring that backup operations proceed smoothly under ready conditions, ultimately improving the overall efficiency and security of the data backup process.

[0158] Figure 3 Flowchart of the data backup method provided in the embodiments of this application Figure 2 In this embodiment, in Figure 2 Based on the provided embodiments, the data backup method is further explained. The data backup method includes:

[0159] S301. Receive the backup plan sent by the database; wherein, the backup plan is created by the server according to the user's requirements and sent to the database. The backup plan is used to define the backup time and backup content instruction set of the data backup.

[0160] S302. Based on the backup plan, create a backup task and obtain the backup task requirements needed to execute the backup task; wherein, a backup task is a set of steps to implement the backup plan.

[0161] S303. Send the backup task request to the scheduling engine so that the scheduling engine can generate resource instance information based on the backup task request; wherein, the resource instance information is the configuration information of the backup resources required by the backup task request.

[0162] S304. Receive resource instance information sent by the scheduling engine.

[0163] S305. Generate backup instructions based on resource instance information; where backup instructions refer to instructions given by the backup server to perform backup tasks.

[0164] S306. Send the backup task and backup instructions to the backup server so that the backup server can execute the backup task according to the backup instructions.

[0165] S301-S306 are similar to S201-S206, and will not be described again in this embodiment.

[0166] S307. Upon receiving a backup completion instruction from the backup server, a release instruction is generated; wherein, the release instruction is used to instruct the backup engine to release backup resources.

[0167] Specifically, release commands can be generated by monitoring the backup server's communication ports. Once the backup task is complete, the backup server sends a backup completion command to the scheduler. Upon receiving this command, the scheduler immediately generates a release command and sends it to the backup engine. This design allows for the timely release of computing and storage resources used during the backup process, thereby optimizing resource utilization, reducing costs, and ensuring the efficient operation of the backup system. In this way, the system can dynamically adjust resource allocation, avoid resource waste, and improve the overall performance and response speed of the backup system.

[0168] S308. Send a release command to the backup engine to cause the backup engine to release backup resources.

[0169] Specifically, a release command can be sent to the backup engine via a preset communication protocol. Once the scheduler generates the release command, it sends it to the designated interface of the backup engine over the network. Upon receiving the release command, the backup engine performs resource release operations, including releasing computing resources, storage space, and network bandwidth. This design allows for the rapid recovery and reuse of system resources used during the backup process, improving resource utilization, reducing operating costs, and freeing up necessary resources for subsequent backup tasks or other system tasks, thereby enhancing the efficiency and flexibility of the entire data backup system.

[0170] S309. Collect log information for data backup.

[0171] Specifically, data backup logs can be collected by integrating logging modules into the backup server and scheduler. During backup task execution, these modules record status information, timestamps, error messages, and other relevant data for each step in real time, storing this data in a centralized log system or database. This design provides detailed operation logs and audit trail capabilities, facilitating subsequent troubleshooting and compliance checks. Simultaneously, it provides data support for optimizing backup strategies and improving system reliability, helping to identify potential problems and implement system improvements.

[0172] S310. Send log information to the database so that the database stores the log information.

[0173] Specifically, log information can be sent to the database using a database interface. After the log information is collected and processed, the scheduler or backup server connects to the log database through a database driver and performs an insert operation, writing the log information to the log table. This design ensures persistent storage of log information, enabling long-term preservation and retrieval of log data. This not only improves the maintainability and auditability of the system but also provides a reliable data foundation for subsequent data analysis, system optimization, and problem diagnosis, supporting more accurate decision-making and improvement measures.

[0174] The technical advantages of this solution in this embodiment are as follows: After the backup task is completed, a release command is generated and sent to the backup engine to ensure the timely release of occupied computing and storage resources. This dynamic resource management improves the system's resource utilization and economy, avoiding long-term resource occupation and waste. Secondly, log information is collected and sent to the database, realizing full recording and traceability of the backup process. This not only helps with troubleshooting and performance monitoring but also supports compliance review and historical data analysis. This method improves the efficiency, reliability, and maintainability of the data backup system, ensuring that the system can flexibly respond to different backup needs and environmental changes.

[0175] Figure 4 Flowchart of the data backup method provided in the embodiments of this application Figure 3 .like Figure 4 As shown, in this embodiment, the execution entity of this invention is a scheduling engine. Therefore, the data backup method provided in this embodiment includes the following steps:

[0176] S401, Receive backup task request sent by the scheduler.

[0177] Specifically, the scheduling engine can receive backup task requests from the scheduler through the communication interface between the scheduling engine and the scheduler. The scheduler generates backup task requests based on preset backup policies or user requests and sends these requests to the scheduling engine through this interface. This design ensures that the scheduling engine can obtain the specific requirements of the backup tasks in a timely manner, thereby providing a basis for subsequently generating resource instance information and optimizing the execution efficiency and resource allocation of backup tasks. In this way, the data backup system can respond to backup requests more flexibly and efficiently, improving the overall system reliability and performance.

[0178] S402. Generate resource instance information according to the backup task requirements.

[0179] Specifically, the scheduling engine can parse the parameters and conditions in the backup task requirements and dynamically generate resource instance information based on the current system resource status and availability. This information may include specific configurations such as required storage space, network bandwidth, and computing resources. This design ensures that backup tasks can be executed under optimal resource configuration, improving backup efficiency and resource utilization, while reducing potential resource conflicts or shortages during the backup process, thereby enhancing the overall performance and reliability of the data backup system.

[0180] S403. Send resource instance information to the scheduler so that the scheduler can generate backup instructions based on the resource instance information and send the backup instructions and backup tasks to the backup server so that the backup server can execute the backup tasks according to the backup instructions.

[0181] Specifically, sending resource instance information to the scheduler can be achieved through the communication protocol between the scheduling engine and the scheduler. Upon receiving this information, the scheduler formulates specific backup instructions based on the resource instance information and sends these instructions, along with the backup tasks, to the backup server. The backup server then executes the corresponding backup tasks based on the received backup instructions. This design enables automated and intelligent scheduling of backup tasks, ensuring that backup tasks are executed under appropriate resource configurations, improving the accuracy and efficiency of backup operations, while reducing human intervention, lowering the probability of errors, and enhancing system reliability and response speed.

[0182] The technical advantages of this solution in this embodiment are as follows: By automatically receiving backup plans, creating backup tasks, generating resource instance information and backup instructions, and sending these instructions to the backup server for execution, the system reduces the user's direct management needs for hardware and network resources, and lowers the technical skill requirements for users. Simultaneously, by optimizing resource configuration and task scheduling, the system can effectively utilize existing resources and avoid unnecessary resource waste. This reduces maintenance costs and reliance on additional resources such as dedicated lines, thereby lowering the overall cost of data backup.

[0183] In one possible design, S402 generates resource instance information based on the backup task requirements, including:

[0184] S4021. Obtain the backup data attributes in the backup task requirements.

[0185] Specifically, the backup data attributes within the backup task requirements can be obtained by parsing the backup task requests sent by the scheduler. After receiving the backup task requirements, the scheduling engine uses preset parsing algorithms or rules to extract key attribute information related to the backup, such as data type, data volume, priority, and backup frequency. This design can accurately identify and extract the core requirements of the backup task, thereby providing basic data support for subsequent resource instance matching and configuration, ensuring that the backup task can be executed efficiently and accurately.

[0186] S4022. Match the backup data attributes with multiple preset backup resource instances to obtain the first resource instance that matches the backup data attributes.

[0187] Specifically, a resource instance library can be established to match backup data attributes with multiple preset backup resource instances, obtaining the first resource instance that matches the backup data attributes. The scheduling engine uses a matching algorithm to compare the backup data attributes extracted from the backup task requirements with the attributes of each resource instance in the resource instance library, identifying the resource instance that best meets the requirements as the first resource instance. This design can quickly and accurately select the resource instance most suitable for the current backup task requirements, thereby optimizing resource utilization and improving the execution efficiency and reliability of the backup task.

[0188] S4023. Configure resources for the first resource instance to obtain resource instance information.

[0189] Specifically, the parameters and configuration of the selected primary resource instance can be adjusted and optimized according to the specific needs of the backup task. This may involve allocating appropriate computing resources, storage space, and network bandwidth to the resource instance to ensure it can effectively support the execution of the backup task. This design allows for dynamic adjustment of the resource instance configuration based on task requirements, thereby improving resource utilization efficiency, ensuring efficient execution of backup tasks and reasonable allocation of system resources, and ultimately enhancing the overall performance and reliability of the data backup system.

[0190] The technical effect of this solution in this embodiment is as follows: By obtaining the backup data attributes in the backup task requirements, the system can accurately identify the specific requirements of the task. By matching these attributes with multiple preset backup resource instances, the system can quickly select the most suitable resource instance, thereby avoiding resource waste and unnecessary performance bottlenecks. Precise resource configuration is then performed on the selected resource instance to ensure that it can fully meet the needs of the backup task. This series of steps improves the efficiency and reliability of data backup, reduces resource waste during the backup process, and enhances the system's flexibility and responsiveness when handling complex backup tasks.

[0191] Figure 5Flowchart of the data backup method provided in the embodiments of this application Figure 4 In this embodiment, in Figure 4 Based on the provided embodiments, the data backup method is further explained. The data backup method includes:

[0192] S501: Receive backup task requests sent by the scheduler.

[0193] S502. Generate resource instance information according to the backup task requirements.

[0194] S503. Send resource instance information to the scheduler so that the scheduler can generate backup instructions based on the resource instance information and send the backup instructions and backup tasks to the backup server so that the backup server can execute the backup tasks according to the backup instructions.

[0195] S501-S503 are similar to S401-S403, and will not be described again in this embodiment.

[0196] S504. Upon receiving a release command from the scheduler, release the backup resources.

[0197] Specifically, upon receiving a release command from the scheduler, releasing backup resources can be achieved through a monitoring mechanism within the scheduling engine. This mechanism continuously monitors commands from the scheduler. When a release command is received, the scheduling engine triggers the resource release process, which may include releasing resource allocation, closing related processes, cleaning up temporary data, and returning the resource to the resource pool. This design allows for the timely release of backup resources that are no longer needed, thereby improving system resource utilization, reducing resource occupancy time, lowering operating costs, and providing sufficient resource support for subsequent backup tasks, thus enhancing the efficiency and flexibility of the entire data backup system.

[0198] The technical effect of this solution in this embodiment is that by introducing a resource release mechanism, the resource management efficiency and overall operational performance of the data backup system are improved. When a backup task is completed, the system can promptly respond to the release command sent by the scheduler, quickly releasing the occupied backup resources. This mechanism ensures rapid resource recovery and reallocation, avoiding long-term idleness and waste, thereby improving the system's resource utilization rate. Furthermore, by reducing unnecessary resource occupation time, the system can reduce operating costs and provide sufficient resource support for other backup tasks, enhancing the system's flexibility and responsiveness in multi-tasking environments. This efficient resource management approach ultimately helps improve the overall performance and reliability of the data backup system.

[0199] This application also provides a data backup system, including: a server, a database, a scheduler, a scheduling engine, and a backup server.

[0200] The scheduler is used to implement Figure 1 or Figure 2 Data backup methods.

[0201] The scheduling engine is used to implement Figure 3 or Figure 4 Data backup methods.

[0202] The server is used to create backup plans.

[0203] The database is used to store backup plans and log information.

[0204] The backup server is used to perform backup tasks.

[0205] Figure 6 A timing diagram illustrating the data backup method provided in an embodiment of this application. (See diagram below.) Figure 6 As shown, the method includes:

[0206] S601: The server creates a backup plan based on user needs.

[0207] S602: The server sends the backup plan to the database.

[0208] S603: Database storage backup plan.

[0209] S604: The database sends a backup plan to the scheduler.

[0210] S605: The scheduler creates backup tasks based on the backup plan and obtains the backup task requirements needed to execute the backup tasks.

[0211] S606: The scheduler sends backup task requests to the scheduling engine.

[0212] S607: The scheduling engine generates resource instance information based on backup task requirements.

[0213] S608: The scheduling engine sends resource instance information to the scheduler.

[0214] S609: The scheduler generates backup instructions based on resource instance information.

[0215] S610: The scheduler sends backup tasks and backup instructions to the backup server.

[0216] S611: The backup server executes backup tasks according to backup instructions.

[0217] S612: The backup server sends a backup completion command to the scheduler.

[0218] S613: The scheduler generates release commands and collects log information from data backups.

[0219] S614: The scheduler sends log information to the database.

[0220] S615: The scheduler sends a release command to the scheduling engine.

[0221] S616: The scheduling engine releases backup resources.

[0222] Figure 7 Schematic diagram of the data backup device provided in the embodiments of this application Figure 1 The data backup device is used in the scheduler of the data backup system, which also includes a server, database, scheduling engine, and backup server, such as... Figure 7 As shown, the data backup device includes:

[0223] The first receiving module 701 is used to receive the backup plan sent by the database. The backup plan is created by the server according to the user's requirements and sent to the database. The backup plan is used to define the backup time and backup content instruction set of the data backup.

[0224] The creation module 702 is used to create backup tasks according to the backup plan and obtain the backup task requirements required to execute the backup tasks; wherein, the backup task is a set of steps to implement the backup plan.

[0225] The first sending module 703 is used to send backup task requirements to the scheduling engine, so that the scheduling engine can generate resource instance information according to the backup task requirements; wherein, the resource instance information is the configuration information of the backup resources required by the backup task requirements.

[0226] The second receiving module 704 is used to receive resource instance information sent by the scheduling engine.

[0227] The instruction generation module 705 is used to generate backup instructions based on resource instance information; wherein, the backup instruction refers to the instruction of the backup server to execute the backup task.

[0228] The second sending module 706 is used to send backup tasks and backup instructions to the backup server, so that the backup server can execute backup tasks according to the backup instructions.

[0229] In one possible design, module 702 is created, comprising:

[0230] The first acquisition unit is used to acquire the data priority, recovery time after damage, backup time, backup frequency and storage capacity requirements in the backup plan.

[0231] The strategy selection unit is used to select a strategy based on data priority and recovery time after damage to obtain the backup strategy for the backup task; where data priority refers to the importance level of different data in the backup data.

[0232] The time planning unit is used to perform time planning based on backup time and backup frequency to obtain the time schedule for backup tasks; where backup time refers to the specific time of data backup operation, and backup frequency refers to the execution interval of data backup operation.

[0233] The media selection unit is used to select the storage media based on the storage capacity requirements and preset budget constraints to obtain the storage scheme for the backup task; whereby the storage capacity requirements refer to the total amount of storage space required to store the backup data.

[0234] The system configuration unit is used to configure the system according to the backup strategy and schedule to obtain the implementation technology of the backup task.

[0235] The task creation unit is used to create backup tasks based on the storage scheme and implementation technology.

[0236] In one possible design, the instruction generation module 705 includes:

[0237] The second acquisition unit is used to acquire the elastic address and software configuration from the resource instance information.

[0238] The software deployment unit is used to generate software deployment instructions based on the software configuration; the software deployment instructions are used to deploy and start the preset backup software on the backup server.

[0239] The sending unit is used to send software deployment instructions to the backup server via an elastic address, so that the backup server can deploy and start the backup software according to the software deployment instructions.

[0240] The receiving unit is used to receive the deployment completion instruction and the software start instruction sent by the backup server; wherein, the deployment completion instruction is used to indicate that the backup software deployment is complete, and the software start instruction is used to indicate that the backup software is started.

[0241] The instruction generation unit is used to generate backup instructions based on deployment completion instructions and software startup instructions.

[0242] Figure 8 Schematic diagram of the data backup device provided in the embodiments of this application Figure 2 The data backup device is used in the scheduler of the data backup system, which also includes a server, database, scheduling engine, and backup server, such as... Figure 8 As shown, the data backup device also includes:

[0243] The release instruction generation module 807 is used to generate a release instruction when a backup completion instruction is received from the backup server; the release instruction is used to instruct the backup engine to release backup resources.

[0244] The fourth sending module 808 is used to send a release command to the backup engine so that the backup engine releases the backup resources.

[0245] The acquisition module 809 is used to collect log information for data backup.

[0246] The fifth sending module 810 is used to send log information to the database so that the database can store the log information.

[0247] The data backup device provided in this embodiment can perform... Figure 2 or Figure 3 The technical solution of the method embodiment shown has the same implementation principle and technical effect as... Figure 2 or Figure 3 The methods and embodiments shown are similar and will not be described in detail here.

[0248] Figure 9 Schematic diagram of the data backup device provided in the embodiments of this application Figure 3 The data backup device is used in the scheduling engine of the data backup system, which also includes a server, database, scheduler, and backup server, such as... Figure 9 As shown, the data backup device includes:

[0249] The third receiving module 901 is used to receive backup task requests sent by the scheduler.

[0250] The information generation module 902 is used to generate resource instance information according to the backup task requirements.

[0251] The third sending module 903 is used to send resource instance information to the scheduler, so that the scheduler can generate backup instructions based on the resource instance information and send the backup instructions and backup tasks to the backup server, so that the backup server can execute the backup tasks according to the backup instructions.

[0252] In one possible design, the information generation module 902 includes:

[0253] The third acquisition unit is used to acquire the backup data attributes required by the backup task.

[0254] The matching unit is used to match backup data attributes with multiple preset backup resource instances to obtain the first resource instance that matches the backup data attributes.

[0255] The resource configuration unit is used to configure resources for the first resource instance and obtain resource instance information.

[0256] Figure 10 Schematic diagram of the data backup device provided in the embodiments of this application Figure 4The data backup device is used in the scheduling engine of the data backup system, which also includes a server, database, scheduler, and backup server, such as... Figure 10 As shown, the data backup device also includes:

[0257] The resource release module 1004 is used to release backup resources when it receives a release command sent by the scheduler.

[0258] The data backup device provided in this embodiment can perform... Figure 3 or Figure 4 The technical solution of the method embodiment shown has the same implementation principle and technical effect as... Figure 3 or Figure 4 The methods and embodiments shown are similar and will not be described in detail here.

[0259] Figure 11 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Figure 11 As shown, the electronic device includes at least one processor 1110 and a memory 1120. The electronic device also includes a communication component 1130. The processor 1110, memory 1120, and communication component 1130 are connected via a bus 1140.

[0260] In a specific implementation, at least one processor 1110 executes computer execution instructions stored in memory 1120, causing at least one processor 1110 to implement the data backup method of the above embodiments.

[0261] The specific implementation process of processor 1110 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0262] In the above embodiments, it should be understood that the processor 1110 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0263] The memory 1120 may include high-speed RAM memory, and may also include non-volatile memory NVM, such as at least one disk storage.

[0264] Bus 1140 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Bus 1140 can be divided into address bus, data bus, control bus, etc. For ease of illustration, bus 1140 in the accompanying drawings of this application is not limited to only one bus or one type of bus.

[0265] The above description of the functions implemented by electronic devices and main control devices has introduced the solutions provided by the embodiments of the present invention. It is understood that, in order to implement the above functions, the electronic device or main control device includes hardware structures and / or software modules corresponding to the execution of each function. By combining the units and algorithm steps of the various examples described in the embodiments of the present invention, the embodiments of the present invention can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the technical solutions of the embodiments of the present invention.

[0266] This application also provides a computer-readable storage medium storing computer-executable instructions. When executed by a processor, these instructions are used to implement the data backup method described in the above embodiments. In the specific implementation of the aforementioned multiprotocol label switching message transmission method, each module can be implemented as a processor.

[0267] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0268] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in application-specific integrated circuits (ASICs). Alternatively, the processor and the readable storage medium can exist as discrete components in an electronic device or a host device.

[0269] This application also provides a computer program product, including a computer program, which, when executed by a processor, is used to implement the data backup method described in the above embodiments.

[0270] The computer program is stored in a readable storage medium, and at least one processor can read the computer program from the readable storage medium and execute the computer program to perform the scheme provided in any of the above embodiments.

[0271] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disk, or optical disk.

[0272] The technical solutions of this application have been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it is readily understood by those skilled in the art that the scope of protection of this application is obviously not limited to these specific embodiments. The above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. These modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A data backup method, characterized in that, The method is applied to the scheduler of a data backup system, which further includes a server, a database, a scheduling engine, and a backup server. The method includes: Receive a backup plan sent by the database; wherein the backup plan is created by the server according to user requirements and sent to the database, and the backup plan is used to define the backup time and backup content instruction set for data backup; According to the backup plan, a backup task is created, and the backup task requirements required to execute the backup task are obtained; wherein, the backup task is a set of steps to implement the backup plan; The backup task request is sent to the scheduling engine, so that the scheduling engine generates resource instance information based on the backup task request; wherein, the resource instance information is the configuration information of the backup resources required by the backup task request; Receive resource instance information sent by the scheduling engine; Obtain the elastic address and software configuration from the resource instance information; Based on the software configuration, a software deployment instruction is generated; wherein, the software deployment instruction is used to deploy and start the preset backup software on the backup server; The software deployment instruction is sent to the backup server via the elastic address, so that the backup server deploys and starts the backup software according to the software deployment instruction; Receive deployment completion instruction and software start instruction sent by the backup server; wherein, the deployment completion instruction is used to indicate that the backup software deployment is complete, and the software start instruction is used to indicate that the backup software is started; Based on the deployment completion instruction and the software startup instruction, a backup instruction is generated; wherein, the backup instruction refers to the instruction of the backup server to execute the backup task; The backup task and the backup instruction are sent to the backup server so that the backup server executes the backup task according to the backup instruction.

2. The data backup method according to claim 1, characterized in that, The step of creating a backup task according to the backup plan includes: Obtain the data priority, recovery time after damage, backup time, backup frequency, and storage capacity requirements in the backup plan; The backup strategy for the backup task is obtained by selecting a strategy based on the data priority and the recovery time after damage; wherein, the data priority refers to the importance level of different data in the backup data; The backup task's time schedule is obtained by performing time planning based on the backup time and the backup frequency; wherein, the backup time refers to the specific time of the data backup operation, and the backup frequency refers to the execution interval of the data backup operation; Based on the storage capacity requirements and the preset budget constraints, a storage medium is selected to obtain the storage scheme for the backup task; wherein, the storage capacity requirements refer to the total amount of storage space required to store the backup data; The system is configured according to the backup strategy and the time schedule to obtain the implementation technology of the backup task; The backup task is created based on the storage scheme and the implementation technology described.

3. The data backup method according to claim 1, characterized in that, After sending the backup task and the backup instruction to the backup server, the method further includes: Upon receiving a backup completion instruction from the backup server, a release instruction is generated; wherein, the release instruction is used to instruct the backup engine to release the backup resources; Send the release command to the backup engine to cause the backup engine to release the backup resources; Collect log information for data backup; The log information is sent to the database so that the database stores the log information.

4. A data backup method, characterized in that, The method is applied to the scheduling engine of a data backup system, which further includes a server, a database, a scheduler, and a backup server. The method includes: Receive backup task requests sent by the scheduler; Based on the backup task requirements, resource instance information is generated; wherein, the resource instance information is the configuration information of the backup resources required by the backup task requirements; The resource instance information is sent to the scheduler so that the scheduler can obtain the elastic address and software configuration from the resource instance information. The scheduler generates a software deployment instruction based on the software configuration and sends the software deployment instruction to the backup server through the elastic address, so that the backup server deploys and starts the backup software according to the software deployment instruction. The scheduler is also used to receive a deployment completion instruction and a software start instruction sent by the backup server. The scheduler also generates a backup instruction based on the deployment completion instruction and the software start instruction and sends the backup instruction and backup task to the backup server, so that the backup server executes the backup task according to the backup instruction. The software deployment instruction is used to deploy and start the preset backup software on the backup server. The deployment completion instruction is used to indicate that the backup software deployment is complete. The software start instruction is used to indicate that the backup software is started. The backup task is created by the scheduler according to the backup plan, and the backup plan is sent to the scheduler by the database.

5. The data backup method according to claim 4, characterized in that, The step of generating resource instance information according to the backup task requirements includes: Obtain the backup data attributes from the backup task requirements; The backup data attributes are matched with a plurality of preset backup resource instances to obtain a first resource instance that matches the backup data attributes. Configure the resources for the first resource instance to obtain the resource instance information.

6. The data backup method according to claim 4, characterized in that, After sending the resource instance information to the scheduler, the method further includes: Upon receiving a release command from the scheduler, the backup resource is released.

7. A data backup system, comprising: Server-side components, database, scheduler, scheduling engine, and backup server; The scheduler is used to implement the data backup method according to any one of claims 1 to 3; The scheduling engine is used to implement the data backup method according to any one of claims 4 to 6; The server is used to create backup plans; The database is used to store the backup plan and log information; The backup server is used to perform backup tasks.

8. A data backup device, characterized in that, The device is used in the scheduler of a data backup system, which further includes a server, a database, a scheduling engine, and a backup server. Therefore, the device comprises: The first receiving module is used to receive the backup plan sent by the database; wherein the backup plan is created by the server according to user requirements and sent to the database, and the backup plan is used to define the backup time and backup content instruction set of the data backup; A creation module is used to create backup tasks according to the backup plan and obtain the backup task requirements required to execute the backup tasks; wherein, the backup task is a set of steps to implement the backup plan; The first sending module is used to send the backup task requirement to the scheduling engine, so that the scheduling engine generates resource instance information according to the backup task requirement; wherein, the resource instance information is the configuration information of the backup resources required by the backup task requirement; The second receiving module is used to receive resource instance information sent by the scheduling engine; The first acquisition module is used to acquire the elastic address and software configuration from the resource instance information; The first generation module is used to generate software deployment instructions based on the software configuration; wherein the software deployment instructions are used to deploy and start the preset backup software on the backup server; The fourth sending module is used to send the software deployment instruction to the backup server through the elastic address, so that the backup server deploys and starts the backup software according to the software deployment instruction; The fourth receiving module is used to receive the deployment completion instruction and the software start instruction sent by the backup server; wherein, the deployment completion instruction is used to indicate that the backup software has been deployed, and the software start instruction is used to indicate that the backup software has started. The second generation module is used to generate a backup instruction based on the deployment completion instruction and the software startup instruction; wherein, the backup instruction refers to the instruction of the backup server to execute the backup task; The second sending module is used to send the backup task and the backup instruction to the backup server, so that the backup server executes the backup task according to the backup instruction.

9. A data backup device, characterized in that, The device is used in the scheduling engine of a data backup system, which also includes a server, a database, a scheduler, and a backup server. Therefore, the device comprises: The third receiving module is used to receive the backup task request sent by the scheduler; The information generation module is used to generate resource instance information according to the backup task requirements; wherein, the resource instance information is the configuration information of the backup resources required by the backup task requirements; The third sending module is used to send the resource instance information to the scheduler, so that the scheduler can obtain the elastic address and software configuration in the resource instance information. The scheduler is used to generate a software deployment instruction according to the software configuration, and send the software deployment instruction to the backup server through the elastic address, so that the backup server can deploy and start the backup software according to the software deployment instruction. The scheduler is also used to receive a deployment completion instruction and a software start instruction sent by the backup server. The scheduler is also used to generate a backup instruction according to the deployment completion instruction and the software start instruction, and send the backup instruction and backup task to the backup server, so that the backup server can execute the backup task according to the backup instruction. The software deployment instruction is used to deploy and start the preset backup software on the backup server. The deployment completion instruction is used to indicate that the backup software deployment is complete. The software start instruction is used to indicate that the backup software is started. The backup task is created by the scheduler according to the backup plan. The backup plan is sent to the scheduler by the database.

10. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; When the processor executes the computer execution instructions stored in the memory, it is used to implement the data backup method as described in any one of claims 1 to 3, or to implement the data backup method as described in any one of claims 4 to 6.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the data backup method as described in any one of claims 1 to 3, or to implement the data backup method as described in any one of claims 4 to 6.

12. A computer program product comprising a computer program, which, when executed by a processor, is used to implement the data backup method as described in any one of claims 1 to 3, or to implement the data backup method as described in any one of claims 4 to 6.

Images