Executable data backup system, method, medium, program product and node device suitable for mimicking environment

Abstract

The present application provides an executable data backup system, method, medium, program product and node device suitable for a mimic environment. The present invention provides an automated solution specifically for the backup and restoration of executable data in a mimic application system. With this invention, users can implement a strategic backup of executable data in a mimic application system, and quickly restore it to all or specific executables when necessary. The backup and restore mechanism of the present invention is seamlessly connected to the mimic call interface of the mimic application system, so that the executable scheduling logic in the backup and restore process can be handled more elegantly and perfectly. Compared with traditional backup and restore software, the present invention greatly reduces the operational complexity of executable backup and restoration in a mimic environment, and significantly reduces the risk of environmental failure or data loss due to misoperation.

Description

Technical Field

[0001] The present application relates to the field of mimicry defense technology, and in particular to an executable data backup system, method, medium, program product and node device suitable for a mimicry environment. Background Art

[0002] In the field of mimicry defense, mimicry application systems often face the challenge of hidden attacks. After such attacks occur, the information returned by the attacker is no different from normal operations, causing the adjudication system to fail to trigger abnormal alarms. Hidden attacks may cause errors in the data on the executive body, and due to the insensitivity of the adjudication system, these errors may be propagated to other executive bodies, eventually causing the failure of the entire mimicry application system. Therefore, it is very important to regularly back up the executive body data of the mimicry application system.

[0003] Unlike conventional information systems, traditional data backup and recovery usually only requires a single data set or a single application. However, in a mimic environment, the same data needs to be restored to multiple executors at the same time, and during the data recovery process, the availability of the entire mimic system must also be taken into account. At the same time, due to the strong isolation requirements of the executor network in the mimic environment, in manual mode, data backup and restoration of the mimic application system are relatively cumbersome. Summary of the invention

[0004] In view of the shortcomings of the prior art described above, the purpose of the present application is to provide a technical problem for solving how to achieve efficient recovery of data to multiple execution bodies in a mimicking environment and maintain high availability of the system, as well as to simplify the manual data backup and restore process under strong isolation requirements.

[0005] To achieve the above-mentioned purpose and other related purposes, the first aspect of the present application provides an executable data backup system suitable for a mimic environment, comprising: a backup and restore management module, which is deployed on a negative feedback scheduling node; a data export module, which is deployed on an executable; a data import module, which is deployed on the executable; the backup and restore management module establishes a communication connection with the data export module and the data import module; the executable is configured with an executable application that can be called through an API interface;

[0006] During the data backup process, the backup and restore management module is used to respond to the received backup request and obtain the current state of the target execution body through the negative feedback scheduling node; if the current state is running, a data export instruction is issued to the data export module on the target execution body; the data export module responds to the data export instruction and exports the corresponding data and sends it to the backup and restore management module for storage and management;

[0007] During the data restoration process, the backup and restoration management module is used to respond to the restoration instruction and obtain the current state of the target execution body through the negative feedback scheduling node; if the current state is an idle state, the backup and restoration management module queries the corresponding backup data and sends it to the data import module on the target execution body; after the import is completed, the data import module notifies the execution body application to perform data restoration.

[0008] In some embodiments of the first aspect of the present application, the negative feedback scheduling node obtains the current state of the target executor in the following manner: the negative feedback scheduling node obtains the executor state by reading the distribution executor list and the voting executor list. The executor is in the running state if it belongs to both lists and is in the idle state if it does not belong to both lists. The executor is in the data synchronization state if it only belongs to the distribution list.

[0009] In some embodiments of the first aspect of the present application, the generation method of the backup request sent to the backup and restore management module includes any one or more of the following combinations: timer-triggered generation, generation triggered in response to administrator user operations, and generation triggered in response to a cleaning execution body instruction sent by a negative feedback scheduling node.

[0010] In some embodiments of the first aspect of the present application, the restore instruction is generated in response to a restore operation in the interactive interface.

[0011] In some embodiments of the first aspect of the present application, after the data import module receives the backup data to be restored, it stores it to the agreed location and notifies the executable application to perform data restoration; the predetermined location includes memory, a temporary folder, a preset storage area or a preset isolation environment.

[0012] In some embodiments of the first aspect of the present application, the communication protocol used between the backup and restore management module and the data export module and the data import module includes HTTP / HTTPS protocol, TCP / IP protocol, UDP protocol or WebSocket protocol.

