Data backup method and device, equipment, storage medium and program product

Abstract

The invention provides a data backup method and device, equipment, a storage medium and a program product, and can be applied to the technical field of computers. The method comprises the following steps: detecting the running state of a target application with a business service function; in response to the detected operation fault alarm information of the target application, performing fault importance detection on the operation fault alarm information based on a preset fault field and a fault mapping relationship to obtain a detection result; in response to the condition that the detection result meets a preset relevance condition, backing up service data in at least one container associated with the target application according to the detection result to obtain backup data; extracting fault information of the target fault to obtain a fault type, a fault occurrence moment, a fault container identifier, a fault level and a backup moment of backup data; and updating the fault backup record according to the fault type, the fault occurrence time, the fault container identifier, the fault level and the backup time of the target fault.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and more specifically, to a data backup method and apparatus, device, storage medium, and program product. Background Art

[0002] Currently, in business scenario operation and maintenance, if an application service or container fails, an operation and maintenance engineer needs to manually determine whether a backup is needed. This requires very high personal qualities and work experience of the operation and maintenance engineer. At the same time, it is difficult to ensure that all failure scenarios that should be backed up are fully covered. When backup is needed, data or failure backup is completed manually.

[0003] In the process of implementing the concept of the present disclosure, the inventors discovered that there are at least the following problems in the related art: the processing efficiency of the fault handling process is low and it is difficult to ensure data integrity. Summary of the invention

[0004] In view of this, the present disclosure provides a data backup method and apparatus, device, storage medium and program product.

[0005] One aspect of the present disclosure provides a data backup method, comprising:

[0006] Performing a running status detection on a target application with a business service function; in response to detecting running fault alarm information of the target application, performing a fault importance detection on the running fault alarm information based on a preset fault field and a fault mapping relationship to obtain a detection result, wherein the preset fault field represents the fault type, the fault mapping relationship represents the fault mapping relationship of the dependency relationship between multiple fault types, and the detection result includes fault information; and in response to the detection result satisfying a preset correlation condition, backing up business data in at least one container associated with the target application according to the detection result to obtain backup data, wherein the preset correlation condition represents that the running fault alarm information matches at least one of the preset fault field and the fault mapping relationship; extracting the fault information of the target fault to obtain the fault type, the time when the fault occurs, the fault container identifier, the fault level and the backup time of the backup data; updating the fault backup record according to the fault type, the time when the fault occurs, the fault container identifier, the fault level and the backup time of the target fault, wherein the target fault represents the fault corresponding to the running fault alarm information of the target application detected.

[0007] According to an embodiment of the present disclosure, the preset fault field includes a first fault field representing a first fault type, and the fault mapping relationship includes a first fault mapping relationship representing a dependency relationship between multiple first fault types; wherein, based on the preset fault field and the fault mapping relationship, the operation fault alarm information is subjected to fault importance detection, and the detection result obtained includes:

[0008] Match multiple operation fault alarm information with the first fault field to obtain multiple first target matching results that represent the match; perform a timing relationship detection based on the alarm moments of the first target alarm information corresponding to each of the multiple first target matching results to obtain a timing relationship detection result, where the operation fault alarm information includes the first target alarm information; and perform an alarm dependency detection on multiple first target alarm information based on the fault mapping relationship and the timing relationship detection result to obtain a first target detection result that represents that a preset correlation condition is met, where the first target detection result represents that the timing relationship between multiple first target alarm information matches the fault mapping relationship.

[0009] According to an embodiment of the present disclosure, the plurality of first target alarm information includes first service state alarm information and first system state alarm information, wherein the first target detection result characterizes that at least one of the following preset correlation conditions is satisfied:

[0010] The first correlation condition indicates that the alarm time of the first business status alarm information and the alarm time of the first system status alarm information are both within the first preset time window; the second correlation condition indicates that in the second preset time window, the timing relationship between the first business status alarm information and the first system status alarm information meets the preset sorting condition.

[0011] According to an embodiment of the present disclosure, the first fault type represents an operating state in which a performance indicator is less than a preset fault indicator threshold, and the performance indicator includes at least one of the following indicators: a transaction response time indicator, a transaction success rate indicator, a transaction change indicator, a thread connection time indicator, and a container response time indicator.

[0012] According to an embodiment of the present disclosure, the preset fault field includes a second fault field representing a second fault type, and the second fault type represents a type of fault whose fault level is greater than or equal to a preset fault level threshold; wherein, based on the preset fault field and the fault mapping relationship, the operation fault alarm information is subjected to fault importance detection, and the detection result obtained further includes:

[0013] Extract the fault information in the operation fault alarm information to obtain the fault type to be matched; perform keyword matching on the fault type to be matched and the second fault field to obtain a second target matching result; obtain a second target detection result based on the second target matching result that matches the representation.

[0014] According to an embodiment of the present disclosure, backing up business data in at least one container associated with a target application according to a detection result, and obtaining the backup data includes:

