Data backup method and device, nonvolatile storage medium and electronic equipment

Abstract

The invention discloses a data backup method and device, a nonvolatile storage medium and electronic equipment. The method relates to the field of financial science and technology, and comprises the following steps: receiving a backup instruction for backing up data of a target type; according to a predefined conversion strategy, converting the backup instruction into a backup request which can be identified by a backup component of the cluster; the backup request is forwarded to a backup component, and the backup component is used for creating a target interface in an interface server according to the backup request and backing up the data of the target type in the cluster in a memory through the target interface. Through the data backup method and device, the problem that in the prior art, only overall backup can be carried out on cluster data, and backup cannot be carried out on data of a specified type in a cluster is solved.

Description

Technical Field

[0001] The present application relates to the field of financial technology, and specifically, to a data backup method, device, non-volatile storage medium and electronic device. Background Art

[0002] The existing method of backing up cluster data is to back up through a distributed key-value storage system, and save a snapshot of the cluster state by performing a snapshot operation on the distributed key-value storage system. However, the distributed key-value storage system backup is based on the entire cluster, and it is not possible to back up specific types of data. In addition, since it is not possible to selectively back up data, it is also impossible to selectively restore specific types of data during data recovery, which may cause resource waste and inefficiency in a cluster environment with large amounts of data and diverse types.

[0003] Currently, no effective solution has been proposed to solve the problem that related technologies can only back up the cluster data as a whole but cannot back up the data of a specified type in the cluster. Summary of the invention

[0004] The main purpose of the present application is to provide a data backup method, device, non-volatile storage medium and electronic device to solve the technical problem in the related art that only the cluster data can be backed up as a whole, but the specified type of data in the cluster cannot be backed up.

[0005] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a data backup method is provided. The method comprises: receiving a backup instruction for backing up data of a target type; converting the backup instruction into a backup request recognizable by a backup component of a cluster according to a predefined conversion strategy; forwarding the backup request to the backup component, wherein the backup component is used to create a target interface in an interface server according to the backup request, and backing up the data of the target type in the cluster in a storage device through the target interface.

[0006] Optionally, according to a predefined conversion strategy, the backup instruction is converted into a backup request recognizable by the backup component of the cluster, including: determining a target conversion strategy that matches the target type in the predefined conversion strategy; generating a backup request according to the backup parameters included in the backup instruction according to the target conversion strategy.

[0007] Optionally, in accordance with the target conversion strategy and according to the backup parameters included in the backup instruction, a backup request is generated, including: filling the backup parameters into the request template included in the target conversion strategy to generate a backup request, wherein the request template includes a code for instructing to perform data backup on the target type of data, and the backup parameters include at least one of the following: backup frequency, retention time of backup data, and the backup component is used to call the target interface to back up the target type of data in the cluster in the memory according to the backup parameters.

[0008] Optionally, the backup component is further used to perform real-time detection of data in the cluster through the target interface, and when it is detected that the data in the cluster is updated, back up the target type data added during the update in the storage.

[0009] Optionally, it also includes: sending a query request for querying data backup status to the interface server, wherein the query request includes a target type, and the interface server is used to determine the backup status of the target interface based on the target type, and return the backup status to the backup management gateway; receiving and displaying the backup status returned by the interface server.

[0010] Optionally, it also includes: receiving a recovery instruction for recovering data of a target type; converting the recovery instruction into a recovery request recognizable by a backup component according to a conversion strategy; forwarding the recovery request to the backup component, wherein the backup component is used to read the data of the target type in the memory, and create a recovery interface in the interface server according to the recovery request, and restore the data of the target type in the memory to the cluster through the recovery interface.

[0011] In order to achieve the above-mentioned purpose, according to another aspect of the present application, a data backup device is provided. The device includes: a receiving module, which is used to receive a backup instruction for backing up target type data; a conversion template, which is used to convert the backup instruction into a backup request recognizable by the backup component of the cluster according to a predefined conversion strategy; and a forwarding module, which is used to forward the backup request to the backup component, wherein the backup component is used to create a target interface in the interface server according to the backup request, and back up the target type data in the cluster in the storage through the target interface.

