A backup system error reporting self-healing method, device, equipment and storage medium

Abstract

This article belongs to the field of automation design and is applied to the financial field. It specifically provides a backup system error self-healing method, device, equipment and storage medium. The method includes: receiving backup job error information; determining the error type and backup job information according to the backup job error information; determining the backup strategy corresponding to the backup job according to the backup job information; determining the repair script corresponding to the error type from a pre-set repair script set, and the repair script set is a set of repair scripts for backup jobs with different error types; loading the repair script into the backup system to adjust the backup strategy, so that the backup system re-backs up the backup job according to the adjusted backup strategy. This article can automatically determine the cause of the error, implement the corresponding solution and perform automatic backup, which improves the efficiency of backup error recovery and thus improves the efficiency of backup.

Description

Technical Field

[0001] This article belongs to the field of automation design, and specifically relates to a backup system error self-healing method, device, equipment and storage medium. Background Art

[0002] With the development of internet technology, all aspects of production, office work, and daily life are increasingly dependent on IT application systems. Application systems and data have become the core assets of system operation. To cope with the challenge of data loss caused by host failures, system errors, virus attacks, and other reasons, it is necessary to implement backup protection with different backup frequency strategies for all IT application systems to ensure that data is not lost and can be rolled back to the previous backup time point.

[0003] Data backup is an offline data protection method. It refers to backing up data to inexpensive media for data recovery when online system media crashes, and for archiving and protecting large amounts of historical data.

[0004] During the backup process, errors can occur, disrupting the backup operation. Currently, backup error handling, from analysis to problem resolution and re-provisioning, requires manual effort. This has several drawbacks: it consumes significant manpower; it relies on manual intervention, which is time-consuming; and it relies on the experience of the operator. With the current acceleration of host application migration and platform architecture transformation, the daily backup data volume and number of backup jobs are increasing dramatically, and the average daily backup error rate is also rising. This requires a significant investment of manpower in backup professionals to ensure backup operations, hindering subsequent development and work. Automated self-healing processes are urgently needed to reduce human intervention. Summary of the Invention

[0005] In view of the above problems in the prior art, the purpose of this article is to provide a backup system error self-recovery method, device, equipment and storage medium, which can improve the efficiency of backup system error recovery.

[0006] In order to solve the above technical problems, the specific technical solutions of this article are as follows:

[0007] In one aspect, this document provides a backup system error self-healing method, the method comprising:

[0008] Receive backup job error information;

[0009] Determining the error type and backup job information according to the backup job error information;

[0010] Determining a backup strategy corresponding to the backup job according to the backup job information;

[0011] Determining a repair script corresponding to the error type from a preset repair script set, wherein the repair script set is a set of repair scripts for backup jobs of different error types;

[0012] The repair script is loaded into the backup system to adjust the backup policy, so that the backup system re-backs up the backup job according to the adjusted backup policy.

[0013] Furthermore, before receiving the backup job error information, the method further includes:

[0014] Collect backup policy parameters from the backup system according to a specified period, wherein the backup policy parameters include at least a policy name, a storage location, a retention period, and a schedule;

[0015] The backup policy parameters are formatted according to a preset storage format and stored in a designated database.

[0016] Furthermore, before receiving the backup job error information, the method further includes:

[0017] Acquire a first parameter of a backup job in the backup system, the first parameter including at least a job ID, a job type, a job status, and a policy name;

[0018] The first parameter of the backup job is stored in a designated database, and the first parameter of the backup job is updated according to a designated period.

[0019] Furthermore, after receiving the backup job error information, the method further includes:

[0020] Determining the job ID of the backup job according to the backup job error information;

[0021] According to the job ID of the backup job, obtaining second parameters of the backup job, the second parameters at least including a tape library, a tape drive, a tape, a backup path, and a media server;

[0022] The second parameter of the backup job is stored in a designated database.

[0023] Furthermore, determining the error type and backup job information according to the backup job error information includes:

[0024] Determining an error code and a job ID of the backup job according to the backup job error information;

[0025] Determining the error type of the error information according to the error code of the backup job;

[0026] The backup job information is extracted according to the job ID of the backup job, where the backup job information is the first parameter.

[0027] Furthermore, determining a backup strategy corresponding to the backup job according to the backup job information includes:

[0028] Determining a policy name adopted by the backup job according to the backup job information;

[0029] A backup policy corresponding to the backup job is determined from a designated database according to the policy name.

[0030] Furthermore, determining the repair script corresponding to the error type from a preset repair script set includes:

[0031] Determining a pre-stored set of repairable error types, wherein the set of error types corresponds to the set of repair scripts;

[0032] Determine whether the error type is in the error type set;

[0033] If yes, extract the repair script corresponding to the error type from the repair script set;

[0034] If it is not there, an alarm will be issued so that the operation and maintenance personnel can repair it manually.

[0035] Furthermore, the step of determining the repair script set includes:

[0036] Obtaining historical error information of the backup system and a repair plan corresponding to the historical error information, wherein the repair plan includes operation steps and operation instructions for operation and maintenance personnel;

