Source: https://patents.google.com/patent/JP5140633B2/en
Timestamp: 2019-12-14 09:36:31
Document Index: 552409413

Matched Legal Cases: ['art 118', 'art 118', 'art 112', 'art 113', 'art 114', 'art 115', 'art 116', 'art 117', 'art 118', 'art 121']

JP5140633B2 - Method for analyzing failure occurring in virtual environment, management server, and program - Google Patents
Method for analyzing failure occurring in virtual environment, management server, and program Download PDF
JP5140633B2
JP5140633B2 JP2009135441A JP2009135441A JP5140633B2 JP 5140633 B2 JP5140633 B2 JP 5140633B2 JP 2009135441 A JP2009135441 A JP 2009135441A JP 2009135441 A JP2009135441 A JP 2009135441A JP 5140633 B2 JP5140633 B2 JP 5140633B2
JP2009135441A
JP2010086516A (en
安彰 齋藤
2008-09-04 Priority to JP2008227401 priority Critical
2008-09-04 Priority to JP2008227401 priority
2009-06-04 Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
2009-06-04 Priority to JP2009135441A priority patent/JP5140633B2/en
2010-04-15 Publication of JP2010086516A publication Critical patent/JP2010086516A/en
2013-02-06 Publication of JP5140633B2 publication Critical patent/JP5140633B2/en
The present invention relates to a method for analyzing a failure that occurs in a virtual environment in which a virtual server is realized by a virtualization mechanism that operates on a physical server, a management server, and a program. It relates to the technology to be performed quickly.
In recent years, so-called virtualization technology has attracted attention for the purpose of effective utilization of hardware resources, load distribution, ensuring availability, and the like accompanying improvement in performance of an information processing system. When dealing with a failure in an information processing system, a quick and reliable response is required in order to prevent influence on business operations. However, in an environment to which the above-described virtualization technology is applied, it is not always easy to specify the location where a failure occurs.
For example, when a failure is reported from a business process operating on a virtual server, the business process, in order to specify whether the cause of the failure is the business process, the virtual server, or the physical server, It is necessary to analyze the log information stored in each of the virtual server and the physical server and specify the failure location based on the analysis result, which requires a great deal of labor.
As a technique for identifying the cause of a failure, for example, in Patent Document 1, in a virtual server environment, when a failure occurs in a virtual server, a system administrator can quickly refer to a log of the virtual server. It describes that every time a virtual server moves to another physical server, its movement history is generated / recorded and managed centrally. In Patent Document 2, in the processing of fault information under the virtual computer system, in order to realize early confirmation of abnormal peripheral devices and early countermeasures, if a fault occurs in a peripheral device during operation of the virtual computer system, the guest Logging information detected by the operating system under the virtual machine and logging information detected by the host system are analyzed / classified by the error reporting system under each guest virtual machine and automatically notified to the maintenance center with the actual machine number. Is described.
JP 2007-323244 A Japanese Patent Laid-Open No. 4-257035
The technologies described in Patent Document 1 and Patent Document 2 are based on the premise that log information is analyzed manually by maintenance personnel, etc., and labor required for analysis when a failure occurs in a virtualized environment Not necessarily alleviated. That is, depending on these technologies, the cause of the failure and the countermeasures cannot always be easily and quickly performed.
The present invention has been made in view of such a background, and provides a failure analysis method and a management server in a virtual environment that enable easy and quick identification of the cause of the failure in the virtual environment. For the purpose.
One aspect of the present invention for achieving the above object is a method for analyzing a failure occurring in a virtual environment in which a virtual server is realized by a virtualization mechanism that operates on the physical server, and is capable of communicating with the physical server. The management server connected to the second storage stores a mapping table in which correspondence between the virtual server and the physical server on which the virtual server is realized is stored, and is a history of events that have occurred in the physical server. and event history, when the the first event history is an event of history occurring in the virtual server accumulates storage, receiving the events related to failure of the business processes running in the virtual server, the first event of history, and event history for the virtual server that issued the event, of the second event history, the mapping table It is obtained from the event history of the physical server that implements the virtual server that issued the event retrieved from the event history that the storage memory, identify the cause of a failure based on the search result A virtual server event analysis policy table in which a first search condition used for searching the first event history and a first failure location are associated with each other, and a second search used for searching the second event history A physical server event analysis policy table that associates a condition with a second failure location is stored, and the first search condition registered in the virtual server event analysis policy table is stored from the stored event history. The first event history corresponding to the above is searched, and as a result, the corresponding first event history cannot be searched. The cause of the failure is identified as the business process, and the first search condition corresponding to the first search condition registered in the virtual server event analysis policy table is determined from the stored event history. The first event history is searched, and the second event history corresponding to the second search condition registered in the physical server event analysis policy table is searched. As a result, the corresponding first event is searched. If the history could be searched but the second event history could not be searched, the cause of the failure is identified in the virtual server, and from the stored event history And searching the first event history corresponding to the first search condition registered in the virtual server event analysis policy table. The second event history corresponding to the second search condition registered in the physical server event analysis policy table is searched, and as a result, the corresponding first event history and the second event are searched. A history can be searched, and the first failure location associated with the first search condition used for searching the searched first event history and the second failure searched If the second failure location associated with the second search condition used for the event history search does not match, the cause of the failure is identified in the virtual server and matches Specifies that the cause of the failure is in the physical server .
In addition, the problems disclosed by the present application and the means for solving the problems will be clarified by the column of the best mode for carrying out the invention and the drawings.
According to the present invention, it is possible to easily and quickly identify the cause of a failure in a virtual environment.
1 is a diagram illustrating a hardware environment used for realizing a virtualization system 1. FIG. 2 is an example of a computer used as a management server 10 or a physical server 20. 4 is a diagram illustrating functions of the management server 10 and data managed in the management server 10. FIG. 2 is a diagram illustrating functions of a physical server 20 and data managed in the physical server 20. FIG. 4 is an example of an event history table 121. It is an example of the working server mapping table 122. 4 is an example of a virtual server event analysis policy table 124. 4 is an example of a physical server event analysis policy table 125. 4 is an example of an analysis history table 123. 4 is an example of a handling table 126. It is an example of the application management table 127. FIG. It is an example of the SLA definition table 128. It is an example of a resource management table 129. 4 is an example of a dependency management table 130. 4 is an example of a server management table 131. 4 is an example of a patch management table 132; 5 is a flowchart for explaining processing performed by a failure monitoring unit 110. It is a flowchart explaining the detail of an analysis process (S413). It is a figure which shows the main functions with which the countermeasure execution part 118 is provided. It is a flowchart explaining the whole flow of failure handling processing S415. It is a flowchart explaining virtual server movement process S621. It is a flowchart explaining rollback processing S643. It is a flowchart explaining application movement process S644.
FIG. 1A shows a hardware environment used for realizing a virtualization system described as an embodiment. As shown in the figure, this hardware environment includes a management server 10, one or more physical servers 20 that are communicably connected to the management server 10 via the communication network 5, and are monitored by the management server 10. The storage device 30 is accessible by the server 20.
The communication network 5 that connects the management server 10 and the physical server 20 is, for example, a LAN (Local Area Network). The physical server 20 and the storage device 30 are communicably connected via, for example, a LAN or a SAN (Storage Area Network). The storage device 30 is, for example, a disk array device or NAS (Network Attached Storage).
The management server 10 or the physical server 20 is a computer (information processing apparatus) such as a personal computer, a blade attached to a blade server, a workstation, or a mainframe. FIG. 1B shows an example of a computer used as the management server 10 or the physical server 20. A computer 100 shown in FIG. 1 includes a central processing unit 101 (for example, CPU (Central Processing Unit) or MPU (Micro Processing Unit)), a main storage device 102 (for example, RAM (Random Access Memory) or ROM (Read Only Memory)), Auxiliary storage device 103 (for example, hard disk), input device 104 (for example, keyboard or mouse) that accepts user operation input, output device 105 (for example, liquid crystal monitor), and communication with other devices via the communication network 5 are realized. Communication interface 106 (for example, NIC (Network Interface Card)).
FIG. 2A shows functions realized in the management server 10 and data managed by the management server 10. Each function in the figure is executed by the central processing unit 101 of the management server 10 by reading and executing a program stored in the main storage device 102 or the auxiliary storage device 103, or by the hardware of the management server 10 itself. Realized by function.
As shown in the figure, the management server 10 executes a program for realizing a function (hereinafter referred to as a failure monitoring unit 110) for identifying the cause of a failure that has occurred in the physical server 20. The failure monitoring unit 110 includes an event history management unit 111, a mapping table management unit 112, a user interface unit 113, a failure analysis unit 114, a policy table management unit 115, an analysis history table management unit 116, a handling table management unit 117, and handling execution. Part 118 is provided. The management server 10 also includes an event history table 121, an active server mapping table 122, an analysis history table 123, a virtual server event analysis policy table 124, a physical server event analysis policy table 125, a handling table 126, an application management table 127, and an SLA definition table. 128, a resource management table 129, a dependency management table 130, a server management table 131, and a patch management table 132 are managed.
Of the functions shown in FIG. 2A, the event history management unit 111 registers an event history ( second event history) related to the physical server 20 based on information transmitted from the physical event notification unit 213 in the event history table 121. To do. Further, the event history management unit 111 registers an event history ( first event history) related to the virtual server 212 based on the information transmitted from the virtual event notification unit 2123 in the event history table 121.
FIG. 3A shows an example of the event history table 121. Each record in the figure is an event history for one event that occurred in the physical server 20 or the virtual server 212. Each event history includes a server name 311 in which information specifying a server (physical server 20 or virtual server 212) in which an event has occurred is set, an occurrence date and time 312 in which an event occurrence date and time is set, and a process in which the event has occurred. Information indicating the process name 313 in which the information to be identified is set, the message 314 in which an error message is set, and the type of event that has occurred (error, warning, general information) is set. Each event type 315.
In the figure, the event history in which the name beginning with “p” is set in the server name 311 is the event history sent from the physical event notification unit 213 of the physical server 20. An event history in which a name beginning with “v” is set in the server name 311 is an event history sent from the virtual event notification unit 2123.
As described above, the event history table 121 in FIG. 3A includes both the event history notified from the physical event notification unit 213 and the event history notified from the virtual event notification unit 2123. It may be managed in the table.
The mapping table management unit 112 in FIG. 2A manages the active server mapping table 122. The mapping table management unit 112 acquires information to be registered in the operating server mapping table 122 actively or passively with respect to the virtualization mechanism 211 and reflects the acquired information in the operating server mapping table 122.
An example of the active server mapping table 122 is shown in FIG. 3B. In the active server mapping table 122, a process name 321 in which information for specifying the business process 2122 is set, a virtual server name 322 in which information for specifying the virtual server 212 on which the business process 2122 is executed, and a virtual server 212 are set. Are registered in association with a physical server name 323 in which information for specifying the physical server 20 that realizes the virtual server 212 and a virtual server operation start date and time 324 in which the date and time when the virtual server 212 starts operating are set. The contents of the active server mapping table 122 are updated when the virtual server 212 is moved (described later), for example.
The user interface unit 113 in FIG. 2A accepts an operation input performed on the input device 104 by the user, such as an operation input for instructing activation or termination of the program.
The failure analysis unit 114 in FIG. 2A analyzes the event history registered in the event history table 121 when any failure occurs in the business process 2122, and registers the analysis result in the analysis history table 123.
The policy table management unit 115 in FIG. 2A manages the virtual server event analysis policy table 124 and the physical server event analysis policy table 125. In these tables, search conditions (first search condition and second search condition) used when the failure analysis unit 114 searches the event history table 121 when analyzing a failure are registered.
FIG. 3C shows an example of the virtual server event analysis policy table 124. As shown in the figure, the virtual server event analysis policy table 124 includes a search condition 331 when searching the event history from the event history table 121 and a cause location that is information set according to the search result based on the search condition. One or more records including 332 are registered. Here, the contents of the search condition 331 for the record in the first row in FIG. 10 are as follows. From the event history table 121, a specific server name ($ virtual server $) is set as the virtual server name 311, and “ The event history including the character string “connect error” (meaning a communication error) is searched. The contents of the search condition 331 for the record in the second line are as follows. From the event history table 121, a specific server name ($ virtual server $) is set for the virtual server name 311 and “aa” is set for the process name 313. An event history that is set and includes the character string “error” in the message 314 is searched. The contents of the search condition 331 for the record in the third line are as follows. From the event history table 121, a specific server name ($ virtual server $) is set for the virtual server name 311 and “bb” is set for the process name 313. The event history that is set and includes the character string “fault” in the message 314 is searched. The contents of the search condition 331 for the record in the fourth line are as follows: from the event history table 121, a specific server name ($ virtual server $) is set for the virtual server name 311 and “Error” is set for the event type 315. An event history that is set or includes a character string “error” in the message 314 is searched.
FIG. 3D is an example of the physical server event analysis policy table 125. This table includes a search condition 341 for searching an event history from the event history table 121, a cause location 342 which is information set according to a search result based on the search condition, and an error level 343 for which an error level is set. One or more records are registered. Here, the contents of the search condition 341 for the record in the first row in FIG. 11 are set in the event history table 121 by setting a specific server name ($ physical server $) for the physical server name 311 and for the process name 313. An event history in which “bb” is set and the event type 315 includes the character string “Error” is searched. The contents of the search condition 341 for the record in the second line are as follows. From the event history table 121, a specific server name ($ physical server $) is set for the physical server name 311 and “aa” is set for the process name 313. The event history that is set and includes the character string “error” in the message 314 is searched. Also, the contents of the search condition 341 for the record in the third row are that a specific server name ($ physical server $) is set as the physical server name 311 from the event history table 121 and “memory fault” is displayed in the message 314. This is to search an event history including a character string. The contents of the search condition 341 for the record in the fourth line are as follows. From the event history table 121, a specific server name ($ physical server $) is set for the physical server name 311 and “ee” is set for the process name 313. Search the set event history. The contents of the search condition 341 for the record in the fifth line are as follows. From the event history table 121, a specific server name ($ physical server $) is set for the physical server name 311 and “bb” is set for the process name 313. The event history that is set and includes the character string “warning” in the message 314 is searched. The content of the search condition 341 for the record in the sixth line is “true” when the event history table 121 does not include any specific physical server name ($ physical server $).
The analysis history table management unit 116 illustrated in FIG. 2A manages the contents of the analysis history table 123 according to the user operation input received from the user interface unit 113. FIG. 3E is an example of the analysis history table 123. Each record of the analysis history table 123 includes a virtual server event 351 in which information on the virtual server searched by the failure analysis unit 114 from the event history table 121 is described, and information on a physical server searched by the failure analysis unit 114 from the event history table 121. Are included, and each item of the analysis result 353 in which the content is set according to the content of the virtual server event 351 or the physical server event 352 is included.
The handling table management unit 117 illustrated in FIG. 2A manages the contents of the handling table 126 according to the user operation input received from the user interface unit 113. FIG. 3F is an example of the countermeasure table 126. As shown in the figure, each record of the countermeasure table 126 includes an error level 361 in which an error level is set, and a countermeasure 362 in which the content of the countermeasure for the failure set in correspondence with the error level 361 is described. Consists of multiple records.
The countermeasure execution unit 118 in FIG. 2A executes processing according to the failure content analyzed by the failure analysis unit 114. Details of the application management table 127, SLA definition table 128, resource management table 129, dependency management table 130, server management table 131, and patch management table 132 will be described later.
FIG. 2B shows functions realized in the physical server 20 and data managed by the physical server 20. Each function in the figure is performed by the central processing unit 101 of the physical server 20 reading and executing a program stored in the main storage device 102 or the auxiliary storage device 103, or by the hardware of the physical server 20 itself. Realized by function.
As shown in the figure, the physical server 20 includes a virtualization mechanism 211, one or more virtual servers 212 realized by the virtualization mechanism 211, and a physical event notification unit 213. Each virtual server 212 operates an operating system 2121, and a business process 2122 and a virtual event notification unit 2123 are realized under the control of the operating system 2121.
The virtualization mechanism 211 shown in the figure virtualizes the resources provided by the physical server 20, and the physical resources (resources) provided by the physical server 20 are provided to end users, applications, operating systems, etc. , To realize a function that looks like one or more logical resources. A plurality of virtual servers 212 shown in the figure are logical resources (virtual computers) realized by the virtualization mechanism 211, and can operate independently from each other.
The virtual server 212 implements a hardware emulation environment with an operating system (host OS) that operates based on the physical resources (hardware) of the physical server 20, and the operating system 2121 ( May be realized by a so-called host OS system that operates a guest OS), or a so-called virtual machine monitor system in which an emulation environment is directly provided in a physical resource without a host OS and the guest OS is operated in that environment. It may be realized by. Also, as a physical resource emulation method, a full virtualization method that completely emulates physical resources may be selected, or a paravirtualization method that emulates only some physical resources may be selected. .
A memory image (virtual server image) corresponding to each virtual server 212 is stored in the storage device 30. When moving the virtual server 212 (changing the correspondence between the virtual server 212 and the physical server 20), the virtual server image is expanded in the storage area of the storage device 30 allocated to the physical server 20. It can be carried out. Note that the above movement is performed by, for example, the function of the virtualization mechanism 211 or in response to an instruction from the management server 10.
The operating system 2121 operates in each virtual server 212, and the business process 2122 and the virtual event notification unit 2123 operate in the operating system 2121.
When an event occurs in each virtual server 212, the virtual event notification unit 2123 operating in each virtual server 212 notifies the management server 10 of an event history corresponding to this event via the communication network 5.
The physical event notification unit 213 operating in each physical server 20 notifies the management server 10 of an event history corresponding to an event that has occurred in the physical server 20 via the communication network 5. Also, the physical event notification unit 213 receives an execution instruction for a response process (for a failure that has occurred) sent from the response execution unit 118 of the management server 10 via the communication network 5, and a response process corresponding to the received execution instruction Execute.
Processing performed by the failure monitoring unit 110 will be described with reference to the flowchart shown in FIG. 4A. In the following description, the letter “S” added in front of the reference sign means a step.
The failure monitoring unit 110 monitors in real time whether or not the user interface unit 113 has received an end operation from the user (S411). If an end operation has been received from the user (S411: YES), the process ends. When the end operation is not accepted (S411: NO), the process proceeds to S412.
In step S <b> 412, the failure monitoring unit 110 determines whether a failure has occurred in the business process 2122 of the virtual server 212. For example, when a new event history related to a failure (error) of the business process 2122 is received from the virtual event notification unit 2123, it is determined that a failure has occurred. Further, it is determined that a failure has occurred when the event history related to the error of the business process 2122 is newly registered in the event history table 121. If it is determined that a failure has occurred (S412: YES), the process proceeds to S413. If a failure has not occurred (S412: NO), the process returns to S411.
In step S413, the failure analysis unit 114 performs a process of specifying the cause of the failure and assigning an error level to the generated failure (hereinafter referred to as an analysis process). FIG. 4B shows details of the analysis process (S413). First, the failure analysis unit 114 searches the event history table 121 for an event history related to the virtual server 212 on which the business process 2122 in which the failure has occurred is executed (S4131). The search here is performed using the search condition 331 (first search condition) registered in the virtual server event analysis policy table 124. That is, in the above search, the virtual server name (for example, “vserver1”) described in the event history that triggered the determination of the occurrence of the failure is the variable “$ virtual server $” described in the search condition 331 shown in FIG. 3C. Is set to "."
Note that the above search may be performed using the server name (virtual server name) of the virtual server 212 described in the event history that triggered the determination of a failure in S412 as a key.
For example, if the contents of the event history table 121 are the contents shown in FIG. 3A and the key virtual server name is “vserver1”, the event histories on the second and fifth lines in FIG. 3 are searched. If the physical server name that is the key is “pserver1”, the corresponding virtual server name “vserver1” is acquired from the active server mapping table 122, and the acquired virtual server name “vserver1” is used as a key for two lines. The event history of the first and fifth lines is searched. It is assumed that the event history that triggered the determination of the occurrence of a failure is excluded from the search target.
Here, when the event history for a long period is managed in the event history table 121 (for example, when the event history deletion cycle is long), the event occurrence date and time 312 of the event history that has been determined to be the occurrence of the failure. Only the event history of events that occurred within a predetermined period (for example, within a predetermined period before and after the event occurrence date and time 312) may be set as search targets. Also, the date and time set in the virtual server operation start date and time 324 that can be acquired from the active server mapping table 122 using the virtual server name 322 and the physical server name 323 as a key (acquired from the event history that triggered the occurrence of the failure) Only the event history of events that occurred within a predetermined period (for example, from the date and time set in the virtual server operation start date and time 324 to the date and time set in the event occurrence date and time 312) starting from the point You may do it. Thus, the accuracy of analysis can be improved by narrowing the search target only to the vicinity when the failure occurs.
In S4132, the failure analysis unit 114 determines whether one or more event histories related to the virtual server 212 can be searched in the search of S4131 (S4132). If the search could not be performed (S4132: NO), the process proceeds to S4133. If the search could be performed (S4132: YES), the process proceeds to S4134.
In S4133, the failure analysis unit 114 registers the contents of the event history determined to have occurred in S412 as the virtual server event 351 of the analysis history table 123, and stores “business process” in the cause location 3531 of the analysis result 353 corresponding thereto. ”And“ 1 ”are registered in the error level 3532. Thereafter, the process proceeds to S414 in FIG. 4A. In other words, the failure analysis unit 114 determines that the cause of the failure is the business process 2122 when the event history of the virtual server 212 could not be searched in S4131.
In step S4134, the failure analysis unit 114 searches the event history table 121 for an event history related to the physical server 20 on which the business process 2122 in which the failure has occurred is executed.
When the event history is notified from the virtual event notification unit 2123 of the virtual server 212, the physical server name corresponding to the server name (virtual server name) described in the event history is set as the active server. The event history is acquired from the mapping table 122 and the event history is searched from the event history table 121 using the acquired physical server name as a key. For example, the contents of the event history table 121 are the contents shown in FIG. 3A (the event history that triggered the occurrence of a failure is omitted in the figure), and the physical server name that is the key is “pserver1”. If there is, the event history on the first line is searched. If the server name as a key is the virtual server “vserver1”, the corresponding physical server name “pserver1” is acquired from the active server mapping table 122, and the acquired physical server name “pserver1” is used as the key. The event history on the line is searched.
Instead of using the server name as a key, the event history related to the physical server 20 may be searched based on the search condition (second search condition) registered in the physical server event analysis policy table 125. In this case, the physical server name (for example, “pserver1”) described in the event history that triggered the determination of the occurrence of the failure is the variable “$ physical server $” described in the search condition shown in FIG. 3D. Set to and search.
As described above, when an event history for a long period is managed in the event history table 121 (for example, when the event history deletion cycle is long), the occurrence of an event in the event history that triggers the determination that a failure has occurred Only event histories of events that occurred within a predetermined period starting from the date and time 312 (for example, within a predetermined period before and after the event occurrence date and time 312) may be searched. Also, the date and time set in the virtual server operation start date and time 324 that can be acquired from the active server mapping table 122 using the virtual server name 322 and the physical server name 323 as a key (acquired from the event history that triggered the occurrence of the failure) Only the event history of events that occurred within a predetermined period (for example, from the date and time set in the virtual server operation start date and time 324 to the date and time set in the event occurrence date and time 312) starting from the point You may do it.
In S4135, the failure analysis unit 114 determines whether one or more event histories related to the physical server 20 have been searched in the search in S4134 (S4135). If the search could not be performed (S4135: NO), the process proceeds to S4136. If the search could be performed (S4135: YES), the process proceeds to S4147.
In S4136, the failure analysis unit 114 registers the contents of the event history determined to have occurred in S412 as the physical server event 352 of the analysis history table 123, and stores “virtual server” in the cause location 3531 of the analysis result 353 corresponding thereto. "2" is registered in the error level 3532. Thereafter, the process proceeds to S414 in FIG. 4A. In other words, the failure analysis unit 114 was able to search the event history of the virtual server 212 in S4131, but could not search the event history of the physical server 20 in S4134. Judge that there is.
In S4137, the failure analysis unit 114 detects the cause of the failure (first failure location) corresponding to the event history of the virtual server 212 searched in S4131 (according to the first search condition), and in S4134 (the second It is determined whether or not the failure cause location (second failure location) corresponding to the retrieved event history of the physical server 20 matches (according to the search condition). Here, when the search conditions registered in the virtual server event analysis policy table 124 or the physical server event analysis policy table 125 are used as search conditions, the cause of the failure corresponding to the event history is the virtual server event analysis. In the policy table 124 or the physical server event analysis policy table 125, the cause locations 332 and 342 are associated with the search conditions used when the searched event history is searched. When the event history is searched using the virtual server name or physical server name described in the event history as a key, the failure analysis unit 114 displays the message 314, event type 315, etc. described in the searched event history. Based on this, identify the cause of the failure. If the cause location matches (S4137: YES), the process proceeds to S4138. If the cause location does not match (S4137: NO), the process proceeds to S4136. In other words, the failure analysis unit 114 was able to search the event history of the virtual server 212 in S4131, and the event history of the physical server 20 in S4134. However, the cause location of each event history did not match. It is determined that the cause is the virtual server 212.
In S4138, the failure analysis unit 114 registers the contents of the event history determined to have occurred in S412 as a virtual server event 351 and a physical server event 352 in the analysis history table 123, and causes of the analysis result 353 corresponding thereto. “Physical server” is registered in 3531, and “3” is registered in error level 3532. Thereafter, the process proceeds to S414 in FIG. 4A. That is, the failure analysis unit 114 can search the event history of the virtual server 212 in S4131, can search the event history of the physical server 20 in S4134, and the cause location of each event history matches in the determination of S4137. Therefore, it is determined that there is a high possibility that the cause of the failure is in the physical server 20.
According to the failure analysis processing S413 described above, it is possible to easily and quickly identify whether the cause of the failure is the business process 2122, the virtual server 212, or the physical server 20 with high accuracy. . Further, since the analysis is performed based on the contents of the event history table 121 whose contents are updated in real time, the cause of the failure can be specified in a short time after the failure occurs. Therefore, it is possible to effectively cope with a failure requiring urgency.
In S414 of FIG. 4A, the user interface unit 113 outputs the contents of the analysis history table 123 to the output device 105 of the management server 10. The user interface unit 113 provides an editing environment for the analysis result 353 among the contents of the output analysis history table 123. The analysis history table management unit 116 reflects the contents of the edited analysis result 353 in the analysis history table 123. The analysis history table management unit 116 also reflects the edited contents of the analysis history table 123 in the virtual server event analysis policy table 124 or the physical server event analysis policy table 125. Accordingly, the correspondence accuracy between the search condition 331 and the cause location 332 in the virtual server event analysis policy table 124 or the correspondence accuracy between the search condition 341, the cause location 342, and the error level 343 in the physical server event analysis policy table 125 is improved. The analysis accuracy of the cause can be improved.
In S415 of FIG. 4A, the countermeasure execution unit 118 performs processing according to the cause of the failure (hereinafter referred to as failure handling processing S415). The handling execution unit 118 uses the application management table 127, SLA definition table 128, resource management table 129, dependency management table 130, server management table 131, and patch management table 132 shown in FIG. . First, the contents of these tables will be described.
FIG. 3G is an example of the application management table 127 among the above tables. The application management table 127 manages information related to applications executed on the virtual server 212. As shown in the figure, the application management table 127 includes an AP name 1271 in which an application name is set, a process name 1272 in which a process name corresponding to an application set by the AP name 1271 is set, and a process name 1272 A process ID 1273 in which an identifier of a process corresponding to the set process name 1272 is set, a virtual server name 1274 in which the name of the virtual server 212 in which the application set in the AP name 1271 is running, and a virtual The server name 1274 includes one or more records including each item of the related SLA 1275 in which the name of the SLA (Service Level Agreement) of the virtual server 212 is set.
FIG. 3H is an example of the SLA definition table 128. Information related to individual SLA is managed in the SLA definition table 128. As shown in the figure, the SLA definition table 128 includes items of an SLA name 1281 in which the SLA name is set and an SLA content 1282 in which the SLA content set in the SLA name 1281 is set. Consists of one or more records.
FIG. 3I is an example of the resource management table 129. The resource management table 129 manages the amount of resources used by software executed on the virtual server 212. As shown in the figure, the resource management table 129 includes an AP name 1291 in which the name of the software is set, a process name 1292 in which the name of the software process set in the AP name 1291 is set, and a process name 1292. Each of the items of used memory amount 1293 in which the amount of memory used by the process set to 1 is set, and used disk amount 1294 in which the capacity of the disk used by the process set in the process name 1292 is set. Consists of one or more records.
FIG. 3J is an example of the dependency relationship management table 130. The dependency management table 130 manages dependencies (layer configuration) between software types such as applications, middleware, drivers, and operating systems (OS) that operate (installed) in the virtual server 212. The As shown in the figure, the dependency management table 130 includes a virtual server name 1301 in which the name of the virtual server 212 is set, and a dependency relationship in the virtual server 212 corresponding to the virtual server name set in the virtual server name 1301. Is composed of one or more records including each item of the configuration information 1302 to be set. As shown in the figure, the configuration information 1302 includes hierarchized sub-records indicating dependencies among software types such as an application 13021, middleware 13022, driver 13023, and operating system 13024.
FIG. 3K is an example of the server management table 131. The server management table 131 manages resources that the physical server 20 or the virtual server 212 have (can provide). As shown in the figure, the server management table 131 includes a server name 1311 in which names of the physical server 20 and the virtual server 212 are set, and a physical server 20 or a virtual server 212 corresponding to the server name set in the server name 1311. Is stored in the CPU 1312 and the server name 1311 in which information (for example, the processor type and type (Xeon (registered trademark)), processing performance such as operation clock and internal cache) related to the processor (central processing unit 101) held by Information (capacity, response speed, etc.) related to the memory (main storage device 102) held by the physical server 20 or the virtual server 212 corresponding to the set server name is set in the memory 1313 and the server name 1311. The physical server 20 or virtual server 212 corresponding to the server name One including each item of the HDD 1314 in which information (capacity, response speed, etc.) relating to the hard disk drive (auxiliary storage device 103) is set, and information 1315 relating to other resources held by the physical server 20 or the virtual server 212 It consists of the above records.
FIG. 3L is an example of the patch management table 132. The patch management table 132 manages information related to the version of software installed in the virtual server 212. As shown in the figure, the patch management table 132 includes a software name 1321 in which the software name is set, a virtual server name 1322 indicating the name of the virtual server in which the software indicated by the software name 1321 is installed, An update date and time 1325 indicating the date on which the software indicated by the software name 1321 is updated, a pre-update version 1323 in which the previous version of the current version (updated version) is set, and an updated version are set. The updated version 1324 includes one or more records including items.
<Action execution unit>
FIG. 5 shows main functions of the countermeasure execution unit 118 shown in FIG. 2A. As shown in the figure, the countermeasure execution unit 118, as a main function related to the failure handling process S415, moves the software executed on the virtual server 212 to another virtual server in units of the virtual server 212. Unit 1181, application migration processing unit 1182 for migrating software executed in virtual server 212 in units of applications, and rolls back the version of software installed in virtual server 212 (returns to the state before version update). A rollback processing unit 1183 and a resource shortage determination unit 1184 that determines whether the cause of the failure is a resource shortage are provided.
<Failure handling process>
FIG. 6 is a flowchart for explaining the overall flow of the failure handling process S415. Hereinafter, the failure handling process S415 will be described with reference to FIG. In the following description, a virtual server 212 in which a failure has occurred is referred to as a failure virtual server 212, and a physical server 20 that implements the failure virtual server 212 is referred to as a failure physical server 20. The business process 2122 executed in the fault virtual server 212 is referred to as a fault business process 2122. The correspondence between the failure virtual server 212 and the failure physical server 20 can be acquired from the active server mapping table 122.
First, the countermeasure execution unit 118 refers to the analysis history table 123 (FIG. 3E), and the cause of the failure occurring in the failed virtual server 212 is the hardware failure of the failed physical server 20 realizing the failed virtual server 212. It is determined whether or not (S611). As an example of a hardware failure, there is a disk access error of the hard disk drive 171 provided in the physical server 20.
When the cause of the failure is a hardware failure of the failed physical server 20 (S611: YES), the handling execution unit 118 moves the failed virtual server 212 from the failed physical server 20 to another physical server 20 (failed virtual server). 212 to change the physical server 20 that implements 212. Hereinafter, it is referred to as a virtual server migration process S621. On the other hand, when it is determined that the cause of the failure is not a hardware failure of the failed physical server 20 (S611: NO), the process proceeds to S631.
<Virtual server migration processing>
FIG. 7 is a flowchart for explaining the virtual server migration process S621. In the virtual server migration process S621, the software executed on the failed virtual server 212 is moved to another virtual server 212 (the physical server 20 that implements the failed virtual server 212 is changed). Hereinafter, the virtual server migration process S621 will be described with reference to FIG.
First, the coping execution unit 118 acquires the software running on each virtual server 212 that is the management target of the management server 10 from the dependency management table 130, and the resource amount used by each software from the resource management table 129. Are obtained, and the obtained resource amounts are totaled to determine the resource amount used by each virtual server 212 (S711).
Next, the coping execution unit 118 acquires the resource amount held by each virtual server 212 from the server management table 131, and from the resource amount used by each virtual server 212 that is the management target obtained in S711, The free resource amount of each virtual server 212 is obtained (S712).
Then, the countermeasure execution unit 118 searches for other virtual servers 212 that can move the failed virtual server 212 by comparing the resource amount used by the failed virtual server 212 with the free resource amount of each virtual server 212. (S713). If the destination virtual server 212 exists (S713: YES), the countermeasure execution unit 118 moves the software of the faulty virtual server 212 to the virtual server 212 (S714). Note that when there are a plurality of migration destination candidate virtual servers 212, for example, the virtual server 212 having the most room for the resource amount is selected. On the other hand, when there is no virtual server 212 that can be moved (S713: NO), the process proceeds to S721.
In S721, the countermeasure execution unit 118 determines whether or not a new virtual server 212 can be created (S721). This determination is made based on, for example, the resource amount held by each physical server 20 that is the management target of the management server 10 or the free resource amount of each physical server 20 that can be acquired from the server management table 131 or the resource management table 129. .
If a new virtual server 212 can be created (S721: YES), a new virtual server 212 is created (S722), and the software of the faulty virtual server 212 is moved to the virtual server 212 (S714). On the other hand, if such a physical server 20 does not exist (S721: NO), a message is displayed on the output device 105 to notify the user that the failed virtual server 212 cannot be moved (S723).
As described above, when the management server 10 determines that the cause of the failure is a hardware failure of the physical server 20, the management server 10 calculates the amount of free resources of each virtual server 212 that is the management target of the management server 10, There is another virtual server 212 that can move the software executed on the failure virtual server 212 by comparing the resource amount and the resource amount used by the software executed on the failure virtual server 212. In the case where it is possible to move the software, the software is moved to another virtual server 212 in units of the virtual server 212.
As described above, according to the above mechanism, when the cause of the failure is the physical server 20, the software is automatically moved to the virtual server 212 other than the other failed virtual server 212. The processing performed by the virtual server 212 can be restored. In addition, since the other virtual server 212 (physical server 20) having free resources is searched for and used as a migration destination, the resources held by the virtualization system can be used effectively.
If a virtual server 212 having free resources is not found, it is determined whether or not a new virtual server 212 can be created. If possible, a new virtual server 212 is created and the software of the failed virtual server 212 is stored there. Since the wear is moved, automatic recovery from a failure can be performed more reliably.
Returning to FIG. 6 again, the description will be continued. In S611 of FIG. 6, when it is determined that the cause of the failure is not a hardware failure of the failed physical server 20 (S611: NO), the countermeasure execution unit 118 adds the failed business process 2122 to the event history table 121 (FIG. 3A). Whether there is a history (for example, a history in which “Information” is set in the event type 315) of the same business process 2122 (the business process 2122 having the same process name 313) that has been processed normally. Is determined (S631). If there is a history of normal termination (S631: YES), the process proceeds to S641. On the other hand, if there is no history of normal termination (S631: NO), the process proceeds to S651.
In S641, the countermeasure execution unit 118 updates the patch management table 132 (FIG. 3L) in the failure virtual server 212 whose update date and time 1325 is after the occurrence date and time 312 of the normally ended history searched in S631. It is determined whether there is an update history (hereinafter referred to as a version update history). If such a version update history exists (S641: YES), the process proceeds to S642, and if not (S641: NO), the process proceeds to S651.
In S642, the countermeasure execution unit 118 sets the occurrence date and time 312 of the normally ended history searched in S631 among the history of the same business process 2122 as the failed business process 2122 in the virtual server 212 other than the failed virtual server 212. It is determined whether there is a normally terminated history (for example, a history in which “Information” is set in the event type 315) after a later version update history (S642). If such a history does not exist (S641: NO), the process proceeds to S643 to perform a process of restoring the version (version down process; hereinafter referred to as rollback process S643). That is, in this case, it is presumed that a failure has occurred due to the recent version update, so the countermeasure execution unit 118 performs processing for restoring the version.
FIG. 8 is a flowchart for explaining the rollback processing S643. First, the coping execution unit 118 uses the dependency management table 130 (FIG. 3J) to determine whether software having a dependency relationship with the application implemented by the faulty business process 2122 (middleware and driver in the dependency management table 130 in FIG. 3J). , Operating system (OS)) is acquired (S811).
Next, the coping execution unit 118 acquires from the patch management table 132 (FIG. 3L) the version (pre-update version 663) prior to the time of failure of each software acquired in S811 (S812). The countermeasure execution unit 118 rolls back the version of each software to the pre-update version 633 (S813).
On the other hand, if such a history exists in S642 (S642: YES), the process proceeds to S644, and the countermeasure execution unit 118 moves the application running on the faulty virtual server 212 to another virtual server 212. Processing (hereinafter referred to as application migration processing S644) is performed. That is, in this case, it is presumed that the latest version update is not necessarily the cause of the failure, so the rollback is not performed, but the countermeasure execution unit 118 moves the application to another virtual server 212.
FIG. 9 is a flowchart for explaining the application movement process S644. First, the coping execution unit 118 uses the dependency management table 130 (FIG. 3J) to determine whether software having a dependency relationship with the application implemented by the faulty business process 2122 (middleware and driver in the dependency management table 130 in FIG. 3J). , Operating system (OS)) is acquired (S911). The application realized by the faulty business process 2122 is specified by searching the application management table 127 using the process name 313 of the faulty business process 2122 as a key.
Next, based on the dependency relationship acquired in S911, the application management table 127, the dependency relationship management table 130 (FIG. 3J), and the SLA definition table 128, a candidate for the virtual server 212 that can be the migration destination of the application is searched (S912).
For example, when the process name of the faulty business process 2122 is “aa”, the application (AP01) is moved in the application management table 127 shown in FIG. 3G. In this case, in the dependency management table 130 in FIG. 3J, the application (AP01) operates in an environment of middleware (middleware 1), driver (driver 1), and operating system (OS1). The server 212 also needs to have such an environment. In addition, since “sla001, sla003” is set in the related SLA 1275 of the application (AP01), the middleware of the destination virtual server 212 needs to satisfy these SLA.
Next, the coping execution unit 118 acquires the resource amount used by each software acquired in S911 from the resource management table 129 (S913).
Next, the countermeasure execution unit 118 obtains the free resource amount of the candidate virtual server 212 searched in S912 from the server management table 131 (S914). The free resource amount is acquired by the same method as described in S711 of FIG.
Next, the countermeasure execution unit 118 compares the resource amount used by each software acquired in S913 and the available resource amount of the candidate virtual server 212 acquired in S914, and moves the application. It is determined whether or not there is a virtual server 212 that can be used (S915).
If there is a virtual server 212 that can be moved (S915: YES), the virtual server 212 is moved to the virtual server 212 that is determined to be capable of moving the application of the failed virtual server 212 (S916). If there is no virtual server 212 that can be moved (S915: NO), the user is notified via the output device 105 that the application of the faulty virtual server 212 cannot be moved (S917).
As described above, when the coping execution unit 118 determines that the cause of the failure is not a hardware failure of the physical server 20, the execution history of the failed business process 2122 and software that implements the failed business process 2122. Based on the update history of the software, it is determined whether or not there is an execution history in which the faulty business process 2122 has been normally terminated after the software has been updated. Roll back the software version. As described above, the management server 10 according to the present embodiment can more accurately identify the cause of the failure and take an appropriate action, and thus can reliably recover from the failure.
On the other hand, when there is an execution history that has ended normally, the faulty business process 2122 (application) is moved to another virtual server 212. As described above, the management server 10 according to the present embodiment identifies the cause of the failure more accurately and moves in units of applications, so that the recovery from the failure can be performed quickly and reliably.
S651 in FIG. 6 will be described. In S651, the countermeasure execution unit 118 determines whether the cause of the failure is a resource shortage. If the resource shortage is the cause (S651: YES), the process proceeds to S644. If the cause is not a resource shortage (S651: NO), the process proceeds to S681.
Here, the determination as to whether or not the resource shortage is the cause is obtained from the resource management table 129 and the dependency management table 130, for example, to determine the resource amount used by the faulty business process 2122, and the method described in S711, for example This is performed by comparing with the free resource amount of the failed physical server 20 obtained by the above.
If there is no update history of the faulty business process 2122 after normal termination (S641: NO), for example, it is determined whether there is a resource shortage as follows. First, the coping execution unit 118 acquires the execution multiplicity of the business process 2122 in the failure virtual server 212 at the time of the failure. On the other hand, the countermeasure execution unit 118 acquires from the event history table 121 the execution multiplicity of the business process 2122 at the normal end time. The coping execution unit 118 determines that the resource is insufficient if, for example, the execution multiplicity at the time of failure is greater than the execution multiplicity at the time of normal termination, and the execution multiplicity at the time of failure occurrence is If it is less than the multiplicity, it is determined that there is no resource shortage.
As described above, the coping execution unit 118 determines whether or not the resource shortage is the cause of the failure, and if it is determined that the resource shortage is the cause (S651: YES), the troubled business process 2122 (application) is changed to another. To the virtual server 212. As described above, the management server 10 according to the present embodiment quickly determines that the resource shortage is the cause of the failure and moves in units of applications, so that the recovery from the failure can be performed quickly and reliably. Further, the coping execution unit 118 determines whether there is a resource shortage by an optimum method according to the situation (in the case of (S631: NO) or (S651: NO)), so recovery from a failure is performed. Can be performed quickly and reliably.
In S661 in FIG. 6, the countermeasure execution unit 118 re-executes the faulty business process 2122. In step S662, the countermeasure execution unit 118 determines whether the re-execution result is a normal end. If it is a normal end (S662: YES), the process ends. If it is not a normal end (S662: NO), the countermeasure execution unit 118 notifies the user through the output device 105 that the countermeasure has not ended normally (S681). In this notification, for example, progress information (log information) of the process performed in the failure handling process S415 may be notified to the user.
The above description of the embodiment is for facilitating the understanding of the present invention, and does not limit the present invention. It goes without saying that the present invention can be changed and improved without departing from the gist thereof, and that the present invention includes equivalents thereof. For example, the error level set according to the cause of the failure is not necessarily limited to the one described above, and the user may arbitrarily set the error level.
DESCRIPTION OF SYMBOLS 10 Management server 20 Physical server 30 Storage device 100 Computer 111 Event history management part 112 Mapping table management part 113 User interface part 114 Failure analysis part 115 Policy table management part 116 Analysis history table management part 117 Dealing table management part 118 Dealing execution part 121 Event history table 122 Active server mapping table 123 Analysis history table 124 Virtual server event analysis policy table 125 Physical server event analysis policy table 126 Handling table 127 Application management table 128 SLA definition table 129 Resource management table 130 Dependency management table 131 Server management table 132 Patch management table 211 Virtualization mechanism 212 Virtual server 2 121 Operating System 2122 Business Process 2123 Virtual Event Notification Unit 213 Physical Event Notification Unit
A method for analyzing a failure that occurs in a virtual environment in which a virtual server is realized by a virtualization mechanism that operates on a physical server,
A management server that is communicably connected to the physical server,
Storing a mapping table in which correspondence between the virtual server and the physical server on which the virtual server is realized is registered;
Storing and storing a second event history that is a history of events that have occurred in the physical server and a first event history that is a history of events that have occurred in the virtual server;
When receiving the event relating to the failure of the business process operating on the virtual server, the event history related to the virtual server that issued the event and the second event history included in the first event history. The event history related to the physical server that realizes the virtual server that has issued the event, obtained from the mapping table, is searched from the stored event history, and the cause of the failure is based on the search result Identify
A virtual server event analysis policy table in which a first search condition used for searching the first event history and a first failure location are associated, and a second search condition used for searching the second event history; Storing a physical server event analysis policy table in which the second failure location is associated;
The first event history corresponding to the first search condition registered in the virtual server event analysis policy table is searched from the stored event history, and as a result, the corresponding first first If the event history cannot be searched, the cause of the failure is identified as the business process,
The first event history corresponding to the first search condition registered in the virtual server event analysis policy table is searched from the stored and stored event history, and the physical server event analysis policy table is stored in the physical server event analysis policy table. The second event history corresponding to the registered second search condition is searched, and as a result, the corresponding first event history can be searched. If the search fails, identify the cause of the failure as the virtual server,
The first event history corresponding to the first search condition registered in the virtual server event analysis policy table is searched from the stored and stored event history, and the physical server event analysis policy table is stored in the physical server event analysis policy table. The second event history corresponding to the registered second search condition is searched, and as a result, the corresponding first event history and the second event history can be searched, and The second fault used for searching the first event location searched for the first fault location associated with the first search condition used for searching the searched first event history. If the second failure location associated with the search condition does not match, the cause of the failure is identified in the virtual server. Analysis method of disorders the cause of failure and identifies the in the physical server.
The failure analysis method according to claim 1,
The cause of the specified failure and the first search condition or the second event history that can be searched for the corresponding first event history in the process leading to the specification can be searched Output the analysis result that is described in association with the second search condition,
The first failure location or physical server event analysis policy associated with the first search condition in the virtual server event analysis policy table based on the received change request is received from the analysis result change request. A failure analysis method, wherein the second failure location associated with the second search condition in the table is changed.
The management server targets only the event history of events that occurred within a predetermined period starting from the date and time when the failure of the event history for the business process occurred, among the stored event history. And performing the search as a failure analysis method.
The management server stores the most recent date and time when the virtual server was moved in the virtual environment,
The management server includes an event that has occurred within a predetermined period starting from the date and time when the virtual server on which the business process in which the failure occurred operates is performed, among the event history stored and stored The failure analysis method, wherein the search is performed only with respect to the event history.
When it is determined that the cause of the failure is a hardware failure of the physical server,
Obtain the free resource amount of each of the virtual servers that are the management target of the management server,
Used by the software executed on the failed virtual server, which is the virtual server realized by the physical server causing the failure, obtained from the obtained free resource amount and the mapping table Compared with the resource amount, it is determined whether there is another virtual server capable of moving the software executed on the failed virtual server, and it is determined that the software can be moved. In this case, the failure analysis method is characterized in that the software is moved to the other virtual server.
The failure analysis method according to claim 5,
When it is determined in the determination that there is no other virtual server capable of moving the software executed on the failed virtual server,
From the amount of free resources of the physical server that is the management target of the management server, determine whether a new virtual server can be created,
A failure analysis method characterized by creating a new virtual server and moving the software to the newly created virtual server when it is determined that it can be created.
Managing the execution history of the business process executed on each of the virtual servers, and the update history of software that implements the business process;
When it is determined that the cause of the failure is not a hardware failure of the physical server,
Based on the execution history and the update history, the business process of the fault virtual server that is the virtual server on which the business process related to the received event related to the fault is operating is normal after the software is updated. Determine whether there is a completed execution history,
If such an execution history does not exist, the software version is rolled back and restarted.
The failure analysis method according to claim 7 ,
If there is such an execution history in the determination of whether or not there is an execution history that has ended normally after the software update, an application corresponding to the business process is realized. And determining whether there is another virtual server capable of moving the application by comparing the amount of resources required for the management server and the amount of free resources of the virtual server that is the management target of the management server And, if present, moving the application to the other virtual server.
Managing the execution history of the business process executed on the virtual server;
Determining whether or not there is the execution history that has been normally terminated for the business process after the occurrence of the failure,
When there is no execution history that has ended normally, it is determined whether the cause of the failure is a resource shortage,
If the cause is a resource shortage, the amount of resources necessary to realize the application corresponding to the business process is compared with the amount of free resources of the virtual server managed by the management server, and the application is moved. A failure analysis method comprising: determining whether or not there is another virtual server that can be executed, and moving the application to the other virtual server when the virtual server exists.
The failure analysis method according to claim 9,
Determining whether or not the cause of the failure is a resource shortage by comparing the execution multiplicity of the business process at the time of occurrence of the failure and the execution multiplicity at the time of normal execution of the business process. How to analyze the failure.
A management server that is used to analyze a failure that occurs in a virtual environment in which a virtual server is realized by a virtualization mechanism that operates on a physical server, and that is communicably connected to each of the physical servers,
The first event history corresponding to the first search condition registered in the virtual server event analysis policy table is searched from the stored and stored event history, and the physical server event analysis policy table is stored in the physical server event analysis policy table. The second event history corresponding to the registered second search condition is searched, and as a result, the corresponding first event history and the second event history can be searched, and The second fault used for searching the first event location searched for the first fault location associated with the first search condition used for searching the searched first event history. If the second failure location associated with the search condition does not match, the cause of the failure is identified in the virtual server. Management server cause of failure and identifies the in the physical server.
The management server according to claim 11,
The first failure location or physical server event analysis policy associated with the first search condition in the virtual server event analysis policy table based on the received change request is received from the analysis result change request. The management server, wherein the second failure location associated with the second search condition in the table is changed.
Of the stored event histories, the search is performed only for the event histories of events that occurred within a predetermined period starting from the date and time when the failure of the event history for the business process occurred. A management server characterized by that.
Storing the most recent date and time when the virtual server was moved in the virtualized environment;
Among the stored event history, the event history for events that occurred within a predetermined period starting from the date and time when the virtual server on which the business process in which the failure occurred is operating was moved The management server is characterized in that the search is performed only on the target.
The obtained free resource amount is compared with the resource amount used by the software executed in the fault virtual server that is the virtual server realized by the physical server acquired from the mapping table, When it is determined that there is another virtual server capable of moving the software executed on the failed virtual server, and when it is determined that the software can be moved, A management server that is moved to the other virtual server.
The management server according to claim 15, wherein
A management server that creates a new virtual server and moves the software to the newly created virtual server when it is determined that it can be created.
A management server that rolls back the software version and restarts when there is no such execution history.
The management server according to claim 17 ,
If there is such an execution history in the determination of whether or not there is an execution history that has ended normally after the software update, an application corresponding to the business process is realized. And determining whether there is another virtual server capable of moving the application by comparing the amount of resources required for the management server and the amount of free resources of the virtual server that is the management target of the management server And if present, the application is moved to the other virtual server.
If the cause is a resource shortage, the amount of resources necessary to realize the application corresponding to the business process is compared with the amount of free resources of the virtual server managed by the management server, and the application is moved. A management server that judges whether or not there is another virtual server that can be executed, and moves the application to the other virtual server if it exists.
The management server according to claim 19,
Determining whether or not the cause of the failure is a resource shortage by comparing the execution multiplicity of the business process at the time of occurrence of the failure and the execution multiplicity at the time of normal execution of the business process. Management server.
A management server that is used to analyze a failure that occurs in a virtual environment in which a virtual server is realized by a virtualization mechanism that operates on a physical server, and that is connected to each of the physical servers to be able to communicate,
A function of storing a mapping table in which correspondence between the virtual server and the physical server on which the virtual server is realized is registered;
A function for accumulating and storing a second event history that is a history of events that have occurred in the physical server and a first event history that is a history of events that have occurred in the virtual server;
When receiving the event relating to the failure of the business process operating on the virtual server, the event history related to the virtual server that issued the event and the second event history included in the first event history. The event history related to the physical server that realizes the virtual server that has issued the event, obtained from the mapping table, is searched from the stored event history, and the cause of the failure is based on the search result With the ability to identify
A virtual server event analysis policy table in which a first search condition used for searching the first event history and a first failure location are associated, and a second search condition used for searching the second event history; A function of storing a physical server event analysis policy table that associates the second failure location;
The first event history corresponding to the first search condition registered in the virtual server event analysis policy table is searched from the stored event history, and as a result, the corresponding first first If the event history cannot be searched, a function that identifies the cause of the failure as the business process,
The first event history corresponding to the first search condition registered in the virtual server event analysis policy table is searched from the stored and stored event history, and the physical server event analysis policy table is stored in the physical server event analysis policy table. The second event history corresponding to the registered second search condition is searched, and as a result, the corresponding first event history can be searched. A function that identifies that the cause of the failure is the virtual server,
The first event history corresponding to the first search condition registered in the virtual server event analysis policy table is searched from the stored and stored event history, and the physical server event analysis policy table is stored in the physical server event analysis policy table. The second event history corresponding to the registered second search condition is searched, and as a result, the corresponding first event history and the second event history can be searched, and The second fault used for searching the first event location searched for the first fault location associated with the first search condition used for searching the searched first event history. If the second failure location associated with the search condition does not match, the cause of the failure is identified in the virtual server. Program for cause of failure and a function of identifying to be in the physical server.
JP2009135441A 2008-09-04 2009-06-04 Method for analyzing failure occurring in virtual environment, management server, and program Expired - Fee Related JP5140633B2 (en)
JP2009135441A JP5140633B2 (en) 2008-09-04 2009-06-04 Method for analyzing failure occurring in virtual environment, management server, and program
US12/551,962 US8006134B2 (en) 2008-09-04 2009-09-01 Method for analyzing fault caused in virtualized environment, and management server
JP2010086516A JP2010086516A (en) 2010-04-15
JP5140633B2 true JP5140633B2 (en) 2013-02-06
JP2009135441A Expired - Fee Related JP5140633B2 (en) 2008-09-04 2009-06-04 Method for analyzing failure occurring in virtual environment, management server, and program
WO2008092162A2 (en) * 2007-01-26 2008-07-31 The Trustees Of Columbia University In The City Of New York Systems, methods, and media for recovering an application from a fault or attack
JP5417264B2 (en) * 2010-06-21 2014-02-12 株式会社日立製作所 Method of providing analysis information
JP5577412B2 (en) * 2010-11-16 2014-08-20 株式会社日立製作所 Computer system, migration method and management server
FR2977691B1 (en) * 2011-07-08 2013-07-12 Bull Sas Method and computer program for dynamic management of services in a cluster of administration
CN102902599B (en) 2012-09-17 2016-08-24 华为技术有限公司 Virtual machine internal fault handling method, Apparatus and system
JP5967215B2 (en) * 2012-11-07 2016-08-10 富士通株式会社 Information processing apparatus, program, and virtual machine migration method
JP6233107B2 (en) * 2014-03-10 2017-11-22 富士通株式会社 Information storage program, information storage method, information storage device, and information storage system
EP3255843A4 (en) * 2015-02-06 2018-01-03 Nec Corporation Failure monitoring device, virtual network system, failure monitoring method and program
JP6493017B2 (en) * 2015-06-26 2019-04-03 セイコーエプソン株式会社 Network system, server, and network system control method
JP2017049711A (en) * 2015-08-31 2017-03-09 キヤノン株式会社 Information processing device, method for controlling information processing device, and program
CN107203451A (en) * 2016-03-18 2017-09-26 伊姆西公司 Method and apparatus for handling failure within the storage system
JP2018018471A (en) * 2016-07-29 2018-02-01 株式会社日立製作所 Operation management device, operation management method and operation management system
2009-06-04 JP JP2009135441A patent/JP5140633B2/en not_active Expired - Fee Related
2009-09-01 US US12/551,962 patent/US8006134B2/en not_active Expired - Fee Related
US8006134B2 (en) 2011-08-23
JP2010086516A (en) 2010-04-15
US20100058108A1 (en) 2010-03-04