[0012] Optionally, in the data backup device provided in an embodiment of the present application, the conversion module includes: a first determination unit, used to determine a target conversion strategy that matches the target type in predefined conversion strategies; and a first generation unit, used to generate a backup request according to the backup parameters included in the backup instruction in accordance with the target conversion strategy.

[0013] Optionally, in the data backup device provided in the embodiment of the present application, the first generation unit includes: a second generation unit, used to fill the backup parameters into the request template included in the target conversion strategy to generate a backup request, wherein the request template includes a code for indicating data backup of the target type of data, and the backup parameters include at least one of the following: backup frequency, retention time of backup data, and the backup component is used to call the target interface according to the backup parameters to back up the target type of data in the cluster in the memory.

[0014] Optionally, the data backup device provided in the embodiment of the present application includes: a detection and backup unit, and the backup component is also used to perform real-time detection of data in the cluster through a target interface, and when a data update in the cluster is detected, the target type data added during the update is backed up in the memory.

[0015] Optionally, the data backup device provided in the embodiment of the present application also includes: a sending unit, used to send a query request for querying the data backup status to the interface server, wherein the query request includes a target type, and the interface server is used to determine the backup status of the target interface according to the target type, and return the backup status to the backup management gateway; a first receiving unit, used to receive and display the backup status returned by the interface server.

[0016] Optionally, the data backup device provided in the embodiment of the present application also includes: a second receiving unit, used to receive recovery instructions for performing data recovery on target type data; a conversion unit, used to convert the recovery instructions into recovery requests recognizable by the backup component according to a conversion strategy; and a forwarding unit, used to forward the recovery request to the backup component, wherein the backup component is used to read the target type data in the memory, and create a recovery interface in the interface server according to the recovery request, and restore the target type data in the memory to the cluster through the recovery interface.

[0017] In an embodiment of the present application, a backup instruction for backing up data of a target type is received; according to a predefined conversion strategy, the backup instruction is converted into a backup request recognizable by a backup component of the cluster; the backup request is forwarded to the backup component, wherein the backup component is used to create a target interface in an interface server according to the backup request, and back up the data of the target type in the cluster in a memory through the target interface, thereby achieving the purpose of backing up data of a specified type in the cluster, solving the technical problem in the related technology that only the cluster data can be backed up as a whole but the data of a specified type in the cluster cannot be backed up, thereby achieving the technical effect of improving the flexibility and accuracy of cluster data backup. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings constituting a part of the present application are used to provide a further understanding of the present application. The illustrative embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0019] Figure 1 is a flow chart of a data backup method provided according to an embodiment of the present application;

[0020] Figure 2 is a schematic diagram of a data backup device provided according to an embodiment of the present application;

[0021] Figure 3 It is a structural block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0022] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0023] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0024] It should be noted that the collected information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in this application are information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of relevant data are in compliance with relevant laws, regulations and standards, necessary confidentiality measures are taken, and public order and good customs are not violated, and corresponding operation entrances are provided for users to choose to authorize or refuse. For example, an interface is set up between this system and relevant users or institutions to provide users with corresponding operation entrances for users to choose to agree or refuse the results of automated decision-making; if the user chooses to refuse, the expert decision-making process will be entered.

[0025] Example 1

[0026] According to an embodiment of the present application, a method embodiment of data backup is also provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0027] The method embodiment provided in the first embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. In the above operating environment, the present application provides the following Figure 1 The data backup method shown. Figure 1 is a flow chart of a data backup method according to Embodiment 1 of the present application, such as Figure 1 As shown, the method comprises the following steps:

[0028] Step S101, receiving a backup instruction for backing up data of a target type;

