JP6429813B2 - Computer system - Google Patents

Description

  The present disclosure relates to a computer system, and more particularly, to a computer system including an active physical system and a standby physical computer in which a virtual environment is constructed.

  Conventionally, when high reliability such as power system control is required, when a failure occurs in the active computer, a dual system with a standby computer that takes over the processing of the active computer has been used. ing.

  In recent years, even in such a dual system, it is possible to construct a virtual computer (virtualized environment) on a physical computer by using a technology for virtualizing the computer. Further, with the improvement in performance of physical computers, it is possible to construct a large number of virtual environments on the same physical computer, and each virtual environment thus constructed is provided to each user. A user can execute an application on the virtual environment.

  As an example of such a virtualization technique, Patent Document 1 (Japanese Patent Laid-Open No. 2010-237742) discloses a virtual machine server. The virtual machine server includes a plurality of dedicated virtual storage areas and a shared virtual storage area. The virtual machine server, when a file requested to be referred to the dedicated virtual storage area corresponding to the arbitrary virtual machine from any virtual machine included in the plurality of virtual machines is stored in the shared virtual storage area, The file requested for reference is read from the shared virtual storage area and output to the arbitrary virtual machine.

JP 2010-237742 A

  Here, according to the technique of Patent Document 1, when updating a file stored in the shared storage area, it is considered that the plurality of virtual machines cannot refer to the file until the update is completed. Cannot execute processing using. Also, in a dual system, it is preferable to maintain a redundant configuration as much as possible even during file update because of high reliability. However, in the technique of Patent Document 1, it is considered that a redundant configuration cannot be realized for all virtual machines during file update.

  The present disclosure has been made in view of the above problems, and an object in one aspect is to improve system reliability when information is updated in a duplex system in which a virtual environment is built on a physical computer. It is to provide technology that can improve

  According to an embodiment, a computer system is provided that includes active and standby physical computers in which a virtual environment is constructed. Each of the active and standby physical computers includes a storage unit having first and second shared storage areas for storing common information used in common in each of the plurality of virtual computers, and each of the plurality of virtual computers. When a plurality of recognized virtual disks, a management unit that manages the correspondence between the first and second shared storage areas, and a plurality of virtual disks are allocated to the first shared storage area, An update control unit that executes an update process of the common information stored in the second shared storage area based on receiving the update request for the common information, and a switch for switching the physical computer system to the active system or the standby system Part. When the update of the common information stored in the second shared storage area is completed, the management unit reassigns the virtual disk assigned to the first shared storage area to the second shared storage area. The switching unit in the standby physical computer transmits a system switching request to the active physical computer when the update of the common information is completed.

  According to the present disclosure, when information is updated in a duplex system in which a virtual environment is constructed on a physical computer, the reliability of the system can be further improved.

It is a figure which shows the structural example of the computer system according to this Embodiment. It is a figure which shows the information table according to this Embodiment. It is a figure which shows the other information table according to this Embodiment. It is a block diagram which shows the hardware structural example of the physical computer according to this Embodiment. It is a schematic diagram which shows the function structure of the physical computer according to this Embodiment. It is a flowchart which shows the process sequence of the standby physical computer according to this Embodiment. It is a flowchart which shows the process sequence of the active physical computer according to this Embodiment. It is a figure which shows the structural example of the computer system according to the modification of this Embodiment. It is a flowchart which shows the process sequence of the standby physical computer according to the modification of this Embodiment.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the same or corresponding portions are denoted by the same reference numerals, and the description thereof may not be repeated. In the embodiments described below, when referring to the number, amount, and the like, the scope of the present invention is not necessarily limited to the number, amount, and the like unless otherwise specified. In the following embodiments, each component is not necessarily essential for the present invention unless otherwise specified.