[0015] According to the detection result, at least one container associated with the target application is determined; according to the container backup component, the container scheduling management component is called; the container scheduling management component backs up the business data in the at least one container to the object storage file to obtain the backup data.

[0016] Another aspect of the present disclosure provides a data backup device, comprising:

[0017] A first detection module is used to detect the running status of a target application having a business service function;

[0018] A second detection module is used for, in response to detecting the operation fault alarm information of the target application, performing fault importance detection on the operation fault alarm information based on a preset fault field and a fault mapping relationship to obtain a detection result, wherein the preset fault field represents the fault type, the fault mapping relationship represents the fault mapping relationship of the dependency relationship between multiple fault types, and the detection result includes the fault information;

[0019] A first backup module, configured to, in response to the detection result satisfying a preset correlation condition, back up business data in at least one container associated with the target application according to the detection result to obtain backup data, wherein the preset correlation condition indicates that the operation fault alarm information matches at least one of a preset fault field and a fault mapping relationship;

[0020] The extraction module is used to extract the fault information of the target fault to obtain the fault type, fault occurrence time, fault container identifier, fault level and backup time of the backup data.

[0021] The second backup module is used to update the fault backup record according to the fault type, fault occurrence time, fault container identifier, fault level and backup time of the target fault, wherein the target fault represents a fault corresponding to the detection of the target application's running fault alarm information.

[0022] Another aspect of the present disclosure provides an electronic device, comprising:

[0023] one or more processors;

[0024] a memory for storing one or more programs,

[0025] When one or more programs are executed by one or more processors, the one or more processors implement the above data backup method.

[0026] Another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the above data backup method when executed.

[0027] Another aspect of the present disclosure provides a computer program product, which includes computer executable instructions, and the instructions are used to implement the above data backup method when executed.

[0028] According to the data backup method and apparatus, device, storage medium and program product provided by the present disclosure, the importance of the fault is detected for the operation fault alarm information based on the preset fault field and the fault mapping relationship, and the detection result is obtained. In the case of successful detection, the backup of the business data and the target fault is automatically triggered. Since the importance of the fault is detected for the operation fault alarm information by using the preset fault fields corresponding to different fault levels and the fault mapping relationship of multiple related faults, the backup of the business data is automatically triggered and completed when the matching detection result is obtained, the target fault is backed up according to the backup result of the business data and the fault information of the target fault, and the fault list is updated in time. The full set of automated backup methods avoids the occurrence of high-importance faults or related faults that are missed, improves the comprehensiveness, timeliness, efficiency and accuracy of fault detection, and reduces the dependence on operation and maintenance personnel. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] The above and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0030] Figure 1 The application scenario of the data backup method according to the embodiment of the present disclosure is schematically shown;

[0031] Figure 2 A flowchart of a data backup method according to an embodiment of the present disclosure is schematically shown;

[0032] Figure 3 An example schematic diagram of a data backup system according to an embodiment of the present disclosure is schematically shown;

[0033] Figure 4 A block diagram schematically shows a data backup device according to an embodiment of the present disclosure; and

[0034] Figure 5 A block diagram of an electronic device suitable for implementing a data backup method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0035] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0036] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0037] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0038] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0039] In the process of implementing the present disclosure, it is found that in the current business scenario operation and maintenance, if an application service or container fails, the operation and maintenance engineer needs to manually determine whether a backup is needed, which requires very high personal quality and work experience of the operation and maintenance engineer. At the same time, it is also difficult to ensure that all the fault scenarios that should be backed up are fully covered. When backup is required, the backup of data or faults is completed manually. The fault handling process is highly dependent on manual labor, and the processing efficiency of the fault handling process is low, making it difficult to ensure data integrity.

[0040] In view of this, the embodiments of the present disclosure provide a data backup method and apparatus, device, storage medium and program product. The method includes: in response to detecting the operation fault alarm information of the target application, based on the preset fault field and the fault mapping relationship, performing fault importance detection on the operation fault alarm information to obtain the detection result, wherein the preset fault field represents the fault type, and the fault mapping relationship represents the fault mapping relationship of the dependency relationship between multiple fault types; and in response to the detection result satisfying the preset correlation condition, backing up the business data in at least one container associated with the target application according to the detection result to obtain the backup data, wherein the preset correlation condition represents that the operation fault alarm information matches at least one of the preset fault field and the fault mapping relationship; extracting the fault information of the target fault to obtain the fault type, the fault occurrence time, the fault container identifier, the fault level and the backup time of the backup data; updating the fault backup record according to the fault type, the fault occurrence time, the fault container identifier, the fault level and the backup time of the target fault.

[0041] It should be noted that the data backup method and data backup device determined in the present disclosure can be used in the financial field, and can also be used in any field other than the financial field. The application field of the data backup method and device determined in the present disclosure is not limited.

