CN110262926B

CN110262926B - Metadata repairing method, device and system for server and computer equipment

Info

Publication number: CN110262926B
Application number: CN201910484286.8A
Authority: CN
Inventors: 田标; 梁鹰; 丘凌; 崔伟; 潘浩
Original assignee: CENTURY DRAGON INFORMATION NETWORK CO LTD
Current assignee: Tianyi Digital Life Technology Co Ltd
Priority date: 2019-06-05
Filing date: 2019-06-05
Publication date: 2021-10-08
Anticipated expiration: 2039-06-05
Also published as: CN110262926A

Abstract

The application relates to a metadata repairing method, a metadata repairing device, a metadata repairing system and computer equipment of a server. The method comprises the following steps: verifying the server metadata and determining abnormal metadata; generating an abnormal repairing message of the abnormal metadata, and pushing the abnormal repairing message to a target user terminal; the exception repair message comprises repair recommendation data; the repair recommendation data is used for repairing the abnormal metadata; and when a repair confirmation instruction of the target user terminal for the repair recommended data is received, repairing the abnormal metadata according to the repair recommended data. By adopting the method, the operation and maintenance efficiency of the server can be improved.

Description

Metadata repairing method, device and system for server and computer equipment

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a system, a computer device, and a storage medium for metadata repair of a server.

Background

With the increasing development of enterprises and the increasing of product traffic, enterprises often need to deploy a large number of servers for software products, so that the software products can provide high-quality and stable services for users.

For example, a business may have a plurality of rooms and 5000 servers all over the country, and these servers often need to have more than 300 projects deployed. The operation and maintenance workload and difficulty of such large number of servers are undoubtedly enormous.

Traditionally, the operation and maintenance management is often performed on the server in a manual management mode, however, when the server faces such a large operation and maintenance workload and operation and maintenance difficulty, the manual management and manual operation often hardly avoid the occurrence of situations such as misoperation and operation and maintenance data error, and the operation and maintenance efficiency is not high.

Therefore, the problem of low operation and maintenance efficiency exists in the operation and maintenance work of the existing server.

Disclosure of Invention

Therefore, it is necessary to provide a method and an apparatus for repairing metadata of a server, a computer device, and a storage medium, which can improve the operation and maintenance efficiency of the server, for solving the problem that the operation and maintenance efficiency of the existing server is not high.

A method of metadata repair for a server, the method comprising:

verifying the server metadata and determining abnormal metadata;

generating an abnormal repairing message of the abnormal metadata, and pushing the abnormal repairing message to a target user terminal; the exception repair message comprises repair recommendation data; the repair recommendation data is used for repairing the abnormal metadata;

and when a repair confirmation instruction of the target user terminal for the repair recommended data is received, repairing the abnormal metadata according to the repair recommended data.

In one embodiment, the generating the fault repair message of the abnormal metadata includes:

determining the type of a data problem according to the abnormal metadata;

inquiring repair recommendation data aiming at the data problem type;

generating a user determined link, and generating the abnormal repairing message according to the data problem type, the repairing recommendation data and the user determined link; and the user determination link is used for triggering the target user terminal to send the repair confirmation instruction.

In one embodiment, the verifying the server metadata and determining the abnormal metadata includes:

acquiring a data verification rule;

performing rule verification on the server metadata by adopting the data verification rule to generate a rule verification result;

and determining the abnormal metadata according to the rule checking result.

In one embodiment, before pushing the exception repair message to the target user terminal, the method further includes:

inquiring server information corresponding to the abnormal metadata;

determining the information of responsible personnel of the server information;

and determining the target user terminal according to the responsible personnel information.

In one embodiment, the repairing the abnormal metadata according to the repair recommendation data includes:

decrypting the repair recommendation data to obtain a decrypted repair parameter;

validity check is carried out on the decryption repair parameters;

and if the verification is passed, replacing the abnormal parameters in the abnormal metadata by using the decryption repair parameters.

In one embodiment, the querying of the repair recommendation data for the data problem type includes:

judging whether the step of inquiring the repair recommendation data aiming at the data problem type is successfully executed or not;

if not, generating a query failure alarm and sending the query failure alarm to the target user terminal; and the query failure alarm is used for reminding operation and maintenance personnel of repairing the failure of the recommended data query.

A metadata repair apparatus of a server, the apparatus comprising:

the verification module is used for verifying the server metadata and determining abnormal metadata;

the pushing module is used for generating an abnormal repairing message of the abnormal metadata and pushing the abnormal repairing message to a target user terminal; the exception repair message comprises repair recommendation data; the repair recommendation data is used for repairing the abnormal metadata;

and the repairing module is used for repairing the abnormal metadata according to the repairing recommended data when a repairing confirmation instruction of the target user terminal for the repairing recommended data is received.

A system for fault remediation of a server, the system comprising:

the collection client is used for collecting server metadata of a plurality of servers; uploading the server metadata to a regional server;

the regional server is used for receiving the server metadata of the acquisition client; compressing the server metadata in batches to obtain a compressed data packet; sending the compressed data packet to a central server;

the central server is used for receiving the compressed data packet of the regional server; decompressing the compressed data packet to obtain server metadata; verifying the server metadata and determining abnormal metadata; generating an abnormal repairing message of the abnormal metadata, and pushing the abnormal repairing message to a target user terminal; the exception repair message comprises repair recommendation data; the repair recommendation data is used for repairing the abnormal metadata; and when a repair confirmation instruction of the target user terminal for the repair recommended data is received, repairing the abnormal metadata according to the repair recommended data.

In one embodiment, the central server is further configured to query server information corresponding to the abnormal metadata; determining the information of responsible personnel of the server information; acquiring account data of the responsible personnel information, and taking the account data as a parameter encryption key; acquiring metadata repair parameters, and encrypting the metadata repair parameters by using the parameter encryption key to obtain the repair recommendation data; the abnormal repairing system is also used for generating a user determined link and a data problem type and generating the abnormal repairing message according to the data problem type, the repairing recommendation data and the user determined link; and the user determination link is used for triggering the target user terminal to send the repair confirmation instruction.