<System configuration>
FIG. 1 is a diagram showing a configuration example of a computer system 1000 according to the present embodiment. The computer system 1000 is applied to monitoring control of a relatively large-scale apparatus or facility such as power system control. For example, the computer system 1000 is disposed in a power supply command station that supervises generator control of the entire power plant in the jurisdiction section.

  Referring to FIG. 1, a computer system 1000 includes two physical computers 100A and 100B that are duplicated. The physical computer 100A and the physical computer 100B have basically the same configuration, and one is set as an active system and the other is set as a standby system to form a duplex configuration.

  The physical computers 100A and 100B (hereinafter collectively referred to as “physical computer 100”) are respectively virtual computers 10A and 10B, virtual computers 20A and 20B, virtual computers 30A and 30B, and shared storage areas 111A and 111B. Shared storage areas 112A and 112B, dedicated storage areas 121A and 121B, dedicated storage areas 122A and 122B, and dedicated storage areas 123A and 123B are included.

  Virtual computers 10A and 10B (hereinafter also collectively referred to as “virtual computer 10”) are respectively virtual disks 11A and 11B (hereinafter also collectively referred to as “virtual disk 11”) and virtual disks 12A and 12B (hereinafter referred to as “virtual disk 11”). And the virtual disk 12 "). The virtual machines 20A and 20B (hereinafter also collectively referred to as “virtual machine 20”) are respectively virtual disks 21A and 21B (hereinafter also collectively referred to as “virtual disk 21”) and virtual disks 22A and 22B (hereinafter referred to as “virtual disk 20”). The virtual disk 22 "). Virtual computers 30A and 30B (hereinafter also collectively referred to as “virtual computer 30”) are respectively virtual disks 31A and 31B (hereinafter also collectively referred to as “virtual disk 31”) and virtual disks 32A and 32B (hereinafter referred to as “virtual computer 30”). And generically referred to as “virtual disk 32”).

  The physical computer 100 executes various functions on an installed host OS (Operating System). The virtual computers 10 to 30 are virtual computers that have a guest OS execution environment prepared independently of the host OS and operate in the physical computer 100 based on the guest OS. Here, it is assumed that the same OS is installed in the virtual machines 10 to 30. Further, the virtual machines 10 to 30 use the same information for the OS system file, registry information, and the like. Furthermore, it is assumed that the virtual machines 10 to 30 use information having different contents for each virtual machine with respect to unique information such as a user account, a computer name, and network information.

  The shared storage areas 111A and 111B (hereinafter also collectively referred to as “shared storage area 111”) store information having the same contents as the shared storage areas 112A and 112B (hereinafter also collectively referred to as “shared storage area 112”), respectively. To do. Specifically, the shared storage areas 111 and 112 are information (system software, information used in common by these virtual machines) among information (data, programs, etc.) necessary for the virtual machines 10 to 30 to operate. System data, registry information, etc.). Note that virtual disks 11, 21, 31 are allocated to one of the shared storage areas 111, 112.

  The dedicated storage areas 121A and 121B (hereinafter collectively referred to as “dedicated storage area 121”) are storage areas dedicated to the virtual machines 10A and 10B, respectively. Similarly, dedicated storage areas 122A and 122B (hereinafter also collectively referred to as “dedicated storage areas 122”) are storage areas dedicated to the virtual machines 20A and 20B, respectively. The dedicated storage areas 123A and 123B (hereinafter also collectively referred to as “dedicated storage area 123”) are storage areas dedicated to the virtual machines 30A and 30B, respectively.

  Specifically, the dedicated storage areas 121 to 123 store information unique to the virtual machines 10 to 30 among information necessary for the virtual machines 10 to 30 to operate. In addition, virtual disks 12 to 32 are allocated to the dedicated storage areas 121 to 123, respectively. Therefore, for example, the dedicated storage area 121 is an area that cannot be accessed from virtual machines other than the virtual machine 10. The same applies to the other dedicated storage areas 122 and 123.

  Incidentally, access to each virtual disk is physically realized by accessing a storage area (shared storage area or dedicated storage area) on the physical computer 100 allocated to the virtual disk.

  Specifically, in the example of FIG. 1, the shared storage area 111A is physically used as the virtual disk 11A, and the dedicated storage area 121A is physically used as the virtual disk 12A. Therefore, access to the virtual disk 11A on the virtual machine 10A is physically realized by accessing the shared storage area 111A, and access to the virtual disk 12A on the virtual machine 10A is physically dedicated to the dedicated storage area. This is realized by accessing 121A.

  Here, the state of the shared storage area and the dedicated storage area allocated to each virtual machine during normal operation of the computer system will be described. For ease of explanation, the state of the shared storage area and the dedicated storage area allocated to each of the virtual machines 10A to 30A of the physical computer 100A will be described.

  FIG. 2 shows information table 400 according to the present embodiment. The information table 400 is stored in the internal memory of the physical computer 100A. A similar information table is stored in the internal memory of the physical computer 100B for the physical computer 100B.

  Referring to FIG. 2, the information table 400 indicates that the read-only shared storage area 111 is allocated to the virtual disks 11A to 31A of the virtual machines 10A to 30A. This is intended to protect common information commonly used in the virtual machines 10A to 30A from unintended changes (or unauthorized changes) during normal operation.

  The information table 400 indicates that dedicated storage areas 121A to 123A in a readable / writable state are allocated to the virtual disks 12A to 32A of the virtual machines 10A to 30A, respectively. As described above, since the dedicated storage area is an area that cannot be accessed from a virtual machine other than the corresponding (allocated) virtual machine, the contents may be changed by another non-corresponding virtual machine. This is because there is not.

  Although details will be described later, in the present embodiment, when updating the common information stored in the shared storage areas 111A and 112A, a shared storage area to which no virtual computer is allocated among these shared storage areas The common information stored in is updated first. Therefore, an information table 500 indicating the (number of virtual machines) assigned to the shared storage areas 111A and 112A may be stored in the internal memory.

  FIG. 3 shows another information table 500 according to the present embodiment. Referring to FIG. 3, information table 500 shows that three virtual machines 10A to 30A are assigned to shared storage area 111A, and no virtual machine is assigned to shared storage area 112A. Yes. For this reason, the processor of the physical computer 100A refers to the information table 500 and first updates the common information stored in the shared storage area 112A. After updating the common information stored in the shared storage area 112A, the processor updates the common information stored in the shared storage area 111A.