[0042] In the technical solution of the present disclosure, the user information (including but not limited to user personal information, user image information, user device information, such as location information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all 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 the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0043] It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, and they should be regarded as exemplary. Their purpose is only to illustrate the feasibility of implementing the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0044] Figure 1 The application scenario of the data backup method according to the embodiment of the present disclosure is schematically illustrated.

[0045] like Figure 1As shown, the system architecture 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104 and a server 105. The network 104 is used to provide a medium for a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0046] The user may use at least one of the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications may be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only for example).

[0047] The first terminal device 101, the second terminal device 102, and the third terminal device 103 may be various electronic devices having display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0048] The server 105 may be a server that provides various services, such as a background management server (only as an example) that provides support for websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

[0049] It should be noted that the data backup method provided in the embodiment of the present disclosure can generally be executed by the server 105. Accordingly, the data backup device provided in the embodiment of the present disclosure can generally be set in the server 105. The data backup method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the server 105. Accordingly, the data backup device provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the server 105.

[0050] Alternatively, the data backup method provided in the embodiment of the present disclosure may also be executed by the first terminal device 101, the second terminal device 102, or the third terminal device 103, or may also be executed by other terminal devices different from the first terminal device 101, the second terminal device 102, or the third terminal device 103. Accordingly, the data backup apparatus provided in the embodiment of the present disclosure may also be provided in the first terminal device 101, the second terminal device 102, or the third terminal device 103, or may be provided in other terminal devices different from the first terminal device 101, the second terminal device 102, or the third terminal device 103.

[0051] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0052] Figure 2 The flowchart of the data backup method according to the embodiment of the present disclosure is schematically shown.

[0053] like Figure 2 As shown, the method 200 includes operations S210 to S250.

[0054] In operation S210, a running state detection is performed on a target application having a business service function.

[0055] According to an embodiment of the present disclosure, the business service function represents the service capabilities provided based on different business transactions. The target application is an application developed based on a running software program on a computer or mobile device. The target application can be a front-end application, a back-end application, an intermediate component, etc.

[0056] According to an embodiment of the present disclosure, the running state of the target application may include the running state of the target application responding to the business transaction and the running state of the target application deployed in the container, central processor, etc. For example, the running state may be the transaction duration state, the connection thread state, the container performance state, etc.

[0057] In operation S220, in response to detecting the operation fault alarm information of the target application, a fault importance detection is performed on the operation fault alarm information based on a preset fault field and a fault mapping relationship to obtain a detection result.

[0058] According to an embodiment of the present disclosure, a microservice application can be developed based on a running software program on a computer or mobile device. The microservice application may include a fault list maintenance application (faultsMtainServiceApp) for maintaining a fault list that needs to be backed up in an interface-based manner, wherein the fault list includes fault fields and fault mapping relationships. The fault list can be adjusted and modified in real time based on the preset fault fields and fault mapping relationships of different levels of fault settings obtained from daily fault backups or maintenance personnel's experience in fault scenarios.

[0059] According to an embodiment of the present disclosure, a preset fault field represents a fault type, and the fault type may be a container performance fault type, a business transaction response performance type, a log exception fault type, an intermediate component exception fault type, and the like.

[0060] According to an embodiment of the present disclosure, the fault mapping relationship represents a fault mapping relationship of dependencies between multiple fault types, and the dependencies may be a time sequence dependency between the fault types. For example, the time sequence dependency between the transaction duration type and the transaction success rate type may be that the interval between the occurrence times of the two is less than a preset interval threshold.

[0061] According to an embodiment of the present disclosure, a fault daemon is built into the fault monitoring tool, and the fault list maintenance application sends the fault fields and fault mapping relationships in the fault list to the fault daemon. In response to detecting the running fault alarm information of the target application, the fault daemon performs fault importance detection on the running fault alarm information according to the preset fault fields and fault mapping relationships to obtain the detection result.

[0062] According to an embodiment of the present disclosure, the fault monitoring tool is a container monitoring component, which is used to monitor the operating status of the container in real time. Once an abnormal alarm is detected, the corresponding operating fault alarm information will be discovered and displayed.

[0063] According to an embodiment of the present disclosure, the detection result may be a result that the running fault alarm information matches at least one of the preset fault fields and fault mapping relationships, or a result that the running fault alarm information does not match either of the preset fault fields and fault mapping relationships.

[0064] In operation S230, in response to the detection result satisfying a preset correlation condition, business data in at least one container associated with the target application is backed up according to the detection result to obtain backup data.

[0065] According to an embodiment of the present disclosure, a fault list maintenance application is used to maintain a fault list that needs to be backed up. When the container is running, the detection result meets the preset correlation condition, indicating that a fault in the fault list has occurred. The fault list maintenance application will send the contents of the fault list to the fault daemon process, and the fault daemon process will update the preset fault fields and fault mapping relationships in the sent fault list in real time.

[0066] According to an embodiment of the present disclosure, the preset correlation condition represents that the operation fault alarm information matches at least one of the preset fault field and the fault mapping relationship.