In one embodiment, the area server is further configured to obtain an IP query interval of the central server; inquiring the current IP information of the plurality of servers according to the IP inquiry interval; obtaining historical IP information of the central server, and comparing the historical IP information with the current IP information to obtain a comparison result; and sending the comparison result to the central server.

In one embodiment, the collection client is further configured to perform a metadata collection operation to obtain initial metadata of the plurality of servers; and performing data format conversion on the initial metadata to obtain the server metadata.

In one embodiment, the collecting client is further configured to determine whether the step of uploading the server metadata to the regional server is successfully performed; if not, generating an uploading failure notice; and sending the uploading failure notice to the central server.

In one embodiment, the central server is further configured to receive a new data item instruction of a user; and adjusting the data item of the metadata of the acquisition server of the acquisition client according to the new data item instruction.

A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:

verifying the server metadata and determining abnormal metadata;

A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:

verifying the server metadata and determining abnormal metadata;

The metadata repairing method, the device, the computer equipment and the storage medium of the server verify the server metadata of each server; after the abnormal metadata is determined in the server metadata, repairing recommendation data is determined according to the abnormal metadata, an abnormal repairing message is generated, and the abnormal repairing message is pushed to a target user terminal of a corresponding operation and maintenance person, so that the operation and maintenance person can check and confirm the abnormal repairing message; when a repair confirmation instruction sent by an operation and maintenance person using a target user terminal is received, automatically repairing abnormal metadata on an abnormal server by using repair recommendation data; therefore, the operation and maintenance personnel can repair the abnormal metadata on the abnormal server under the condition that the operation and maintenance personnel do not log in the abnormal server system, the abnormal data problem of the abnormal server is solved, and the working efficiency of the operation and maintenance personnel operation and maintenance server is improved.

Drawings

FIG. 1 is a diagram of an application environment of a method for metadata repair for a server, according to an embodiment;

FIG. 2 is a flow diagram that illustrates a method for metadata repair for a server, according to one embodiment;

FIG. 3 is a block diagram of an apparatus for metadata recovery of a server according to an embodiment;

FIG. 4 is a block diagram of a metadata repair system for a server in one embodiment;

FIG. 5 is a flow diagram that illustrates operation of a central server of a metadata repair system of a server, under an embodiment;

FIG. 6 is a flow diagram that illustrates operation of a metadata repair system of a server, in one embodiment;

FIG. 7 is a diagram illustrating an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The metadata repairing method for the server can be applied to the application environment shown in fig. 1. Wherein the repair server 110 communicates with the target user terminal 120 through a network. The target user terminal 120 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the repair server 110 may be implemented by an independent server or a server cluster composed of a plurality of servers.

In one embodiment, as shown in fig. 2, there is provided a metadata repair method for a server, including the steps of:

step 210, the server metadata is checked to determine abnormal metadata.

The server metadata may refer to various data required for the server to operate. In practical applications, the server metadata may refer to attribute data of a server, a network device, a DNS, a load balancing service, and the like, and may also refer to item composition data of a program item (e.g., Web server, item role, database service, various middleware services or various URLs of an item) and item call data between items (item dependency data).

Wherein, the abnormal metadata may refer to server metadata in which an abnormality exists.

In specific implementation, operation and maintenance personnel firstly need to install the acquisition client to a plurality of servers which need to be automatically repaired. Then, the collecting client collects and packages the server metadata on each server according to the preset configuration information, wherein the data format of the server metadata is a JSON (JavaScript Object notification, a lightweight data exchange format); specifically, the server metadata may include: the system comprises equipment metadata such as machine room data, equipment IP, virtual IP, public network IP, host names, equipment types (including physical machines and virtual machines/cloud machines), memories, CPU models, CPU core numbers, manufacturers, models, hard disk spaces, racks where the equipment is located, names of operating systems, version numbers, service data mainly running and the like, and project metadata such as project calling data and project composition data. And the expansion can be carried out according to the actual situation. Finally, the server metadata is sent to the repair server 110. After the repair server 110 receives the server metadata, machine room information and IP information in the server metadata are extracted, and the repair server 110 locates the entity servers corresponding to different server metadata by using a unique combination principle of the machine room information and the IP information.

Meanwhile, the repair server 110 compares the newly received server metadata with the existing server metadata, and directly stores the newly received server metadata when the existing server metadata is empty. When the existing server metadata is not empty, differences between the newly received server metadata and the existing server metadata are recorded.

The repair server 110 checks the server metadata at regular time according to a preset check rule, determines abnormal metadata that does not meet the check rule, and obtains a check result. And finally, automatically recording the verification result for subsequent specific checking at any time.

In addition, the repair server 110 may also display the verification result on the display page, and the user may log in to the management system carried by the repair server 110, adjust the relevant data after comprehensively querying the data of each part, and send out a real-time data query operation to the client on the management system to check whether the logged data of the system is consistent with the actual data.

Meanwhile, the repair server 110 completes the process of verifying the server metadata in the process of storing the server metadata in the database, so that the problems of slow performance, unstable system and the like caused by excessive database table query and data can be avoided.

Step 220, generating an abnormal repairing message of the abnormal metadata, and pushing the abnormal repairing message to a target user terminal; the exception repair message includes repair recommendation data; the repair recommendation data is data for repairing the abnormal metadata.

The exception repair message may be a message for notifying the operation and maintenance staff that the server metadata needs to be repaired.