[0013] To achieve the above-mentioned purpose and other related purposes, the second aspect of the present application provides an executable data backup method suitable for a simulated environment, which is applied to the executable data backup system suitable for the simulated environment; the backup method includes: during the data backup process, the backup and restore management module deployed on the negative feedback scheduling node responds to the received backup request and obtains the current state of the target executable through the negative feedback scheduling node; if the current state is running, a data export instruction is issued to the data export module on the target executable; the data export module responds to the data export instruction, exports the corresponding data and sends it to the backup and restore management module for storage and management; during the data restoration process, the backup and restore management module responds to the restore instruction and obtains the current state of the target executable through the negative feedback scheduling node; if the current state is an idle state, the backup and restore management module queries the corresponding backup data and sends it to the data import module on the target executable; after the import is completed, the data import module notifies the executable application to restore the data.

[0014] To achieve the above-mentioned purpose and other related purposes, the third aspect of the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the executable data backup method suitable for a simulated environment is implemented.

[0015] To achieve the above-mentioned purpose and other related purposes, the fourth aspect of the present application provides a computer program product, which includes a computer program code. When the computer program code runs on a computer, the computer implements the executable data backup method suitable for a simulated environment.

[0016] To achieve the above-mentioned purpose and other related purposes, the fifth aspect of the present application provides a node device, including a memory, a processor and a computer program stored in the memory; the processor executes the computer program to implement the executable data backup method suitable for the simulated environment.

[0017] As described above, the executable data backup system, method, medium, program product and node device of the present application suitable for a mimic environment have the following beneficial effects: The present invention provides an automated solution specifically for the backup and restoration of executable data in a mimic application system. With the help of this invention, users can implement strategic backup of executable data in a mimic application system, and quickly restore it to all or specific executables when necessary. The backup and restore mechanism of the present invention is seamlessly connected to the mimic call interface of the mimic application system, so that the executable scheduling logic in the backup and restore process can be handled more elegantly and perfectly. Compared with traditional backup and restore software, the present invention greatly reduces the operational complexity of executable backup and restoration in a mimic environment, and significantly reduces the risk of environmental failure or data loss due to misoperation. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 Shown is a structural schematic diagram of an executable data backup system suitable for a mimicking environment in one embodiment of the present application.

[0019] Figure 2 Shown is a schematic diagram of the backup process of the execution volume data backup system in one embodiment of the present application.

[0020] Figure 3 Shown is a schematic diagram of the restoration process of a single executable body in one embodiment of the present application.

[0021] Figure 4 Shown is a flowchart of an executable data backup method suitable for a mimic environment in one embodiment of the present application.

[0022] Figure 5 Shown is a schematic diagram of the structure of a node device in an embodiment of the present application. DETAILED DESCRIPTION

[0023] The following describes the embodiments of the present application through specific examples, and those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0024] Before further describing the present invention in detail, the nouns and terms involved in the embodiments of the present invention are explained. The nouns and terms involved in the embodiments of the present invention are applicable to the following interpretations:

[0025] <1> Mimic Defense (MD) is a network security technology inspired by the mimicry phenomenon in nature. It is based on the principle of biological mimicry and uses dynamic heterogeneous redundant construction, mimicry camouflage mechanism, uncertainty effect and other means to achieve active defense and intrinsic security in cyberspace. This technology aims to deal with various unknown threats in cyberspace and improve the efficiency and effectiveness of network security defense. The basic idea of ​​mimicry defense is to root the security gene into the network information system from the source by constructing a dynamically changing multiple parallel collaborative architecture, establish an immune system with endogenous effects, and effectively solve the problem of defense difficulties against unknown attacks that exploit unknown vulnerabilities and unknown backdoors.

[0026] <2> Mimic environment: The environment in which an information system that uses mimic defense technology operates.

[0027] Figure 1 A schematic diagram of the structure of an executable data backup system applicable to a mimic environment provided in an embodiment of the present application is shown, wherein the backup system comprises:

[0028] The backup and restore management module 101 is deployed on the negative feedback scheduling node.

[0029] The data export module 102 is deployed to the executable body.

[0030] The data import module 103 is deployed to the executable body.

[0031] The backup and restore management module 101 establishes a communication connection with the data export module 102 and the data import module 103. The communication protocols used between the backup and restore management module 101 and other modules include but are not limited to: HTTP / HTTPS, TCP / IP, UDP, WebSocket and other protocols. The backup and restore management module can actively initiate a connection request, or wait for a connection request from the data export module and the data import module.

