Protecting virtual machines against storage connectivity failures
US-9361199-B2 · Jun 7, 2016 · US
US10108508B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10108508-B2 |
| Application number | US-201615173320-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 3, 2016 |
| Priority date | Aug 24, 2012 |
| Publication date | Oct 23, 2018 |
| Grant date | Oct 23, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A system for monitoring a virtual machine executed on a host. The system includes a processor that receives an indication that a failure caused a storage device to be inaccessible to the virtual machine, the inaccessible storage device impacting an ability of the virtual machine to provide service, and applies a remedy to restore access to the storage device based on a type of the failure.
Opening claim text (preview).
What is claimed is: 1. A system for monitoring software application instances, the system comprising: a host executing a software application instance; and a processor programmed to: receive an indication that a failure caused a storage device to be inaccessible to the software application instance and impacted an ability of the software application instance to provide service; determine if the failure is permanent or transient; and apply a remedy comprising: if the failure is permanent, terminating the software application instance and restarting the software application instant on a healthy host, and if the failure is transient, waiting for a predefined period of time, and if the transient failure does not clear within the predefined period of time, terminating the software application instance and restarting the software application instance on a healthy host. 2. The system of claim 1 , wherein the host comprises a fault domain manager (FDM), and wherein the FDM is configured to determine if the failure is permanent or transient. 3. The system of claim 1 , wherein the storage device is a datastore. 4. The system of claim 1 , wherein the processor is configured to determine that the failure is permanent, if the failure is a Permanent Device Loss (PDL). 5. The system of claim 1 , wherein the processor is configured to determine that the failure is transient, if the failure is an All Paths Down (APD). 6. The system of claim 1 , wherein the remedy further comprises resetting the software application instance if the failure is transient and clears before a predefined period of time has elapsed. 7. The system of claim 1 , the remedy further comprises, if restarting the software application instance on the healthy host fails, retrying to restart the software application instance on the healthy host or another healthy host. 8. The system of claim 7 , wherein retrying to restart the software application instance on the healthy host is limited to a predefined number of retries. 9. The system of claim 7 , wherein retrying to restart the software application instance on the healthy host is continued until the software application instance is restarted on the healthy host or another healthy host. 10. A computer-readable storage medium having instructions stored thereon which, when executed by at least one processor, performs a method for monitoring a software application instance executed on a host, the method comprising: receiving an indication that a failure caused a storage device to be inaccessible to the software application instance and impacted an ability of the software application instance to provide service; determining if the failure is permanent or transient; and applying a remedy comprising: if the failure is permanent, terminating the software application instance and restarting the software application instant on a healthy host, and if the failure is transient, waiting for a predefined period of time, and if the transient failure does not clear within the predefined period of time, terminating the software application instance and restarting the software application instance on a healthy host. 11. The computer-readable storage medium of claim 10 , wherein the storage device is a datastore. 12. The computer-readable storage medium of claim 10 , wherein the failure is determined to be permanent, if the failure is a Permanent Device Loss (PDL). 13. The computer-readable storage medium of claim 10 , wherein the failure is determined to be transient, if the failure is an All Paths Down (APD). 14. The computer-readable storage medium of claim 10 , wherein the remedy further comprises resetting the software application instance if the failure is transient and clears before a predefined period of time has elapsed. 15. The computer-readable storage medium of claim 10 , the remedy further comprises, if restarting the software application instance on the healthy host fails, retrying to restart the software application instance on the healthy host or another healthy host. 16. The computer-readable storage medium of claim 10 , wherein, if the failure is transient and if the host and a master host, which coordinates activity of hosts and/or software application instances, are separated by a network partition, the software application instance is either restarted on the healthy host or is moved to a reset state after the transient failure clears, based on a predefined policy. 17. The computer-readable storage medium of claim 10 , wherein: the software application instance is one of a pair of software application instances; and if the failure is transient, the software application instance is terminated and restarted on the healthy host if the software application instance is the only software application instance in the pair of software application instances impacted by the transient failure. 18. The computer-readable storage medium of claim 17 , wherein if both software application instances in the pair of software application instances are impacted by a transient failure and if the host and a master host, which coordinates activity of hosts and/or software application instances, are separated by a network partition, the transient failure is either ignored or both software application instances in the pair of software application instances are restarted on one or more healthy hosts, based on a predefined policy. 19. A method for monitoring a software application instance executed on a host, the method comprising: receiving an indication that a failure caused a storage device to be inaccessible to the software application instance and impacted an ability of the software application instance to provide service; determining if the failure is permanent or transient; and applying a remedy comprising: if the failure is permanent, terminating the software application instance and restarting the software application instant on a healthy host, and if the failure is transient, waiting for a predefined period of time, and if the transient failure does not clear within the predefined period of time, terminating the software application instance and restarting the software application instance on a healthy host. 20. The method of claim 19 , wherein the storage device is a datastore.
using migration · CPC title
where processing functionality is redundant (redundant communication control functionality G06F11/2005, redundant storage control functionality G06F11/2089) · CPC title
involving virtual machines · CPC title
Restarting or rejuvenating · CPC title
in a virtual computing platform, e.g. logically partitioned systems · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.