[0037] Encapsulate the operation steps and operation instructions of the operation and maintenance personnel to obtain a repair script for the historical error information;

[0038] Establishing a mapping relationship between the error type of the historical error information and the repair script;

[0039] The repair script set is formed according to the mapping relationship and the repair script.

[0040] Furthermore, after determining the error type and the backup job information according to the backup job error information, the following steps are further included:

[0041] Determining the running status of the backup job in the backup job information;

[0042] Determine whether the running state is ended with an error;

[0043] If yes, then executing the step of repairing the error information;

[0044] If not, cancel the error message and continue to perform the backup of the backup job.

[0045] Furthermore, the step of loading the repair script into the backup system to adjust the backup policy so that the backup system re-backs up the backup job according to the adjusted backup policy includes:

[0046] Obtain the adjusted backup strategy;

[0047] Generate a re-backup instruction according to the adjusted backup strategy;

[0048] According to the re-backup instruction, the backup job that has error information is re-backed up.

[0049] Furthermore, after re-backing up the backup job that has error information according to the re-backup instruction, the method further includes:

[0050] Acquire adjustment information of the backup strategy, the adjustment information including adjustment time;

[0051] Acquire the backup job information of the backup job in real time, wherein the backup job information includes the backup time;

[0052] The adjustment information and the operation information are placed in a designated monitoring platform to monitor the self-healing status of the error information.

[0053] On the other hand, this article also provides a backup system error reporting self-healing device, the device comprising:

[0054] An error information acquisition module is used to receive backup job error information;

[0055] An error information processing module, configured to determine an error type and backup job information based on the backup job error information;

[0056] A backup strategy determination module, configured to determine a backup strategy corresponding to the backup job based on the backup job information;

[0057] A repair script determining module, configured to determine a repair script corresponding to the error type from a preset repair script set, wherein the repair script set is a set of repair scripts for backup jobs of different error types;

[0058] The re-backup module is used to load the repair script into the backup system to adjust the backup strategy, so that the backup system re-backs up the backup job according to the adjusted backup strategy.

[0059] On the other hand, this document also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method described above when executing the computer program.

[0060] Finally, this document also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the method described above.

[0061] By adopting the above-mentioned technical solution, a backup system error self-healing method, device, equipment and storage medium described in this article determines the error type and backup job information based on the received backup job error information, and then determines the backup strategy based on the backup job information, and determines the repair script corresponding to the error type from a pre-set repair script set, and then loads the repair script into the backup system to adjust the backup strategy, thereby realizing the re-backup of the backup job. This article can automatically determine the cause of the error, implement the corresponding solution and perform automatic backup, thereby improving the efficiency of backup error recovery, and thus improving the efficiency of backup.

[0062] In order to make the above and other purposes, features and advantages of this article more obvious and easy to understand, the following specifically cites preferred embodiments and provides detailed descriptions in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] In order to more clearly illustrate the technical solutions in the embodiments of this article or the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of this article. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0064] Figure 1 A schematic diagram of an implementation environment of a backup system error self-healing method provided in an embodiment of this document is shown;

[0065] Figure 2 A schematic diagram of the communication process between the self-healing device and the backup system in the embodiment of this document is shown;

[0066] Figure 3 A schematic diagram showing the steps of a backup system error self-healing method provided in an embodiment of this document is shown;

[0067] Figure 4 A schematic diagram of error information processing steps in the embodiment of this article is shown;

[0068] Figure 5 A schematic diagram of the steps for repairing error information in the embodiment of this article is shown;

[0069] Figure 6 A schematic diagram of the steps for determining a repair script set in an embodiment of this invention is shown;

[0070] Figure 7A schematic structural diagram of a backup system error reporting and self-healing device provided in an embodiment of this invention is shown;

[0071] Figure 8 A schematic diagram of the structure of a computer device provided in an embodiment of this invention is shown.

[0072] Description of the accompanying symbols:

[0073] 10. Backup system;

[0074] 20. Database;

[0075] 30. Self-healing device;

[0076] 100. Error information acquisition module;

[0077] 200. Error information processing module;

[0078] 300. Backup strategy determination module;

[0079] 400. Repair script determination module;

[0080] 500. Re-backup module;

[0081] 802. Computer equipment;

[0082] 804, processor;

[0083] 806, memory;

[0084] 808, driving mechanism;

[0085] 810, input / output module;

[0086] 812. Input devices;

[0087] 814. Output device;

[0088] 816. Presentation equipment;

[0089] 818. Graphical User Interface;

[0090] 820, network interface;

[0091] 822, communication link;

[0092] 824. Communication bus. DETAILED DESCRIPTION

[0093] The following will be combined with the accompanying drawings to clearly and completely describe the technical solutions in the embodiments of this document. Obviously, the embodiments described are only part of the embodiments of this document, not all of the embodiments. Based on the embodiments of this document, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this document.

[0094] It should be noted that the terms "first," "second," and the like in the specification and claims herein and in the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, apparatus, product, or device comprising a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to these processes, methods, products, or devices.