[0032] The executable body is configured with an executable body application 104 that can be called through an API interface. It should be understood that the executable body is the entity that actually executes the task or operation, which can be a physical device, a virtual machine instance or a container instance. For example, in a network service system, the executable body can be a Web service container responsible for processing user requests and providing services. The executable body application refers to the specific application program or software run by the executable body, which is the specific implementation of the executable body function. For example, if the executable body is a Web server, the executable body application can be an e-commerce website running on the Web server.

[0033] Negative feedback scheduling node refers to a scheduling node that uses negative feedback mechanism to dynamically adjust the behavior and performance of the system. Negative feedback is a control system design principle that adjusts the behavior and performance of the system by feeding back part of the system output signal to the input end. This mechanism can make the system more stable, accurate and reliable, and has the advantages of suppressing system fluctuations, reducing errors and improving response speed. In the mimic environment, the negative feedback scheduling node dynamically adjusts the scheduling strategy of the executor by monitoring the status and output of the executor, distributor, and arbiter in the mimic system to increase the dynamics and uncertainty of the system, reduce the probability of continuous occurrence of the same attack, and increase the difficulty of exploiting vulnerabilities and backdoors.

[0034] During the data backup process, the backup and restore management module 101 is used to respond to the received backup request and obtain the current state of the target execution body through the negative feedback scheduling node; if the current state is running, a data export instruction is issued to the data export module 102 on the target execution body; the data export module 102 responds to the data export instruction, exports the corresponding data and sends it to the backup and restore management module 101 for storage and management.

[0035] In some examples, the negative feedback scheduling node obtains the current state of the target executor in the following manner: the negative feedback scheduling node obtains the executor state by reading the distribution executor list and the voting executor list; an executor that belongs to both lists is in the running state, and that does not belong to both lists is in the idle state; and an executor that only belongs to the distribution list is in the data synchronization state. Among them, the distribution executor list is a list of executors managed by the distributor, which usually includes executors that can currently receive requests and process them. The voting executor list is a list of executors managed by the arbitrator, which usually includes executors that participate in the vote.

[0036] In an embodiment of the present application, the backup request sent to the backup and restore management module 101 is generated in any of the following ways: timer-triggered generation, generation triggered in response to administrator user operations, and generation triggered in response to a cleaning execution body instruction sent by a negative feedback scheduling node.

[0037] Timer-triggered backup request generation refers to triggering the backup operation based on the timer in the scheduled backup strategy, and then generating a backup request sent to the backup and restore management module. This is an automated backup mechanism, usually used to automatically perform backup tasks regularly (such as daily, weekly or monthly) without manual intervention, which can ensure the regularity and consistency of backup operations.

[0038] The backup request is triggered in response to the administrator user's operation, which means that the administrator user clicks the backup button of the backup and restore management module to trigger the backup operation. This is a manually triggered backup method, usually operated by the system administrator as needed, and the backup time can be flexibly selected according to the actual situation, for example, the backup can be performed before the system changes or important operations.

[0039] The generation of a backup request is triggered in response to a cleaning executive body instruction issued by a negative feedback scheduling node, which means that the executive body data backup system receives a cleaning executive body instruction issued by a negative feedback scheduling node and triggers a backup operation, thereby generating a backup request sent to the backup and restore management module. This method can automatically trigger a backup when certain anomalies or errors are detected. As an emergency measure, it can quickly respond to system anomalies and protect data from further damage.

[0040] Preferably, in order to ensure the reliability of the system and the security of the data, the above three methods are usually used in combination to cover different backup needs and scenarios. For example, scheduled backup can be set as a basic guarantee, while allowing administrators to manually trigger backups at critical moments, and automatically trigger backups when the system detects serious problems. Such a combination can minimize the risk of data loss.

[0041] It should be noted here that before executing the backup, the current state of the target executable is queried through the negative feedback scheduling node. If the state of the target executable is "running", this means that the executable is in normal working condition and data backup can be performed safely. If the state of the target executable is in other states, such as "stopped", "abnormal", "maintenance", etc., backup is not allowed to avoid data corruption or system instability. Once the backup operation is completed, the system will record the backup log, including information such as the backup time, the amount of data backed up, and the storage location of the backup for future reference. If the backup request is rejected, the system should provide a corresponding error message or warning to inform the requester why the backup failed to execute, and may suggest to try the backup again after the state of the executable changes. This design ensures the security and reliability of the backup operation, while also improving the stability of the system.

[0042] For ease of understanding, combined Figure 2 The backup process diagram of the executive body data backup system in is further explained.