[0029] The executor of this step is the backup management gateway. Users or system administrators will define backup instructions based on the type of data that needs to be backed up (for example, data under a specific namespace) and enter the backup instructions into the backup management gateway. In the scenario of cluster data backup, the backup management gateway can be regarded as a bridge between users and automated backup tools to control and manage the backup strategies and processes of the entire cluster. Through the backup management gateway, users do not need to understand the command syntax and usage of the backup components in detail. They only need to select or define backup strategies according to their own needs, which reduces the difficulty of user operation and improves user experience.

[0030] Step S102, converting the backup instruction into a backup request recognizable by the backup component of the cluster according to a predefined conversion strategy;

[0031] In this step, after the backup management gateway receives the user's backup instruction, it converts it into a backup request that can be recognized by the backup component server, thereby automating the backup process. This automation can reduce human errors and improve the execution efficiency and consistency of backup tasks. Among them, the backup component is used to implement the backup, recovery and migration functions of cluster data and application resources. The backup operation can be for the entire cluster or selectively for a specific namespace or resource type. Through the backup component, users can also restore previously backed up data and application resources in the cluster. This is very useful in data loss, configuration errors or disaster recovery scenarios. The backup component also supports migrating resources and data in the cluster to different clusters, including cloud migration.

[0032] Optionally, in the data backup method provided in an embodiment of the present application, the backup instruction is converted into a backup request recognizable by the backup component of the cluster according to a predefined conversion strategy, including: determining a target conversion strategy that matches the target type in the predefined conversion strategy; and generating a backup request according to the backup parameters included in the backup instruction in accordance with the target conversion strategy.

[0033] Optionally, the conversion strategy is a set of rules predefined in the backup management gateway, which is used to convert the above-mentioned backup instructions into an instruction format that can be recognized and executed by the cluster backup component. These strategies include corresponding processing methods for different data types and parameters to ensure that the backup instructions can be accurately converted into the request format of the backup component. Once the target conversion strategy is determined, the backup management gateway will fill in the backup parameters into the request template according to the specifications of the backup component, and generate a backup request that the backup component can understand and execute, ensuring that the backup request meets the syntax requirements and functional support of the backup component. This mechanism not only increases the degree of automation of the backup process, but also improves the flexibility and accuracy of backup operations, allowing users to back up specific data resources in the cluster according to actual needs.

[0034] Optionally, in the data backup method provided in the embodiment of the present application, a backup request is generated according to the backup parameters included in the backup instruction in accordance with the target conversion strategy, including: filling the backup parameters into the request template included in the target conversion strategy to generate a backup request, wherein the request template includes a code for instructing to back up data of the target type, and the backup parameters include at least one of the following: backup frequency, retention time of backup data, and the backup component is used to call the target interface to back up the target type data in the cluster in the memory according to the backup parameters.

[0035] Optionally, a request template is preset in the backup management gateway. The request template is a pre-designed formatted structure that contains codes for instructing the backup component of the cluster how to perform a backup operation. These code instructions are usually written in accordance with the custom resource format in the cluster. These templates contain codes for instructing the backup component to perform a specific type of data backup. When the user submits a backup instruction, the backup management gateway identifies the backup parameters contained in the backup instruction, such as the backup frequency, the retention time of the backup data, the namespace to which the backup data belongs, the target data type, etc. The backup frequency refers to the interval at which the user wants the backup operation to be performed, such as once a day, a week, or a month. The retention time of the backup data refers to how long the backup data should be retained in the storage. If this time is exceeded, the data can be deleted to save storage space. The namespace to which the backup data belongs refers to the cluster namespace that needs to be backed up, which allows the user to back up specific parts of the cluster. The target resource type refers to the type of data that needs to be backed up, which makes the backup more accurate and targeted. Then, the gateway fills these parameters into the corresponding request template. This process is similar to filling in specific values ​​in a pre-made instruction framework, so that the generated request can carry the backup policy information specified by the user. After receiving the backup request forwarded by the backup management gateway, the server of the backup component will call the target interface previously created in the interface server according to the backup parameters to back up the data in the cluster in a specific storage. Users can accurately control the frequency of data backup and the life cycle of data through backup parameters, thereby improving the flexibility and accuracy of backup operations. At the same time, by retaining backup data in the storage according to parameters, data management is optimized and unnecessary data redundancy is avoided.