[0067] According to an embodiment of the present disclosure, the detection result satisfies a preset correlation condition, indicating that the operation fault alarm information is a fault involved in the fault list, and at least one container associated with the target application represents a container serving the target application when processing business transactions.

[0068] According to an embodiment of the present disclosure, in response to the detection result satisfying a preset correlation condition, the fault daemon backs up the business data in at least one container associated with the target application to obtain backup data. The business data represents the storage data related to the business in the container.

[0069] In operation S240, the fault information of the target fault is extracted to obtain the fault type, the time when the fault occurs, the fault container identifier, the fault level, and the backup time of the backup data.

[0070] According to an embodiment of the present disclosure, the target fault characterization is in response to detecting a fault corresponding to the operation fault alarm information of the target application.

[0071] According to an embodiment of the present disclosure, the microservice application may further include a container backup component. After the container backup component completes the backup of the business data, a backup result indicating successful backup is obtained, and the backup result is returned to the fault daemon.

[0072] According to the embodiment of the present disclosure, the detection result includes fault information, and the fault daemon extracts the fault information of the target fault according to the fault list and the detection result to obtain the fault type, fault occurrence time, fault container identifier, fault level and backup time of the backup data. The fault occurrence time is the alarm time.

[0073] In operation S250, the fault backup record is updated according to the fault type, fault occurrence time, fault container identifier, fault level, and backup time of the target fault.

[0074] According to an embodiment of the present disclosure, the fault daemon sends the backup result and information such as the fault type, fault occurrence time, fault container identifier, fault level and backup time of the target fault to the fault list maintenance application, thereby updating the fault backup record in the fault list maintenance application.

[0075] According to an embodiment of the present disclosure, the fault list maintenance application can also update the fault list, for example, add the fault type, fault occurrence time, and fault container identifier of the target fault to the sub-entry of the preset fault field corresponding to the target fault in the fault list.

[0076] According to the embodiments of the present disclosure, fault importance detection is performed on the operation fault alarm information through preset fault fields corresponding to different fault levels and fault mapping relationships of multiple related faults, and the backup of business data is automatically triggered and completed when a matching detection result is obtained. The target fault is backed up according to the backup result of the business data and the fault information of the target fault, and the fault list is updated in time. The full set of automated backup methods avoids the occurrence of omissions of faults with high importance levels or related faults, improves the comprehensiveness, timeliness, efficiency and accuracy of fault detection, and reduces dependence on operation and maintenance personnel.

[0077] According to an embodiment of the present disclosure, the preset fault field includes a first fault field representing a first fault type, and the fault mapping relationship includes a first fault mapping relationship representing a dependency relationship between multiple first fault types; based on the preset fault field and the fault mapping relationship, the operation fault alarm information is subjected to fault importance detection, and the detection result obtained includes:

[0078] Match multiple operation fault alarm information with the first fault field to obtain multiple first target matching results that represent the match; perform a timing relationship detection based on the alarm moments of the first target alarm information corresponding to each of the multiple first target matching results to obtain a timing relationship detection result, where the operation fault alarm information includes the first target alarm information; and perform an alarm dependency detection on multiple first target alarm information based on the fault mapping relationship and the timing relationship detection result to obtain a first target detection result that represents that a preset correlation condition is met, where the first target detection result represents that the timing relationship between multiple first target alarm information matches the fault mapping relationship.

[0079] According to an embodiment of the present disclosure, the first fault type represents a type of medium fault level, and therefore, it is necessary to determine whether backup is required in combination with a fault mapping relationship between multiple first fault types.

[0080] According to an embodiment of the present disclosure, keywords are extracted from multiple operation fault alarm information, and the keywords are matched with the first fault field to obtain multiple first target matching results with matching characteristics. For example, the keywords may be transaction duration and transaction success rate. When the first fault field includes transaction duration and transaction success rate, two first target matching results with matching characteristics are obtained.

[0081] According to an embodiment of the present disclosure, a time sequence relationship detection is performed on the alarm moments of the first target alarm information corresponding to the two first target matching results to obtain a time sequence relationship detection result. The time sequence relationship detection may include a sequence detection of the occurrence of the moments.

[0082] According to an embodiment of the present disclosure, based on the fault mapping relationship and timing relationship detection results, multiple first target alarm information is subjected to alarm dependency detection to obtain a first target detection result characterizing that the timing relationship between the multiple first target alarm information matches the fault mapping relationship.

[0083] For example, the fault mapping relationship between the transaction duration type and the transaction success rate type may be that the alarm time of the transaction duration type is later than the alarm time of the transaction success rate type, and the interval between the alarm times of the two is less than 0.01 ms.

[0084] According to an embodiment of the present disclosure, the plurality of first target alarm information includes first service state alarm information and first system state alarm information, and the first target detection result characterizes that at least one of the following preset correlation conditions is satisfied:

[0085] The first correlation condition indicates that the alarm time of the first business status alarm information and the alarm time of the first system status alarm information are both within the first preset time window; the second correlation condition indicates that in the second preset time window, the timing relationship between the first business status alarm information and the first system status alarm information meets the preset sorting condition.

[0086] According to an embodiment of the present disclosure, the first business status alarm information represents information about the business transaction status, such as transaction response time, transaction success rate, etc. The first system status alarm information represents information about the running status of each container, component, etc. in the system, such as thread connection time, container response time, etc.

[0087] For example, the first preset time window is from 4:00 to 4:05. The first correlation condition is that the alarm time of the first service state alarm information and the alarm time of the first system state alarm information are both between 4:00 and 4:05.

[0088] According to an embodiment of the present disclosure, the preset sorting condition may be that the alarm time of the first service status alarm information is smaller than the alarm time of the first system status alarm information.

[0089] According to an embodiment of the present disclosure, the first fault type represents an operating state in which a performance indicator is less than a preset fault indicator threshold, and the performance indicator includes at least one of the following indicators: a transaction response time indicator, a transaction success rate indicator, a transaction change indicator, a thread connection time indicator, and a container response time indicator.

[0090] According to an embodiment of the present disclosure, for faults with a medium fault importance level, the performance index is further considered, and the fault type with a performance index less than a preset fault index threshold is the first fault type, and the preset fault index threshold can be set according to the importance of the performance index. For example, the preset fault index threshold corresponding to the transaction response time index can be 0.001ms.

[0091] According to the embodiments of the present disclosure, faults with medium or low importance levels do not need to be backed up, but related faults with medium importance levels often have a greater impact and require timely attention and backup. Therefore, the fault importance detection is performed on the operation fault alarm information of the related faults with medium importance levels using preset correlation conditions, preset sorting conditions, preset fault fields, and fault mapping relationships, and the detection results are obtained and then backed up in time, avoiding the omission of related faults and improving the comprehensiveness and timeliness of fault detection.

[0092] According to an embodiment of the present disclosure, the preset fault field includes a second fault field representing a second fault type, and the second fault type represents a type of fault whose fault level is greater than or equal to a preset fault level threshold.

[0093] According to an embodiment of the present disclosure, the preset fault level threshold can be obtained according to the fault importance. For example, if the level of the middleware abnormal fault is 0.8 and the preset fault level threshold is 0.6, the middleware abnormal fault is identified as the second fault type.

[0094] According to an embodiment of the present disclosure, the second fault type may be a memory leak fault type, a central processing unit abnormal fault type, a database abnormal fault type, a container abnormal fault type, etc.

[0095] According to an embodiment of the present disclosure, based on a preset fault field and a fault mapping relationship, the operation fault alarm information is subjected to a fault importance detection, and the detection result obtained further includes:

[0096] Extract the fault information in the operation fault alarm information to obtain the fault type to be matched; perform keyword matching on the fault type to be matched and the second fault field to obtain a second target matching result; obtain a second target detection result based on the second target matching result that matches the representation.

[0097] According to an embodiment of the present disclosure, information of the error keyword error in the fault information in the operation fault alarm information is extracted to obtain the fault type to be matched. For example, the fault type to be matched may be an abnormal fault type of an intermediate component.

[0098] According to an embodiment of the present disclosure, keyword matching is performed on the fault type to be matched and the second fault field to obtain a second target matching result. The second target matching result may be a matching result or a non-matching result.

[0099] According to an embodiment of the present disclosure, after obtaining a second target matching result that matches the characterization, a second target detection result is obtained. The second target detection result includes relevant information of the fault.

[0100] According to an embodiment of the present disclosure, for a fault with a high importance level, a match is directly performed with the second fault field, and after obtaining a second target matching result with a matching characterization, a backup operation can be automatically and quickly triggered according to the second target detection result.

[0101] According to an embodiment of the present disclosure, backing up business data in at least one container associated with a target application according to a detection result, and obtaining the backup data includes:

[0102] According to the detection result, at least one container associated with the target application is determined; according to the container backup component, the container scheduling management component is called; the container scheduling management component backs up the business data in the at least one container to the object storage file to obtain the backup data.

[0103] According to an embodiment of the present disclosure, the detection result includes information such as a matching result of the fault, a target application where the fault occurs, and a container associated with the target application.

[0104] According to an embodiment of the present disclosure, the microservice application may further include a container backup component, a container scheduling management component, and a container storage management component. In response to the detection result satisfying a preset correlation condition, the container backup component is automatically triggered, and the container backup component calls the interface of the container scheduling management component.

[0105] According to an embodiment of the present disclosure, the container scheduling management component is used for management services and scheduling services of a container cluster, and the container storage management component is used to manage storage services for containers, and is generally used in conjunction with the container scheduling management component.