In a specific implementation, after the repair server 110 determines that abnormal metadata exists in the server metadata, a specific abnormal type of the data problem is determined according to the abnormal metadata; then, the repair server 110 may actively call an auto discovery function to find the recommended repair data; and encrypting the repair data to obtain repair recommendation data. Wherein the repair recommendation data is data for repairing the abnormal metadata. Then, according to the specific exception type and the repair recommendation data of the data problem, an exception repair message is generated, wherein the exception repair message can be automatically generated by using an Html (hypertext Markup Language) template written by Freemarker (a template engine). Finally, the repair server 110 regularly pushes the abnormal repair message to the target user terminal 120. The target user terminal 120 is a user terminal of an operation and maintenance worker responsible for maintaining the server to be maintained. In practical applications, the repair server 110 may be configured to push the abnormal repair message regularly through enterprise mail or enterprise instant messaging software every day, every week or every month.

And step 230, when a repair confirmation instruction of the target user terminal for repairing the recommended data is received, repairing the abnormal metadata according to the repair recommended data.

Wherein the repair confirm instruction may be an instruction for the repair server to repair the abnormal metadata.

In a specific implementation, after the target user terminal 120 of the operation and maintenance person receives the abnormal repair message pushed by the repair server 110, the target user terminal displays the abnormal repair message, so that the operation and maintenance person can refer to the specific abnormal type and the abnormal metadata of the server to be maintained and the repair recommendation data recommended by the repair server 110. When the operation and maintenance personnel confirm that there is no error and decide to let the repair server 110 perform automatic repair, the operation and maintenance personnel perform repair determination operation, and the target user terminal 120 sends a repair determination instruction to the repair server 110 in response to the repair determination operation. Meanwhile, the target user terminal 120 returns the repair recommendation data to the repair server 110. Finally, the repair server 110 repairs the abnormal metadata according to the repair recommendation data returned by the target user terminal 120.

In the above method for repairing metadata of a server, the server metadata of each server is verified; after the abnormal metadata is determined in the server metadata, repairing recommendation data is determined according to the abnormal metadata, an abnormal repairing message is generated, and the abnormal repairing message is pushed to a target user terminal of a corresponding operation and maintenance person, so that the operation and maintenance person can check and confirm the abnormal repairing message; when a repair confirmation instruction sent by an operation and maintenance person using a target user terminal is received, automatically repairing abnormal metadata on an abnormal server by using repair recommendation data; therefore, the operation and maintenance personnel can repair the abnormal metadata on the abnormal server under the condition that the operation and maintenance personnel do not log in the abnormal server system, the abnormal data problem of the abnormal server is solved, and the working efficiency of the operation and maintenance personnel operation and maintenance server is improved.

In one embodiment, generating a failover message for exception metadata includes: determining the type of the data problem according to the abnormal metadata; inquiring repair recommendation data aiming at the data problem type; generating a user determined link, and generating an abnormal repairing message according to the data problem type, the repairing recommendation data and the user determined link; the user determination link is used for triggering the target user terminal to send a repair confirmation instruction.

In a specific implementation, the process of generating the fault repairing message by the repairing server 110 specifically includes; the repair server 110 determines the type of data problem of the server according to the abnormal metadata, for example, the project does not include any server IP, the server does not have an IP, the server does not have a person in charge, the self-built virtual machine does not have a host, the server does not have CPU data, the server does not have memory data, the server does not have hard disk data, the server does not associate any product or project, the server does not have a machine room, the server does not have a host name, and the use data.

For some data problem types, the repair server 110 may actively call an auto discovery function to query repair recommendation data for the data problem type; meanwhile, the repair server 110 generates a user determined link, and generates an abnormal repair message according to the data problem type, the repair recommendation data and the user determined link; for the operation and maintenance personnel to review, refer to and determine whether to have the repair server 110 perform automatic repair of the abnormal metadata. When the user confirms that the repair recommendation data recommended by the repair server 110 is correct, the operation and maintenance personnel only need to click the user determination link, and then trigger the target user terminal 120 to send a repair confirmation instruction, so that the repair server 110 automatically repairs the abnormal metadata according to the repair recommendation data returned by the target user terminal 120.

According to the technical scheme of the embodiment, the abnormal repairing message generated by the repairing server comprises a user determined link; when the operation and maintenance personnel check detailed information in the abnormal repairing message, for example, the data problem type, the repairing recommended data and other contents are correct, the operation and maintenance personnel click the user determined link to trigger the target user terminal to send a repairing confirmation instruction, so that the repairing server automatically repairs the abnormal metadata on the abnormal server; the abnormal metadata on the abnormal server is repaired under the condition that the operation and maintenance personnel do not log in the abnormal server system, the abnormal data problem of the abnormal server is solved, and the working efficiency of the operation and maintenance personnel operation and maintenance server is improved.

In another embodiment, verifying the server metadata to determine anomalous metadata includes: acquiring a data verification rule; performing rule verification on the server metadata by adopting a data verification rule to generate a rule verification result; and determining abnormal metadata according to the rule checking result.

In a specific implementation, the process of verifying the server metadata by the repair server 110 and determining the abnormal metadata specifically includes: acquiring a data verification rule predefined by operation and maintenance personnel; the repair server 110 performs rule verification on the server metadata at regular time by adopting a data verification rule to generate a rule verification result; the data checking rules are mainly determined according to business requirements, and the method further comprises the steps of automatically scanning a database table, and searching whether important attributes corresponding to an entity server of the server metadata are empty or not, wherein the tables are specifically scanned, and fields of the tables can be customized by a user, main checking items comprise cyclic calling among items, whether the items comprise any server IP or not, whether the server comprises the IP or not, whether the entity server comprises a responsible person or not, whether a self-built virtual machine comprises a host or not, whether the server comprises CPU information, memory information and hard disk information or not, whether the server is associated with any product or item or not, whether the server comprises a machine room or not, whether the server comprises a host name and application data or not, and the like, and meanwhile, the user is allowed to define and start a new data checking rule. Meanwhile, the repair server 110 completes the process of verifying the server metadata in the process of storing the server metadata in the database, so that the problems of slow performance, unstable system and the like caused by excessive database table query and data can be avoided.

