Dynamic erasure coding
US-2019332473-A1 · Oct 31, 2019 · US
US11892914B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11892914-B2 |
| Application number | US-202016925621-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 10, 2020 |
| Priority date | May 27, 2020 |
| Publication date | Feb 6, 2024 |
| Grant date | Feb 6, 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.
The method includes obtaining, by a restoration policy manager, a restoration request for a plurality of application containers, and in response to the restoration request: obtaining, by a backup server, container information associated with the plurality of application containers, assigning a restoration type to each application container in the plurality of application containers, updating a restoration type list based on the assigning, and initiating a restoration of the plurality of application containers using the restoration type list.
Opening claim text (preview).
What is claimed is: 1. A method for managing application containers, the method comprising: obtaining, by a restoration policy manager, a restoration request for a plurality of application containers to be restored in a production host; and in response to the restoration request: obtaining, by a backup server, container information associated with the plurality of application containers, wherein the container information comprises information for an application container that was at one point in time in the production host, a second application container that is scheduled to be hosted by the production host, and a third application container that has never been hosted by the production host; assigning a restoration type to each application container in the plurality of application containers using the container information, wherein the plurality of application containers comprises the application container, the second application container, and the third application container; updating a restoration type list based on the assigning; and initiating a restoration of the plurality of application containers using the restoration type list. 2. The method of claim 1 , wherein the container information is obtained from a container information repository. 3. The method of claim 1 , wherein the restoration type comprises at least one of: an instant restoration type, a write-ahead restoration type, and a simple point-in-time restoration type. 4. The method of claim 1 , wherein initiating the restoration of the plurality of application containers comprises: sending a restoration initiation request to a restoration agent executing on the production host, wherein the restoration initiation request specifies each of the plurality of application containers and the restoration type of each of the plurality of application containers. 5. The method of claim 4 , wherein the restoration policy manager is operatively connected to the production host. 6. The method of claim 1 , wherein the container information is obtained using a container application programming interface (API). 7. A system, comprising: a processor; and memory comprising instructions which, when executed by the processor, perform a method, the method comprising: obtaining, by a restoration policy manager, a restoration request for a plurality of application containers to be restored in a production host; and in response to the restoration request: obtaining, by a backup server, container information associated with the plurality of application containers, wherein the container information comprises information for an application container that was at one point in time in the production host, a second application container that is scheduled to be hosted by the production host, and a third application container that has never been hosted by the production host; assigning a restoration type to each application container in the plurality of application containers using the container information, wherein the plurality of application containers comprises the application container, the second application container, and the third application container; updating a restoration type list based on the assigning; and initiating a restoration of the plurality of application containers using the restoration type list. 8. The system of claim 7 , wherein the container information is obtained from a container information repository. 9. The system of claim 7 , wherein the restoration type comprises at least one of: an instant restoration type, a write-ahead restoration type, and a simple point-in-time restoration type. 10. The system of claim 7 , wherein initiating the restoration of the plurality of application containers comprises: sending a restoration initiation request to a restoration agent executing on the production host, wherein the restoration initiation request specifies each of the plurality of application containers and the restoration type of each of the plurality of application containers. 11. The system of claim 10 , wherein the restoration policy manager is operatively connected to the restoration agent. 12. The system of claim 7 , wherein the container information is obtained using a container application programming interface (API). 13. 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, the method comprising: obtaining a restoration request for a plurality of application containers to be restored in a production host; and in response to the restoration request: obtaining, by a backup server, container information associated with the plurality of application containers, wherein the container information comprises information for an application container that was at one point in time in the production host, a second application container that is scheduled to be hosted by the production host, and a third application container that has never been hosted by the production host; assigning a restoration type to each application container in the plurality of application containers using the container information, wherein the plurality of application containers comprises the application container, the second application container, and the third application container; updating a restoration type list based on the assigning; and initiating a restoration of the plurality of application containers using the restoration type list. 14. The non-transitory computer readable medium of claim 13 , wherein the container information is obtained from a container information repository. 15. The non-transitory computer readable medium of claim 13 , wherein the restoration type comprises at least one of: an instant restoration type, a write-ahead restoration type, and a simple point-in-time restoration type. 16. The non-transitory computer readable medium of claim 13 , wherein initiating the restoration of the plurality of application containers comprises: sending a restoration initiation request to a restoration agent executing on the production host, wherein the restoration initiation request specifies each of the plurality of application containers and the restoration type of each of the plurality of application containers. 17. The non-transitory computer readable medium of claim 13 , wherein the container information is obtained using a container application programming interface (API).
Backup restoration techniques · CPC title
Interprogram communication · CPC title
Real-time · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.