Data backup method and system

Abstract

The invention discloses a data backup method and system, and relates to the technical field of artificial intelligence, and the method comprises the steps: creating a backup task in an interaction module, and transmitting the backup task to a client through a core control module; the client applies for mounting storage from the storage management module, and after storage resource mounting is completed, the task execution module is triggered to start a backup task execution process; and the task execution module executes the backup command in the mounted storage environment to complete the data backup operation, so that the problem that in the prior art, flexible configuration of backup logic, guarantee of storage adaptation stability and efficient data backup compatible with multiple types of storage cannot be achieved at the same time is solved.

Description

Technical Field

[0001] This invention relates to the field of artificial intelligence technology, and in particular to a data backup method and system. Background Technology

[0002] Current traditional data backup software mostly uses a closed architecture with built-in functions. Users can only call the software's preset backup functions, which cannot adapt to subsequent new backup and recovery needs that are not built in. This results in a serious lack of flexibility and makes it difficult to cope with the diverse data protection scenarios brought about by the expansion of enterprise business. Meanwhile, backup and recovery commands often need to be executed locally on the client and must be compatible with local paths and object storage such as OSS / S3. However, existing closed software lacks a general mechanism to adapt to such storage environments, resulting in poor storage compatibility and limited custom operations.

[0003] Therefore, there is an urgent need for a data backup method that can overcome the limitations of both functionality and storage compatibility. Summary of the Invention

[0004] In view of this, the present invention proposes a data backup method and system that can achieve data security isolation and privacy protection, and ensure the security and compliant use of data throughout the entire process.

[0005] To achieve the above objectives, the present invention provides the following technical solution: A data backup method, comprising: A backup task is created in the interaction module and then sent to the client through the core control module. When the storage management module receives the client's request to mount storage, The client requests storage to be mounted to the storage management module. After the storage resources are mounted, the task execution module is triggered to start the backup task execution process. The task execution module executes backup commands in the mounted storage environment to complete the data backup operation.

[0006] Based on the above technical solution, the present invention can be further improved as follows: Optionally, before the step of creating a backup task in the interactive module, the following may also be included: Several custom command templates are created, and these custom command templates are forwarded to the core control module via the relay module for storage management.

[0007] Optionally, the command template includes command execution environment parameters, backup function description, execution object information, a list of parameters to be filled, and success identifier keywords, error identifier keywords, and alarm identifier keywords for judging the execution result.

[0008] Optionally, the interaction module creates a backup task, including: Select a registered custom command template to create a backup task and configure the storage parameters for the backup task.

[0009] Optionally, after the task execution module executes the backup command in the mounted storage environment and completes the data backup operation steps, the method further includes: The task execution module sends the execution log and execution results back to the core control module; The core control module processes the received execution results and displays the execution status of the backup task to the user through the interaction module.

[0010] Optionally, the data backup method further includes: During the backup task execution, the storage management module continuously provides storage read and write capabilities to the task execution module to ensure that the backup data can be accessed normally and stored in the mounted storage resources.

[0011] Optionally, the data backup method further includes: When the task execution module executes backup commands in the mounted storage environment, it monitors the execution process of the backup commands in real time. When an execution timeout or abnormal resource usage is detected, it automatically pauses the execution of the backup commands and generates alarm information.

[0012] A data backup system, comprising: The interactive module is used to create backup tasks; The core control module is used to send the backup task to the client; The client is used to request storage to be mounted when the storage management module receives the storage mounting request from the client. After the storage resource is mounted, the task execution module is triggered to start the backup task execution process. The task execution module is used to execute backup commands in the mounted storage environment to complete the data backup operation.

[0013] An electronic device includes a memory, a processor, and a computer program stored in the memory and running on the processor, wherein the processor executes the computer program to implement the steps of the method described herein.

[0014] A non-transitory computer-readable storage medium having a computer program stored thereon, the computer program implementing the steps of the method when executed by a processor.

[0015] The present invention has the following advantages: The data backup method in this invention breaks through the functional limitations of traditional closed backup software. Through a collaborative architecture of "task creation by the interactive module + scheduling by the core control module," it supports flexible configuration of backup logic without relying on built-in software functions and can quickly adapt to new backup needs. The client actively requests storage to be mounted from the storage management module, ensuring that the storage environment is ready before backup and avoiding task interruption due to storage compatibility issues, thus improving the stability of backup execution. The task execution module executes commands in the mounted storage environment, solving the compatibility problem of multiple storage types and balancing backup efficiency with scenario versatility. Attached Figure Description

[0016] For illustrative and not limiting purposes, the present invention will now be described in conjunction with embodiments and accompanying drawings, wherein: Figure 1 This is a flowchart illustrating the data backup method in an embodiment of the present invention; Figure 2 This is a schematic diagram of the main components of the data backup system in an embodiment of the present invention; Figure 3 This is a schematic diagram of the physical structure of the electronic device provided by the present invention. Detailed Implementation