[0036] Step S103: forwarding the backup request to the backup component, wherein the backup component is used to create a target interface in the interface server according to the backup request, and back up the target type of data in the cluster in the storage through the target interface.

[0037] In this step, the backup management gateway sends the processed backup instructions to the server of the backup component. After receiving these instructions, the server will create a target interface in the interface server. The target interface usually refers to a custom resource created by the backup component in the cluster after receiving the backup request. The target interface allows the interface server to manage custom resource types, that is, the backup component can define and control the backup behavior by creating a specific target interface. For example, a target interface may define a set of rules indicating how to back up a specific type of data and the storage location of the backup data. The interface server is the core component of the cluster and the central entrance of the cluster. It provides an application interface to interact with the cluster, so that other backup components can operate and manage cluster resources through standard transmission protocol requests. In the process of data backup and recovery, the backup component needs to monitor and operate these resources through the interface server, such as creating, updating and deleting resources. By creating a target interface in the interface server, the backup component can flexibly expand its functions, such as adding new data type support or optimizing backup strategies. At the same time, this architecture also allows users to customize backup requests to meet backup needs in specific scenarios.

[0038] Optionally, in the data backup method provided in the embodiment of the present application, the backup component is also used to perform real-time detection of data in the cluster through the target interface, and when a data update in the cluster is detected, the target type data added during the update is backed up in the memory.

[0039] Optionally, the backup component performs real-time detection of the data in the cluster through the target interface. This means that the backup component continuously monitors the custom resources associated with data backup. The purpose of real-time detection is to promptly detect any updates or changes to the data so that these changes can be responded to quickly to ensure the timeliness and accuracy of the backup data. When the data in the cluster is updated, such as when new data of a specified type is created or the content of existing data of a specified type is modified or deleted, the backup component receives these update events through interaction with the interface server. This is because one of the design principles of the cluster is that the interface server is the only source of cluster status, and all resource updates are reflected in the interface server. The backup component determines whether the data needs to be backed up again by listening to these updates.

[0040] Once a data update is detected, the backup component does not perform a full backup of the entire cluster or resource type, but instead performs an incremental backup, that is, backing up only the updated or newly added target type data. This approach greatly improves backup efficiency and reduces storage requirements and cluster resource usage, especially in large clusters or environments with frequent data changes. If the user specifies a backup frequency of once a day and a retention period of 30 days in the backup instructions, the backup request generated according to the target conversion policy will configure the backup component to perform these operations. When the backup component finds that the specified type of data has been updated after the backup during real-time detection, it will only back up the updated specified type of data, and will not repeatedly back up other unchanged data in the cluster. The incremental backup policy can be further refined, such as setting a minimum update interval to avoid unnecessary backup operations due to frequent small changes, or defining a specific data change threshold, and only triggering the backup when this threshold is reached to optimize resource usage. Through continuous monitoring and incremental backup, the backup component can ensure the integrity of cluster data, and accurately capture every update even if the data is frequently updated in a short period of time to avoid data loss. Since the updated data is backed up and stored in a timely manner, when data needs to be restored, the nearest update point can be quickly located, reducing data recovery time and improving business continuity.

[0041] Optionally, the data backup method provided in the embodiment of the present application also includes: sending a query request for querying the data backup status to the interface server, wherein the query request includes a target type, and the interface server is used to determine the backup status of the target interface according to the target type, and return the backup status to the backup management gateway to receive and display the backup status returned by the interface server.