[0106] According to an embodiment of the present disclosure, business data in a container is stored in a container storage management component, and a container scheduling management component backs up business data in at least one container in the container storage management component to an object storage file through an interface to obtain backup data.

[0107] According to an embodiment of the present disclosure, the object storage file is applicable to a distributed storage service on the cloud, is used to back up business data, and can store business data of a container.

[0108] Figure 3 An example schematic diagram of a data backup system according to an embodiment of the present disclosure is schematically shown.

[0109] like Figure 3 As shown, the microservice application may include a fault list maintenance application 301, a container backup component 302, a container scheduling management component 303, and a container storage management component 304. A fault daemon 306 is built into the fault monitoring tool 305. The fault list maintenance application 301 sends the fault fields and fault mapping relationships in the fault list to the fault daemon 306. In response to detecting the operation fault alarm information of the target application, the fault daemon performs fault importance detection on the operation fault alarm information according to the preset fault fields and fault mapping relationships to obtain the detection result. In response to the detection result meeting the preset correlation condition, the container backup component 302 is automatically triggered. The container backup component 302 calls the container scheduling management component 303 to back up the business data in at least one container in the container storage management component 304 to the object storage file 307. After the container backup component 302 completes the backup of the business data, the backup result is returned to the fault daemon 306. The fault daemon 306 sends the fault type, fault occurrence time, fault container identifier, fault level and backup time of the backup data to the fault list maintenance application 301 , and then updates the fault backup record in the fault list maintenance application 301 .

[0110] According to the embodiments of the present disclosure, timely backup of business data and faults is automatically triggered and completed according to the fault list, and a full set of automated backup methods can ensure the integrity, timeliness and efficiency of fault backup coverage.

[0111] Based on the above data backup method, the present disclosure also provides a data backup device. Figure 4 The device is described in detail.

[0112] Figure 4 A structural block diagram of a data backup device according to an embodiment of the present disclosure is shown.

[0113] like Figure 4 As shown, the data backup device 400 of this embodiment includes a first detection module 410 , a second detection module 420 , a first backup module 430 , an extraction module 440 and a second backup module 450 .

[0114] The first detection module 410 is used to detect the running status of the target application with the business service function. In one embodiment, the first detection module 410 can be used to perform the operation S210 described above, which will not be described in detail here.

[0115] The second detection module 420 is used for the processing module, and is used to detect the operation fault alarm information of the target application in response to the operation fault alarm information being detected, based on the preset fault field and the fault mapping relationship, to perform fault importance detection on the operation fault alarm information, and obtain a detection result, wherein the preset fault field represents the fault type, the fault mapping relationship represents the fault mapping relationship of the dependency relationship between multiple fault types, and the detection result includes the fault information. In one embodiment, the second detection module 420 can be used to perform the operation S220 described above, which will not be repeated here.

[0116] The first backup module 430 is used to input the key features into the risk prediction model and output the risk prediction result. In one embodiment, the first backup module 430 can be used to perform the operation S230 described above, which will not be described in detail here.

[0117] The extraction module 440 is used to extract the fault information of the target fault to obtain the fault type, fault occurrence time, fault container identifier, fault level and backup time of the backup data. In one embodiment, the extraction module 440 can be used to perform the operation S240 described above, which will not be repeated here.

[0118] The second backup module 450 is used to update the fault backup record according to the fault type, fault occurrence time, fault container identifier, fault level and backup time of the target fault, wherein the target fault represents a fault corresponding to the detection of the running fault alarm information of the target application. In one embodiment, the second backup module 450 can be used to perform the operation S250 described above, which will not be repeated here.

[0119] According to an embodiment of the present disclosure, the second detection module 420 includes a first detection submodule, a second detection submodule and a third detection submodule.

[0120] The first detection submodule is used to match the multiple operation fault alarm information with the first fault field to obtain multiple first target matching results representing matching.

[0121] The second detection submodule is used to perform a timing relationship detection based on the alarm time of the first target alarm information corresponding to each of the multiple first target matching results to obtain the timing relationship detection result, and the operating fault alarm information includes the first target alarm information.

[0122] The third detection submodule is used to perform alarm dependency detection on multiple first target alarm information based on the fault mapping relationship and timing relationship detection results, and obtain the first target detection result that represents the satisfaction of the preset correlation condition. The first target detection result represents that the timing relationship between the multiple first target alarm information matches the fault mapping relationship.

[0123] According to an embodiment of the present disclosure, the second detection module 420 further includes a fourth detection submodule, a fifth detection submodule and a sixth detection submodule.

[0124] The fourth detection submodule is used to extract the fault information in the operation fault alarm information to obtain the fault type to be matched.

[0125] The fifth detection submodule is used to perform keyword matching on the fault type to be matched and the second fault field to obtain a second target matching result.

[0126] The sixth detection submodule is used to obtain a second target detection result according to the second target matching result that matches the representation.

[0127] According to an embodiment of the present disclosure, the first backup module 430 includes a first backup submodule, a second backup submodule, and a third backup submodule.