[0043] Step S21: the backup and restore management module 101 receives a backup request from a timer, an administrator user, or a negative feedback schedule.

[0044] Step S22: After receiving the backup request, the backup and restore management module 101 first determines the current state of the target executable body through the negative feedback scheduling node; if the current state of the target executable body is running, data backup is allowed; otherwise, data backup is not allowed.

[0045] Step S23: When the target executable body is in the running state, the backup and restore management module sends a data export instruction to the data export module on the target executable body. That is, once it is confirmed that the target executable body is in the running state, the backup and restore management module sends a data export instruction to the data export module on the target executable body.

[0046] Step S24: After receiving the data export instruction, the data export module calls the API interface of the execution body application to notify the execution body application to perform data preparation operations. That is, after receiving the instruction, the data export module will communicate with the execution body application through the API interface to notify it to prepare the data to be backed up. The preparation work includes locking the data to prevent changes during the backup process, or organizing the data into a format suitable for backup.

[0047] Step S25: After the execution body application prepares the data, it notifies the data export module; the data export module sends the prepared data to the backup and restore management module.

[0048] Step S26: The backup and restore management module stores the received backup data and records the backup element information, including the backup reason, backup time, target executable name, backup file size, backup file name, etc. That is, after receiving the data, the backup and restore management module will store it in the backup medium for summary and record the backup element information, which is crucial for backup management and recovery. At this point, the data backup operation on an executable is completed.

[0049] During the data restoration process, the backup and restoration management module 101 is used to respond to the restoration instruction and obtain the current state of the target execution body through the negative feedback scheduling node; if the current state is an idle state, the backup and restoration management module queries the corresponding backup data and sends it to the data import module on the target execution body; after the import is completed, the data import module notifies the execution body application to perform data restoration.

[0050] Furthermore, after the execution body application has completed restoring all data, the data import module 103 notifies the backup and restore management module 101 to perform subsequent operations, including but not limited to notifying the negative feedback scheduling node to force the current execution body to go online, which means that after the data restoration operation is completed, the system needs to ensure that all key components and services are started and running. This operation is some additional steps that the backup and restore management module needs to perform after the data restoration operation is completed to ensure the integrity of the system and the consistency of the data.

[0051] like Figure 3 As shown, a schematic diagram of the restoration process of a single executable body in an embodiment of the present invention is shown.

[0052] Step S31: generating a restore instruction in response to a restore operation in the interactive interface.

[0053] Step S32: After receiving the restore instruction, the backup and restore management module queries the state of the target execution body through the negative feedback scheduling node.

[0054] Step S33: If the target executable body is in an idle state, the backup and restore management module queries the corresponding backup data and sends it to the data import module on the target executable body.

[0055] Step S34: After receiving the backup data to be restored, the data import module stores it in a predetermined location and notifies the execution application to restore the data; the predetermined location includes a temporary folder, a preset storage area or a preset isolation environment. In this way, the security and consistency of the data can be ensured.

[0056] Step S35: After receiving the restore instruction, the execution application automatically loads the data to be restored from the agreed location and notifies the data import module after the restoration is completed.

[0057] For example, when restoring data, the execution body application generally follows the following steps:

[0058] (1) Based on the parameters or configuration in the restore instruction, the executor application determines the agreed location of the data to be restored.

[0059] (2) Before starting the restore, the executive application checks the integrity of the data to ensure that the data has not been damaged or tampered with.

[0060] (3) The executor application loads the data to be restored from the agreed location (such as the backup server, local disk, etc.). These operations include file system read operations, database queries, etc.

[0061] (4) The executive application performs corresponding restore operations according to the type and format of the data, such as copying files, inserting database records, restoring system configurations, etc.

[0062] (5) After the restore operation is completed, the executor application performs verification to ensure that the data has been correctly restored to the expected state.

[0063] The entire restore process is logged, including success or failure information, to facilitate problem tracking.

[0064] Step S36: After receiving the notification of restoration completion, the data import module reports the restoration result information to the backup and restoration management module.

[0065] Step S37: The backup and restore management module displays the restore result information and records the corresponding operation log.

[0066] It is worth noting that although the process of batch restore of multiple executables is essentially similar to the restore process of a single executable, in order to make the description more concise and clear, this document does not discuss in depth various potential errors and failures. It should be pointed out that failure and error handling are standard technical measures in the field of information systems, and they do not affect the scope of protection covered by this patent.

[0067] It should be understood that the division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present application may be integrated into a processor, or may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules.