[0042] Optionally, the user can issue a request to query the data backup status through the backup management gateway. This request will contain information about the target type, that is, the type of data whose backup status the user wants to query. For example, if the user previously requested to back up data of type A, then when querying, the user will send a query request with type A as the target type through the backup management gateway. The query request is sent to the interface server, and the interface server will determine the status of the corresponding data backup according to the target type in the received query request, such as checking the relevant backup log, the execution history of the backup job, and the storage in a specific storage device to obtain the latest backup status information, including whether it has been backed up, the backup time, the amount of backup data, the backup status (successful, failed, in progress), etc. Once the backup status is determined, the interface server will organize this information into a response format and return it to the backup management gateway. After receiving the backup status response returned by the interface server, the backup management gateway will parse the response data and display the backup status progress bar, backup timestamp, backup data size, whether the backup is successful, etc. through a visual interface, so that the user can understand the current status of his data backup at a glance. For example, if the query is about the backup status of type A data, the interface of the backup management gateway may display the following information: Last backup time: 2023-04-05 10:00:00; Backup size: 50MB; Backup status: Success (or Failure, In Progress); Detailed error information: If the backup fails, the specific error cause and log will be displayed. This query function is very important for monitoring the execution of backup jobs, ensuring the integrity and availability of data, and providing decision support during data recovery, so that users or system administrators can discover and solve problems in a timely manner and ensure the effectiveness of data protection measures.

[0043] Optionally, the data backup method provided in the embodiment of the present application also includes: receiving a recovery instruction for recovering data of a target type; converting the recovery instruction into a recovery request recognizable by a backup component according to a conversion strategy; forwarding the recovery request to the backup component, wherein the backup component is used to read the data of the target type in the memory, and create a recovery interface in the interface server according to the recovery request, and restore the data of the target type in the memory to the cluster through the recovery interface.

[0044] Optionally, the backup management gateway receives an instruction from the user to restore a certain type of data that has been backed up before. After receiving the restore instruction, the backup management gateway converts the instruction into a restore request that the backup component can understand and execute according to a predefined conversion strategy. The generated restore request will contain all necessary information, such as the target type of resource, the namespace to be restored, and the backup version to be restored from. The conversion strategy ensures that the restore instruction can be correctly parsed and formatted so that the backup component can perform the restore operation. This process is similar to the conversion of the backup instruction, except that the restore instruction is converted into a restore request. The converted restore request will be forwarded to the backup component by the backup management gateway. After receiving the request, the backup component creates and calls a restore interface, transfers the data of the target type in the storage to the cluster through the restore interface, and restores the data to the corresponding location of the cluster according to the specific parameters of the restore request. The restore process includes operations such as data decompression, verification, and matching with cluster resources to ensure that the data can be accurately restored to its original state. Through this method, users can accurately specify the target type of data to be restored, avoid unnecessary full recovery, and save time and resources.

[0045] The data backup method provided in the embodiment of the present application receives a backup instruction for backing up data of a target type; according to a predefined conversion strategy, converts the backup instruction into a backup request recognizable by a backup component of the cluster; and forwards the backup request to the backup component, wherein the backup component is used to create a target interface in an interface server according to the backup request, and backs up the data of the target type in the cluster in a memory through the target interface, thereby achieving the purpose of backing up data of a specified type in the cluster, solving the technical problem in the related technology that only the cluster data can be backed up as a whole but the data of a specified type in the cluster cannot be backed up, thereby achieving the technical effect of improving the flexibility and accuracy of cluster data backup.

[0046] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0047] As a specific implementation example, in a cluster, there is an application running a critical business. According to business needs, data of specified types in the business needs to be backed up regularly and be able to be quickly restored when data is lost or configuration is deleted by mistake to ensure business continuity and data security.

