Redistributing data across drives of a storage array based on drive health metrics
US-2020133772-A1 · Apr 30, 2020 · US
US12032473B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12032473-B2 |
| Application number | US-202217994833-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 28, 2022 |
| Priority date | Nov 28, 2022 |
| Publication date | Jul 9, 2024 |
| Grant date | Jul 9, 2024 |
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.
Embodiments described herein relate to methods, systems, and non-transitory computer readable mediums storing instructions for placing an application in an external environment such as a cloud or edge environment, when it is rendered unavailable on a local environment such as a local host. The application's instance is moved after a connection test reveals that the application, related applications, and/or underlying physical computing devices hosting the applications and/or their data, do not respond to the test within an acceptable level of performance. By placing the application instances in an external environment, the application(s) can continue to provide an adequate level of service to one or more users until the application can be restored to its better function local host.
Opening claim text (preview).
What is claimed is: 1. A method for maintaining availability of an application, the method comprising: performing a connection test of an application located on a local production host; making a first determination, based on the connection test, that the connection test failed; replicating, after the first determination, the application to an external environment, separate from the local production host, to obtain a replicated application, wherein the replicated application is configured to continue receiving interaction from a user while the application on the local production host is being repaired; determining a cause of the connection test failure; correcting, after determining the cause of the connection test failure, the cause of the connection test failure; performing, after correcting the cause of the connection test failure, an additional test to determine if the cause of the connection test failure has been corrected; making a second determination, based on the additional test, that the cause of the connection test failure has been corrected; and transferring, in response to the second determination, the replicated application from the external environment to the local production host to restore the application on the local production host, wherein transferring the replicated application results in at least a state of the replicated application being transferred to the local production host. 2. The method of claim 1 , wherein the external environment is an edge environment. 3. The method of claim 1 , wherein the external environment is a cloud environment. 4. The method of claim 1 , wherein when the connection test fails, prior to correcting the cause of the connection test, a user is notified. 5. The method of claim 4 , wherein the additional test is performed after the user is notified and a predetermined period of time has passed since the connection test failed. 6. The method of claim 1 , wherein the connection test is also performed on all applications that are related to the application and if the connection test fails on at least one of all the applications that are related to the application, the connection test is considered to have failed for the application. 7. The method of claim 6 , wherein when the connection test fails, the application and all the applications that are related to the application have their context moved to the external environment. 8. The method of claim 6 , wherein only the application and only those applications of all the applications that are related to the application that have failed the connection test are transferred to the external environment. 9. A non-transitory computer readable medium comprising computer readable program code, which when executed by a computer processor enables the computer processor to perform a method for performing a method for maintaining availability of an application, the method comprising: performing a connection test of an application located on a local production host; making a first determination, based on the connection test, that the connection test failed; replicating, after the first determination, the application to an external environment, separate from the local production host, to obtain a replicated application, wherein the replicated application is configured to continue receiving interaction from a user while the application on the local production host is being repaired; determining a cause of the connection test failure; correcting, after determining the cause of the connection test failure, the cause of the connection test failure; performing, after correcting the cause of the connection test failure, an additional test to determine if the cause of the connection test failure has been corrected; making a second determination, based on the additional test, that the cause of the connection test failure has been corrected; and transferring, in response to the second determination, the replicated application from the external environment to the local production host to restore the application on the local production host, wherein transferring the replicated application results in at least a state of the replicated application being transferred to the local production host. 10. The non-transitory computer readable medium of claim 9 , wherein the external environment is an edge environment. 11. The non-transitory computer readable medium of claim 9 , wherein the external environment is a cloud environment. 12. The non-transitory computer readable medium of claim 9 , wherein when the connection test fails, prior to correcting the cause of the connection test, a user is notified. 13. The non-transitory computer readable medium of claim 12 , wherein the additional test is performed after the user is notified and a predetermined period of time has passed since the connection test failed. 14. The non-transitory computer readable medium of claim 9 , wherein the connection test is also performed on all applications that are related to the application and if the connection test fails on at least one of all the applications that are related to the application, the connection test is considered to have failed for the application. 15. The non-transitory computer readable medium of claim 14 , wherein when the connection test fails, the application and all the applications that are related to the application have their context moved to the external environment. 16. The non-transitory computer readable medium of claim 14 , wherein only the application and only those applications of all the applications that are related to the application that have failed the connection test are transferred to the external environment. 17. A system comprising: at least one local production host that hosts a plurality of applications which comprises: at least one processor; a storage device; and at least one memory that includes instructions, which when executed by the processor, performs a method for maintaining availability of an application, the method comprising: performing a connection test of an application located on the at least one local production host; making a first determination, based on the connection test, that the connection test failed; replicating, after the first determination, the application to an external environment, separate from the local production host, to obtain a replicated application, wherein the replicated application is configured to continue receiving interaction from a user while the application on the local production host is being repaired; determining a cause of the connection test failure; correcting, after determining the cause of the connection test failure, the cause of the connection test failure; performing, after correcting the cause of the connection test failure, an additional test to determine if the cause of the connection test failure has been corrected; making a second determination, based on the additional test, that the cause of the connection test failure has been corrected; and transferring, in response to the second determination, the replicated application from the external environment to the local production host to restore the application on the local production host, wherein transferring the replicated application results in at least a state of the replicated application being transferred to the local production host. 18. The system of claim 17 , wherein the external environment is an edge environment. 19. The system of claim 17 , wherein the external environment is a cloud environment.
Environments for analysis, debugging or testing of software · CPC title
Physics · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.