[0128] The first backup submodule is used to determine at least one container associated with the target application according to the detection result.

[0129] The second backup submodule is used to call the container scheduling management component according to the container backup component.

[0130] The third backup submodule is used for the container scheduling management component to back up the business data in at least one container to the object storage file to obtain backup data.

[0131] According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits, or at least part of the functions of any one of them can be implemented in one module. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be split into multiple modules for implementation. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be at least partially implemented as hardware circuits, such as field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), systems on chips, systems on substrates, systems on packages, application specific integrated circuits (ASICs), or can be implemented by hardware or firmware in any other reasonable way of integrating or packaging circuits, or can be implemented in any one of the three implementation methods of software, hardware, and firmware, or in any appropriate combination of any of them. Alternatively, according to the embodiments of the present invention, one or more of the modules, submodules, units, and subunits can be at least partially implemented as computer program modules, and when the computer program modules are run, the corresponding functions can be performed.

[0132] For example, any of the first detection module 410, the second detection module 420, the first backup module 430, the extraction module 440 and the second backup module 450 can be combined in one module / unit / sub-unit for implementation, or any of the modules / units / sub-units can be split into multiple modules / units / sub-units. Alternatively, at least part of the functions of one or more of these modules / units / sub-units can be combined with at least part of the functions of other modules / units / sub-units and implemented in one module / unit / sub-unit. According to an embodiment of the present disclosure, at least one of the first detection module 410, the second detection module 420, the first backup module 430, the extraction module 440 and the second backup module 450 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or by any one of the three implementation methods of software, hardware and firmware or by a suitable combination of any of them. Alternatively, at least one of the first detection module 410, the second detection module 420, the first backup module 430, the extraction module 440 and the second backup module 450 may be at least partially implemented as a computer program module, which may perform a corresponding function when executed.

[0133] Figure 5 A block diagram of an electronic device suitable for implementing a data backup method according to an embodiment of the present invention is shown.

[0134] Figure 5 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0135] like Figure 5 As shown, the computer electronic device 500 according to an embodiment of the present invention includes a processor 501, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 502 or the program loaded from the storage part 508 to the random access memory (RAM) 503. The processor 501 may include, for example, a general-purpose microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (for example, an application-specific integrated circuit (ASIC)), etc. The processor 501 may also include an on-board memory for caching purposes. The processor 501 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present invention.

[0136] In RAM 503, various programs and data required for the operation of electronic device 500 are stored. Processor 501, ROM 502 and RAM 503 are connected to each other via bus 504. Processor 501 performs various operations of the method flow according to the embodiment of the present invention by executing the program in ROM 502 and / or RAM 503. It should be noted that the program can also be stored in one or more memories other than ROM 502 and RAM 503. Processor 501 can also perform various operations of the method flow according to the embodiment of the present invention by executing the program stored in one or more memories.

[0137] Optionally, the electronic device 500 may further include an input / output (I / O) interface 505, which is also connected to the bus 504. The electronic device 500 may further include one or more of the following components connected to the input / output (I / O) interface 505: an input portion 506 including a keyboard, a mouse, etc.; an output portion 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 508 including a hard disk, etc.; and a communication portion 509 including a network interface card such as a LAN card, a modem, etc. The communication portion 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the input / output (I / O) interface 505 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 510 as needed, so that a computer program read therefrom is installed into the storage portion 508 as needed.

[0138] Optionally, the method flow according to the embodiment of the present invention can be implemented as a computer software program. For example, an embodiment of the present invention includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program contains a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 509, and / or installed from the removable medium 511. When the computer program is executed by the processor 501, the above-mentioned functions defined in the system of the embodiment of the present invention are executed. Optionally, the system, equipment, device, module, unit, etc. described above can be implemented by a computer program module.

[0139] The present invention also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiment; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the data backup method according to the embodiment of the present invention is implemented.

[0140] Optionally, the computer-readable storage medium may be a non-volatile computer-readable storage medium. For example, it may include, but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, apparatus, or device.

[0141] For example, optionally, the computer-readable storage medium may include the ROM 502 and / or the RAM 503 described above and / or one or more memories other than the ROM 502 and the RAM 503 .

[0142] An embodiment of the present invention also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method provided by the embodiment of the present invention. When the computer program product runs on an electronic device, the program code is used to enable the electronic device to implement the data backup method provided by the embodiment of the present invention.