[0048] The administrator sends a backup instruction through the backup management gateway (for example, a front-end interface), specifies that the target type to be backed up is type A, sets the backup frequency to once a day, and sets the retention time of the backup data to 30 days. The backup management gateway converts the backup instruction into a backup request that the backup component can recognize based on the predefined conversion strategy. This conversion process includes filling in parameters such as "target type, backup frequency, once a day, and retention time of 30 days" into the request template of the backup component to generate a backup request containing these parameters.

[0049] The backup management gateway forwards the converted backup request to the client of the backup component. After receiving the request, the client of the backup component communicates with the interface server to create a target interface in the cluster. This target interface is used to monitor the update of the target type data in the cluster data. Once the backup component detects that the specified type of data in the cluster data is updated, it will automatically back up the latest state of the specified type of data to the specified storage to ensure the real-time and consistency of the backup data.

[0050] During the continuous backup process, if the administrator wants to know the backup status, the administrator can send a query command through the backup management gateway to request the backup status of the specified data. The backup management gateway forwards the query request to the interface server, which queries the backup status of the corresponding specified type of data and returns the result to the backup management gateway, which displays it to the administrator to show whether the backup is successful, the progress of the backup, and detailed information of the backup data.

[0051] If data of a specified type is accidentally lost in the cluster, the administrator can send a recovery command through the backup management gateway to specify the data to be restored. The backup management gateway converts this command into a recovery request that the backup component can recognize and forwards it to the backup component client. The backup component client reads the backup copy of the specified data from the specified storage, creates a recovery interface, and restores the data to the cluster through the interface, so that the lost configuration information can be quickly restored and business applications can continue to operate normally.

[0052] The embodiment of the present application also provides a data backup device. It should be noted that the data backup device of the embodiment of the present application can be used to execute the data backup method provided by the embodiment of the present application. The data backup device provided by the embodiment of the present application is introduced below.

[0053] According to an embodiment of the present application, a device for implementing the above data backup method is also provided, such as Figure 2As shown, the device includes: a receiving module 21, used to receive a backup instruction for backing up data of a target type; a conversion module 22, connected to the receiving module 21, used to convert the backup instruction into a backup request recognizable by the backup component of the cluster according to a predefined conversion strategy; a forwarding module 23, connected to the conversion module 22, used to forward the backup request to the backup component, wherein the backup component is used to create a target interface in the interface server according to the backup request, and back up the data of the target type in the cluster in the memory through the target interface.

[0054] Optionally, in the data backup device provided in an embodiment of the present application, the conversion module includes: a first determination unit, used to determine a target conversion strategy that matches the target type in predefined conversion strategies; and a first generation unit, used to generate a backup request according to the backup parameters included in the backup instruction in accordance with the target conversion strategy.

[0055] Optionally, in the data backup device provided in the embodiment of the present application, the first generation unit includes: a second generation unit, used to fill the backup parameters into the request template included in the target conversion strategy to generate a backup request, wherein the request template includes a code for indicating data backup of the target type of data, and the backup parameters include at least one of the following: backup frequency, retention time of backup data, and the backup component is used to call the target interface according to the backup parameters to back up the target type of data in the cluster in the memory.

[0056] Optionally, the data backup device provided in the embodiment of the present application includes: a detection and backup unit, and the backup component is also used to perform real-time detection of data in the cluster through a target interface, and when a data update in the cluster is detected, the target type data added during the update is backed up in the memory.

[0057] Optionally, the data backup device provided in the embodiment of the present application also includes: a sending unit, used to send a query request for querying the data backup status to the interface server, wherein the query request includes a target type, and the interface server is used to determine the backup status of the target interface according to the target type, and return the backup status to the backup management gateway; a first receiving unit, used to receive and display the backup status returned by the interface server.

[0058] Optionally, the data backup device provided in the embodiment of the present application also includes: a second receiving unit, used to receive recovery instructions for performing data recovery on target type data; a conversion unit, used to convert the recovery instructions into recovery requests recognizable by the backup component according to a conversion strategy; and a forwarding unit, used to forward the recovery request to the backup component, wherein the backup component is used to read the target type data in the memory, and create a recovery interface in the interface server according to the recovery request, and restore the target type data in the memory to the cluster through the recovery interface.

