[go: up one dir, main page]

WO2011074284A1 - Procédé de migration pour machine virtuelle, système de machines virtuelles et support de stockage contenant un programme - Google Patents

Procédé de migration pour machine virtuelle, système de machines virtuelles et support de stockage contenant un programme Download PDF

Info

Publication number
WO2011074284A1
WO2011074284A1 PCT/JP2010/063273 JP2010063273W WO2011074284A1 WO 2011074284 A1 WO2011074284 A1 WO 2011074284A1 JP 2010063273 W JP2010063273 W JP 2010063273W WO 2011074284 A1 WO2011074284 A1 WO 2011074284A1
Authority
WO
WIPO (PCT)
Prior art keywords
computer
virtual
physical
management
virtual machine
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2010/063273
Other languages
English (en)
Japanese (ja)
Inventor
齋藤　浩
高本　良史
正芳 北村
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Ltd
Original Assignee
Hitachi Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hitachi Ltd filed Critical Hitachi Ltd
Publication of WO2011074284A1 publication Critical patent/WO2011074284A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2023—Failover techniques
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2035—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant without idle spare hardware
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2043—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant where the redundant components share a common memory address space
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
    • G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
    • G06F9/45533—Hypervisors; Virtual machine monitors
    • G06F9/45558—Hypervisor-specific management and integration aspects
    • G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/815—Virtual