[0143] When the computer program is executed by the processor 501, the above functions defined in the system / device of the embodiment of the present invention are performed. Optionally, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0144] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 509, and / or installed from the removable medium 511. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0145] Optionally, the program code for executing the computer program provided by the embodiment of the present invention can be written in any combination of one or more programming languages, specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, such as Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0146] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram may represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box may also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions. It can be understood by those skilled in the art that the features recorded in the various embodiments of the present disclosure can be combined and / or combined in a variety of ways, even if such a combination or combination is not explicitly recorded in the present disclosure. In particular, without departing from the spirit and teaching of the present disclosure, the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0147] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A data backup method, characterized in that: The method comprises: Perform running status detection on target applications with business service functions; In response to detecting the operation fault alarm information of the target application, based on a preset fault field and a fault mapping relationship, performing a fault importance detection on the operation fault alarm information to obtain a detection result, wherein the preset fault field represents a fault type, the fault mapping relationship represents a fault mapping relationship of a dependency relationship between multiple fault types, and the detection result includes fault information; and In response to the detection result satisfying a preset correlation condition, backing up business data in at least one container associated with the target application according to the detection result to obtain backup data, wherein the preset correlation condition indicates that the operation fault alarm information matches at least one of the preset fault field and the fault mapping relationship; Extracting the fault information of the target fault to obtain the fault type, fault occurrence time, fault container identifier, fault level and backup time of the backup data; The fault backup record is updated according to the fault type, the fault occurrence time, the fault container identifier, the fault level and the backup time of the target fault, wherein the target fault representation is in response to detecting a fault corresponding to the operation fault alarm information of the target application.

2. The method according to claim 1, characterized in that The preset fault field includes a first fault field representing a first fault type, and the fault mapping relationship includes a first fault mapping relationship representing a dependency relationship between a plurality of the first fault types; Wherein, based on the preset fault field and the fault mapping relationship, the operation fault alarm information is subjected to fault importance detection, and the detection result obtained includes: Matching the plurality of operation fault alarm information with the first fault field to obtain a plurality of first target matching results representing matching; Performing a timing relationship detection based on the alarm time of the first target alarm information corresponding to each of the plurality of first target matching results to obtain a timing relationship detection result, wherein the operation fault alarm information includes the first target alarm information; and Based on the fault mapping relationship and the timing relationship detection results, an alarm dependency detection is performed on multiple first target alarm information to obtain a first target detection result that represents that the preset correlation condition is met. The first target detection result represents that the timing relationship between multiple first target alarm information matches the fault mapping relationship.

3. The method according to claim 2, characterized in that The plurality of first target alarm information includes first service status alarm information and first system status alarm information, The first target detection result representation satisfies at least one of the following preset correlation conditions: A first correlation condition, indicating that the alarm time of the first service status alarm information and the alarm time of the first system status alarm information are both within a first preset time window; The second correlation condition indicates that in the second preset time window, the timing relationship between the first service status alarm information and the first system status alarm information satisfies a preset sorting condition.

4. The method according to claim 2, characterized in that: The first fault type represents an operating state in which a performance indicator is less than a preset fault indicator threshold, and the performance indicator includes at least one of the following indicators: a transaction response time indicator, a transaction success rate indicator, a transaction change indicator, a thread connection time indicator, and a container response time indicator.

5. The method according to claim 1, characterized in that The preset fault field includes a second fault field representing a second fault type, wherein the second fault type represents a type of fault having a fault level greater than or equal to a preset fault level threshold; Wherein, based on the preset fault field and the fault mapping relationship, the operation fault alarm information is subjected to fault importance detection, and the detection result obtained further includes: Extracting fault information from the operation fault alarm information to obtain a fault type to be matched; Perform keyword matching on the to-be-matched fault type and the second fault field to obtain a second target matching result; A second target detection result is obtained based on the second target matching result that matches the representation.

6. The method according to claim 1, characterized in that Backing up the business data in at least one container associated with the target application according to the detection result, and obtaining the backup data includes: Determine, according to the detection result, at least one container associated with the target application; Calling a container scheduling management component according to the container backup component; The container scheduling management component backs up the business data in the at least one container to an object storage file to obtain backup data.

7. A data backup device, comprising: A first detection module is used to detect the running status of a target application having a business service function; a second detection module, configured to, in response to detecting the operation fault alarm information of the target application, perform fault importance detection on the operation fault alarm information based on a preset fault field and a fault mapping relationship to obtain a detection result, wherein the preset fault field represents a fault type, the fault mapping relationship represents a fault mapping relationship of a dependency relationship between multiple fault types, and the detection result includes fault information; A first backup module, configured to, in response to the detection result satisfying a preset correlation condition, back up business data in at least one container associated with the target application according to the detection result to obtain backup data, wherein the preset correlation condition indicates that the operation fault alarm information matches at least one of the preset fault field and the fault mapping relationship; The extraction module is used to extract the fault information of the target fault to obtain the fault type, fault occurrence time, fault container identifier, fault level and backup time of the backup data. The second backup module is used to update the fault backup record according to the fault type, fault occurrence time, fault container identifier, fault level and backup time of the target fault, wherein the target fault represents a fault corresponding to the detection of the target application's running fault alarm information.

8. An electronic device comprising: one or more processors; a memory for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, enables the processor to implement the method according to any one of claims 1 to 6.

10. A computer program product comprising a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 6.

Images