According to the technical scheme of the embodiment, the server metadata is subjected to regulation and verification according to the data verification rule preset by the user, so that abnormal metadata can be accurately determined in the server metadata; meanwhile, the process of verifying the server metadata is completed in the process of storing the server metadata in the database, so that the problems of slow performance, unstable system and the like caused by querying of too many database tables and data can be avoided, the processing efficiency of repairing the server is improved, and the working efficiency of the existing operation and maintenance personnel operation and maintenance server is improved.

In another embodiment, before pushing the exception recovery message to the target ue, the method further includes: inquiring server information corresponding to the abnormal metadata; determining the information of responsible personnel of the server information; and determining the target user terminal according to the information of the responsible personnel.

The responsible personnel may refer to operation and maintenance personnel responsible for operating the server where the abnormal metadata currently occurs.

The responsible person information may refer to account information of the responsible person.

In a specific implementation, before the repair server 110 pushes the abnormal repair message to the target user terminal, the repair server 110 queries server information corresponding to the abnormal metadata; specifically, the repair server 110 extracts the machine room information and the IP information in the server metadata, and the repair server 110 locates the entity server corresponding to the abnormal metadata by using the principle that the combination of the machine room information and the IP information is unique, and determines the server information of the entity server; then, according to the server information, specific information of an operation and maintenance person responsible for operating and maintaining the entity server is determined, and therefore the information is named as responsible person information; then, a target user terminal is determined among a plurality of user terminals communicating with the repair server 110 according to the responsible person information, thereby enabling an abnormal repair message to be accurately transmitted to the target user terminal 120 of the operation and maintenance person responsible for the entity server.

According to the technical scheme of the embodiment, server information corresponding to abnormal metadata is determined; determining the information of responsible personnel of operation and maintenance personnel responsible for operating the server with the abnormal metadata according to the server information; and finally, accurately determining the target user terminal according to the information of the responsible personnel.

In another embodiment, repairing the exception metadata based on the repair recommendation data includes: decrypting and repairing the recommended data to obtain a decrypted and repaired parameter; validity check is carried out on the decryption restoration parameters; and if the verification is passed, replacing the abnormal parameters in the abnormal metadata by using the decryption repair parameters.

In a specific implementation, after the repair server 110 receives the repair recommendation data returned by the target user terminal 120, the repair server 110 decrypts the repair recommendation data by using a key corresponding to the target user terminal 120 to obtain a decrypted repair parameter; then, the repair server 110 performs validity check on the decrypted repair parameter, for example, checks whether the decrypted repair parameter is null; and checking whether the actual responsible person for decrypting the repair parameters and the notification channel do not accord with the preset configuration. When the verification is passed, the repair server 110 replaces the abnormal parameter in the abnormal metadata by using the decrypted repair parameter, and meanwhile, the repair server 110 generates a running log.

According to the technical scheme, when the repair server transmits repair recommended data to the target user terminal, the repair recommended data are encrypted through a key corresponding to the target user terminal, when the repair server receives the repair recommended data returned by the target user terminal, the repair recommended data need to be decrypted through the key, whether decrypted repair parameters obtained through decryption are valid or not is verified, and if the decrypted repair parameters are valid, the decrypted repair parameters are used for replacing abnormal parameters in abnormal metadata; therefore, the safety of data transmission and the accuracy of automatically repairing abnormal metadata are improved, and the working efficiency of the existing operation and maintenance personnel operation and maintenance server is further improved.

In another embodiment, querying repair recommendation data for a data problem type includes: judging whether the step of inquiring the repair recommendation data aiming at the data problem type is successfully executed or not; if not, generating a query failure alarm and sending the query failure alarm to the target user terminal; and the query failure alarm is used for reminding the operation and maintenance personnel of repairing the failure of the recommended data query.

In a specific implementation, in the process that the repair server 110 queries the repair recommendation data for the data problem type, the repair server 110 further needs to determine whether the step of querying the repair recommendation data for the data problem type is successfully executed; if the repair server 110 cannot inquire the repair recommendation data for the data problem type, for example, the data of the server data and the data of the item, the repair server 110 generates an inquiry failure alarm and sends the inquiry failure alarm to the target user terminal 120; the query failure alarm is used to remind the operation and maintenance staff of failure in repairing the recommended data query, and meanwhile, the repair server 110 generates a query failure log.

According to the technical scheme of the embodiment, when the query of the repair recommendation data aiming at the data problem type fails, the query failure alarm is generated and sent to the target user terminal, so that operation and maintenance personnel responsible for operating and maintaining the abnormal server can be informed in time.

It should be understood that, although the steps in the flowchart of fig. 2 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in fig. 2 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.

In one embodiment, as shown in fig. 3, there is provided a metadata repair apparatus of a server, the apparatus including:

the checking module 310 is configured to check the server metadata and determine abnormal metadata;

the pushing module 320 is configured to generate an abnormal repairing message of the abnormal metadata, and push the abnormal repairing message to the target user terminal; the exception repair message includes repair recommendation data; the repair recommendation data is data for repairing abnormal metadata;

and the repairing module 330 is configured to repair the abnormal metadata according to the repair recommended data when a repair confirmation instruction for the repair recommended data by the target user terminal is received.

In another embodiment, the pushing module 320 includes: the type determining submodule is used for determining the type of the data problem according to the abnormal metadata; the query submodule is used for querying the repair recommendation data aiming at the data problem type; the generation submodule is used for generating a user determined link and generating the abnormal repairing message according to the data problem type, the repairing recommendation data and the user determined link; and the user determination link is used for triggering the target user terminal to send the repair confirmation instruction.

In another embodiment, the verification module 310 includes: the acquisition submodule is used for acquiring a data verification rule; the verification submodule is used for performing rule verification on the server metadata by adopting the data verification rule to generate a rule verification result; and the exception determining submodule is used for determining the exception metadata according to the rule checking result.

In another embodiment, the above metadata repair apparatus for a server further includes: the query module is used for querying the server information corresponding to the abnormal metadata; the responsible person determining module is used for determining responsible person information of the server information; and the terminal determining module is used for determining the target user terminal according to the information of the responsible personnel.