[0017] To enable those skilled in the art to better understand the present invention, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0018] It should be noted that the terms "first," "second," etc., in the specification and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be used interchangeably where appropriate for the embodiments of the invention described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0019] It should be noted that, where there is no conflict, the embodiments and features of the present invention can be combined with each other. The embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0020] Figure 1This is a flowchart illustrating the data backup method in an embodiment of the present invention, such as... Figure 1 As shown, the data backup method provided in this embodiment of the invention includes the following steps S101 to S103.

[0021] S101, the interaction module creates a backup task and sends the backup task to the client through the core control module.

[0022] The step of creating a backup task in the interactive module also includes: Several custom command templates are created, and these custom command templates are forwarded to the core control module via the relay module for storage management.

[0023] The command template includes command execution environment parameters, backup function description, execution object information, a list of parameters to be filled, and success identifier keywords, error identifier keywords, and alarm identifier keywords used to determine the execution result.

[0024] Creating a backup task in the interactive module includes: Select a registered custom command template to create a backup task and configure the storage parameters for the backup task.

[0025] S102, when the storage management module receives the client's request to mount storage, the client requests to mount storage from the storage management module. After the storage resource is mounted, the task execution module is triggered to start the backup task execution process.

[0026] S103, the task execution module executes backup commands in the mounted storage environment to complete the data backup operation.

[0027] After the task execution module executes the backup command in the mounted storage environment and completes the data backup operation steps, the following steps are also included: The task execution module sends the execution log and execution results back to the core control module; The core control module processes the received execution results and displays the execution status of the backup task to the user through the interaction module.

[0028] Data backup methods also include: During the backup task execution, the storage management module continuously provides storage read and write capabilities to the task execution module to ensure that the backup data can be accessed normally and stored in the mounted storage resources.

[0029] When the task execution module executes backup commands in the mounted storage environment, it monitors the execution process of the backup commands in real time. When an execution timeout or abnormal resource usage is detected, it automatically pauses the execution of the backup commands and generates alarm information.

[0030] The data backup method includes the following steps: 1. Register a custom template: Users can register custom command templates through Ybm-ui.

[0031] Ybm-gin forwards templates to Ybm-Server for storage and management.

[0032] 2. Create a backup task: Users create backup tasks through Ybm-ui, select templates, and configure storage.

[0033] Ybm-gin forwards the backup task to Ybm-Server.

[0034] 3. Assign tasks: Ybm-Server sends the task to YBM-Client, which includes storage requirements and cmd commands.

[0035] 4. Mount storage: YBM-Client requests storage to be mounted from YBM-bakstor.

[0036] 5. Trigger task execution: YBM-Client triggers YBM-TASK to perform a backup task.

[0037] 6. Execute the backup command: YBM-TASK executes the backup command.

[0038] 7. Returned results: YBM-TASK sends the execution log and execution results back to Ybm-Server.

[0039] 8. Display task status: Ybm-Server displays the task status on Ybm-ui.

[0040] 9. Provides storage read and write capabilities: YBM-bakstor provides storage read and write capabilities for YBM-TASK, ensuring that backup tasks can access storage.

[0041] UI (Ybm-ui): The interaction module used to operate and view task status.

[0042] GIN (Ybm-gin): The front-end, responsible for forwarding user requests.

[0043] SVR (Ybm-Server): The core control module, responsible for task scheduling and management.

[0044] CLI (YBM-Client): The client, responsible for receiving and executing tasks.

[0045] TSK (YBM-TASK): Task executor, responsible for actually executing backup commands.

[0046] STR (YBM-bakstor): Storage management module, responsible for mounting and providing storage read and write capabilities.

[0047] Figure 2 This is a schematic diagram illustrating the main components of the data backup system in an embodiment of the present invention. (See diagram below.) Figure 2 As shown, the data backup system 1 provided in this embodiment of the invention includes an interaction module 10, a core control module 20, a client 30, a storage management module 40, and a task execution module 50.

[0048] Interactive module 10 is used to create backup tasks; The interactive module is responsible for providing users with an operation entry point, supporting backup / restore task creation, configuration management, and status query.

[0049] Interactive module functional module Task creation: Visually configure backup / recovery strategies (such as cycle, storage target, command template).

[0050] Template Management: Register and edit cmd execution templates, and associate them with backup / restore logic.

[0051] Status monitoring: Real-time display of task progress, execution logs, and anomaly alerts.

[0052] The core control module 20 is used to send the backup task to the client; The core control module is responsible for connecting user needs with execution logic and playing a key role in process orchestration and task management.

[0053] Disassembly of the core control module's 20 sub-modules: Ybm-gin (Gateway / Dispatch Center): Task forwarding: Receives Ybm-ui requests and converts them into executable tasks for Ybm-Server.

[0054] Command Management: Upload and update custom cmd programs, and maintain the command version repository.

[0055] Ybm-Server (Core Service): Template / Plan Library: Stores cmd execution templates and task scheduling plans (when to execute and execution strategy).

[0056] Task orchestration: Integrates user configurations and templates to generate complete task information that can be distributed.

[0057] Status synchronization: Collect the execution results of YBM-TASK and send them back to Ybm-ui for display.