<Hardware configuration>
FIG. 4 is a block diagram showing a hardware configuration example of the physical computer 100 according to the present embodiment. Referring to FIG. 4, the physical computer 100 includes, as its components, a processor 150, a main storage device 152, a secondary storage device 154, a failure monitoring module 156, and a network interface (I / F) 158. The input device 160 and a general-purpose interface (I / F) 162 are included. These components are communicably connected to each other via an internal bus 164.

  The processor 150 is typically an arithmetic processing unit such as a CPU (Central Processing Unit) or an MPU (Multi Processing Unit), and reads various programs including an OS installed in the secondary storage device 154 to obtain main memory. It is executed while being deployed on the device 152. The main storage device 152 is typically a volatile storage medium such as a DRAM (Dynamic Random Access Memory) and is necessary for executing various programs in addition to codes of various programs including an OS executed by the processor 150. Holds various work data. The secondary storage device 154 is a non-volatile storage medium such as a hard disk or SSD (Solid State Drive), and holds various setting values in addition to various programs including an OS.

  The failure monitoring module 156 periodically monitors the health of each component, and when any failure occurs in any component, notifies the failure to another physical computer or the like. As a result, the operation mode is changed, or a line or physical computer switching operation is executed.

  The network interface 158 executes processing related to communication with other physical computers. The input device 160 typically includes a keyboard and a mouse, and receives various settings and operations from the user.

  The general-purpose interface 162 typically includes a USB (Universal Serial Bus) interface, a serial communication interface according to RS-232C, a parallel communication interface, and the like, and exchanges data with an external device or the like.

