CN107957928A - A kind of software synchronization operation detection and analysis and troubleshooting methodology - Google Patents
A kind of software synchronization operation detection and analysis and troubleshooting methodology Download PDFInfo
- Publication number
- CN107957928A CN107957928A CN201711138293.XA CN201711138293A CN107957928A CN 107957928 A CN107957928 A CN 107957928A CN 201711138293 A CN201711138293 A CN 201711138293A CN 107957928 A CN107957928 A CN 107957928A
- Authority
- CN
- China
- Prior art keywords
- software
- troubleshooting
- fault
- detected
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000013024 troubleshooting Methods 0.000 title claims abstract description 98
- 238000000034 method Methods 0.000 title claims abstract description 48
- 238000001514 detection method Methods 0.000 title claims abstract description 25
- 238000004458 analytical method Methods 0.000 title claims abstract description 24
- 230000007717 exclusion Effects 0.000 claims description 13
- 230000007547 defect Effects 0.000 claims description 12
- 238000004088 simulation Methods 0.000 claims description 12
- 230000004888 barrier function Effects 0.000 claims description 11
- 238000004891 communication Methods 0.000 claims description 9
- 230000007257 malfunction Effects 0.000 claims description 3
- 238000004321 preservation Methods 0.000 claims description 3
- 238000007689 inspection Methods 0.000 claims 1
- 238000007726 management method Methods 0.000 abstract 1
- 230000006855 networking Effects 0.000 abstract 1
- 230000008569 process Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000009825 accumulation Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1446—Point-in-time backing up or restoration of persistent data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/32—Monitoring with visual or acoustical indication of the functioning of the machine
- G06F11/324—Display of status information
- G06F11/327—Alarm or error message display
Abstract
The present invention relates to a kind of software synchronization operation detection and analysis and troubleshooting methodology, including compilation task distribution, collect personnel assignment, four steps such as hardware device networking and software compilation.The method of the present invention is simple, operation and implementation are easy, on the one hand the work efficiency of software compilation work and the quality of management coordination work are effectively raised, on the other hand the reasonability and reliability of software compilation operation framework layout are effectively raised, the labor intensity of software compilation work and the requirement to computer hardware equipment are separately effectively reduced at the same time, so as to achieve the purpose that to reduce software compilation work operations cost and improve work quality.
Description
Technical field
The present invention relates to a kind of software synchronization operation detection and analysis and troubleshooting methodology, belongs to computer software technology neck
Domain.
Background technology
The various kinds of equipment based on computer software operation all kinds of at present are in the fields such as routine office work, automated control
It is widely used, in real work, in order to improve equipment reliability of operation and stability, and meets equipment to not
With the needs of working status operation, it is required to carry out the software run in each equipment failure progress active retrieval, repairs and work as
Software fault is passively repaired when software breaks down, but is currently carrying out software systems fault detection analysis and failure row
During except operation, toward in the past being established the link by dedicated fault detect platform and running software equipment to be detected, then to be checked
The operation troubles for surveying software is detected, and carries out corresponding troubleshooting according to the result of detection, although this mode can be with
Meet the needs of actual use to a certain degree, but found in actual work, currently when carrying out troubleshooting, on the one hand led
Cause Current software operational outfit normally can not be operated and run, seriously affect the reliability that equipment uses, the opposing party
In troubleshooting operation, the information such as retrieval, exclusion program that also break down in various degree can not in time be retrieved, updated in face
And compile and edit so that cause currently carry out software fault analysis and exclude operation when flexibility and reliability it is relatively poor,
It cannot effectively meet the needs of actual use, therefore be directed to this problem, there is an urgent need to develop a kind of brand-new software fault
Method for removing, to meet the needs of actual use.
The content of the invention
The object of the invention, which is that, overcomes above-mentioned deficiency, there is provided a kind of software synchronization operation detection and analysis and troubleshooting side
Method.
To achieve the above object, the present invention is to be achieved through the following technical solutions：
A kind of software synchronization operation detection and analysis and troubleshooting methodology, comprise the following steps：
The first step, software information collection, builds troubleshooting server, then by troubleshooting service first in communication network
Device establishes data link by communication network and each operation by the terminal device of server to be detected, then by troubleshooting service
Device collects each current runs software information of terminal device；
Second step, software backup, after completing the first step, replicates pending fault detecting software by troubleshooting server
Backup to barrier to exclude in server and preserve, while software during to the current start time for carrying out software backup, backup is at end
The running environment information of end equipment is together backed up, and is established software to be detected according to the software of each backup and identified root；
3rd step, fault case are collected, after completing second step operation, according to the software version information of first step collection, software school
Value information and software upgrading policy information are tested, collecting software to be detected by communication network by troubleshooting server identifies root mesh
Each the software most common failure to be detected and troubleshooting methods example enumerated in record, know then in conjunction with the software to be detected of second step
Other root directory contents establish software fault identification information root to be detected, the software most common failure to be detected that then will be collected
And troubleshooting methods example is saved under software fault identification information root to be detected, is finally set in troubleshooting server
Put at least one software fault detection software systems；
4th step, collect jump routine, after completing the 3rd step operation, is established in troubleshooting server and at least one redirects end
Program is held, software to be detected is then identified into root, software fault identification information root mesh to be detected by redirecting terminal program
Data link is established between record and software fault detection software systems；
5th step, fault detect exclude, and after completing the 4th step operation, exclude server by barrier first and treat inspection software identification root
The software to be detected that preservation is backed up under catalogue carries out simulation run, during simulation run, passes through software fault detection software
System is treated inspection software operating status and is monitored, and after running software failure is detected, on the one hand treats inspection software
Trouble point recorded, and establish software fault catalogue to be detected, and the malfunction routine segment information for treating inspection software carries out
Backup be put under inspection software defect list, be on the other hand directed to current failure by redirecting terminal program, first with it is to be detected
Most common failure information under software fault identification information root is compared identification, and compare complete current failure with it is to be checked
When surveying fault case matching under software fault identification information root, which is backuped into inspection software failure mesh
Under record, if fault case is without match information under comparison completion current failure and software fault identification information root to be detected,
Failure is then marked under software fault catalogue to be detected and does not exclude information, and it is defeated to feed this information to barrier exclusion server progress
Go out；
6th step, troubleshooting, after completing the 5th step operation, when faulty exclusion program under inspection software defect list, then
Inspection software is directly treated by the troubleshooting methods to be repaired, if fault-free exclusion program under inspection software defect list
When, alarm is sent by troubleshooting server, and collected corresponding troubleshooting methods and to be saved in detection soft by staff
After under part defect list, software fault exclusion is being carried out, and after completing software fault and excluding, treat inspection software and be carried out continuously
At least 2 simulation runs, and in simulation run after fault-free, the software systems after pushing troubleshooting to terminal device, and
The software systems after troubleshooting are downloaded from troubleshooting server by terminal device, and by the software systems after troubleshooting
Covering substitutes priginal soft system, realizes that software fault excludes.
Further, the runs software information in the first step includes software version information, software check value information
And software upgrading policy information.
Further, troubleshooting server is at least one in the first step, and troubleshooting server separately set to
A few operation control terminal.
Further, the operation control terminal includes appointing in industrial computer, PC computers, intelligent movable communicating terminal
Meaning is one or more of to be shared.
Further, in the second step, when being backed up to pending fault detecting software, each is pending
Fault detecting software is backed up twice, and one of backup file is used for troubleshooting, another backup file is used for eventually
End equipment device software system is recovered.
Further, in the 4th step, the software most common failure to be detected collected and troubleshooting side
In case, when a failure possesses multiple troubleshooting methods, each troubleshooting methods are mutually juxtaposed, and according to troubleshooting side
Case, which corresponds to program and arrives from childhood, to be arranged greatly, and establishes software fault identification information level-one specific item to be detected after completing to arrange
Record.
Further, in the 5th step when to redirect terminal program be two or more, respectively redirect terminal journey
It is parallel with one another between sequence, and data are separate between respectively redirecting terminal program, and establish unified redirect respectively to redirect terminal program
Routine call catalogue.
Further, in the 6th step, after completing to terminal device software troubleshooting, and tire out in terminal device
After when software program 12-72 is small after plot operation renewal, the software systems after troubleshooting are carried out in troubleshooting server
Backup, and cover the original pending fault detecting software backed up in second step.
The method of the present invention is simple, and operation and implementation are easy, is on the one hand carrying out software fault detection, analysis and is excluding operation
During do not interfere with equipment normal operation, so as to effectively raise software fault detection, analysis and exclude activity
Convenience, flexibility and reliability, on the other hand in carrying out fault detect, analysis and excluding operation process, can be directed to current
Fault message obtain total failure be directed to analytical plan and optimal troubleshooting methods, so as to effectively raise software system
System fault detect and flexibility and the reliability for excluding operation.
Brief description of the drawings
Fig. 1 is assembly process flow diagram of the present invention；
Fig. 2 is this hair assemble system structure diagram.
Embodiment
As illustrated in fig. 1 and 2, a kind of software synchronization operation detection and analysis and troubleshooting methodology, comprise the following steps：
The first step, software information collection, builds troubleshooting server, then by troubleshooting service first in communication network
Device establishes data link by communication network and each operation by the terminal device of server to be detected, then by troubleshooting service
Device collects each current runs software information of terminal device, and wherein runs software information includes software version information, software check value
Information and software upgrading policy information, and troubleshooting server sets at least one operation control terminal；
Second step, software backup, after completing the first step, replicates pending fault detecting software by troubleshooting server
Backup to barrier to exclude in server and preserve, while software during to the current start time for carrying out software backup, backup is at end
The running environment information of end equipment is together backed up, and is established software to be detected according to the software of each backup and identified root,
When wherein being backed up to pending fault detecting software, each pending fault detecting software is backed up twice, its
In a backup file be used for troubleshooting, another backup file for terminal device device software system recover；
3rd step, fault case are collected, after completing second step operation, according to the software version information of first step collection, software school
Value information and software upgrading policy information are tested, collecting software to be detected by communication network by troubleshooting server identifies root mesh
Each the software most common failure to be detected and troubleshooting methods example enumerated in record, know then in conjunction with the software to be detected of second step
Other root directory contents establish software fault identification information root to be detected, the software most common failure to be detected that then will be collected
And troubleshooting methods example is saved under software fault identification information root to be detected, is finally set in troubleshooting server
At least one software fault detection software systems are put, wherein the software most common failure to be detected and troubleshooting methods collected
In, when a failure possesses multiple troubleshooting methods, each troubleshooting methods are mutually juxtaposed, and according to troubleshooting methods
Corresponding program arrives from childhood to be arranged greatly, and establishes software fault identification information first level subdirectory to be detected after completing to arrange；
4th step, collect jump routine, after completing the 3rd step operation, is established in troubleshooting server and at least one redirects end
Program is held, software to be detected is then identified into root, software fault identification information root mesh to be detected by redirecting terminal program
Data link is established between record and software fault detection software systems；
5th step, fault detect exclude, and after completing the 4th step operation, exclude server by barrier first and treat inspection software identification root
The software to be detected that preservation is backed up under catalogue carries out simulation run, during simulation run, passes through software fault detection software
System is treated inspection software operating status and is monitored, and after running software failure is detected, on the one hand treats inspection software
Trouble point recorded, and establish software fault catalogue to be detected, and the malfunction routine segment information for treating inspection software carries out
Backup be put under inspection software defect list, be on the other hand directed to current failure by redirecting terminal program, first with it is to be detected
Most common failure information under software fault identification information root is compared identification, and compare complete current failure with it is to be checked
When surveying fault case matching under software fault identification information root, which is backuped into inspection software failure mesh
Under record, if fault case is without match information under comparison completion current failure and software fault identification information root to be detected,
Failure is then marked under software fault catalogue to be detected and does not exclude information, and it is defeated to feed this information to barrier exclusion server progress
Go out, wherein when to redirect terminal program be two or more, respectively redirect parallel with one another between terminal program, and respectively redirect terminal journey
Data are separate between sequence, and establish unified jump routine calling catalogue respectively to redirect terminal program；
6th step, troubleshooting, after completing the 5th step operation, when faulty exclusion program under inspection software defect list, then
Inspection software is directly treated by the troubleshooting methods to be repaired, if fault-free exclusion program under inspection software defect list
When, alarm is sent by troubleshooting server, and collected corresponding troubleshooting methods and to be saved in detection soft by staff
After under part defect list, software fault exclusion is being carried out, and after completing software fault and excluding, treat inspection software and be carried out continuously
2 simulation runs, and in simulation run after fault-free, the software systems after pushing troubleshooting to terminal device, and by end
End equipment downloads the software systems after troubleshooting from troubleshooting server, and is covered by the software systems after troubleshooting
Priginal soft system is substituted, realizes that software fault excludes, after completing to terminal device software troubleshooting, and in terminal device
Accumulation operation renewal after software program 12-72 it is small when after, to the software systems after troubleshooting in troubleshooting server into
Row backup, and cover the original pending fault detecting software backed up in second step.
In the present embodiment, the operation control terminal is included in industrial computer, PC computers, intelligent movable communicating terminal
Any one or a few is shared.
The method of the present invention is simple, and operation and implementation are easy, is on the one hand carrying out software fault detection, analysis and is excluding operation process
In do not interfere with equipment normal operation so that effectively raise software fault detection, analysis and exclude activity it is convenient
Property, flexibility and reliability, on the other hand in carrying out fault detect, analysis and excluding operation process, current event can be directed to
Barrier information acquisition total failure is directed to analytical plan and optimal troubleshooting methods, so as to effectively raise software systems event
Barrier detection and flexibility and the reliability for excluding operation.
The basic principles, main features and the advantages of the invention have been shown and described above.The technology of the industry
Personnel are it should be appreciated that the present invention is not limited to the above embodiments, and the above embodiments and description only describe this
The principle of invention, without departing from the spirit and scope of the present invention, various changes and modifications of the present invention are possible, these changes
Change and improvement all fall within the protetion scope of the claimed invention.The claimed scope of the invention by appended claims and its
Equivalent thereof.
Claims (8)
1. a kind of software synchronization operation detection and analysis and troubleshooting methodology, it is characterised in that：The software synchronization operation inspection
Survey analysis and troubleshooting methodology comprises the following steps：
The first step, software information collection, builds troubleshooting server, then by troubleshooting service first in communication network
Device establishes data link by communication network and each operation by the terminal device of server to be detected, then by troubleshooting service
Device collects each current runs software information of terminal device；
Second step, software backup, after completing the first step, replicates pending fault detecting software by troubleshooting server
Backup to barrier to exclude in server and preserve, while software during to the current start time for carrying out software backup, backup is at end
The running environment information of end equipment is together backed up, and is established software to be detected according to the software of each backup and identified root；
3rd step, fault case are collected, after completing second step operation, according to the software version information of first step collection, software school
Value information and software upgrading policy information are tested, collecting software to be detected by communication network by troubleshooting server identifies root mesh
Each the software most common failure to be detected and troubleshooting methods example enumerated in record, know then in conjunction with the software to be detected of second step
Other root directory contents establish software fault identification information root to be detected, the software most common failure to be detected that then will be collected
And troubleshooting methods example is saved under software fault identification information root to be detected, is finally set in troubleshooting server
Put at least one software fault detection software systems；
4th step, collect jump routine, after completing the 3rd step operation, is established in troubleshooting server and at least one redirects end
Program is held, software to be detected is then identified into root, software fault identification information root mesh to be detected by redirecting terminal program
Data link is established between record and software fault detection software systems；
5th step, fault detect exclude, and after completing the 4th step operation, exclude server by barrier first and treat inspection software identification root
The software to be detected that preservation is backed up under catalogue carries out simulation run, during simulation run, passes through software fault detection software
System is treated inspection software operating status and is monitored, and after running software failure is detected, on the one hand treats inspection software
Trouble point recorded, and establish software fault catalogue to be detected, and the malfunction routine segment information for treating inspection software carries out
Backup be put under inspection software defect list, be on the other hand directed to current failure by redirecting terminal program, first with it is to be detected
Most common failure information under software fault identification information root is compared identification, and compare complete current failure with it is to be checked
When surveying fault case matching under software fault identification information root, which is backuped into inspection software failure mesh
Under record, if fault case is without match information under comparison completion current failure and software fault identification information root to be detected,
Failure is then marked under software fault catalogue to be detected and does not exclude information, and it is defeated to feed this information to barrier exclusion server progress
Go out；
6th step, troubleshooting, after completing the 5th step operation, when faulty exclusion program under inspection software defect list, then
Inspection software is directly treated by the troubleshooting methods to be repaired, if fault-free exclusion program under inspection software defect list
When, alarm is sent by troubleshooting server, and collected corresponding troubleshooting methods and to be saved in detection soft by staff
After under part defect list, software fault exclusion is being carried out, and after completing software fault and excluding, treat inspection software and be carried out continuously
At least 2 simulation runs, and in simulation run after fault-free, the software systems after pushing troubleshooting to terminal device, and
The software systems after troubleshooting are downloaded from troubleshooting server by terminal device, and by the software systems after troubleshooting
Covering substitutes priginal soft system, realizes that software fault excludes.
2. a kind of software synchronization operation detection and analysis stated according to claim 1 and troubleshooting methodology, it is characterised in that：It is described
The first step in runs software information include software version information, software check value information and software upgrading policy information.
3. a kind of software synchronization operation detection and analysis stated according to claim 1 and troubleshooting methodology, it is characterised in that：It is described
The first step in troubleshooting server it is at least one, and troubleshooting server separately sets at least one operation control terminal.
4. a kind of software synchronization operation detection and analysis stated according to claim 3 and troubleshooting methodology, it is characterised in that：It is described
Operation control terminal include industrial computer, PC computers, any one or a few in intelligent movable communicating terminal and share.
5. a kind of software synchronization operation detection and analysis stated according to claim 1 and troubleshooting methodology, it is characterised in that：It is described
Second step in, when being backed up to pending fault detecting software, each pending fault detecting software carries out two
Secondary backup, one of backup file are used for troubleshooting, and it is extensive that another backup file is used for terminal device device software system
It is multiple.
6. a kind of software synchronization operation detection and analysis stated according to claim 1 and troubleshooting methodology, it is characterised in that：It is described
The 4th step in, in the software most common failure to be detected collected and troubleshooting methods, when a failure possess it is more
During a troubleshooting methods, each troubleshooting methods are mutually juxtaposed, and according to troubleshooting methods correspond to program arrive from childhood greatly into
Row arrangement, and establish software fault identification information first level subdirectory to be detected after completing to arrange.
7. a kind of software synchronization operation detection and analysis stated according to claim 1 and troubleshooting methodology, it is characterised in that：It is described
The 5th step in when to redirect terminal program be two or more, respectively redirect parallel with one another between terminal program, and respectively redirect
Data are separate between terminal program, and establish unified jump routine calling catalogue respectively to redirect terminal program.
8. a kind of software synchronization operation detection and analysis stated according to claim 1 and troubleshooting methodology, it is characterised in that：It is described
The 6th step in, complete to terminal device software troubleshooting after, and terminal device accumulate operation renewal after software program
12-72 it is small when after, the software systems after troubleshooting are backed up in troubleshooting server, and covers in second step
The original pending fault detecting software of backup.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711138293.XA CN107957928B (en) | 2017-11-16 | 2017-11-16 | A kind of operation of software synchronization tests and analyzes and troubleshooting methodology |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711138293.XA CN107957928B (en) | 2017-11-16 | 2017-11-16 | A kind of operation of software synchronization tests and analyzes and troubleshooting methodology |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107957928A true CN107957928A (en) | 2018-04-24 |
| CN107957928B CN107957928B (en) | 2019-06-07 |
Family
ID=61963525
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711138293.XA Active CN107957928B (en) | 2017-11-16 | 2017-11-16 | A kind of operation of software synchronization tests and analyzes and troubleshooting methodology |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107957928B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111813427A (en) * | 2019-04-12 | 2020-10-23 | 杭州海康威视数字技术股份有限公司 | Equipment repairing method and device, electronic equipment and storage medium |
| CN114756429A (en) * | 2022-04-13 | 2022-07-15 | 嘉兴职业技术学院 | Software operation fault detection method |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101001183A (en) * | 2007-01-10 | 2007-07-18 | 网之易信息技术（北京）有限公司 | Test method and system for network application software |
| CN101944778A (en) * | 2010-10-09 | 2011-01-12 | 华北电网有限公司 | Isolation debugging system and debugging method of transformer substation monitoring system |
| CN102521116A (en) * | 2011-12-29 | 2012-06-27 | 苏州佰思迈信息咨询有限公司 | Fault monitoring software |
| CN104503920A (en) * | 2015-01-23 | 2015-04-08 | 桂林电子科技大学 | Software system fault detection method based on dynamic description logic and case-based reasoning |
| US20160306721A1 (en) * | 2005-02-17 | 2016-10-20 | International Business Machines Corporation | Creation of Highly Available Pseudo-Clone Standby Servers for Rapid Failover Provisioning |
| CN106844194A (en) * | 2016-12-21 | 2017-06-13 | 北京航空航天大学 | A kind of construction method of multi-level software fault diagnosis expert system |
-
2017
- 2017-11-16 CN CN201711138293.XA patent/CN107957928B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160306721A1 (en) * | 2005-02-17 | 2016-10-20 | International Business Machines Corporation | Creation of Highly Available Pseudo-Clone Standby Servers for Rapid Failover Provisioning |
| CN101001183A (en) * | 2007-01-10 | 2007-07-18 | 网之易信息技术（北京）有限公司 | Test method and system for network application software |
| CN101944778A (en) * | 2010-10-09 | 2011-01-12 | 华北电网有限公司 | Isolation debugging system and debugging method of transformer substation monitoring system |
| CN102521116A (en) * | 2011-12-29 | 2012-06-27 | 苏州佰思迈信息咨询有限公司 | Fault monitoring software |
| CN104503920A (en) * | 2015-01-23 | 2015-04-08 | 桂林电子科技大学 | Software system fault detection method based on dynamic description logic and case-based reasoning |
| CN106844194A (en) * | 2016-12-21 | 2017-06-13 | 北京航空航天大学 | A kind of construction method of multi-level software fault diagnosis expert system |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111813427A (en) * | 2019-04-12 | 2020-10-23 | 杭州海康威视数字技术股份有限公司 | Equipment repairing method and device, electronic equipment and storage medium |
| CN114756429A (en) * | 2022-04-13 | 2022-07-15 | 嘉兴职业技术学院 | Software operation fault detection method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107957928B (en) | 2019-06-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR101856543B1 (en) | Failure prediction system based on artificial intelligence | |
| CN110717665B (en) | System and method for fault identification and trend analysis based on scheduling control system | |
| CN108199922B (en) | System and method for diagnosing and repairing network equipment and server faults | |
| CN113112086A (en) | Intelligent production system based on edge calculation and identification analysis | |
| CN105337765A (en) | Distributed hadoop cluster fault automatic diagnosis and restoration system | |
| CN110650052B (en) | Customer reason fault identification processing method and system based on intelligent algorithm | |
| US10444746B2 (en) | Method for managing subsystems of a process plant using a distributed control system | |
| CN110990391A (en) | Integration method and system of multi-source heterogeneous data, computer equipment and storage medium | |
| CN103425116B (en) | A kind of electric power scheduling automatization system troubleshooting methodology | |
| CN105306272A (en) | Method and system for collecting fault scene information of information system | |
| CN105095052A (en) | Fault detection method and fault detection device in SOA (Service-Oriented Architecture) environment | |
| CN102479113A (en) | Abnormal self-adapting processing method and system | |
| CN211321337U (en) | Monitoring system for communication system | |
| CN103023028A (en) | Rapid grid failure positioning method based on dependency graph of entities | |
| CN109062723A (en) | The treating method and apparatus of server failure | |
| KR101171274B1 (en) | System and method with erp system to manage planet risk during outage | |
| KR20140036375A (en) | Intelligent failure asset management system for railway car | |
| CN107957928A (en) | A kind of software synchronization operation detection and analysis and troubleshooting methodology | |
| CN104794771B (en) | One kind patrols inspection automatic planning and a device | |
| CN112733147A (en) | Equipment safety management method and system | |
| CN106022582A (en) | Work order control system service automatic analyzing and processing method and system | |
| CN111130934A (en) | Monitoring method, device and system of communication system | |
| CN212990152U (en) | Agricultural sewage management system | |
| CN116345699B (en) | Internet-based power transmission circuit information acquisition system and acquisition method | |
| CN107992408B (en) | A kind of software probe method of software probe |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20201222 Address after: 510620 room 524, No.1 Mingxu street, Tianhe District, Guangzhou City, Guangdong Province Patentee after: KINTH INFORMATION TECHNOLOGY SERVICE Co.,Ltd. Address before: 211100 two, B unit 300, Zhihui Road, Kirin science and Technology Innovation Park, Jiangning District, Nanjing, Jiangsu. Patentee before: NANJING XUANSHI QIYUAN SOFTWARE TECHNOLOGY Co.,Ltd. |