Definitions

  • the present invention relates to a method and system for improving the reliability of a virtual server.
  • the server virtualization technology is a technology capable of operating a plurality of virtual servers on a single physical server.
  • Physical servers have resources such as processors and memory.
  • Server virtualization technology divides physical resources and assigns each of the divided resources to different virtual servers on a single physical server. Run multiple virtual servers at the same time.
  • the need for server virtualization technology has increased due to improved processor performance and lower costs for resources such as memory.
  • the problem to be solved by the present invention is to achieve high reliability at low cost even in a virtualized server environment. In particular, it is to reduce the number of alternate (standby) servers for high reliability.
  • a virtual server In order for a server to fail and to switch to a replacement server, it is necessary to know exactly which virtual server was running. Unlike a physical server, a virtual server can be increased or decreased relatively easily if there are sufficient resources such as a processor and memory of the physical server.
  • the above-described conventional example has a problem that a failure cannot be recovered when resources are not sufficient. For example, when a serious failure occurs in a virtual server to which a resource with a CPU of 3 GHz and a memory of 4 GB is allocated, there must be a physical server having an equivalent resource.
  • the present invention has been made in view of the above problems, and enables a virtual server to take over even if the takeover destination physical server has fewer resources than the takeover source physical server.
  • the purpose is to do.
  • a typical example of the invention disclosed in this specification is as follows. That is, a virtual computer system including a plurality of physical computers having a virtualization unit that includes a processor and a memory to construct a plurality of virtual computers, and a management computer that includes the processor and the memory and is connected to the physical computer via a network.
  • FIG. 1 is a block diagram of a virtual machine system to which the present invention is applied.
  • the center of control in this embodiment is the management server 101.
  • the management server 101 includes a failure recovery unit 102, a virtual server definition information management unit 103, a failure sign management unit 104, a virtual server recovery method selection unit 105, a virtual server recovery unit 106, a virtual server management table 107, a server management table 108, a virtual server A server definition information table 118 and a virtual server return unit 119 are included.
  • the management server 101 manages the network switch 120, the physical servers 111-1 to 111-n, the server virtualization mechanism 110, the storage switch 112, the virtual server 109, and the disk array device 116.
  • the server virtualization mechanism 110 has a function of making the physical server 111 appear to the plurality of virtual servers 109, and can integrate the plurality of servers into the single physical server 111.
  • the server virtualization mechanism 110 can be configured by a hypervisor, a VMM (Virtual Machine Manager), or the like.
  • the physical server 111-1 to 111-n is collectively referred to as the physical server 111.
  • the disk array device 116 is connected to the physical server 111 via the storage switch 112.
  • the storage switch 112 that connects the disk array device 116 and the physical server 111 constitutes a SAN (Storage Area Network).
  • the network switch 120 that connects the management server 101 and the physical server 111 constitutes the network 207 shown in FIG.
  • the disk array device 116 has a virtual server image storage disk 114 storing a program executed by the virtual server 109 and a definition information storage disk 115 storing computer resource allocation information of the virtual server 109.
  • a highly reliable system is configured by moving a virtual server affected by the failure or the failure sign to another physical server.
  • the failure recovery unit 102 controls recovery of the physical server 111 and recovery of the virtual server 109 when the occurrence of a failure of the physical server 111 or a failure sign is detected.
  • the virtual server definition information management unit 103 performs processing for improving reliability by moving the virtual server 109 even when there is not enough free resources in the physical server 111 that is the takeover destination of the virtual server 109.
  • the failure sign management unit 104 checks the occurrence of a failure or a sign of failure for each physical server 111 managed by the management server 101.
  • the virtual server recovery method selection unit 105 selects the virtual server 109 based on the detection result of the failure or predictive failure of the physical server 111, the priority of the virtual server 109 affected by the failure, and the availability of computer resources of the physical server 111. Process to select the recovery method.
  • the virtual server recovery unit 106 executes recovery of the virtual server 109 based on the execution result of the virtual server recovery method selection unit 105.
  • the virtual server management table 107 stores detailed information regarding the server virtualization mechanism 110.
  • the server management table 108 manages resources of the physical server 111.
  • the virtual server definition information table 118 stores the priority for each virtual server 109, the position of the original (original) allocation information to which the resources of the physical server 111 are allocated, and information regarding the takeover of the virtual server.
  • the virtual server return unit 119 executes a process for returning the virtual server 109 moved to the standby physical server 111 to the original active physical server 111.
  • the physical servers 111-1 and 111-2 can configure the active system
  • the physical server 111-n can configure the standby system.
  • FIG. 2 is a block diagram showing the configuration of the management server 101 in the present invention.
  • the management server 101 includes a memory 202, a processor 203, a FCA (Fibre Channel Adapter) 204, a NIC (Network Interface Card) 205, and a BMC (Baseboard Management Controller) 206.
  • FCA Fibre Channel Adapter
  • NIC Network Interface Card
  • BMC Base Management Controller
  • the processor 203 executes various programs stored in the memory 202.
  • the FCA 204 is connected to an external storage (for example, the disk array device 116).
  • the NIC 205 and the BMC 206 are connected to the network 207.
  • the NIC 205 communicates with other servers via the network 207 mainly in response to requests from various programs on the memory 202.
  • the BMC 206 is used to detect a failure of the management server 101 and communicate with other servers via the network 207.
  • the NIC 205 and the BMC 206 are connected to the same network 207, but may be connected to different networks.
  • one FCA 204 and one NIC 205 are provided, but a plurality of FCAs 204 and NICs 205 may exist.
  • a failure recovery unit 102 On the memory 202, a failure recovery unit 102, a virtual server definition information management unit 103, a failure sign management unit 104, a virtual server recovery method selection unit 105, a virtual server recovery unit 106, a virtual server management table 107, a server management table 108,
  • the virtual server definition information table 118 is stored as a program.
  • Each program stored in the memory 202 is executed by the processor 203.
  • Each of the above programs is stored in a storage (for example, the disk array device 116) as a storage medium, and loaded into the memory 202 as necessary.
  • FIG. 3 is a block diagram showing a detailed configuration of the physical server 111 on which the server virtualization mechanism 110 to be managed by the management server 101 is operating.
  • the physical server 111 includes a memory 301, a processor 303, an FCA (Fibre Channel Adapter) 304, an NIC (Network Interface Card) 305, and a BMC (Baseboard Management Controller) 306.
  • FCA Fibre Channel Adapter
  • NIC Network Interface Card
  • BMC Base Management Controller
  • the processor 303 executes various programs stored in the memory 301.
  • the FCA 304 is connected to the disk array device 116 via the storage switch 112 shown in FIG.
  • the NIC 305 and the BMC 306 are connected to the network 207.
  • the NIC 305 mainly communicates with other servers in response to requests from various programs on the memory 301.
  • the BMC 306 is used to detect a failure of the physical server 111 and communicate with the management server 101 and other servers via the network 207.
  • the NIC 305 and the BMC 306 are connected to the same network, but may be connected to different networks.
  • one FCA 304 and one NIC 305 are provided, but a plurality of FCAs 304 and NICs 305 may exist.
  • a plurality of virtual servers 109-1 to 109-m can be constructed by operating the server virtualization mechanism 110 on the memory 301.
  • the virtual servers 109-1 to 109 -m are collectively referred to as the virtual server 109.
  • Each virtual server 109 can operate an OS (Operating System) 302 independently.
  • OS Operating System
  • a plurality of virtual servers 109 can be constructed on the server virtualization mechanism 110.
  • the virtual server 109 reads and executes a predetermined virtual server OS image 308 in the virtual server image storage disk 114 set in advance in the disk array device 116, and thereby the independent virtual server 109 is constructed. Is done. Also, the definition information storage disk 115 of the disk array device 116 stores virtual server definition information 309 in which definition information of each virtual server 109 is stored.
  • the virtual server definition information 309 of the disk array device 116 is shared from a plurality of physical servers 111 via the storage switch 112, and can be set so that it can be referenced from any physical server 111.
  • the virtual server OS image 308 and the virtual server definition information 309 for each of the plurality of virtual servers 109 completely different OSs and applications can be operated on the single physical server 301 for each virtual server 109.
  • a control I / F (Interface) 311 is an interface for controlling the server virtualization mechanism 110 from the external management server 101 or the like via the network 207.
  • the management server 101 can create or delete the virtual server 109 on the physical server 111 via the control I / F 311. For this reason, a network address is set in the control I / F 311 of the virtualization mechanism 110 of each physical server 111.
  • FIG. 4 is a block diagram showing an outline of the operation of the virtual computer system of the present invention.
  • the management server 101 is connected to a plurality of physical servers 111 to be managed via a network 207, and can transfer failure information, failure sign information, control information, and the like of each physical server 111.
  • the management server 101 detects (1) the occurrence of a failure or a failure sign of the physical server 111
  • control is performed to move the virtual server 109 affected by the detection of the failure or the failure sign to another physical server 111.
  • the definition information 309 of the virtual server is updated according to the actual operating status and the free computer resource status that are the actual operating status.
  • the updated virtual server definition information 309 makes it possible to recover the virtual server 109 from a failure or a failure sign by using the physical server 111-n having fewer computer resources than the physical server 111-1 before the migration (3).
  • FIG. 5 is an explanatory diagram showing details of the server management table 108.
  • the server management table 108 stores detailed information regarding the physical server 111.
  • the physical server identifier 501 stores an identifier for specifying the physical server 111.
  • the startup disk 502 indicates the location (for example, path) of the startup disk of the physical server 111.
  • the server identifier 503 indicates a unique identifier (for example, World Wide Name: WWN) that the FCA 304 connected to the disk array device 116 has.
  • the server mode 504 indicates the operating state of the physical server 111 and stores information for determining whether or not the server virtualization mechanism 110 is operating.
  • the processor / memory 505 stores processor information and memory capacity of the physical server 111.
  • the processor information includes the processor clock speed and the number of cores.
  • the network identifier 506 stores information for identifying the NIC 205 that the physical server 111 has. When there are a plurality of NICs 205 in one physical server 111, a plurality of identifiers are stored.
  • the network port 507 stores the port number of the network switch 120 to which the NIC 205 is connected. This is stored for setting the VLAN of the network switch when maintaining the network security of the physical server 111.
  • the disk 508 stores the identifier of the disk in the disk array device 116 of the physical server 111.
  • the disk identifier is, for example, LUN (Logical Unit Number), and LUN 10 is described in a plurality of physical servers 111 (servers 1 to 4 in the figure) in FIG. It can be shared from.
  • the virtualization mechanism identifier 509 stores an identifier that identifies the server virtualization mechanism 110 when the server virtualization mechanism 110 is operating on the physical server 111. This virtualization mechanism identifier 509 is associated with a server virtualization mechanism management table (virtual server management table 107) described later.
  • the server status 510 indicates the status and role of the physical server 111, and stores, for example, information indicating whether it is an active system or a standby system. In the embodiment of the present invention, it is used when performing a process of switching to a standby system when a failure occurs in any of the active systems.
  • FIG. 6 is an explanatory diagram showing details of the virtual server management table 107.
  • the virtual server management table 107 stores detailed information regarding the server virtualization mechanism 110 of each physical server 111.
  • the virtualization mechanism identifier 601 stores information for identifying the server virtualization mechanism 110 for each physical server 111 managed by the management server 101.
  • the control I / F address 602 stores a network address serving as access information to the control I / F 311 that controls the server virtualization mechanism 110 from the outside.
  • the virtual server identifier 603 stores a unique identifier for each virtual server 109.
  • the virtual server OS image 604 stores the OS image used by the virtual server 109 and the location (path) of the virtual server OS image 308.
  • the processor / memory allocation amount 605 indicates a computer resource amount allocated to the virtual server.
  • the computer resource amount includes, for example, the processor clock speed and the memory capacity allocated to the virtual server 109.
  • the state 606 stores information indicating whether or not the virtual server 109 is currently operating.
  • the processor / memory actual usage 607 stores the usage rate and memory capacity of the processor actually used by the virtual server.
  • the processor / memory actual usage 607 includes means for collecting actual usage (performance information) for resources periodically allocated from, for example, the OS running on the server virtualization mechanism 110 or the virtual server 109. Can be acquired. As the processor / memory actual usage 607, a method of storing an average usage (or usage rate) per unit time can be considered.
  • the average usage rate of the processor 303 is represented by “GHz” in terms of the clock speed, and the average usage amount of the memory 301 is represented by “GB”.
  • the average usage rate of the processor 303 is an actual usage rate for the resource (virtual processor) of the processor 303 allocated to the virtual server 109.
  • the network assignment 608 stores a NIC identifier of the virtual server and assignment information between the NIC 305 of the physical server 111 corresponding to the NIC identifier.
  • the disk 609 stores the location of the virtual server OS image 308 assigned to the virtual server 109 and the image file for data storage.
  • FIG. 7 shows the configuration of the virtual server definition information table 118.
  • the virtual server identifier 701 stores a unique identifier for each virtual server 109.
  • the virtual server priority 702 stores the importance of the virtual server 109 as a numerical value. The priority is “1” having the highest importance, and the importance decreases as the numerical value increases.
  • the numerical value of the virtual server priority 702 is input according to the priority of a task executed on the virtual server when the administrator generates a virtual server from the management server 101 or the like.
  • the original definition information 703 stores the location where the definition information of the original of the virtual server 109 (a state initially assigned to the physical server 111) is stored.
  • the present invention is characterized in that the reliability is improved by moving a virtual server to another physical server 111 by detecting the occurrence of a failure or a failure sign, but the definition information depends on the situation of the destination computer resource at that time. There is a case to change.
  • the definition information of the original virtual server 109 is required when returning the virtual server 109 to the original physical server 111 after removing the cause of the occurrence of the failure or the failure sign.
  • the original definition information 703 can be referred to and the configuration of the original virtual server 109 can be always restored.
  • the moving definition information 704 stores definition information of the virtual server 109 that is updated when the virtual server 109 is moved.
  • the movement date and time 705 stores the date and time when the virtual server 109 was moved.
  • the movement definition information 704 and the movement date / time 705 may store a history. By leaving a history of changes in allocated resources that occur during migration, the location of the physical server 111 where the failure has occurred can be easily identified. This facilitates failure analysis. Further, the movement definition information 704 and the movement date and time 705 may be added each time the virtual server 109 moves when the virtual server 109 has moved a plurality of times. For example, after detecting a failure sign and moving the virtual server 109, it is possible to detect the failure sign again at the destination and move the virtual server 109 further.
  • the virtual server 109 moves a plurality of times, but the movement definition information 704 and the movement date / time 705 are added each time the virtual server 109 moves.
  • the migration order may be restored in an order that goes back to the original order.
  • the virtual server 109 may be moved based on the original definition information 703. Where to return can be flexibly dealt with in accordance with the purpose of moving the virtual server 109, such as repairing the physical server 111 or moving to the physical server 111 with higher performance.
  • having the movement history of the virtual server 109 a plurality of times can increase the options for returning to the physical server 111 and moving, so that the virtual server 109 can be operated more flexibly. Become.
  • FIG. 8 is an explanatory diagram showing the contents of the virtual server definition information 309.
  • the virtual server name 801 stores the name of the virtual server 109.
  • the allocation resource 802 suggests the processor allocation amount, the memory allocation amount, the network allocation information, the location where the virtual server OS image 308 is stored, and generates the virtual server 109 such as the location where the data disk image is stored. Information for storing is stored.
  • the priority 803 stores the same content as the virtual server priority 702 stored in the virtual server definition information table 118.
  • movement history 804 movement history information of the virtual server 109 is stored.
  • the movement history 804 can be used as information for determining a movement destination when the virtual server 109 moves. For example, when the movement histories 804 of a plurality of definition information are aggregated and the movement frequency is high due to a failure sign for a specific virtual server 109, it means that there is a high risk of lowering the service level of the virtual server 109. Therefore, the movement history 804 can also be used as analysis information when the physical server 111 with higher reliability is selected and the virtual server 109 is moved.
  • Definition information 805 indicates the storage location of the original definition information of the virtual server 109.
  • the definition information used at the destination may be stored as a history each time the virtual server 109 moves.
  • FIG. 9 is a flowchart showing an outline of processing performed in the failure recovery unit 102. This flowchart is executed by the management server 101 at a predetermined cycle.
  • the failure recovery unit 102 calls the failure sign management unit 104.
  • the failure sign management unit 104 checks for occurrence of a failure or a failure sign for each physical server 111 that is the management target of the management server 101, as will be described later. That is, the failure sign management unit 104 inquires the BMC 203 and the failure sign detection unit 310 of each physical server 111 about the operation information, and acquires the operation information for each server 111.
  • step 902 the failure sign management unit 104 determines the occurrence of a failure or the presence or absence of a failure sign for each operation information of each server 111.
  • the failure sign management unit 104 detects the occurrence of a failure or a failure sign
  • the failure sign management unit 104 identifies the physical server 111 and notifies the failure recovery unit 102, and the process proceeds to step 903.
  • the process is terminated.
  • the failure recovery unit 102 determines whether or not the virtualization mechanism is being executed on the physical server 111 in which a failure or a failure sign is detected. If the server virtualization mechanism 110 is being executed on the target physical server 111, the failure recovery unit 102 calls the virtual server 109 recovery method selection unit 105 in step 904.
  • step 904 the virtual server recovery method selection unit 105 recovers the virtual server 109 based on the detection result of the failure or the failure sign, the priority of the affected virtual server 109, and the availability of the computer resources of the physical server 111. Process to select the method. The processing of this recovery method will be described later.
  • the failure recovery unit 102 calls the virtual server recovery unit 106.
  • the virtual server recovery unit 106 executes recovery of the virtual server 109 based on the execution result of the virtual server recovery method selection unit 105 as described later.
  • step 907 the result of the recovery process is notified to the administrator. This notification is performed by displaying the result on a display device (not shown) of the management server 101.
  • step 903 if there is a failure or sign of failure from the physical server 111 in which the server virtualization mechanism 110 is not executed, the physical server 111 is recovered in step 905.
  • the recovery of the physical server 111 that is not executing the server virtualization mechanism 110 is the same as that in the conventional example, and thus will not be described in detail in this embodiment.
  • the failure recovery unit 102 detects the occurrence of a failure or a failure sign in the physical server 111 executing the server virtualization mechanism 110, the amount of computer resources actually used by the virtual server 109 Alternatively, the allocation is performed again in accordance with the ratio, the computer resources less than those when the computer resources are initially allocated are reset, and the virtual server 109 is taken over by the standby physical server 111.
  • FIG. 10 is a flowchart illustrating an example of processing performed by the failure sign management unit 104. This processing corresponds to the processing in step 901 in FIG.
  • the failure sign management unit 104 performs processing to check whether a failure or a sign of failure has occurred in the physical server 111 to be managed.
  • the failure sign management unit 104 selects a target physical server 111.
  • the failure sign management unit 104 accesses the BMC 206 of the target physical server 111, and checks whether a hardware failure or a failure sign has occurred.
  • the BMC 206 of each physical server 111 can monitor the hardware state.
  • processor 303 For example, processor 303, memory 301, temperature, fan, power supply status monitoring, and the like.
  • a failure or a failure sign is, for example, detection of a failure sign when the BMC 206 detects some failure from the processor 303 and the failure is resolved by a number of retries, and is detected as a failure when the retry does not recover. To do. The same applies to other parts.
  • a predetermined threshold value is exceeded. If the temperature remains above the threshold, it may be detected as a failure.
  • the importance level can be set in the failure predictor according to the influence level when the failure is reached.
  • the failure sign of the processor 303 is highly important because it is highly likely that the failure of the processor 303 will substantially stop the entire system when the processor 303 is stopped, but the failure sign of the memory 301 is within a range in which a bit error can be corrected.
  • the importance is low.
  • the importance may be lowered when a plurality of processors 303 are installed. In this way, it is possible to control to increase the options of the recovery means by providing the importance to the failure sign.
  • Step 1003 it is determined whether or not a hardware failure or failure sign is detected. If a failure or failure sign is detected, the process proceeds to Step 1006 and the detection result is reported to the failure recovery unit 102. To do.
  • the failure sign detection unit 310 is called in step 1004 to detect a software level failure or failure sign that cannot be detected at the hardware level. The detection result by the failure sign detection unit 310 is reported to the failure sign management unit 104 in step 1006.
  • step 1007 the failure sign management unit 104 determines whether or not all the management target physical servers 111 have been inspected. If there is an uninspected physical server 111, the processing is repeated from step 1001.
  • FIG. 11 is a flowchart illustrating an example of processing performed by the virtual server recovery method selection unit 105. This process corresponds to step 904 in FIG.
  • the virtual server recovery method selection unit 105 determines how to recover the virtual server 109 when a failure or failure sign is detected in the physical server 111.
  • a failure or a failure sign is analyzed. For example, if the failure predictor of the processor 303 is analyzed, the core number of the processor 303 that detected the failure predictor and the importance of the predictor are analyzed.
  • the virtual server recovery method selection unit 105 investigates the influence range of the failure and specifies the affected virtual server 109.
  • the virtual server recovery method selection unit 105 determines whether or not there is a high possibility that the virtual server 109 is stopped due to the detected failure or failure sign. Note that there is a high possibility that the virtual server 109 will stop, for example, when the temperature of the processor 303 of the physical server 111 exceeds a predetermined value, or when the cooling fan of the processor 303 stops, In other words, the physical server 111 is currently operating but is expected to stop in the future.
  • step 1105 the virtual server recovery method selection unit 105 checks the priority of the virtual server 109 affected by the failure. This priority can be acquired by searching the virtual server priority 702 in the virtual server definition information table 118.
  • the virtual server recovery method selection unit 105 in step 1105 causes the other physical server 111 to be free.
  • the resource is searched, and the migration destination candidate of the virtual server 109 that is likely to be stopped is determined. If there are sufficient free resources in the migration destination physical server 111, the virtual server recovery method selection unit 105 determines the recovery method of the virtual server 109 as the virtual server migration method in step 1112.
  • the virtual server recovery method selection unit 105 determines the definition change method in step 1113. If there is a low possibility that the virtual server 109 will be stopped, or if the virtual server 109 with a low priority is affected, the status is reported to the administrator at step 1110 or step 1111. These reports notify the virtual server 109 that receives a failure occurrence or a failure sign to a display device (not shown) of the management server 101. By these processes, it is possible to widen the recovery range of the failure of the virtual server 109, and it is possible to recover the failure of the virtual server 109 with higher reliability than before.
  • Step 1112 or Step 1113 This selected process will be described in detail in the process of the virtual server recovery unit 106 described later.
  • FIG. 12 is a flowchart showing an outline of processing performed by the virtual server recovery unit 106. This process corresponds to the process in step 906 of FIG.
  • the virtual server recovery unit 106 executes the recovery process of the virtual server 109 according to the recovery method (virtual server migration or definition change) determined by the virtual server recovery method selection unit 105.
  • the virtual server recovery unit 106 determines whether or not the recovery method determined by the virtual server recovery method selection unit 105 is a definition change method. If the determined recovery method is not the definition change method, that is, if the recovery method has sufficient free resources to move, the virtual server recovery unit 106 extracts necessary resources from the definition information of the virtual server 109 in step 1202. This can be realized by referring to the original definition information 703 in the virtual server definition information table 118 and referring to the contents of the definition file. In other words, it indicates that the computer resource is allocated to the physical server 111 with the occurrence of a failure or a sign of failure, and is moved to a new physical server 111.
  • step 1203 the virtual server recovery unit 106 searches the server management table 108 for a physical server 111 having a free resource equivalent to or higher than that of the physical server 111 where a failure has occurred or is predictive of failure.
  • step 1204 the virtual server recovery unit 106 allocates the computer resource of the original definition information 703 to the searched physical server 111 and moves the virtual server 109.
  • the virtual server recovery unit 106 calls the virtual server definition information management unit 103 in step 1207.
  • the called virtual server definition information management unit 103 updates the virtual server definition information 309 by reducing the allocated amount of computer resources of the migration target virtual server 109, as will be described later.
  • Step 1208 moves the virtual server 109 using the changed virtual server definition information 309 used by the virtual server definition information management unit 103 at the destination.
  • the movement of the virtual server 109 is to move the virtual server 109 onto the destination physical server 111.
  • a resource for executing the virtual server 109 is temporarily secured at both the movement source and the movement destination. Processing to secure memory 301, CPU 303, and I / O (FCA 304, NIC 305) as the migration destination, and then copy the memory information and I / O status of the migration source virtual server 109 to the migration destination virtual server 109 I do. There may be fewer computer resources to move to.
  • the processing performance of the virtual server 109 decreases, but no particular processing is required for migration.
  • the migration destination physical server 111 has a small memory capacity
  • several methods are conceivable. One is a method of making the OS 302 appear as if it has the same capacity as the migration source.
  • copying the memory 301 the unused area that does not affect the operation of the OS 302 and the cache information of the OS 302 and the application are not copied, and a program such as a driver running on the OS 302 appears to have secured the insufficient memory area. Can be realized. Note that the above processing is not necessary in the case of moving while operating and the case where the virtual server 109 is temporarily shut down and started at the destination.
  • the virtual server definition information management unit 103 performs a process for improving reliability by moving the virtual server 109 even when there are not enough free resources in the physical server 111. Specifically, in order to move the virtual server 109 as much as possible, that is, to enable protection of the virtual server 109, the definition information is changed based on free resources, priorities, and actual usage of computer resources to enable the movement. Process.
  • FIG. 13 is a flowchart showing an outline of processing performed by the virtual server definition information management unit 103. This process corresponds to the process of step 1207 in FIG.
  • the virtual server definition information management unit 103 searches the virtual server 109 for the migration target virtual server 109 from the virtual server management table 107 for the actual actual usage of computer resources.
  • the virtual server definition information management unit 103 refers to the processor / memory actual usage 607 stored in the virtual server management table 107 to obtain the actual usage of computer resources.
  • Step 1302 the virtual server definition information management unit 103 searches the virtual server management table 107, selects, for example, the physical server 111 having the largest unused resource, and acquires unused resource information.
  • step 1303 the virtual server definition information management unit 103 compares the unused resource information acquired in step 1302 with the actual usage of the computer resource acquired in step 1301. It is judged whether it is larger than. This is because when only a part of the computer resources allocated to the virtual server 109 is operating, the physical server 111 having the minimum resources necessary to maintain the service level such as the current performance is selected. Is meant to do. When the unused resource information is larger than the actual usage amount and the physical server 111 holding the minimum computer resource capable of executing the migration target virtual server 109 is found, the process proceeds to step 1307 and the virtual server definition is performed. The information management unit 103 copies the virtual server definition information 309.
  • step 1308 the virtual server definition information management unit 103 applies the virtual server definition information 309 copied in step 1307 to the virtual server definition information 309 and information on unused resources of the physical server 111 searched in step 1302. To change.
  • the virtual server definition information 309 to be moved can execute the virtual server 109 with fewer computer resources than the original virtual server definition information 309.
  • the virtual server definition information management unit 103 reflects the virtual server definition information 309 changed in step 1308 in the virtual server definition information table 118. That is, the virtual server definition information management unit 103 stores the virtual server definition information 309 that has been copied and changed to unused resource information in the definition information storage disk 115 of the disk array device 116. Then, the virtual server definition information management unit 103 adds the storage location (path) of the virtual server definition information 309 that has been copied and changed to the movement definition information 704 in the virtual server definition information table 108, and also displays the current date and time. Stored in the movement date 705. Thereby, a movement history of the virtual server 109 to be moved is generated.
  • step 1303 determines whether unused resource larger than the actual usage amount is found. If it is determined in step 1303 that no unused resource larger than the actual usage amount is found, the process proceeds to step 1304.
  • step 1304 when the virtual server 109 having the minimum free resource does not exist, the virtual server definition information management unit 103 selects, for example, the physical server 111 having the most unused resources.
  • step 1306 the allocated resources of the virtual server 109 selected in step 1305 are stripped and accommodated to the virtual server 109 having a high priority. That is, the virtual server definition information management unit 103 reduces the allocated resources of the virtual server 109 having a lower priority than the virtual server 109 to be moved, and adds the reduced allocated resources to the unused resources of the physical server 111. Then, the virtual server definition information management unit 103 allocates unused resources, which have been increased by the amount of computer resources deprived from the virtual server 109 with low priority, to the virtual server 109 to be moved. Then, the process proceeds to step 1307 described above.
  • the amount of computer resources to be deprived from the virtual server 109 with low priority refers to the virtual server management table 107 and the processor / memory allocation 605 to the processor / memory actual use amount 607 of the virtual server 109 to be deprived.
  • the virtual server definition information management unit 103 updates the virtual server definition information 309 of the virtual server 109 to be stripped with the reduced computer resources.
  • the virtual server definition information management unit 103 when the computer resource stripped from one virtual server 109 cannot secure a computer resource that can execute the migration target virtual server 109, is more than the migration target virtual server 109. Computer resources are stripped from a plurality of low priority virtual servers 109.
  • the above processing makes it possible to recover the virtual server 109 affected by the detection of the state of a free resource, a failure, or a failure sign in a stepwise manner.
  • the computer resources allocated to the migration target virtual server 109 are reduced to the computer resources actually used, and the unused resources of the migration destination physical server 111 are allocated to the migration target virtual server 109, thereby minimizing the necessary amount.
  • Computer resources can be secured in the migration destination physical server 111 to guarantee the operation of the virtual server 109.
  • step 1303 it is determined whether the unused resource information is larger than the actual usage amount. However, it may be determined whether the unused resource information is equal to or greater than the actual usage amount.
  • FIG. 14 is a flowchart showing an outline of processing performed by the virtual server return unit 119. This process is executed when an administrator or the like instructs activation from a console (not shown) of the management server 101.
  • Step 1401 selects the virtual server 109 to which the virtual server return unit 119 returns.
  • the administrator may explicitly select the virtual server 109 that the administrator wants to return to, or the standby system is triggered when an event that the physical server 111 is restored to a normal state by replacement of the physical server 111 or the like is received.
  • the virtual server 109 moved to the physical server 111 may be automatically selected.
  • step 1402 the virtual server return unit 119 determines whether or not the virtual server 109 selected in step 1401 is moving. Determination of whether or not the migration is in progress can be made by determining whether or not the definition information is recorded in the migration definition information 704 of the virtual server definition information table 118. If the virtual server 109 is moving, the process proceeds to step 1403. If the virtual server 109 is in the original state, the process proceeds to step 1403.
  • step 1403 the virtual server return unit 119 extracts the movement definition information 704 of the virtual server 109 selected in step 1401 from the virtual server definition information table 118.
  • step 1404 when the extracted movement definition information 704 has been moved a plurality of times, the virtual server return unit 119 selects the physical server 111 that is the movement destination. Whether or not the movement has been performed a plurality of times can be determined by the virtual server return unit 119 based on whether or not a plurality of movement histories are described in the movement definition information 704.
  • Several methods are conceivable for selecting the physical server 111 to be moved to. In the case where the physical server 111 that has detected the failure sign is replaced with a new physical server 111 and repaired, the replaced physical server 111 may be selected.
  • a new physical server 111 that is different from the moved physical server 111 may be selected. At this time, it is possible to maintain high reliability by selecting the physical server 111 in which a failure or a failure sign has not occurred as much as possible.
  • the virtual server return unit 119 acquires the definition information of the virtual server 109 used at the movement destination from the movement definition information 704 in the virtual server definition information table 118. This acquires the movement definition information 704 corresponding to the physical server 111 selected as the movement destination from the movement definition information 704 extracted in step 1403. If moving to a physical server 111 different from the physical server 111 that has moved multiple times, the original virtual server definition information may be used.
  • the original (initially assigned) virtual server definition information 309 can be acquired by referring to the virtual server definition information 309 described in the original definition information 703 of the virtual server 109 in the virtual server definition information table 118.
  • step 1406 the virtual server return unit 119 searches for a free resource of the physical server 111 that is the movement destination.
  • the same physical properties as before the movement of the virtual server 109 are necessarily used.
  • computer resources of the server 111 may not be secured, and this is a necessary step for confirmation.
  • step 1407 it is determined whether or not the free resource acquired by the virtual server return unit 119 in step 1406 satisfies the contents of the virtual server definition information 309 of the virtual server 109 acquired in step 1405. If the free resource cannot satisfy the contents of the virtual server definition information 309 of the virtual server 109 acquired in step 1405, the administrator is notified that the resource is insufficient in step 1409. As another means, the processing of the virtual server definition information management unit 103 may be executed, the virtual server definition information 309 of the virtual server 109 may be changed within a range that satisfies the performance, and the movement may be continued.
  • Step 1408 moves the virtual server 109 using the virtual server definition information 309 of the virtual server 109 used at the destination.
  • the virtual server 109 can be restored to the computer resource before the movement without degrading the service level such as performance.
  • the original definition information 703 is referred to.
  • the virtual server 109 can be returned to the active physical server 111 very easily.
  • the present invention can also be applied to a trigger other than a failure or a failure sign.
  • the virtual server 109 is used to distribute the load by using the present invention. May be. That is, when the load (for example, the processor usage rate) of the physical server 111 exceeds a predetermined threshold, the virtual server 109 can be moved to the physical server 111 whose load is less than the predetermined threshold among other physical servers 111. .
  • the virtual server 109 having a low load is moved and aggregated on the specific physical server 111 using the present invention.
  • the power consumption of the entire system can be reduced.
  • the physical server 111 can be used to move the virtual server 109 for the purpose of load distribution and power consumption optimization.
  • the present invention can be applied to a virtual computer system that operates a plurality of virtual servers on a plurality of physical servers.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • Software Systems (AREA)
  • Hardware Redundancy (AREA)

