Global backup scheduler based on integer programming and machine learning
US-2021232461-A1 · Jul 29, 2021 · US
US11436094B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11436094-B2 |
| Application number | US-202016886178-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 28, 2020 |
| Priority date | May 28, 2020 |
| Publication date | Sep 6, 2022 |
| Grant date | Sep 6, 2022 |
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.
One example method includes identifying a group of asset backups to be performed, and each asset backup is associated with a respective asset and has an associated backup time and RPO, selecting an asset backup to run first, and the asset backup that will run first is chosen based on a start deadline of that asset backup relative to respective start deadlines of one or more other asset backups, and the start deadline falls within a time slot, selecting a stream from a group of streams for the selected asset backup, and the selected stream is a stream with a lowest value of first available time slot, and backing up the asset at a backup server by running the selected asset backup, and backup begins at a start time that is a time when the selected stream becomes available, and the asset backup runs on the selected stream.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: identifying a group of asset backups to be performed, where each asset backup is associated with a respective asset and has an associated backup time and RPO; selecting an asset backup to run first, wherein the asset backup that will run first is chosen based on a start deadline of that asset backup relative to respective start deadlines of one or more other asset backups, and the start deadline falls within a time slot; selecting a stream from a group of streams for the selected asset backup, wherein the selected stream is a stream with a lowest value of first available time slot; and backing up the asset at a backup server by running the asset backup selected to run first, and that backup begins at a start time that is a time when the selected stream becomes available, and the asset backup runs on the selected stream. 2. The method as recited in claim 1 , wherein a start of the time slot of the stream occurs no later than the time slot of the selected backup. 3. The method as recited in claim 1 , further comprising: providing a first backup schedule to the asset, wherein the first backup schedule includes the time slot for performance of the asset backup and the start time of the asset backup; and providing a second backup schedule to the backup server, wherein the second backup schedule includes the selected stream and the asset backup scheduled to be performed on the selected stream. 4. The method as recited in claim 1 , wherein multiple assets are backed up to the backup server. 5. The method as recited in claim 1 , wherein a number of backup servers used for asset backups is smaller than a number of assets to be backed up, and/or a number of assets is greater than a number of streams. 6. The method as recited in claim 1 , further comprising using a machine learning process to estimate, for each asset, an amount of time needed to back up that asset. 7. The method as recited in claim 1 , wherein the operations of identifying the asset backup, selecting the asset to backup, and selecting the stream, are performed iteratively for each asset in the group. 8. The method as recited in claim 7 , wherein the method stops either when: each of the assets in the group has been scheduled to be backed up at least once; or a given time slot has been reached. 9. The method as recited in claim 1 , further comprising generating an updated start deadline for the selected asset backup after the selected asset backup has been scheduled. 10. The method as recited in claim 9 , wherein the updated start deadline=the start time for the backup asset+the RPO for the backup asset. 11. A non-transitory storage medium having stored therein instructions that are executable by one or more hardware processors to perform operations comprising: identifying a group of asset backups to be performed, where each asset backup is associated with a respective asset and has an associated backup time and RPO; selecting an asset backup to run first, wherein the asset backup that will run first is chosen based on a start deadline of that asset backup relative to respective start deadlines of one or more other asset backups, and the start deadline falls within a time slot; selecting a stream from a group of streams for the selected asset backup, wherein the selected stream is a stream with a lowest value of first available time slot; and backing up the asset at a backup server by running the asset backup selected to run first, and that backup begins at a start time that is a time when the selected stream becomes available, and the asset backup runs on the selected stream. 12. The non-transitory storage medium as recited in claim 11 , wherein a start of the time slot of the stream occurs no later than the time slot of the selected backup. 13. The non-transitory storage medium as recited in claim 11 , wherein the operations further comprise: providing a first backup schedule to the asset, wherein the first backup schedule includes the time slot for performance of the asset backup and the start time of the asset backup; and providing a second backup schedule to the backup server, wherein the second backup schedule includes the selected stream and the asset backup scheduled to be performed on the selected stream. 14. The non-transitory storage medium as recited in claim 11 , wherein multiple assets are backed up to the backup server. 15. The non-transitory storage medium as recited in claim 11 , wherein a number of backup servers used for asset backups is smaller than a number of assets to be backed up, and/or a number of assets is greater than a number of streams. 16. The non-transitory storage medium as recited in claim 11 , wherein the operations further comprise using a machine learning process to estimate, for each asset, an amount of time needed to back up that asset. 17. The non-transitory storage medium as recited in claim 11 , wherein the operations of identifying the asset backup, selecting the asset to backup, and selecting the stream, are performed iteratively for each asset in the group. 18. The non-transitory storage medium as recited in claim 17 , wherein the operations stop either when: each of the assets in the group has been scheduled to be backed up at least once; or a given time slot has been reached. 19. The non-transitory storage medium as recited in claim 11 , wherein the operations further comprise generating an updated start deadline for the selected asset backup after the selected asset backup has been scheduled. 20. The non-transitory storage medium as recited in claim 19 , wherein the updated start deadline=the start time for the backup asset+the RPO for the backup asset.
by selection of backup contents · CPC title
Backup scheduling policy · CPC title
Machine learning · CPC title
for networked environments · CPC title
Timestamp · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.