[0058] The client 30 is used to request storage to be mounted to the storage management module 40 when the storage management module receives the storage mounting request from the client. After the storage resource is mounted, the task execution module 50 is triggered to start the backup task execution process. Storage Management Module 40 (YBM-bakstor) Storage Management Module 40's responsibilities: to interface with various storage media, provide a unified storage abstraction, and decouple business operations from underlying storage differences.

[0059] Storage management module 40 supports the following storage types: Local / Network Storage: NAS (File Sharing), iSCSI (Block Storage).

[0060] Object storage: S3 (compatible with OSS / AWS / MinIO, etc.).

[0061] Scalability: Third-party storage management (supports more types via plugins / adapters). Core logic: Storage mounting: Dynamically mount the corresponding storage according to task requirements (e.g., mount S3 during backup and NAS during recovery).

[0062] Metadata management: Records storage usage and path mapping, and works with the task execution layer to read and write data.

[0063] The task execution module 50 is used to execute backup commands in the mounted storage environment to complete the data backup operation.

[0064] Task Execution Module 50's responsibilities include: implementing specific tasks, executing backup / restore commands, and interacting with the storage layer.

[0065] Task execution module 50 sub-module breakdown: YBM-Client (proxy / client): Task parsing: Receives tasks from Ybm-Server and parses them into locally executable logic.

[0066] Environment preparation: Mount storage (NAS / iSCSI / S3, etc.) as needed to ensure the execution environment is ready.

[0067] YBM-TASK (Task Executor): Command execution: Invokes the cmd program to perform backup / restore operations.

[0068] Process feedback: Real-time recording of execution logs and status (success / failure / progress), and transmission back to Ybm-Server.

[0069] The data backup system has industry-standard storage functions such as NAS and iSCSI or the ability to manage third-party storage, and can mount backup storage space to backup clients through the above protocols; The backup system has the S3 object storage protocol, or can register and manage third-party object storage such as OSS as a backup storage pool; Users can customize the execution template, defining the cmd command execution environment, function, execution target, required parameters, and output success, error, and alarm keywords; The backup system can upload and recognize user-defined cmd commands; The backup system can issue scheduled tasks and user-defined cmd commands as needed, and can also control modules such as start, stop, and pause. The backup system can capture the input and output of user-defined backup and restore command prompts and determine whether the execution result is successful or unsuccessful.

[0070] Figure 3 This is a schematic diagram of the physical structure of an electronic device provided in an embodiment of the present invention, such as... Figure 3 As shown, the electronic device 60 includes: a processor 601, a memory 602, and a bus 603; The processor 601 and the memory 602 communicate with each other via the bus 603. The processor 601 is used to call program instructions in the memory 602 to execute the methods provided in the above-described method embodiments, and to execute the methods provided in the embodiments of the present invention.

[0071] This embodiment provides a non-transitory computer-readable storage medium that stores computer instructions, which cause a computer to execute the method provided in this embodiment of the invention.

[0072] 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. The aforementioned storage medium includes various storage media capable of storing program code, such as ROM, RAM, magnetic disk, or optical disk.

[0073] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A data backup method, characterized in that, include: The interaction module creates a backup task and sends the backup task to the client through the core control module; When the storage management module receives the client's request to mount storage, the client requests to mount storage to the storage management module. After the storage resource is mounted, the task execution module is triggered to start the backup task execution process. The task execution module executes backup commands in the mounted storage environment to complete the data backup operation.

2. The data backup method according to claim 1, characterized in that, Before the step of creating a backup task in the interactive module, the following is also included: Several custom command templates are saved, and the custom command templates are forwarded to the core control module via the relay module for storage management.

3. The data backup method according to claim 1, characterized in that, The command template includes command execution environment parameters, backup function description, execution object information, a list of parameters to be filled, and success identifier keywords, error identifier keywords, and alarm identifier keywords used to determine the execution result.

4. The data backup method according to claim 3, characterized in that, The interactive module creates a backup task, including: Select a registered custom command template to create a backup task and configure the storage parameters for the backup task.

5. The data backup method according to claim 1, characterized in that, After the task execution module executes the backup command in the mounted storage environment and completes the data backup operation steps, the following steps are also included: The task execution module sends the execution log and execution results back to the core control module; The core control module processes the received execution results and displays the execution status of the backup task to the user through the interaction module.

6. The data backup method according to claim 1, characterized in that, The data backup method further includes: During the backup task execution, the storage management module continuously provides storage read and write capabilities to the task execution module to ensure that the backup data can be accessed normally and stored in the mounted storage resources.

7. The data backup method according to claim 1, characterized in that, The data backup method further includes: When the task execution module executes backup commands in the mounted storage environment, it monitors the execution process of the backup commands in real time. When an execution timeout or abnormal resource usage is detected, it automatically pauses the execution of the backup commands and generates alarm information.

8. A data backup system, characterized in that, include: The interactive module is used to create backup tasks; The core control module is used to send the backup task to the client; The client is used to request storage to be mounted to the storage management module when the storage management module receives the storage mounting request from the client. After the storage resource is mounted, the task execution module is triggered to start the backup task execution process. The task execution module is used to execute backup commands in the mounted storage environment to complete the data backup operation.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method as described in any one of claims 1 to 7.

10. A non-transitory computer-readable medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 7.

Images