[0059] The data backup device provided in the embodiment of the present application is configured to receive a backup instruction for backing up data of a target type through a receiving module; a conversion template is configured to convert the backup instruction into a backup request recognizable by the backup component of the cluster according to a predefined conversion strategy; and a forwarding module is configured to forward the backup request to the backup component, wherein the backup component is configured to create a target interface in the interface server according to the backup request, and back up the data of the target type in the cluster in the memory through the target interface, thereby achieving the purpose of backing up data of a specified type in the cluster, solving the technical problem in the related technology that only the cluster data can be backed up as a whole but the data of a specified type in the cluster cannot be backed up, thereby achieving the technical effect of improving the flexibility and accuracy of cluster data backup.

[0060] It should be noted here that the above-mentioned data backup device includes a processor and a memory, and the above-mentioned receiving module 21, conversion module 22, forwarding module 23, etc. are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.

[0061] The processor includes a kernel, which calls the corresponding program unit from the memory. One or more kernels can be set, and data backup can be achieved by adjusting kernel parameters.

[0062] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0063] An embodiment of the present invention provides a computer-readable storage medium on which a program is stored. When the program is executed by a processor, the data backup method is implemented.

[0064] An embodiment of the present invention provides a processor, which is used to run a program, wherein the data backup method is executed when the program is running.

[0065] like Figure 3As shown, an embodiment of the present invention provides an electronic device, the device includes a processor, a memory, and a program stored in the memory and executable on the processor, and the processor implements the following steps when executing the program: receiving a backup instruction for backing up data of a target type; converting the backup instruction into a backup request recognizable by a backup component of a cluster according to a predefined conversion strategy; forwarding the backup request to the backup component, wherein the backup component is used to create a target interface in an interface server according to the backup request, and backing up the data of the target type in the cluster in the memory through the target interface.

[0066] Optionally, according to a predefined conversion strategy, the backup instruction is converted into a backup request recognizable by the backup component of the cluster, including: determining a target conversion strategy that matches the target type in the predefined conversion strategy; generating a backup request according to the backup parameters included in the backup instruction according to the target conversion strategy.

[0067] Optionally, in accordance with the target conversion strategy and according to the backup parameters included in the backup instruction, a backup request is generated, including: filling the backup parameters into the request template included in the target conversion strategy to generate a backup request, wherein the request template includes a code for instructing to perform data backup on the target type of data, and the backup parameters include at least one of the following: backup frequency, retention time of backup data, and the backup component is used to call the target interface to back up the target type of data in the cluster in the memory according to the backup parameters.

[0068] Optionally, the backup component is further used to perform real-time detection of data in the cluster through the target interface, and when it is detected that the data in the cluster is updated, back up the target type data added during the update in the storage.

[0069] Optionally, it also includes: sending a query request for querying data backup status to the interface server, wherein the query request includes a target type, and the interface server is used to determine the backup status of the target interface based on the target type, and return the backup status to the backup management gateway; receiving and displaying the backup status returned by the interface server.

[0070] Optionally, it also includes: receiving a recovery instruction for recovering data of a target type; converting the recovery instruction into a recovery request recognizable by a backup component according to a conversion strategy; forwarding the recovery request to the backup component, wherein the backup component is used to read the data of the target type in the memory, and create a recovery interface in the interface server according to the recovery request, and restore the data of the target type in the memory to the cluster through the recovery interface.

[0071] The devices in this article can be servers, PCs, PADs, mobile phones, etc.

[0072] It can be understood by those skilled in the art that Figure 3 The structure shown is for illustration only, and the electronic device may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (Mobile Internet Devices, MID), a PAD, or other terminal devices. Figure 3 The structure of the electronic device is not limited. Figure 3 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Figure 3 Different configurations are shown.

