Adaptive data backup scheduling based on reliability metric or metrics
US-2021049075-A1 · Feb 18, 2021 · US
US11593221B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11593221-B2 |
| Application number | US-202016805149-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 28, 2020 |
| Priority date | Feb 28, 2020 |
| Publication date | Feb 28, 2023 |
| Grant date | Feb 28, 2023 |
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 method for generating a backup schedule, that includes receiving, by a scheduling agent, an event entry specifying an event associated with a container, determining that the event entry specifies an alert event, adding the event entry to a plurality of historical event entries in a historical event repository, determining that the plurality of historical event entries indicates a repeating error state of the container, determining that an error frequency of the repeating error state is greater than an existing backup frequency of a container backup schedule, and generating a backup schedule warning indicating a recommended backup frequency.
Opening claim text (preview).
What is claimed is: 1. A method for generating a container backup schedule to perform a backup, comprising: receiving, by a scheduling agent, an event entry specifying an event associated with a container; making a first determination that the event entry specifies an alert event; adding, based on the first determination, the event entry to a plurality of historical event entries in a historical event repository; making a second determination that the plurality of historical event entries indicates a repeating error state of the container; making a third determination, based on the second determination, that an error frequency of the repeating error state is greater than an existing backup frequency of the container backup schedule; generating, based on the third determination, a container backup schedule warning indicating a recommended backup frequency; updating the container backup schedule from the existing backup frequency to the recommended backup frequency; and performing the backup based on the container backup schedule. 2. The method of claim 1 , wherein making the first determination that the event entry specifies the alert event comprises: matching at least a portion of the event entry to alert event data associated with the alert event. 3. The method of claim 1 , wherein the event entry indicates a container error at a first time, wherein the plurality of historical event entries comprises a second historical event entry that indicates a second container error at a second time. 4. The method of claim 3 , wherein the error frequency is based on the first time and the second time. 5. The method of claim 4 , wherein the recommended backup frequency is greater than the error frequency. 6. The method of claim 1 , wherein generating the container backup schedule warning comprises: issuing the container backup schedule warning to a user interface. 7. A non-transitory computer readable medium comprising instructions which, when executed by a computer processor, enables the computer processor to perform a method for generating a container backup schedule to perform a backup, comprising: receiving, by a scheduling agent, an event entry specifying an event associated with a container; making a first determination that the event entry specifies an alert event; adding, based on the first determination, the event entry to a plurality of historical event entries in a historical event repository; making a second determination that the plurality of historical event entries indicates a repeating error state of the container; making a third determination, based on the second determination, that an error frequency of the repeating error state is greater than an existing backup frequency of the container backup schedule; generating, based on the third determination, a container backup schedule warning indicating a recommended backup frequency; updating the container backup schedule from the existing backup frequency to the recommended backup frequency; and initiating the backup based on the container backup schedule. 8. The non-transitory computer readable medium of claim 7 , wherein making the first determination that the event entry specifies the alert event comprises: matching at least a portion of the event entry to alert event data associated with the alert event. 9. The non-transitory computer readable medium of claim 7 , wherein the event entry indicates a container error at a first time, wherein the plurality of historical event entries comprises a second historical event entry that indicates a second container error at a second time. 10. The non-transitory computer readable medium of claim 9 , wherein the error frequency is based on the first time and the second time. 11. The non-transitory computer readable medium of claim 10 , wherein the recommended backup frequency is greater than the error frequency. 12. The non-transitory computer readable medium of claim 7 , wherein generating the container backup schedule warning comprises: issuing the container backup schedule warning to a user interface. 13. A backup manager, comprising: memory; and a processor, wherein the processor is configured to perform a method, comprising: receiving, by a scheduling agent, an event entry specifying an event associated with a container; making a first determination that the event entry specifies an alert event; adding, based on the first determination, the event entry to a plurality of historical event entries in a historical event repository; making a second determination that the plurality of historical event entries indicates a repeating error state of the container; making a third determination, based on the second determination, that an error frequency of the repeating error state is greater than an existing backup frequency of a container backup schedule; generating, based on the third determination, a container backup schedule warning indicating a recommended backup frequency; updating the container backup schedule from the existing backup frequency to the recommended backup frequency; and initiating a backup based on the container backup schedule. 14. The backup manager of claim 13 , wherein making the first determination that the event entry specifies the alert event comprises: matching at least a portion of the event entry to alert event data associated with the alert event. 15. The backup manager of claim 13 , wherein the event entry indicates a container error at a first time, wherein the plurality of historical event entries comprises a second historical event entry that indicates a second container error at a second time. 16. The backup manager of claim 15 , wherein the error frequency is based on the first time and the second time. 17. The backup manager of claim 16 , wherein the recommended backup frequency is greater than the error frequency. 18. The backup manager of claim 13 , wherein generating the container backup schedule warning comprises: issuing the container backup schedule warning to a user interface.
Dumping, i.e. gathering error/state information after a fault for later diagnosis · CPC title
by exceeding a count or rate limit, e.g. word- or bit count limit · CPC title
for networked environments · CPC title
Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers · CPC title
Backup scheduling policy · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.