<Functional configuration>
FIG. 5 is a schematic diagram showing a functional configuration of physical computers 100A and 100B according to the present embodiment. Referring to FIG. 5, physical computers 100A and 100B include management units 202A and 202B, update control units 204A and 204B, and switching units 206A and 206B, respectively. Each of these functions is realized by the processor 150 executing a program stored in the secondary storage device 154, for example. Note that some or all of these functions may be implemented by hardware. The physical computers 100A and 100B further include storage units 200A and 200B realized by the main storage device 152 and the secondary storage device 154, respectively.

  In the following description, it is assumed that the physical computers 100A and 100B are operating as standby and active physical computers, respectively. Since each functional configuration of the physical computer 100B is the same as each functional configuration of the corresponding physical computer 100A, detailed description thereof will not be given.

  The storage unit 200A includes shared storage areas 111A and 112A that store common information that is commonly used in each of the virtual machine groups 10A to 30A, and dedicated storage areas 121A, 122A, which correspond to the virtual machines 10A, 20A, and 30A, respectively. 123A.

  The management unit 202A manages the virtual machine groups 10A to 30A. Specifically, the management unit 202A manages the correspondence relationship between the virtual disks 11A to 31A recognized in the virtual machine groups 10A to 30A and the shared storage areas 111A and 112A. More specifically, the management unit 202A allocates all of the virtual disks 11A to 31A to either the shared storage area 111A or the shared storage area 112A.

  The management unit 202A manages the correspondence between the virtual disks 12A to 32A recognized in the virtual machine groups 10A to 30A and the dedicated storage areas 121A to 123A. More specifically, the management unit 202A allocates the virtual disks 12A to 32A to the dedicated storage areas 121A to 123A, respectively.

  The management unit 202A monitors the connection (allocation) state of the shared storage areas 111A and 112A, the dedicated storage areas 121A to 123A, and the virtual machines 10A to 30A, and stores the information tables 400 and 500 based on the monitoring results. create.

  When the virtual disks 11A to 31A are assigned to the shared storage area 111A, the update control unit 204A performs an update process of the common information stored in the shared storage area 112A based on the reception of the common information update request. Run.

  Specifically, the update control unit 204A accepts an update request for common information from one virtual machine (for example, the virtual machine 10A) among the plurality of virtual machines 10A to 30A. Note that the virtual machine 10A transmits the update request to the update control unit 204A based on, for example, receiving an update instruction for common information from the user of the virtual machine 10A.

  Based on the update request, the update control unit 204A inquires of the management unit 202A about the current allocation state of the shared storage area. As a response to the inquiry, the management unit 202A notifies, for example, that all of the virtual disks 11A to 31A are allocated to the shared storage area 111A. The update control unit 204A selects the shared storage area 112A to which the virtual disks 11A to 31A are not allocated among the shared storage areas 111A and 112A as an update target. The update control unit 204A instructs the management unit 202A to allocate the virtual disk 11A to the shared storage area 112A in a readable / writable state.

  The management unit 202A allocates the virtual disk 11A to the shared storage area 112A according to the instruction and restarts the virtual machine 10A. As a result, the virtual machine 10A is started with the shared storage area 112A assigned to the virtual disk 11A and the dedicated storage area 121A assigned to the virtual disk 12A.

  Subsequently, the update control unit 204A instructs the virtual computer 10A to update the common information stored in the shared storage area 112A. The virtual machine 10A updates the contents of the common information (system file, registry information, etc.) by applying a patch and installing an application.

  When the update control unit 204A receives a notification of completion of updating of the common information from the virtual machine 10A, the update control unit 204A instructs the management unit 202A to set the shared storage area 112A to read-only. The management unit 202A sets the shared storage area 112A to read-only according to the instruction, and restarts the virtual machine 10A.

  In addition, after the virtual machine 10A is restarted, the management unit 202A assigns the virtual disk 21A to the shared storage area 112A set to read-only, assigns the virtual disk 22A to the dedicated storage area 122A, and restarts the virtual machine 20A. Start. Further, the management unit 202A allocates the virtual disk 31A to the shared storage area 112A set to read-only, allocates the virtual disk 32A to the dedicated storage area 123A, and restarts the virtual computer 30A. That is, when the update of the common information stored in the shared storage area 112A is completed, the management unit 202A assigns each of the virtual disks 21A and 31A assigned to the shared storage area 111A to the shared storage area 112A. Reassign.

  When the management unit 202A causes the virtual disks 11A to 31A to be assigned to the shared storage area 112A, the update control unit 204A uses the common information stored in the shared storage area 111A to which no virtual computer is assigned. Execute the update process.

  Specifically, the update control unit 204A instructs the management unit 202A to allocate the virtual disk 11A to the shared storage area 111A in a readable / writable state. The management unit 202A allocates the virtual disk 11A to the shared storage area 111A according to the instruction and restarts the virtual machine 10A. Subsequently, the update control unit 204A instructs the virtual computer 10A to update the common information stored in the shared storage area 111A. When the update control unit 204A receives a notification of the end of the update of the common information from the virtual computer 10A, the update control unit 204A instructs the management unit 202A to set the shared storage area 111A to read-only and to allocate the virtual disk 11A to the shared storage area 112A. To do.

  As a result, the common information stored in the shared storage areas 111A and 112A has the same content, and the shared storage area 112A is allocated to the virtual disks 11A to 31A.

  The switching unit 206A switches the system of the physical computer 100A to an active system or a standby system. Here, it is assumed that the physical computer 100A is set as a standby system. Therefore, the switching unit 206A in the standby physical computer 100A transmits a system switching request to the active physical computer 100B when the update of the common information is completed. When the update of the common information is completed, all virtual machines 10A to 30A are allocated to one shared storage area (here, the shared storage area 112A), and the shared storage areas 111A and 112A are assigned. This is a case where the update of the stored common information has been completed.

  When the switching unit 206A receives a response to the switching request from the switching unit 206B of the physical computer 100B, the switching unit 206A switches the system of the physical computer 100A from the standby system to the active system. The switching unit 206B of the physical computer 100B switches the system of the physical computer 100B from the active system to the standby system. Similarly, the physical computer 100B also updates the common information.