In another embodiment, the repair module 330 includes: the decryption submodule is used for decrypting the repair recommended data to obtain a decryption repair parameter; the verification submodule is used for verifying the validity of the decryption repair parameters; and the repair submodule is used for replacing the abnormal parameters in the abnormal metadata by using the decrypted repair parameters if the verification is passed.

In another embodiment, the query submodule includes: the judging unit is used for judging whether the step of inquiring the repair recommendation data aiming at the data problem type is successfully executed or not; the warning unit is used for generating a query failure warning if the target user terminal does not receive the query failure warning, and sending the query failure warning to the target user terminal; and the query failure alarm is used for reminding operation and maintenance personnel of repairing the failure of the recommended data query.

For specific limitations of the metadata repair apparatus for a server, reference may be made to the above limitations of the metadata repair method for a server, which are not described herein again. The modules in the metadata repair apparatus of the server described above may be implemented in whole or in part by software, hardware, and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, as shown in fig. 4, there is provided a fault repair system of a server, the system including: acquisition client 410, regional server 420 and central server 430;

an acquisition client 410 for acquiring server metadata of a plurality of servers; upload server metadata to the regional server 420.

In a specific implementation, the acquisition client 410 may be a client program developed by adopting a go language; the operation and maintenance personnel firstly need to install the acquisition client to a plurality of servers which need to be automatically repaired. Then, the collecting client collects and packages server metadata on each server according to the preset configuration information, wherein the data format of the server metadata is a JSON (JavaScript Object notification, a lightweight data exchange format); specifically, the server metadata may include: the system comprises machine room data, equipment IP, virtual IP, public network IP, host names, equipment types (including physical machines and virtual machines/cloud machines), memories, CPU models, CPU core numbers, manufacturers, models, hard disk spaces, a machine frame where the equipment is located, operating system names, project calling data, project composition data and version numbers, main running service data and the like, and can be expanded according to actual conditions; finally, the server metadata is uploaded to the regional server 420.

A regional server 420 for receiving server metadata of the acquisition client 410; compressing server metadata in batches to obtain compressed data packets; the compressed data packet is sent to the central server 430.

In a specific implementation, after receiving the server metadata uploaded by the acquisition client 410, the regional server 420 caches the server metadata in an embedded database SQLite (a lightweight database) of the regional server 420. After receiving the server metadata uploaded by the acquisition client 410 and the preset collection time, the regional server 420 extracts the server metadata of the center server 430 to be uploaded from the embedded database SQLite, and performs batch compression on the server metadata according to the preset batch uploading amount to obtain a compressed data packet; specifically, the number of batch uploads may be 200. Finally, the regional server 420 sends the compressed data packet to the central server 430.

In practical applications, the area server 420 is a simplified HTTPS communication server, and is deployed in a computer room. If there is a dedicated line between multiple machine rooms, one machine room deployment area server 420 can be found in the machine rooms, and the machine rooms are mainly used as the transfer of communication and data transfer between the central server 430 and the acquisition client 410, so that data loss is prevented, and unstable conditions can not occur even when the acquired data volume is large.

After the compressed data packet is successfully uploaded to the central server 430, the uploaded server metadata in the SQLite embedded database is deleted; if the compressed data packets uploaded to the central server 430 by the regional server 420 are unsuccessful, recording failure information, and after the next group of compressed data packets are successfully uploaded, immediately uploading a group of compressed data packets which are unsuccessfully uploaded, wherein all the compressed data packets are uploaded to the central server 430 through a JSON format and an HTTPS (Hypertext Transfer Protocol Secure).

A central server 430 for receiving the compressed data packet of the regional server 420; decompressing the compressed data packet to obtain server metadata; verifying the server metadata and determining abnormal metadata; generating an abnormal repair message of the abnormal metadata, and pushing the abnormal repair message to the target user terminal 120; the exception repair message includes repair recommendation data; the repair recommendation data is data for repairing abnormal metadata; when a repair confirmation instruction for the repair recommendation data by the target user terminal 120 is received, the abnormal metadata is repaired according to the repair recommendation data.

In a specific implementation, the central server 430 receives the compressed data packet of the regional server 420; decompressing the compressed data packet to obtain server metadata; the central server 430 checks the server metadata at regular time according to a preset check rule, determines abnormal metadata which does not conform to the check rule, and obtains a check result. And finally, automatically recording the verification result for subsequent specific checking at any time.

After the central server 430 determines that abnormal metadata exists in the server metadata, the specific abnormal type of the data problem is determined according to the abnormal metadata; then, the central server 430 actively calls an auto discovery function to find out the recommended repair data; and encrypting the repair data to obtain repair recommendation data. Wherein the repair recommendation data is data for repairing the abnormal metadata. Then, according to the specific exception type and the repair recommendation data of the data problem, an exception repair message is generated, wherein the exception repair message can be automatically generated by using an Html (hypertext Markup Language) template written by Freemarker (a template engine). Finally, the central server 430 pushes the abnormal repairing message to the target user terminal 120 at regular time. The target user terminal 120 is a user terminal of an operation and maintenance worker responsible for maintaining the server to be maintained. In practical application, the abnormal repairing message can be pushed in a mode of enterprise mail or enterprise instant messaging software and the like.

After the target user terminal 120 of the operation and maintenance personnel receives the abnormal repairing message pushed by the central server 430, the target user terminal displays the abnormal repairing message, so that the operation and maintenance personnel can refer to the specific abnormal type and the abnormal metadata of the server to be maintained and the repairing recommendation data recommended by the central server 430. When the operation and maintenance personnel confirm that there is no error and decide to let the central server 430 perform automatic repair, the operation and maintenance personnel perform repair determination operation, and the target user terminal 120 sends a repair determination instruction to the central server 430 in response to the repair determination operation. Meanwhile, the target user terminal 120 returns the repair recommendation data to the central server 430. Finally, the central server 430 repairs the abnormal metadata according to the repair recommendation data returned by the target user terminal 120.