Abstract

L'invention porte sur un système de machine virtuelle qui comprend une pluralité d'ordinateurs physiques ayant des unités de virtualisation qui configurent une pluralité de machines virtuelles, et un ordinateur de gestion qui est connecté par l'intermédiaire d'un réseau. L'ordinateur de gestion alloue les ressources informatiques d'un premier ordinateur physique parmi la pluralité d'ordinateurs physiques et fait fonctionner les machines virtuelles. Des informations concernant les ressources informatiques allouées aux machines virtuelles sont retenues sous la forme d'informations de définition de la machine virtuelle, et les ressources informatiques du premier ordinateur physique réellement utilisées par les machines virtuelles sont acquises à titre de quantité d'utilisation réelle. Lorsque des conditions prédéterminées surviennent, un ordinateur physique qui peut maintenir au moins la même quantité de ressources informatiques que la quantité d'utilisation réelle est sélectionné parmi la pluralité d'ordinateurs physiques à titre de second ordinateur physique à utiliser comme destination de migration pour les machines virtuelles. Les informations de définition sont ensuite mises à jour à la quantité d'utilisation réelle et les machines virtuelles sont migrées vers le second ordinateur physique sélectionné.
PCT/JP2010/063273 2009-12-18 2010-08-05 Procédé de migration pour machine virtuelle, système de machines virtuelles et support de stockage contenant un programme Ceased WO2011074284A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2009288000A JP2011128967A (ja) 2009-12-18 2009-12-18 仮想計算機の移動方法、仮想計算機システム及びプログラム
JP2009-288000 2009-12-18