<Processing procedure>
Next, the flow of updating the common information in each of the standby and active physical computers will be described more specifically with reference to FIGS. Here, in the initial state of the flowchart, it is assumed that the physical computers 100A and 100B operate as standby and active physical computers, respectively.

  FIG. 6 is a flowchart showing a processing procedure of standby-system physical computer 100A according to the present embodiment. Typically, each step shown in FIG. 6 is executed by the processor 150 of the physical computer 100A.

  Referring to FIG. 6, the processor 150 of the physical computer 100 </ b> A uses a virtual machine (here, referred to as a virtual machine 10 </ b> A) among a plurality of virtual machines 10 </ b> A to 30 </ b> A via an input device 160. It is determined whether or not a shared information update request has been received (step S10).

  If an update request has not been received (NO in step S10), processor 150 repeats the process of step S10. If an update request has been received (YES in step S10), processor 150 selects a shared storage area to be updated (step S12). Specifically, the processor 150 refers to the information table 500 and selects the shared storage area 112A to which the virtual disks 11A to 31A are not assigned as an update target.

  Next, the processor 150 allocates the virtual disk 11A of the virtual machine 10A to the selected shared storage area 112A (step S14). The processor 150 sets the shared storage area 112A to be readable and writable, and restarts the virtual machine 10A (step S16). As a result, the virtual machine 10A is started in a state where the virtual disks 11A and 12A are allocated to the shared storage area 112A and the dedicated storage area 121A, respectively.

  The processor 150 uses the virtual computer 10A to update the common information stored in the shared storage area 112A set to be readable and writable (step S18). The processor 150 sets the shared storage area 112A that has been updated to read-only, and restarts the virtual machine 10A (step S20). Furthermore, the processor 150 allocates the virtual disks 21A and 31A of the virtual machines 20A and 30A to the shared storage area 112A (step S22).

  The processor 150 restarts the virtual machines 20A and 30A (step S24). As a result, the virtual machine 20A starts up with the virtual disks 21A and 22A allocated to the shared storage area 112A and the dedicated storage area 121A, respectively. The virtual computer 30A starts up with virtual disks 31A and 32A allocated to the shared storage area 112A and the dedicated storage area 121A, respectively.

  Next, the processor 150 executes a process for updating the common information stored in the shared storage area 111A to which no virtual machine is assigned (step S26). Specifically, the processor 150 allocates the virtual disk 11A of the virtual machine 10A to the shared storage area 111A set to be readable and writable, and restarts the virtual machine 10A. The processor 150 updates the common information stored in the shared storage area 111A using the virtual computer 10A. The processor 150 sets the shared storage area 111A that has been updated to read-only, assigns the virtual disk 11A to the shared storage area 112A, and restarts the virtual machine 10A.

  Next, the processor 150 transmits a switching request for switching the standby physical computer 100A to the active system to the active physical computer 100B (step S28). At this time, the processor 150 may notify the physical computer 100B that the update of the common information has been completed.

  When the processor 150 receives a response to the switching request (response to permit switching) from the physical computer 100B, the processor 150 switches the system of the physical computer 100A to the active system (step S30), and ends the processing.

  FIG. 7 is a flowchart showing a processing procedure of the active physical computer 100B according to the present embodiment. Typically, each step shown in FIG. 7 is executed by the processor 150 of the physical computer 100B.

  Referring to FIG. 7, the processor 150 of the active physical computer 100B determines whether or not a system switching request has been received from the standby physical computer 100A (step S50). If the switching request has not been received (NO in step S50), processor 150 repeats the process of step S50. When the switching request is received (YES in step S50), the processor 150 transmits a response indicating that the system switching is permitted to the physical computer 100A (step S52), and sets the system of the physical computer 100B to the standby system. Switching (step S54).

  The processing of steps S56 to S70 is the same as the processing of steps S12 to S26 in FIG. 6 (corresponding to the case where the sign of “A” is replaced with “B”), respectively. Therefore, detailed description thereof will not be repeated.