In addition, when the central server 430 can actively initiate query of server metadata, the central server 430 generates and sends a corresponding operation request to the regional server 420, the regional server 420 selects a mode to call the acquisition client of the target server to acquire data and return the data, when an infrastructure channel is available, the infrastructure channel is preferentially used, otherwise, the central server logs in the target server through SSH to call the acquisition client 410, acquires a result and returns the result.

According to the technical scheme, the collection of server metadata of each server by the collection client is improved; the regional server transfers the metadata of the server, so that data loss is prevented, and unstable conditions can not occur even if the acquired data volume is large; the central server checks the server metadata, determines repair recommendation data according to the abnormal metadata after determining the abnormal metadata in the server metadata, generates abnormal repair information, and pushes the abnormal repair information to a target user terminal corresponding to the operation and maintenance personnel so as to allow the operation and maintenance personnel to check and confirm; when a repair confirmation instruction sent by an operation and maintenance person using a target user terminal is received, the central server automatically repairs abnormal metadata on the abnormal server by using repair recommendation data; therefore, the operation and maintenance personnel can repair the abnormal metadata on the abnormal server under the condition that the operation and maintenance personnel do not log in the abnormal server system, the abnormal data problem of the abnormal server is solved, and the working efficiency of the operation and maintenance personnel operation and maintenance server is improved.

In another embodiment, the central server 430 is further configured to query server information corresponding to the abnormal metadata; determining the information of responsible personnel of the server information; acquiring account data of the responsible personnel information, and using the account data as a parameter encryption key; acquiring metadata repair parameters, and encrypting the metadata repair parameters by using a parameter encryption key to obtain repair recommendation data; the system is also used for generating a user determined link and a data problem type, and generating an abnormal repairing message according to the data problem type, the repairing recommendation data and the user determined link; the user determination link is used for triggering the target user terminal to send a repair confirmation instruction.

In a specific implementation, the central server 430 queries server information corresponding to the abnormal metadata; determining the information of responsible personnel of the server information; specifically, the central server 430 extracts the machine room information and the IP information in the server metadata, and the central server 430 locates the entity server corresponding to the abnormal metadata by using the principle that the combination of the machine room information and the IP information is unique, and determines the server information of the entity server; then, according to the server information, specific information of an operation and maintenance person responsible for operating and maintaining the entity server is determined, and therefore the information is named as responsible person information; and meanwhile, determining account data of the responsible personnel information. Then, the central server 430 uses the account data as a parameter encryption key, obtains the metadata repair parameter at the same time, and encrypts the metadata repair parameter by using the parameter encryption key to obtain repair recommendation data.

The central server 430 is further configured to generate a user-determined link and a data problem type, and generate an abnormal repair message according to the data problem type, the repair recommendation data, and the user-determined link; the user determination link is used for triggering the target user terminal to send a repair confirmation instruction.

According to the technical scheme, when the central server transmits the repair recommendation data to the target user terminal, the repair recommendation data are obtained by using account data of operation and maintenance personnel as a parameter encryption key and encrypting the parameter encryption key, so that the safety of data transmission and the accuracy of automatic repair of abnormal metadata are improved, and meanwhile, an abnormal repair message generated by the encryption repair server comprises a user determination link; when the operation and maintenance personnel check detailed information in the abnormal repairing message, for example, the data problem type, the repairing recommended data and other contents are correct, the operation and maintenance personnel click the user determined link to trigger the target user terminal to send a repairing confirmation instruction, so that the repairing server automatically repairs the abnormal metadata on the abnormal server; the abnormal metadata on the abnormal server is repaired under the condition that the operation and maintenance personnel do not log in the abnormal server system, the abnormal data problem of the abnormal server is solved, and the working efficiency of the operation and maintenance personnel operation and maintenance server is improved.

In another embodiment, the area server 420 is further configured to obtain an IP query interval of the central server 430; inquiring current IP information of a plurality of servers according to the IP inquiry interval; acquiring historical IP information of the central server 430, and comparing the historical IP information with the current IP information to obtain a comparison result; and sends the comparison result to the central server 430.

In a specific implementation, the regional server 420 obtains an IP query interval, e.g., an IP segment, of the central server 430; then, inquiring the current IP information of a plurality of servers according to the IP inquiry interval; calling the central server 430 to inquire historical IP information of the plurality of servers, and obtaining a comparison result by comparing the historical IP information with the current IP information; and sends the comparison result to the central server 430. Specifically, a server IP which is newly online but not managed in time can be found out according to the comparison result, or a server IP which is managed but cannot be connected can be found out.

According to the technical scheme, the regional server carries out IP scanning on the currently controlled server, so that the IP information of the server can be managed in time, and the operating efficiency of the metadata repairing system of the server is improved.

In another embodiment, the collecting client 410 is further configured to perform a metadata collecting operation to obtain initial metadata of a plurality of servers; and performing data format conversion on the initial metadata to obtain server metadata.

In a specific implementation, the collection client 410 performs metadata collection, specifically, the collection client 410 may check the item type first, and in addition, the item type may also be configured from a configuration file of the client itself, or obtained through notification of a central server. Then, the acquisition client 410 reads the project composition data and the project dependency data from the configuration file of the project according to the project type, specifically, the acquisition client 410 reads all IP, URL, port information and configuration items thereof in the configuration file, for common middleware such as a database, Redis, MongoDB and the like, the configuration information can be obtained according to the corresponding configuration items in a targeted manner, and finally, the project composition data and the project dependency data are encapsulated to obtain server metadata in a JSON format, and the server metadata is uploaded to the regional server 420. For each type of project, corresponding project composition and automatic discovery realization of dependency information need to be specially developed, meanwhile, the collection of error conditions is emphasized, and the error conditions are transmitted back to a central server for basic management and processing, and the information can be used for continuously improving the supporting conditions of the client on different types of project information, so that more and more project information can be automatically discovered.