[0095] In the existing technology, when an error occurs in a backup job, the backup job will be temporarily suspended. The general processing method is to complete it manually, such as analyzing and solving the backup error, and finally completing the backup. This backup error processing method requires a lot of manpower and relies on human operations, which is time-consuming. Under the current situation of accelerated downward migration of host applications and accelerated transformation of platform architecture, the daily backup data volume and the number of backup jobs have increased sharply, and the average daily backup error volume has also increased. As a result, the backup profession needs to invest a lot of manpower to ensure the backup operation, which has a lagging effect on subsequent development and work.

[0096] In order to solve the above problems, the embodiment of this specification provides a backup system error self-healing method, such as Figure 1 As shown, it is a schematic diagram of the implementation environment framework of the method, and the framework includes a backup system 10, a database 20 and a self-healing device 30; the backup system 10 is used to receive host backup tasks for backup, and the database 20 can receive the backup information of the backup system 10, such as backup strategy information and backup job information, and store it; the self-healing device 30 is used to receive the backup job error information of the backup system 10, analyze the error information to determine the cause of the error, and send the pre-stored solution to the backup system 10 so that the backup system 10 can adjust the backup strategy of the error backup job, thereby realizing re-backup.

[0097] The backup system 10 , the database 20 , and the self-healing device 30 are communicatively connected to each other, for example, by wired communication or wireless communication.

[0098] The backup system 10 may be a network backup system (NetBackUp, NBU) of Veritas, and may include at least one backup server for receiving and implementing the backup tasks of the host.

[0099] Taking NBU as an example, each backup system is equipped with a backup management (NBU Master) server to complete the backup task, and the self-healing device is equipped with a backup self-healing management server (Handler) for self-healing management. Based on Socket communication development, a listener (Listener) is deployed in each NBU Master server to listen to the request sent by the backup self-healing management server (the Sender in the Handler sends the request), and sends the response result to the Handler service. The receiver (Receiver) in the Handler receives the response result, and then the Handler is used to realize the automatic self-healing processing of the error job. Figure 2 As shown in the figure, the communication process between the NBU Master and Handler is as follows:

[0100] Step 1.1: The task dispatching device (Sender) sends the command to be issued and generates a unique command identifier. Through Socket communication, it sends the command identifier and command text to the designated port of each NBU Master. The listener (Listener) deployed on the designated port of each NBU Master receives the command information and command identifier after passing the server authentication.

[0101] Step 1.2: After the Listener receives the command, the NBU Master executes the corresponding command or deployed script and returns the execution result to the result receiver of the centralized Handler. The Handler pairs the returned result with the unique command identifier to obtain the final command result.

[0102] Specifically, the embodiments of this document provide a backup system error reporting and self-healing method, which can improve the efficiency of the backup system error reporting and self-healing. Figure 3 This is a schematic diagram of the steps of a backup system error self-healing method provided in the embodiment of this article. This specification provides the method operation steps as described in the embodiment or flowchart, but based on conventional or non-creative labor, more or fewer operation steps may be included. The order of steps listed in the embodiment is only one way of executing the steps among many steps, and does not represent the only execution order. When the actual system or device product is executed, it can be executed in the order or in parallel according to the method shown in the embodiment or the accompanying drawings. Specifically, Figure 3 As shown, the method may include:

[0103] S101: receiving backup job error information;

[0104] S102: Determine the error type and backup job information according to the backup job error information;

[0105] S103: Determine a backup policy corresponding to the backup job according to the backup job information;

[0106] S104: Determine a repair script corresponding to the error type from a preset repair script set, where the repair script set is a set of repair scripts for backup jobs of different error types;

[0107] S105: Load the repair script into the backup system to adjust the backup policy, so that the backup system re-backs up the backup job according to the adjusted backup policy.

[0108] It can be understood that this article pre-generates solutions (i.e., repair scripts) for different error types. When an error message appears, the error type and corresponding backup job information are obtained by analyzing the error message. The backup strategy corresponding to the backup job can be determined through the backup job information, and the repair script corresponding to the error type can be determined at the same time. The repair script is then loaded into the backup system to adjust the backup strategy, thereby realizing the re-backup of the backup job. This article can automatically repair the error backup job and realize automatic backup, thereby improving the backup repair efficiency and saving labor costs.

[0109] During the actual backup process, different faults may generate different error messages. For example, backup timeouts due to interface failures, communication failures, or tape drive failures, or tapes that have run out and not been replaced, may all cause errors. An error generation script may be set in advance. Different error generation scripts may generate different error files for different faults, which may include error status, error reasons, etc.

[0110] The backup strategy can be the data backup retention period and media usage in the backup job. In actual work, each backup domain (or backup system) can set multiple backup strategies, and different backup jobs can use different backup strategies for backup. Therefore, the backup strategy can be configured in advance. When backup is needed, just select the corresponding backup strategy, which can improve the efficiency of backup.

[0111] Therefore, before receiving the backup job error information, the following steps are also included:

[0112] Collect backup policy parameters from the backup system according to a specified period, wherein the backup policy parameters include at least a policy name, a storage location, a retention period, and a schedule;

[0113] The backup policy parameters are formatted according to a preset storage format and stored in a designated database.

[0114] It can be understood that a corresponding backup policy information collector can be set up to collect the backup policy configuration information in each backup domain according to a specified period. The specified period can be set according to actual conditions and is not limited in the embodiments of this specification. Since the backup policy configuration information is relatively complex, with a large number of parameter types and quantities, and different backup policy parameters may be shared, common data structures cannot associate various aspects of the backup policy information. Therefore, the backup policy can be parsed by establishing a tree model. For example, a policy tree model can be generated for each backup policy. The root node of the policy tree model is the policy unique identifier (such as the policy name), and is divided into multiple levels of sub-nodes, such as storage unit, retention period, scheduling, etc., and each node corresponds to corresponding data information, which facilitates the search for detailed backup configuration information for each backup policy.

[0115] Furthermore, due to the complexity of the backup strategy parameters, according to the node path and node data information of the strategy tree model, such as strategy name: attribute: schedule: schedule one: schedule name, in order to facilitate the storage of the backup strategy parameters, the strategy tree model can also be parsed to create multiple Redis configuration information key-value pairs. For example, corresponding key-value pairs can be created based on the path of each node of the strategy tree model (the path from the root node to the child node) and the node data; the configuration information key-value pairs are used to cache the backup configuration and other information of each backup strategy, and are updated regularly; at the same time, the backup strategy information that is different from the previous period is persistently stored in the MYSQL database to form a historical information table for each backup strategy for comparative analysis of subsequent error reports.

[0116] For example, taking NBU as an example, the NBU backup policy information collection process is as follows:

[0117] Step 2.1: The Handler periodically sends NBU backup policy configuration storage commands to each NBU Master;

[0118] Step 2.2: Each NBU Master executes the policy configuration generation command and imports the policy configuration file;

[0119] Step 2.3: Each NBU Master transfers the generated policy configuration file to the Handler;

[0120] Step 2.4: The Handler parses the backup policy configuration files collected from each NBU Master into a policy tree model. The policy name is the root node of the policy tree, and other configuration information of the backup policy is parsed as other child nodes of the policy tree.

[0121] Step 2.5: Parse the strategy tree model into multiple key-value pairs and insert them into the Handler's local Redis instance;

[0122] Step 2.6: Convert the strategy tree model into JSON format and perform a custom hash algorithm operation. Compare the hash value with the persistent strategy information stored in MYSQL. If there is no identical hash value, mark the strategy tree with a timestamp and store it in MYSQL for persistent storage.

[0123] In the embodiment of this specification, in addition to obtaining the backup strategy, it is also necessary to determine the backup business information in the backup queue to facilitate subsequent analysis of the error-reporting job. Optionally, before receiving the backup job error information, the following steps are further included:

[0124] Acquire a first parameter of a backup job in the backup system, the first parameter including at least a job ID, a job type, a job status, and a policy name;

[0125] The first parameter of the backup job is stored in a designated database, and the first parameter of the backup job is updated according to a designated period.

[0126] It can be understood that the first parameter is the backup information of the backup job during the normal backup process, such as job ID, job type, job status, job status code, policy name, scheduling, storage unit, media server, client, start time, end time, duration, rate, master server, etc., wherein the first parameter may include the backup policy information in the backup job, such as the policy name, and the backup policy parameters corresponding to the policy name (such as scheduling, storage unit, etc.), the job ID is the unique identifier of the backup job, the job type can be the data type in the backup job, the job status can be the status information of the backup job during the backup process, such as the job status can be waiting for backup, backing up, backup completed, etc. Correspondingly, each job status can correspond to a job status code, which is convenient for operation and maintenance personnel to quickly determine the status of the backup job.

[0127] Since the job status in the first parameter will change as the backup job progresses, the first parameter needs to be updated according to a specified period. Optionally, the collected first parameter can be inserted into the JOB instance in the MYSQL database, and the first parameter of the backup job can be updated in the MYSQL database according to the specified period.

[0128] For example, taking NBU as an example, the NBU backup job information collection process is as follows:

[0129] Step 3.1: The Handler sends a command to the NBU Master to store the backup job within the specified time period (i.e., the backup window).

[0130] Step 3.2: Each NBU Master executes the backup job information generation command and imports the backup job information CSV file;

[0131] Step 3.3: Each NBU Master transmits the generated backup job information CSV file to the Handler;

[0132] Step 3.4: The Handler parses the received CSV file of backup job information of each NBU Master into a LIST data model;

[0133] Step 3.5: Import the LIST data model into the NBUJOB instance in the Handler local MYSQL database.

[0134] In a further embodiment, when an error job occurs, in order to facilitate analysis of the error job, as shown, after receiving the backup job error information, the step further includes:

[0135] Determining the job ID of the backup job according to the backup job error information;

[0136] According to the job ID of the backup job, obtaining second parameters of the backup job, the second parameters at least including a tape library, a tape drive, a tape, a backup path, and a media server;