Publications (1)

Publication Number Publication Date
WO2011074284A1 true WO2011074284A1 (fr) 2011-06-23

Family

ID=44167050

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2010/063273 Ceased WO2011074284A1 (fr) 2009-12-18 2010-08-05 Procédé de migration pour machine virtuelle, système de machines virtuelles et support de stockage contenant un programme

Country Status (2)

Country Link
JP (1) JP2011128967A (fr)
WO (1) WO2011074284A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102946413A (zh) * 2012-10-17 2013-02-27 北京搜狐新媒体信息技术有限公司 虚拟机调度和执行部署过程中的资源预处理方法及系统
JPWO2013094006A1 (ja) * 2011-12-19 2015-04-27 富士通株式会社 プログラム、情報処理装置および方法
JP2015108899A (ja) * 2013-12-03 2015-06-11 富士通株式会社 制御プログラム、制御装置及び制御方法
WO2015114816A1 (fr) * 2014-01-31 2015-08-06 株式会社日立製作所 Ordinateur de gestion et programme de gestion
US9699509B2 (en) 2014-04-22 2017-07-04 Olympus Corporation Alternate video processing on backup virtual machine due to detected abnormalities on primary virtual machine

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5725191B2 (ja) 2011-09-22 2015-05-27 富士通株式会社 電源管理装置、電源管理方法および電源管理プログラム
US9183102B2 (en) * 2011-09-30 2015-11-10 Alcatel Lucent Hardware consumption architecture
JP5949782B2 (ja) 2011-12-28 2016-07-13 富士通株式会社 監視プログラム、監視方法および監視装置
WO2013114829A1 (fr) * 2012-02-01 2013-08-08 日本電気株式会社 Système de traitement d'informations, centre de traitement d'information, procédé de migration de système et programme
WO2013121531A1 (fr) * 2012-02-15 2013-08-22 株式会社日立製作所 Système d'ordinateur virtuel et procédé de récupération de symptôme de défaillance d'ordinateur virtuel
JP5948933B2 (ja) * 2012-02-17 2016-07-06 日本電気株式会社 ジョブ継続管理装置、ジョブ継続管理方法、及び、ジョブ継続管理プログラム
JP5983746B2 (ja) 2012-07-05 2016-09-06 富士通株式会社 処理装置、処理システム、及びプログラム
WO2014073046A1 (fr) 2012-11-07 2014-05-15 富士通株式会社 Dispositif de traitement d'informations, programme et procédé de migration de machine virtuelle
JP6164283B2 (ja) 2013-02-28 2017-07-19 日本電気株式会社 ソフトウェア安全停止システム、ソフトウェア安全停止方法、およびプログラム
WO2014147802A1 (fr) * 2013-03-21 2014-09-25 富士通株式会社 Dispositif de traitement d'informations, procédé d'allocation de ressources et programme
JP2015022385A (ja) * 2013-07-17 2015-02-02 日本電気株式会社 仮想システムおよび仮想システム制御方法
JP6194761B2 (ja) * 2013-11-07 2017-09-13 富士通株式会社 情報処理方法、装置、及びプログラム
SG11201605576RA (en) * 2014-01-10 2016-08-30 Priviti Pte Ltd System and method for communicating credentials
WO2015114791A1 (fr) * 2014-01-31 2015-08-06 株式会社日立製作所 Dispositif de gestion de sécurité
JP6269199B2 (ja) * 2014-03-13 2018-01-31 日本電気株式会社 管理サーバおよび障害復旧方法、並びにコンピュータ・プログラム
JP6260375B2 (ja) * 2014-03-17 2018-01-17 富士通株式会社 管理装置、管理プログラム及び情報処理システム
JP6398641B2 (ja) * 2014-11-19 2018-10-03 日本電気株式会社 管理装置、サービス提供管理方法およびサービス提供管理プログラム
JP6540072B2 (ja) * 2015-02-16 2019-07-10 富士通株式会社 管理装置、情報処理システム及び管理プログラム
KR101900727B1 (ko) 2018-06-14 2018-09-20 김상순 가상 서버 관리 장치

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007148839A (ja) * 2005-11-29 2007-06-14 Hitachi Ltd 障害回復方法
JP2008293117A (ja) * 2007-05-22 2008-12-04 Hitachi Ltd 仮想計算機の性能監視方法及びその方法を用いた装置
JP2009252204A (ja) * 2008-04-11 2009-10-29 Hitachi Ltd 計算機の運用管理システム及び運用管理方法

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007148839A (ja) * 2005-11-29 2007-06-14 Hitachi Ltd 障害回復方法
JP2008293117A (ja) * 2007-05-22 2008-12-04 Hitachi Ltd 仮想計算機の性能監視方法及びその方法を用いた装置
JP2009252204A (ja) * 2008-04-11 2009-10-29 Hitachi Ltd 計算機の運用管理システム及び運用管理方法

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPWO2013094006A1 (ja) * 2011-12-19 2015-04-27 富士通株式会社 プログラム、情報処理装置および方法
CN102946413A (zh) * 2012-10-17 2013-02-27 北京搜狐新媒体信息技术有限公司 虚拟机调度和执行部署过程中的资源预处理方法及系统
CN102946413B (zh) * 2012-10-17 2015-07-08 北京搜狐新媒体信息技术有限公司 虚拟机调度和执行部署过程中的资源预处理方法及系统
JP2015108899A (ja) * 2013-12-03 2015-06-11 富士通株式会社 制御プログラム、制御装置及び制御方法
WO2015114816A1 (fr) * 2014-01-31 2015-08-06 株式会社日立製作所 Ordinateur de gestion et programme de gestion
US9990258B2 (en) 2014-01-31 2018-06-05 Hitachi, Ltd. Management computer and management program
US9699509B2 (en) 2014-04-22 2017-07-04 Olympus Corporation Alternate video processing on backup virtual machine due to detected abnormalities on primary virtual machine