<Advantages>
According to the present embodiment, two shared storage areas for storing common information are provided in the physical computer, and update processing of the common information stored in one shared storage area is performed using one virtual machine. Even during execution, the remaining virtual machines are connected to the other shared storage area. Therefore, it is possible to realize a state in which the redundant configuration of the standby system and the active system is maintained for at least the remaining virtual machines.

  According to this embodiment, after the common information is updated using one virtual machine, it is only necessary to allocate the corresponding virtual disk to the updated shared storage area and restart the remaining virtual machines. . Therefore, even when the number of virtual machines provided in the physical computer increases, the time required for updating the common information does not change.

  According to the present embodiment, in a computer system including active and standby physical computers in which a plurality of virtual computers are constructed, when updating information common to these virtual computers, the update time is increased. In addition, since it is possible to maintain the duplex configuration of the system as much as possible, the reliability of the computer system can be improved.

<Modification>
In the above-described embodiment, a configuration in which the common information is updated using any one of the virtual machines 10A to 30A using the common information stored in the shared storage areas 111A and 112A (for example, the virtual machine 10A). Explained. In the modification of the present embodiment, a configuration will be described in which a virtual computer dedicated to update processing that does not use the common information is newly constructed in the physical computer, and the common information is updated using the virtual computer.

  FIG. 8 is a diagram illustrating a configuration example of a computer system 1100 according to the modification of the present embodiment. Referring to FIG. 8, a computer system 1100 includes two physical computers 100A1 and 100B1 that are duplicated. The physical computer 100A1 corresponds to a virtual computer 40A added to the physical computer 100A in FIG. 1 and a dedicated storage area 124A added to the dedicated storage areas 121A to 123A in FIG. Similarly, the physical computer 100B1 corresponds to the physical computer 100B in FIG. 1 with the virtual computer 40B added and the dedicated storage regions 121B to 123B in FIG. 1 added with the dedicated storage region 124B.

  The virtual machine 40A is a virtual machine built exclusively for updating common information, and includes a virtual disk 42A. Note that the virtual machine 40A is different from the other virtual machines 10A to 30A in that the process using the common information is not executed during normal operation. Specifically, the virtual disk 42A of the virtual computer 40A is not allocated to the shared storage areas 111A and 112A for storing common information during normal operation, and only when the shared information is updated, the shared storage area 111A or 112A. More specifically, the virtual disk 42A is allocated to the dedicated storage area 124A and one of the shared storage areas 111A and 112A when the common information is updated.

  In the above-described embodiment, the update control unit 204A instructs one virtual machine among the plurality of virtual machines 10A to 30A to execute the update of common information. Instructing a specific virtual machine 40A other than the plurality of virtual machines 10A to 30A not to use the common information to update the common information.

  FIG. 9 is a flowchart showing the processing procedure of the standby physical computer 100A1 according to the modification of the present embodiment. Referring to FIG. 9, the processor 150 of the physical computer 100A1 determines whether or not a shared information update request has been received from a user using the virtual computer 40A dedicated for update via the input device 160 (step S80). .

  When the update request is received (YES in step S80), the processor 150 refers to the information table 500 and selects the shared storage area 112A to which the virtual disks 11A to 31A are not allocated (step S82).

  Next, the processor 150 allocates the virtual disk 42A of the virtual machine 40A to the shared storage area 112A (step S84), sets the shared storage area 112A to be readable and writable, and restarts the virtual machine 40A (step S86). . As a result, the virtual computer 40A starts up with the virtual disk 42A allocated to the shared storage area 112A and the dedicated storage area 124A.

  The processor 150 updates the common information stored in the shared storage area 112A using the virtual machine 40A (step S88). The processor 150 sets the shared storage area 112A that has been updated to read-only (step S90), and allocates the virtual disks 11A to 31A of the virtual machines 10A to 30A to the shared storage area 112A (step S92). The processor 150 restarts the virtual machines 10A to 30A (step S94). Thereby, the virtual machines 10A to 30A are started in a state where the shared storage area 112A is allocated to the virtual disks 11A to 31A and the dedicated storage areas 121A to 123A are allocated to the virtual disks 12A to 32A, respectively.

  Next, the processor 150 executes a process for updating the common information stored in the shared storage area 111A (step S96). Specifically, the processor 150 allocates the virtual disk 42A of the virtual machine 40A to the shared storage area 111A and restarts the virtual machine 40A. The processor 150 updates the common information stored in the shared storage area 111A using the virtual computer 40A. The processor 150 sets the updated shared storage area 111A to read-only, allocates the virtual disk 42A only to the dedicated storage area 124A, and restarts the virtual machine 40A.

  Since the processes of steps S98 and S100 are the same as the processes of steps S28 and S30 in FIG. 6, detailed description thereof will not be repeated.

  Further, the processing procedure of the active physical computer 100B1 is the same as the processing in steps S82 to S96 described above after executing the processing in steps S50 to S54 in FIG. 7 (the symbol “A” is denoted by “B”). The detailed description thereof will not be repeated.