In addition, the acquisition client 410 acquires information by executing a command of Linux, reading a file, or accessing third-party software, and the acquired metadata is converted by a JSON format to obtain server metadata. Finally, the server metadata is sent to the regional server 420. The metadata data items collected and reported comprise a machine room, an equipment IP, a virtual IP, a public network IP, a host name, an equipment type (comprising a physical machine and a virtual machine/cloud machine), a memory, a CPU (Central processing Unit) model, a CPU core number, a manufacturer, a model, a hard disk space, a machine frame, an operating system name, an operating system version number, main running services and the like, and can be expanded according to actual conditions.

According to the technical scheme of the embodiment, the acquisition client can accurately and comprehensively acquire the metadata of the server by executing data acquisition operation; meanwhile, the data format of the server metadata is a JSON format, the JSON format has a simple and clear hierarchical structure, reading and writing of personnel are easy, machine analysis and generation are easy, and network transmission efficiency is effectively improved.

In another embodiment, the collecting client 410 is further configured to determine whether the step of uploading the server metadata to the area server 420 is successfully performed; if not, generating an uploading failure notice; and sends an upload failure notification to the central server 430.

In a specific implementation, the acquisition client 410 determines whether the step of uploading the server metadata to the area server 420 is successfully executed; if uploading the server metadata to the regional server 420 is unsuccessful, generating an upload failure notification; and sends an upload failure notification to the central server 430. The upload failure notification is used to notify the operation and maintenance staff that the uploading of the server metadata from the acquisition client 410 to the area server 420 is unsuccessful.

According to the technical scheme of the embodiment, when the metadata of the server is uploaded to the regional server by the acquisition client and the metadata is unsuccessful, an uploading failure notice is generated; and sending an uploading failure notice to the central server, and managing and controlling the acquisition client with uploading abnormality in time.

In another embodiment, the central server 430 is further configured to receive a new data item instruction from the user; and adjusting the collection client 410 to collect the data items of the metadata of the server according to the instruction of the newly added data items.

In the specific implementation, in the process that the central server 430 receives a new data item instruction of a user, the method specifically includes that the user inputs the new data item instruction in an operating system of the central server 430, for example, a data item of newly-added acquired data is configured, that is, a data item which needs to be newly-added and acquired for the server and the project; meanwhile, the user can also designate to select the acquisition range according to the object, for example, the acquisition range is designated according to a machine room, a version number of a server operating system and the like; the lowest version number of the client supporting the acquisition of new data, the script used when acquiring the new data, and the like can also be configured, so as to adjust the data item of the metadata of the server acquired by the acquisition client 410. The configuration contents are all instructions for adding new data items. In practical application, the collection client 410 uses default collection data items, and when the user needs to adjust, a new data item instruction can be input to the central server 430.

Then, after the central server 430 uploads the data in the area server 420, it searches whether the acquisition client 410 corresponding to the area server 420 needs to add more acquisition data items according to the newly-added data item instruction, and if so, issues the data acquisition requirement in the newly-added data item instruction of the user to the area server 420 along the corresponding communication interface, specifically, the data acquisition requirement includes the newly-added acquired data item name, the script download path, and the MD5 code, the client IP, and the required client version number of the script file. The regional server 420 issues the data acquisition requirement to the corresponding acquisition client 410, and meanwhile, the regional server 420 records the information of the acquisition client 410 that has been successfully issued in the SQLite.

Then, after receiving the data acquisition requirement of the area server 420, the acquisition client 410 downloads the corresponding data acquisition script by using a script download path according to the data acquisition requirement; the data acquisition script is verified by using the MD5 code of the script file; meanwhile, before downloading, the corresponding data acquisition client 410 will first check whether the script exists locally, and if so, download the script; if the script is not needed to adjust the condition of the collected data item, the collection of new data is supported by the update collection client 410, and in this case, the operation and maintenance personnel can use the infrastructure batch update.

When the acquisition client 410 acquires new data each time, the data acquisition script is automatically executed, the data acquisition script outputs a result according to a format of 'index | value', the acquisition client 410 analyzes and reports the result, and if an error occurs, different negative error codes are returned to the central server 430 to explain the error reason; for the unnecessary data acquisition script, the acquisition client 410 automatically acquires and packages the data of the data acquisition log and reports the data to the central server 430.

According to the technical scheme of the embodiment, the data item of the metadata of the acquisition server of the acquisition client side is adjusted according to the newly-added data item instruction input by the user; the method and the device realize the flexible adjustment of the data type of the metadata of the acquisition server of the acquisition client according to the requirements of users, the acquisition object type, the acquisition data range and other data items.

To facilitate understanding by those skilled in the art, in one embodiment, as shown in FIG. 5, a flow diagram of the operation of a central server of a metadata repair system for a server is provided; firstly, the central server 430 calls a rule to detect the problem of IT metadata, then the central server 430 merges the found data problems, then the central server 430 classifies the data problems according to the responsible persons, then the central server 430 actively initiates the query of the attribute of the problem entity, and the central server 430 judges whether the query is successful; if the query is successful, the central server 430 merges the results and generates a repair suggestion, then the central server 430 generates data notification content according to the template, and finally the central server 430 sends a notification to the user; if the query is unsuccessful, the central server 430 notifies system maintenance personnel.

The metadata repairing system of the server can automatically repair abnormal metadata on an abnormal server; therefore, the operation and maintenance personnel can repair the abnormal metadata on the abnormal server under the condition that the operation and maintenance personnel do not log in the abnormal server system, the abnormal data problem of the abnormal server is solved, and the working efficiency of the operation and maintenance personnel operation and maintenance server is improved.

To facilitate understanding by those skilled in the art, in one embodiment, as shown in FIG. 6, a flow diagram of the operation of a metadata repair system for a server is provided; the acquisition client 410 acquires server data, the acquisition client 410 acquires project data, and then the acquisition client 410 packages the data and sends the data to the area server 420; the acquisition client 410 judges whether the transmission is successful, if the transmission is successful, the area server 420 compresses in batch and uploads the data to the central server 430; the central server 430 receives, analyzes and stores the data; if the sending is unsuccessful, the collecting client 410 records the log and notifies the central server 430.