[0137] The second parameter of the backup job is stored in a designated database.

[0138] It can be understood that the second parameter is further precision information of the backup job that reports an error, so that when performing error analysis, more dimensions can be analyzed to improve the accuracy of the analysis and achieve subsequent more accurate optimization. Optionally, the second parameter can include library, tape drive, tape, backup path, media server, backup log. For example, the second parameter can be inserted into the JOB_DETAIL instance for multi-dimensional analysis of subsequent errors.

[0139] Therefore, after step 3.5, you can also include:

[0140] Step 3.6: If an error occurs during the transfer process, the Handler sends a deep analysis and collection command to the NBUMaster where the backup job with the error occurs. The Handler collects relevant information about the library, drive, tape, backup path, media server, and backup logs involved in the backup job with the error, and stores the information in a persistent variable.

[0141] Step 3.7: The NBU Master transmits the generated variables to the Handler.

[0142] Step 3.8: Parse the variables through the custom interface and insert them into the NBUJOB_DETAIL instance in MYSQL.

[0143] In the embodiments of this specification, Figure 4 As shown, the determining of the error type and backup job information according to the backup job error information includes:

[0144] S201: Determine the error code and job ID of the backup job according to the backup job error information;

[0145] S202: Determine the error type of the error information according to the error code of the backup job;

[0146] S203: Extracting and obtaining the backup job information according to the job ID of the backup job, where the backup job information is a first parameter.

[0147] It can be understood that the error information is automatically generated by the backup system. For example, an error generation script can be set up. When an error occurs, the error information is generated by the error generation script and uploaded to the self-healing device. The error information can include an error code indicating the error type and the job ID of the backup job that reported the error. Of course, other information can also be included, such as the time of the error, which is not limited in the embodiments of this specification. Based on the determination of the error code and the job ID of the backup job, the corresponding error type can be determined based on the error code, and the corresponding backup job information of the error can be queried based on the backup job information collected in advance.

[0148] In the embodiment of this specification, determining the backup policy corresponding to the backup job according to the backup job information includes:

[0149] Determining a policy name adopted by the backup job according to the backup job information;

[0150] A backup policy corresponding to the backup job is determined from a designated database according to the policy name.

[0151] It can be understood that the backup job information (i.e., the first parameter) includes the backup strategy adopted during the backup, that is, the backup job information includes the policy name of the backup strategy. Therefore, the policy name can be directly extracted from the backup job information, and then the corresponding backup strategy can be determined based on the policy name. In some other embodiments, a mapping relationship between the backup job and the backup strategy can also be established, so that when determining the backup job, the backup strategy can be determined through the mapping relationship.

[0152] It should be noted that determining the backup strategy may be determining configuration parameters in the backup strategy, so as to facilitate subsequent adjustment of the configuration parameters to determine the success of the backup.

[0153] In the embodiments of this specification, Figure 5 As shown, the determining of the repair script corresponding to the error type from a preset repair script set includes:

[0154] S301: Determine a pre-stored set of repairable error types, where the set of error types corresponds to the set of repair scripts;

[0155] S302: Determine whether the error type is in the error type set;

[0156] S303: If yes, extract the repair script corresponding to the error type from the repair script set;

[0157] S304: If it is not, an alarm is issued to enable operation and maintenance personnel to manually repair it.

[0158] It can be understood that due to the complexity of the backup system, any failure in the system may cause the backup job to fail. Therefore, the error type set can be a set of historical error types. In this way, for the error information corresponding to the historical error type, the operation and maintenance personnel have corresponding recovery means, that is, the recovery means can be implemented in the form of a repair script. In this way, the historical error type is a repairable type, and the corresponding repair script is pre-stored. When an error type that is consistent with the historical error type occurs, the corresponding repair script can be extracted for automatic repair, thereby realizing self-healing of backup errors, saving labor costs, and improving repair efficiency.

[0159] In a further embodiment, the repair script can also be directly determined by the error code. Specifically, the historical error code set can be determined first, that is, the set of error codes that have appeared in the history. Each error code corresponds to an error type. Accordingly, the error type corresponding to each error code can also have a repair script to repair it. Then, it is determined whether the current error code is in the historical error code set. If it exists, the repair script corresponding to the error code can be directly extracted. If it does not exist, that is, the error code is a newly appeared error code, an alarm can be issued to enable the operation and maintenance personnel to manually repair it.

[0160] It should be noted that after manual repair, newly encountered error codes or error types can be added to the historical error code set or error type set. The manual repair process can then be coded into a repair script, which is added to the repair script set. A correspondence between the repair script and the newly added error code or error type is also established. This allows the backup system's self-healing capabilities to be expanded in real time, improving self-healing efficiency.

[0161] In a further embodiment, the repair script set is a set of repair scripts for backup jobs corresponding to historical error types, such as Figure 6 As shown, the step of determining the repair script set includes:

[0162] S401: Obtain historical error information of the backup system and a repair plan corresponding to the historical error information, wherein the repair plan includes operation steps and operation instructions for operation and maintenance personnel;