(advantage)
According to the modification of the present embodiment, since a virtual machine dedicated to update is newly constructed, a plurality of pieces of common information are used even while the update process of the common information stored in one shared storage area is being executed. The virtual machine remains connected to the other shared storage area. Therefore, it is possible to realize a state in which the standby system and the active system are maintained at least for the plurality of virtual machines.

[Other embodiments]
In the above-described embodiment, the configuration in which the update of the common information is executed when an update request from the user is received has been described. However, the configuration is not limited to the configuration, and after the common information is updated, The configuration may be such that, when a software failure is detected in the computer, the common information is updated in the standby physical computer.

  Specifically, it is assumed that a software failure has occurred in the physical computer 100A after the physical computer 100A has been switched to the active system after the update of the common information (after the processing in step S30 in FIG. 6). The A software failure is a failure set in advance as a software failure related to a physical computer. For example, a behavior contrary to the creator's intention (abnormal termination, abnormal stop, etc.) due to a defect in an application program or a bug in the software. It is to become.

  When the processor 150 of the physical computer 100A switched to the active system detects a software failure, it transmits a system switch request to the standby physical computer 100B. Subsequently, the processor 150 (switching unit) receives a system switching response from the physical computer 100B, and switches the system of the physical computer 100A from the active system to the standby system. Then, the processor 150 (update control unit) executes a process of updating the updated common information to the pre-update common information. This process is executed in the same procedure as the update process described above (for example, steps S12 to S26). When the processing is completed, the system switching is performed again (for example, steps S28 to S30), and the physical computer 100B similarly performs processing for updating the common information before the update (see FIG. 7). Note that the common information before update may be stored in the shared storage area without being deleted, or may be stored in another storage area.

  The configuration illustrated as the above-described embodiment is an example of the configuration of the present invention, and can be combined with another known technique, and a part of the configuration is omitted without departing from the gist of the present invention. It is also possible to change the configuration.

  In the above-described embodiment, the processing and configuration described in the other embodiments may be adopted as appropriate.

  The embodiment disclosed this time should be considered as illustrative in all points and not restrictive. The scope of the present invention is defined by the terms of the claims, rather than the description above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims.

  10, 20, 30, 40A, 40B Virtual computer, 11, 12, 21, 22, 31, 32, 42A Virtual disk, 100 Physical computer, 111, 112 Shared storage area, 121, 122, 123, 124A, 124B Dedicated storage Area, 150 processor, 152 main storage device, 154 secondary storage device, 156 fault monitoring module, 158 network interface, 160 input device, 162 general-purpose interface, 164 internal bus, 200A, 200B storage unit, 202A, 202B management unit, 204A , 204B update control unit, 206A, 206B switching unit, 400, 500 information table, 1000, 1100 computer system.