[0068] Figure 4 The flowchart of the method for backing up executable data in a simulated environment according to an embodiment of the present invention is shown. The method for backing up executable data in a simulated environment includes the following steps:

[0069] Step S41: During the data backup process, the backup and restore management module deployed on the negative feedback scheduling node responds to the received backup request and obtains the current state of the target execution body through the negative feedback scheduling node; if the current state is running, a data export instruction is issued to the data export module on the target execution body; the data export module responds to the data export instruction, exports the corresponding data and sends it to the backup and restore management module for storage and management.

[0070] Step S42: During the data restoration process, the backup and restore management module responds to the restore instruction and obtains the current state of the target execution body through the negative feedback scheduling node; if the current state is an idle state, the backup and restore management module queries the corresponding backup data and sends it to the data import module on the target execution body; after the import is completed, the data import module notifies the execution body application to perform data restoration.

[0071] It should be noted that the implementation process and principle of the executable data backup method applicable to the mimic environment in the embodiment of the present application are similar to those of the executable data backup system applicable to the mimic environment mentioned above, and will not be repeated here.

[0072] It should also be noted that in the embodiments of the present application, words such as "exemplary" or "for example" represent examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0073] In the embodiments of the present application, "at least one" refers to one or more, and "plurality" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can represent: a, b, c, ab, ac, bc or abc, where a, b, c can be single or multiple.

[0074] Figure 5 is a schematic block diagram of a node device provided in an embodiment of the present application. Figure 5 As shown in FIG. 1 , the node device includes: at least one processor 501, a memory 502, and at least one network interface 503. The various components in the device are coupled together through a bus system 504. It can be understood that the bus system 504 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 504 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 5 In the specification, various buses are labeled as bus systems.

[0075] It is understood that the memory 502 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM). The memory described in the embodiments of the present invention is intended to include but is not limited to these and any other suitable categories of memory.

[0076] The memory 502 in the embodiment of the present invention is used to store various types of data to support the operation of the electronic terminal 500. Examples of these data include: any executable program used to operate on the electronic terminal 500, such as an operating system 5021 and an application 5022; the operating system 5021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks. The application 5022 can include various applications, such as a media player (Media Player), a browser (Browser), etc., for implementing various application services. The XX method provided by the embodiment of the present invention can be included in the application 5022.

[0077] The method disclosed in the above embodiment of the present invention can be applied to the processor 501, or implemented by the processor 501. The processor 501 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit in the processor 501 or the instruction in the form of software. The above processor 501 may be a general processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 501 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiment of the present invention. The general processor 501 may be a microprocessor or any conventional processor, etc. In combination with the steps of the accessory optimization method provided in the embodiment of the present invention, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0078] In an exemplary embodiment, the electronic terminal 500 may be implemented by one or more application specific integrated circuits (ASIC), DSP, programmable logic device (PLD), complex programmable logic device (CPLD) to execute the aforementioned method.

[0079] According to the method provided in the embodiment of the present application, the present application also provides a computer program product, which includes: a computer program code, when the computer program code is run on a computer, the computer executes Figures 1 to 4Any of the embodiments shown in the drawings is an executable data backup method applicable to a mimic environment.

[0080] According to the method provided in the embodiment of the present application, the present application also provides a computer-readable storage medium, which stores a program code. When the program code runs on a computer, the computer executes the above method.

[0081] The terms "component", "module", "system", etc. used in this specification are used to represent computer-related entities, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to, a process running on a processor, a processor, an object, an executable file, an execution thread, a program and / or a computer. By way of illustration, both applications running on a computing device and a computing device can be components. One or more components may reside in a process and / or an execution thread, and a component may be located on a computer and / or distributed between two or more computers. In addition, these components may be executed from various computer-readable media having various data structures stored thereon. Components may, for example, communicate through local and / or remote processes according to signals having one or more data packets (e.g., data from two components interacting with another component between a local system, a distributed system and / or a network, such as the Internet interacting with other systems through signals).

[0082] Those of ordinary skill in the art will appreciate that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0083] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0084] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. 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 devices or units, which can be electrical, mechanical or other forms.

[0085] 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.

[0086] 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.