[0163] S402: Encapsulate the operation steps and operation instructions of the operation and maintenance personnel to obtain a repair script for the historical error information;

[0164] S403: Establishing a mapping relationship between the error type of the historical error information and the repair script;

[0165] S404: Form the repair script set according to the mapping relationship and the repair script.

[0166] By establishing the repair script set, after determining the error type, the corresponding repair script can be extracted from the repair script set by combining the error type with the set mapping relationship, thereby realizing self-healing of the backup system.

[0167] In another embodiment of the present specification, a mapping relationship between the error code of the historical error information and the repair script can be established, and the repair script set is formed based on the mapping relationship and the repair script. In this way, the corresponding repair script can be directly extracted from the error code.

[0168] The repair script is the engineering and coding of the operation steps and operation instructions. Different repair scripts correspond to different processing logics, which are encapsulated and processed through code logic blocks, so that the corresponding operation steps and operation instructions can be automatically executed.

[0169] In the embodiment of the present specification, in order to avoid the temporary suspension of the backup system due to a false error, optionally, after determining the error type and the backup job information according to the backup job error information, the following steps are further included:

[0170] Determining the running status of the backup job in the backup job information;

[0171] Determine whether the running state is ended with an error;

[0172] If yes, then executing the step of repairing the error information;

[0173] If not, cancel the error message and continue to perform the backup of the backup job.

[0174] It can be understood that the running status of the backup job, that is, the job status, is actually updated according to a specified period. By obtaining the information of the running status, the latest status of the backup job that reported an error can be determined in a timely manner. That is, when the running status is "end with error", it means that the backup job is in a tentative state and needs to be repaired before it can be backed up again. Therefore, the step of repairing the error information can be performed; when it is not "end with error", such as "running" or "backup completed", it means that the backup job is still in a normal state, then the error information should be canceled and the backup of the backup job should continue. By further judging the error information, this article can improve the reliability of the backup job, avoid the occurrence of false error reports, and improve the continuity of the backup job and the backup efficiency of the backup system.

[0175] In the embodiment of this specification, after the backup policy corresponding to the backup job reporting an error is adjusted using the repair script, the backup of the backup job may include:

[0176] Obtain the adjusted backup strategy;

[0177] Generate a re-backup instruction according to the adjusted backup strategy;

[0178] According to the re-backup instruction, the backup job that has error information is re-backed up.

[0179] It can be understood that the backup is also an automatically executed process, that is, when the repair script is executed, it can be determined that the backup policy adjustment is completed, and a re-backup instruction is generated according to the backup job information and the adjusted backup policy to realize the re-backup of the backup job that reported an error, thereby completing the self-healing processing of the backup job and reducing labor costs.

[0180] In the embodiment of this specification, in order to facilitate subsequent tracking of error information that has occurred, optionally, after re-backing up the backup job that has error information according to the re-backup instruction, the method further includes:

[0181] Acquire adjustment information of the backup strategy, the adjustment information including adjustment time;

[0182] Acquire the backup job information of the backup job in real time, wherein the backup job information includes the backup time;

[0183] The adjustment information and the operation information are placed in a designated monitoring platform to monitor the self-healing status of the error information.

[0184] This means that by monitoring and recording the processing of each error message, the corresponding information can be quickly identified during subsequent centralized error processing, improving error information management efficiency. Simultaneously, by displaying the error information on the monitoring platform, the progress and status of backup jobs can be tracked in real time, providing effective data and a basis for judgment for operations personnel to monitor backup job execution, reducing the likelihood of oversight or delayed processing.

[0185] Taking NBU as an example, the NBU backup self-recovery process is as follows:

[0186] Step 4.1: The Handler periodically sends a command to send NBU backup job error information.

[0187] Step 4.2: Each NBU Master executes the backup error job information generation script and imports the backup error job information file;

[0188] Step 4.3: Each NBU Master transmits the generated backup error job information file to the Handler. The Handler receives the error information, imports the real-time job information into the MYSQL database, and determines the latest running status of the backup job with the error (for example, running, error reporting completed, backup completed) based on the backup job information in the MYSQL database.

[0189] Step 4.4: If the backup is in progress or completed, no further processing is required. The backup job corresponding to the updated policy is written to the MYSQL database.

[0190] Step 4.5: If the error reporting ends, it is determined that action is required. The backup strategy monitoring information related to the backup error is entered into the InfluxDB monitoring library. Each backup strategy with an error is a separate Measurement. Monitoring information is regularly collected based on the Measurements in InfluxDB for closed-loop management and backup strategy adjustment records.

[0191] Step 4.6: Analyze the error code and error details according to the error job information file;

[0192] Step 4.7: Based on different error codes and error information, engineer and code the manual operation and maintenance experience and develop corresponding code logic blocks. In other steps, you can also develop code logic blocks in advance, so that you can directly extract them based on the error code.