Claims (4)

A computer system comprising an active and standby physical computer in which a virtual environment is constructed,
Each of the active and standby physical computers
A storage unit having first and second shared storage areas for storing common information used in common in each of the plurality of virtual machines;
A management unit that manages the correspondence between the plurality of virtual disks recognized in each of the plurality of virtual machines and the first and second shared storage areas;
When the plurality of virtual disks are allocated to the first shared storage area, the update of the common information stored in the second shared storage area is performed based on reception of the update request for the common information. An update control unit that executes processing;
Including a switching unit for switching the physical computer system to an active system or a standby system,
When the update of the common information stored in the second shared storage area in the standby physical computer ends, the management unit in the standby physical computer allocates to the first shared storage area The virtual disk being reassigned to the second shared storage area,
When the virtual disk allocated to the first shared storage area is reassigned to the second shared storage area by the management unit of the standby physical computer, The update control unit further executes an update process of the common information stored in the first shared storage area;
The switching unit in the standby physical computer operates a system switch request when the update of the common information stored in the first and second shared storage areas in the standby physical computer is completed. A computer system for transmitting to the physical computer of the system.   The computer system according to claim 1, wherein the update control unit instructs one virtual computer of the plurality of virtual computers to update the common information.   The computer system according to claim 1, wherein the update control unit instructs a specific virtual machine other than the plurality of virtual machines that does not use the common information to update the common information. When a software failure occurs in the active physical computer after the update of the common information is completed, the switching unit of the active physical computer transmits a system switch request to the standby physical computer, Switch the active physical computer to the standby system,
The computer system according to any one of claims 1 to 3, wherein the update control unit of the physical computer switched to the standby system re-updates the updated common information to the common information before update. .

Images