[0087] In the above embodiments, the functions of each functional unit can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When loading and executing computer program instructions (programs) on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. Computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that contains one or more available media integrations. Available media may be magnetic media (e.g., floppy disks, hard disks, tapes), optical media (e.g., high-density digital video discs (DVDs), or semiconductor media (e.g., solid state disks (SSDs), etc.).

[0088] If the function 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 the 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 the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

[0089] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0090] In summary, the present application provides an executable data backup system, method, medium, program product and node device suitable for a mimic environment. The present invention provides an automated solution specifically for the backup and restoration of executable data in a mimic application system. With this invention, users can implement a strategic backup of executable data in a mimic application system, and quickly restore it to all or specific executables when necessary. The backup and restore mechanism of the present invention is seamlessly connected to the mimic call interface of the mimic application system, so that the executable scheduling logic in the backup and restore process can be handled more elegantly and perfectly. Compared with traditional backup and restore software, the present invention greatly reduces the operational complexity of executable backup and restoration in a mimic environment, and significantly reduces the risk of environmental failure or data loss due to misoperation. Therefore, the present application effectively overcomes the various shortcomings of the prior art and has a high industrial utilization value.

[0091] The above embodiments are merely illustrative of the principles and effects of the present application and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.

Claims

1. An executable data backup system suitable for a simulated environment, characterized in that: include: The backup and restore management module is deployed on the negative feedback scheduling node; The data export module is deployed to the executable body; A data import module is deployed to the execution body; The backup and restore management module establishes a communication connection with the data export module and the data import module; the execution body is configured with an execution body application that can be called through an API interface; During the data backup process, the backup and restore management module is used to obtain the current state of the target executable body through the negative feedback scheduling node in response to the received backup request; If the current state is running, a data export instruction is issued to a data export module on the target execution body; The data export module exports the corresponding data in response to the data export instruction and sends it to the backup and restore management module for storage and management; During data restoration, the backup and restoration management module is used to obtain the current state of the target executable body through the negative feedback scheduling node in response to the restoration instruction; If the current state is idle, the backup and restore management module queries the corresponding backup data and sends it to the data import module on the target execution body; After the import is completed, the data import module notifies the executor application to restore the data.

2. The executable data backup system applicable to a simulated environment according to claim 1, characterized in that: The negative feedback scheduling node obtains the current state of the target executable body in the following manner: The negative feedback scheduling node obtains the state of the executor by reading the distribution executor list and the voting executor list; if the executor belongs to both lists at the same time, it is in the running state, and if it does not belong to both lists at the same time, it is in the idle state; Only the distribution list is in the data synchronization state.

3. The executable data backup system applicable to a simulated environment according to claim 1, characterized in that: The generation method of the backup request sent to the backup and restore management module includes any one or more combinations of the following: generation triggered by a timer, generation triggered in response to an administrator user operation, and generation triggered in response to a cleaning execution body instruction sent by a negative feedback scheduling node.

4. The executable data backup system applicable to a simulated environment according to claim 1, characterized in that: The restore instruction is generated in response to a restore operation in the interactive interface.

5. The executable data backup system applicable to a simulated environment according to claim 1, characterized in that: After receiving the backup data to be restored, the data import module stores it in a predetermined location and notifies the execution application to restore the data; the predetermined location includes a memory, a temporary folder, a preset storage area or a preset isolation environment.

6. The executable data backup system applicable to a simulated environment according to claim 1, characterized in that: The communication protocols used between the backup and restore management module and the data export module and the data import module include HTTP / HTTPS protocol, TCP / IP protocol, UDP protocol or WebSocket protocol.

7. A method for backing up executable data in a simulated environment, characterized in that: The executable data backup system applicable to the mimic environment as claimed in any one of claims 1 to 6; the backup method comprises: During the data backup process, the backup and restore management module deployed on the negative feedback scheduling node responds to the received backup request and obtains the current state of the target execution body through the negative feedback scheduling node; if the current state is running, a data export instruction is issued to the data export module on the target execution body; the data export module responds to the data export instruction and exports the corresponding data and sends it to the backup and restore management module for storage and management; During the data restoration process, the backup and restoration management module responds to the restoration instruction and obtains the current state of the target execution body through the negative feedback scheduling node; if the current state is idle, the backup and restoration management module queries the corresponding backup data and sends it to the data import module on the target execution body; after the import is completed, the data import module notifies the execution body application to perform data restoration.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the executable data backup method applicable to a simulated environment as claimed in claim 7 is implemented.

9. A computer program product, characterized in that The computer program product includes computer program codes, and when the computer program codes are executed on a computer, the computer implements the executable data backup method applicable to a simulated environment as claimed in claim 7.

10. A node device, characterized in that: A backup and restore management module is deployed thereon, and the backup and restore management module is configured to execute the executable data backup method applicable to the mimic environment as claimed in claim 7.

Images