[0193] Step 4.8: Based on the error code and error information, call the custom code logic block to perform targeted self-healing of the NBU backup error. For example, if the error code is 199 and the error is caused by backup failure due to backup timeout, the Handler parses the error to obtain the backup policy corresponding to the error cause, obtains the policy name and schedule name in the backup policy from Redis, generates a backup re-completion command, and sends it to the NBU Master, instructing it to re-execute the backup. The NBU Master then executes the command directly in the background.

[0194] The backup system error self-healing method provided in the embodiments of this specification can effectively improve the emergency response and recovery efficiency in backup job error scenarios, avoid delays in backup error processing, reduce the risk of backup job failure, and realize the further transformation of manual experience processing by operation and maintenance personnel to automated self-healing, further improving the efficiency and level of backup error emergency response.

[0195] Based on the same inventive concept, the embodiment of this specification also provides a backup system error self-healing device, such as Figure 7 As shown, the device includes:

[0196] The error information acquisition module 100 is used to receive the backup operation error information;

[0197] The error information processing module 200 is used to determine the error type and backup job information according to the backup job error information;

[0198] A backup strategy determination module 300 is configured to determine a backup strategy corresponding to the backup job based on the backup job information;

[0199] A repair script determining module 400 is configured to determine a repair script corresponding to the error type from a preset repair script set, where the repair script set is a set of repair scripts for backup jobs of different error types.

[0200] The re-backup module 500 is configured to load the repair script into the backup system to adjust the backup strategy, so that the backup system re-backs up the backup job according to the adjusted backup strategy.

[0201] The beneficial effects achieved by the above-mentioned device are consistent with the beneficial effects achieved by the above-mentioned method, and are not described in detail in the embodiments of this specification.

[0202] It should be noted that the backup system error self-healing method and device provided in the embodiments of this specification can be used for backup systems in the financial field, and can also be used in any field other than the financial field. The application field of the backup system error self-healing method and device provided in the embodiments of this specification is not limited.

[0203] like Figure 8 As shown, a computer device provided in an embodiment of this document is provided. The backup system error self-healing device described herein may be a computer device in this embodiment, executing the method described herein. The computer device 802 may include one or more processors 804, such as one or more central processing units (CPUs), each of which may implement one or more hardware threads. The computer device 802 may also include any memory 806 for storing any type of information, such as code, settings, data, etc. For example, and without limitation, the memory 806 may include any one or more combinations of the following: any type of RAM, any type of ROM, a flash memory device, a hard disk, an optical disk, etc. More generally, any memory may use any technology to store information. Furthermore, any memory may provide volatile or non-volatile retention of information. Furthermore, any memory may represent a fixed or removable component of the computer device 802. In one embodiment, when the processor 804 executes associated instructions stored in any memory or combination of memories, the computer device 802 may perform any operation of the associated instructions. The computer device 802 also includes one or more drive mechanisms 808 for interacting with any storage, such as a hard disk drive mechanism, an optical disk drive mechanism, and the like.

[0204] The computer device 802 may also include an input / output module 810 (I / O) for receiving various inputs (via input devices 812) and providing various outputs (via output devices 814). A specific output mechanism may include a presentation device 816 and an associated graphical user interface (GUI) 818. In other embodiments, the input / output module 810 (I / O), input devices 812, and output devices 814 may not be included, and the computer device 802 may simply be a computer device in a network. The computer device 802 may also include one or more network interfaces 820 for exchanging data with other devices via one or more communication links 822. One or more communication buses 824 couple the components described above together.

[0205] The communication link 822 may be implemented in any manner, for example, via a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 822 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.

[0206] Corresponding to Figure 3-Figure 6 The embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which executes the steps of the above method when executed by a processor.

[0207] The embodiment of the present invention also provides a computer readable instruction, wherein when the processor executes the instruction, the program causes the processor to execute the following Figures 3 to 6 The method shown.

[0208] It should be understood that in the various embodiments of this document, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this document.

[0209] It should also be understood that in the embodiments herein, the term "and / or" merely describes an association between associated objects, indicating that three possible relationships exist. For example, "A and / or B" could represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates an "or" relationship between the associated objects.

[0210] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the composition and steps of each example according to function. 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 can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this document.

[0211] Those skilled in the art will 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.

[0212] In the several embodiments provided herein, 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 merely illustrative. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices, or units, or can be an electrical, mechanical, or other form of connection.

[0213] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the embodiments herein.

[0214] In addition, the functional units in the various embodiments herein may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0215] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this article is essentially or the part that contributes to the existing technology, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of this article. The aforementioned storage medium includes: various media that can store program code, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0216] This article uses specific embodiments to illustrate the principles and implementation methods of this article. The description of the above embodiments is only used to help understand the methods and core ideas of this article. At the same time, for those skilled in the art, based on the ideas of this article, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation to this article.

Claims