[0073] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program that initializes the following method steps: receiving a backup instruction for backing up data of a target type; converting the backup instruction into a backup request recognizable by a backup component of the cluster according to a predefined conversion strategy; forwarding the backup request to the backup component, wherein the backup component is used to create a target interface in an interface server according to the backup request, and backing up the data of the target type in the cluster in a memory through the target interface.

[0074] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0075] The embodiment of the present application further provides a storage medium. Optionally, in this embodiment, the storage medium can be used to store the program code executed by the data backup method provided in the first embodiment.

[0076] Optionally, in this embodiment, the above storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group.

[0077] The present application also provides a computer program product, which is suitable for executing the steps of the data backup method when executed on a data processing device.

[0078] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0079] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0080] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic, for example, the division of units is only a logical function division, and there may be other division methods in actual implementation, for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0081] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0082] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0083] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art or all or part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server or network device, etc.) to perform all or part of the steps of each embodiment method of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk, etc. Various media that can store program codes.

[0084] The above are only preferred implementations of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A data backup method, characterized in that: include: receiving a backup instruction for backing up data of a target type; According to a predefined conversion strategy, convert the backup instruction into a backup request recognizable by the backup component of the cluster; The backup request is forwarded to the backup component, wherein the backup component is used to create a target interface in an interface server according to the backup request, and back up the data of the target type in the cluster in a memory through the target interface.

2. The method according to claim 1, characterized in that The step of converting the backup instruction into a backup request recognizable by the backup component of the cluster according to a predefined conversion strategy includes: Determining a target conversion strategy matching the target type among the predefined conversion strategies; The backup request is generated according to the target conversion strategy and the backup parameters included in the backup instruction.

3. The method according to claim 2, characterized in that Generating the backup request according to the target conversion strategy and the backup parameters included in the backup instruction includes: Fill the backup parameters into the request template included in the target conversion strategy to generate the backup request, wherein the request template includes a code for instructing to back up the data of the target type, and the backup parameters include at least one of the following: backup frequency, retention time of backup data, and the backup component is used to call the target interface to back up the data of the target type in the cluster in the storage according to the backup parameters.

4. The method according to claim 1, characterized in that The backup component is also used to perform real-time detection of the data in the cluster through the target interface, and when it is detected that the data in the cluster is updated, back up the data of the target type added during the update in the memory.

5. The method according to claim 1, characterized in that Also includes: Sending a query request for querying the data backup status to the interface server, wherein the query request includes the target type, and the interface server is used to determine the backup status of the target interface according to the target type, and return the backup status to the backup management gateway; Receive and display the backup status returned by the interface server.

6. The method according to any one of claims 1 to 5, characterized in that Also includes: receiving a recovery instruction for recovering the target type of data; According to the conversion strategy, converting the recovery instruction into a recovery request recognizable by the backup component; The recovery request is forwarded to the backup component, wherein the backup component is used to read the data of the target type in the memory, and create a recovery interface in the interface server according to the recovery request, and restore the data of the target type in the memory to the cluster through the recovery interface.

7. A data backup device, characterized in that: include: A receiving module, used for receiving a backup instruction for backing up data of a target type; A conversion template, used to convert the backup instruction into a backup request recognizable by the backup component of the cluster according to a predefined conversion strategy; A forwarding module is used to forward the backup request to the backup component, wherein the backup component is used to create a target interface in the interface server according to the backup request, and to back up the data of the target type in the cluster in the memory through the target interface.

8. A non-volatile storage medium, characterized in that: The non-volatile storage medium includes a stored program, wherein when the program is executed, the device where the non-volatile storage medium is located is controlled to execute the data backup method according to any one of claims 1 to 6.

9. An electronic device, characterized in that: It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the data backup method described in any one of claims 1 to 6.

10. A computer program product comprising computer instructions, characterized in that: The computer instructions are executed by a processor to implement the data backup method according to any one of claims 1 to 6.

Images