Also Published As

Publication number Publication date
JP2011128967A (ja) 2011-06-30

Similar Documents

Publication Publication Date Title
WO2011074284A1 (fr) Procédé de migration pour machine virtuelle, système de machines virtuelles et support de stockage contenant un programme
US12450081B2 (en) System and method for managing size of clusters in a computing environment
US11182220B2 (en) Proactive high availability in a virtualized computer system
US11321197B2 (en) File service auto-remediation in storage systems
US7992032B2 (en) Cluster system and failover method for cluster system
EP2800303B1 (fr) Procédé, dispositif et système de commutation, pour une machine d'application virtuelle à double élément, dans un environnement en nuage
US8713362B2 (en) Obviation of recovery of data store consistency for application I/O errors
JP6054522B2 (ja) 統合型ストレージ／ｖｄｉプロビジョニング方法
US7925923B1 (en) Migrating a virtual machine in response to failure of an instruction to execute
KR101471879B1 (ko) 하이퍼바이저 기반 서버 이중화 시스템, 그 방법 및 서버 이중화 컴퓨터 프로그램이 기록된 기록매체
US8078824B2 (en) Method for dynamic load balancing on partitioned systems
US9652326B1 (en) Instance migration for rapid recovery from correlated failures
US8122212B2 (en) Method and apparatus for logical volume management for virtual machine environment
US9037826B1 (en) System for optimization of input/output from a storage array
US10108517B1 (en) Techniques for data storage systems using virtualized environments
US20100186010A1 (en) Dynamic Checking of Hardware Resources for Virtual Environments
WO2011074152A1 (fr) Serveur de gestion, procédé de gestion et programme de gestion pour disque dur virtuel
US20150074251A1 (en) Computer system, resource management method, and management computer
CN101273334A (zh) 向逻辑分区指派处理器以及在故障时用不同的处理器替换该处理器
US11900159B2 (en) Method for repointing resources between hosts
JP2010257274A (ja) 仮想化環境におけるストレージ管理システム及びストレージ管理方法
WO2012004902A1 (fr) Système informatique et procédé de commande d'un commutateur système pour système informatique
JP5998577B2 (ja) クラスタ監視装置、クラスタ監視方法、及びプログラム
JP2015075898A (ja) 処理再開方法、処理再開プログラムおよび情報処理システム
US12189573B2 (en) Technique for creating an in-memory compact state of snapshot metadata

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 10837315

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 10837315

Country of ref document: EP

Kind code of ref document: A1