1. A backup system error self-healing method, characterized in that: The method comprises: Collect backup policy parameters from the backup system according to a specified period, wherein the backup policy parameters include at least a policy name, a storage location, a retention period, and a schedule; According to a preset storage format, the backup strategy parameters are formatted to establish a backup strategy tree model, and stored in a designated database; Creating corresponding key-value pairs according to the path of each node of the strategy tree model and the data of the node; The configuration information key-value pair is used to cache the backup configuration information of each backup strategy and update it regularly; The backup strategy information that differs from the previous one is formed into a historical information table of each backup strategy for subsequent error comparison and analysis; Receive backup job error information; Determine the error type and backup job information according to the backup job error information; Determining a backup strategy corresponding to the backup job according to the backup job information; Determine a repair script corresponding to the error type from a preset repair script set, wherein the repair script set is a set of repair scripts for backup jobs of different error types; The repair script is loaded into the backup system to adjust the backup strategy, so that the backup system re-backs up the backup job according to the adjusted backup strategy.

2. The method according to claim 1, characterized in that The step of receiving the backup operation error message also includes: Acquire a first parameter of a backup job in the backup system, wherein the first parameter includes at least a job ID, a job type, a job status, and a policy name; The first parameter of the backup job is stored in a designated database, and the first parameter of the backup job is updated according to a designated period.

3. The method according to claim 2, characterized in that After receiving the backup operation error information, the method further includes: Determine the job ID of the backup job according to the backup job error information; According to the job ID of the backup job, obtaining the second parameter of the backup job, the second parameter at least including the tape library, tape drive, tape, backup path and media server; The second parameter of the backup job is stored in a designated database.

4. The method according to claim 2, characterized in that: The step of determining the error type and the backup job information according to the backup job error information includes: Determine the error code and job ID of the backup job according to the backup job error information; Determining the error type of the error information according to the error code of the backup job; The backup job information is extracted according to the job ID of the backup job, where the backup job information is the first parameter.

5. The method according to claim 1, characterized in that: The step of determining a backup strategy corresponding to the backup job according to the backup job information includes: Determining a policy name adopted by the backup job according to the backup job information; According to the policy name, a backup policy corresponding to the backup job is determined from a designated database.

6. The method according to claim 1, characterized in that The step of determining a repair script corresponding to the error type from a preset repair script set includes: Determine a pre-stored set of repairable error types, wherein the set of error types corresponds to the set of repair scripts; Determine whether the error type is in the error type set; If yes, extracting the repair script corresponding to the error type from the repair script set; If it is not there, an alarm will be issued so that the operation and maintenance personnel can repair it manually.

7. The method according to claim 6, characterized in that The step of determining the repair script set includes: Obtaining historical error information of the backup system and a repair plan corresponding to the historical error information, wherein the repair plan includes operation steps and operation instructions of an operation and maintenance personnel; The operation steps and operation instructions of the operation and maintenance personnel are packaged and processed to obtain a repair script for the historical error information; Establishing a mapping relationship between the error type of the historical error information and the repair script; The repair script set is formed according to the mapping relationship and the repair script.

8. The method according to claim 1, characterized in that: According to the backup job error information, after determining the error type and the backup job information, the method further includes: Determining the running status of the backup job in the backup job information; Determine whether the running state is an error end; If yes, then execute the step of repairing the error information; If not, the error message is cancelled and the backup of the backup job continues.

9. The method according to claim 1, characterized in that: The step of loading the repair script into the backup system to adjust the backup strategy so that the backup system can re-back up the backup job according to the adjusted backup strategy includes: Get the adjusted backup strategy; Generate a re-backup instruction according to the adjusted backup strategy; According to the re-backup instruction, the backup job with error information is re-backed up.

10. The method according to claim 9, characterized in that The step of re-backing up the backup job that has error information according to the re-backup instruction includes: Acquire adjustment information of the backup strategy, wherein the adjustment information includes an adjustment time; Acquire the re-backup job information of the backup job in real time, wherein the job information includes the re-backup time; The adjustment information and the operation information are placed in a designated monitoring platform to monitor the self-healing status of the error information.

11. A backup system error self-healing device, characterized in that: The device comprises: An error information acquisition module, used to collect backup strategy parameters from the backup system according to a specified period, wherein the backup strategy parameters at least include a strategy name, a storage location, a retention period, and a schedule; According to a preset storage format, the backup strategy parameters are formatted to establish a backup strategy tree model, and stored in a designated database; Creating corresponding key-value pairs according to the path of each node of the strategy tree model and the data of the node; The configuration information key-value pair is used to cache the backup configuration information of each backup strategy and update it regularly; The backup strategy information that differs from the previous one is formed into a historical information table of each backup strategy for subsequent error comparison and analysis; Receive backup job error information; An error information processing module, used to determine the error type and backup job information according to the backup job error information; A backup strategy determination module, used to determine the backup strategy corresponding to the backup job according to the backup job information; A repair script determination module, used to determine a repair script corresponding to the error type from a preset repair script set, where the repair script set is a set of repair scripts for backup jobs of different error types; The re-backup module is used to load the repair script into the backup system to adjust the backup strategy, so that the backup system re-backs up the backup job according to the adjusted backup strategy.

12. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method according to any one of claims 1 to 10 is implemented.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 10 is implemented.

Images