In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 7. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing metadata repair data of the server. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a method of metadata repair for a server.

Those skilled in the art will appreciate that the architecture shown in fig. 7 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:

step 210, verifying server metadata and determining abnormal metadata;

step 220, generating an abnormal repairing message of the abnormal metadata, and pushing the abnormal repairing message to a target user terminal; the exception repair message comprises repair recommendation data; the repair recommendation data is used for repairing the abnormal metadata;

step 230, when a repair confirmation instruction of the target user terminal for the repair recommended data is received, repairing the abnormal metadata according to the repair recommended data.

In one embodiment, the processor, when executing the computer program, further performs the steps of: determining the type of a data problem according to the abnormal metadata; inquiring repair recommendation data aiming at the data problem type; generating a user determined link, and generating the abnormal repairing message according to the data problem type, the repairing recommendation data and the user determined link; and the user determination link is used for triggering the target user terminal to send the repair confirmation instruction.

In one embodiment, the processor, when executing the computer program, further performs the steps of: acquiring a data verification rule; performing rule verification on the server metadata by adopting the data verification rule to generate a rule verification result; and determining the abnormal metadata according to the rule checking result.

In one embodiment, the processor, when executing the computer program, further performs the steps of: inquiring server information corresponding to the abnormal metadata; determining the information of responsible personnel of the server information; and determining the target user terminal according to the responsible personnel information.

In one embodiment, the processor, when executing the computer program, further performs the steps of: decrypting the repair recommendation data to obtain a decrypted repair parameter; validity check is carried out on the decryption repair parameters; and if the verification is passed, replacing the abnormal parameters in the abnormal metadata by using the decryption repair parameters.

In one embodiment, the processor, when executing the computer program, further performs the steps of: judging whether the step of inquiring the repair recommendation data aiming at the data problem type is successfully executed or not; if not, generating a query failure alarm and sending the query failure alarm to the target user terminal; and the query failure alarm is used for reminding operation and maintenance personnel of repairing the failure of the recommended data query.

In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:

step 210, verifying server metadata and determining abnormal metadata;

In one embodiment, the computer program when executed by the processor further performs the steps of: determining the type of a data problem according to the abnormal metadata; inquiring repair recommendation data aiming at the data problem type; generating a user determined link, and generating the abnormal repairing message according to the data problem type, the repairing recommendation data and the user determined link; and the user determination link is used for triggering the target user terminal to send the repair confirmation instruction.

In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring a data verification rule; performing rule verification on the server metadata by adopting the data verification rule to generate a rule verification result; and determining the abnormal metadata according to the rule checking result.

In one embodiment, the computer program when executed by the processor further performs the steps of: inquiring server information corresponding to the abnormal metadata; determining the information of responsible personnel of the server information; and determining the target user terminal according to the responsible personnel information.

In one embodiment, the computer program when executed by the processor further performs the steps of: decrypting the repair recommendation data to obtain a decrypted repair parameter; validity check is carried out on the decryption repair parameters; and if the verification is passed, replacing the abnormal parameters in the abnormal metadata by using the decryption repair parameters.

In one embodiment, the computer program when executed by the processor further performs the steps of: judging whether the step of inquiring the repair recommendation data aiming at the data problem type is successfully executed or not; if not, generating a query failure alarm and sending the query failure alarm to the target user terminal; and the query failure alarm is used for reminding operation and maintenance personnel of repairing the failure of the recommended data query.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.

Claims

1. A method for metadata repair of a server, the method comprising:

verifying the server metadata and determining abnormal metadata; the method comprises the steps that server metadata on each server are acquired and packaged through acquisition clients installed on a plurality of servers according to preset configuration information; the server metadata comprises at least one of server attribute data, project composition data of program projects and project calling data among the program projects;

2. The method of claim 1, wherein generating the fault repair message for the anomaly metadata comprises:

determining the type of a data problem according to the abnormal metadata;

inquiring repair recommendation data aiming at the data problem type;

3. The method of claim 1, wherein the verifying the server metadata, determining anomalous metadata, comprises:

acquiring a data verification rule;

and determining the abnormal metadata according to the rule checking result.

4. The method according to claim 1, wherein before pushing the exception repair message to the target ue, further comprising:

inquiring server information corresponding to the abnormal metadata;

determining the information of responsible personnel of the server information;

5. The method of claim 1, wherein repairing the abnormal metadata according to the repair recommendation data comprises:

validity check is carried out on the decryption repair parameters;

6. An apparatus for metadata repair of a server, the apparatus comprising:

the verification module is used for verifying the server metadata and determining abnormal metadata; the method comprises the steps that server metadata on each server are acquired and packaged through acquisition clients installed on a plurality of servers according to preset configuration information; the server metadata comprises at least one of server attribute data, project composition data of program projects and project calling data among the program projects;

7. A system for server failover, the system comprising: collecting a client, a regional server and a central server;

the collection client is used for collecting server metadata of a plurality of servers; uploading the server metadata to the regional server;

the regional server is used for receiving the server metadata of the acquisition client; compressing the server metadata in batches to obtain a compressed data packet; sending the compressed data packet to the central server;

8. The system of claim 7, wherein the central server is further configured to query server information corresponding to the abnormal metadata; determining the information of responsible personnel of the server information; acquiring account data of the responsible personnel information, and taking the account data as a parameter encryption key; acquiring metadata repair parameters, and encrypting the metadata repair parameters by using the parameter encryption key to obtain the repair recommendation data; the abnormal repairing system is also used for generating a user determined link and a data problem type and generating the abnormal repairing message according to the data problem type, the repairing recommendation data and the user determined link; and the user determination link is used for triggering the target user terminal to send the repair confirmation instruction.

9. A computer device comprising a memory and a processor, the memory storing a computer program, wherein the processor implements the steps of the method of any one of claims 1 to 5 when executing the computer program.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 5.