Regenerating a chain of backups
US-2023205639-A1 · Jun 29, 2023 · US
US12147315B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12147315-B2 |
| Application number | US-202218070954-A |
| Country | US |
| Kind code | B2 |
| Filing date | Nov 29, 2022 |
| Priority date | Nov 29, 2022 |
| Publication date | Nov 19, 2024 |
| Grant date | Nov 19, 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.
A system identifies an intent policy model associated with an initial time. The system updates a data structure to cause the data structure to include one or more portions. Each portion of the data structure is associated with a start time and an end time. Each portion includes: a first delta snapshot that indicates one or more first changes to the intent policy model from the initial time to the start time associated with the portion, and one or more additional delta snapshots that respectively indicate one or more incremental changes to the intent policy model at times from the start time and to the end time associated with the portion of the data structure.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: generating, by a system, an initial delta snapshot that indicates one or more first changes to an intent policy model from an initial time to a first time; storing, by the system, the initial delta snapshot in a first portion of a data structure; generating, by the system and after storing the initial delta snapshot, a first delta snapshot that indicates one or more second changes to the intent policy model from the first time to a second time; storing, by the system, the first delta snapshot in the first portion of the data structure; generating, by the system and after storing the first delta snapshot, a second delta snapshot that indicates one or more third changes to the intent policy model from the second time to a third time; storing, by the system, the second delta snapshot in the first portion of the data structure; determining, by the system and after storing the second delta snapshot, that additional delta snapshots are not to be stored in the first portion of the data structure; generating, by the system, based on determining that additional delta snapshots are not be stored in the first portion of the data structure, and based on the initial delta snapshot, the first delta snapshot, and the second delta snapshot, an accumulated delta snapshot that indicates the one or more first changes, the one or more second changes, and the one or more third changes to the intent policy model from the initial time to the third time; storing, by the system, the accumulated delta snapshot in a second portion of the data structure; identifying, based on a message indicating that the system is to deploy an updated version of the intent policy model at a deployment time to a device, a previous deployment time at which the system deployed a previous version of the intent policy model to the device; and generating, based on the data structure, the previous deployment time, and the deployment time, a differential deployment snapshot. 2. The method of claim 1 , further comprising: generating, after storing the accumulated delta snapshot, a third delta snapshot that indicates one or more fourth changes to the intent policy model from the third time to a fourth time; and storing the third delta snapshot in the second portion of the data structure. 3. The method of claim 1 , wherein determining that additional delta snapshots are not to be stored in the first portion of the data structure comprises at least one of: determining that a total amount of time since the first time is greater than or equal to a time duration threshold; determining that a total number of delta snapshots stored in the first portion of the data structure is greater than or equal to a delta snapshot number threshold; or determining that a total number of resources identified by the delta snapshots stored in the first portion of the data structure is greater than or equal to a resource number threshold. 4. The method of claim 1 , further comprising: receiving, after storing the accumulated delta snapshot, the message indicating that the system is to deploy the version of the intent policy model at the deployment time to the device. 5. The method of claim 1 , wherein generating the differential deployment snapshot comprises: identifying a portion of the data structure associated with the previous deployment time; identifying another portion of the data structure associated with the deployment time; and generating, based on at least one delta snapshot included in the portion of the data structure and at least one delta snapshot included in the other portion of the data structure, the differential deployment snapshot. 6. The method of claim 1 , further comprising: generating, based on the differential deployment snapshot, device-level provisioning configuration information for the device; and providing the device-level provisioning configuration information to the device, wherein providing the device-level provisioning configuration information permits the updated version of the intent policy model to be deployed on the device. 7. The method of claim 1 , further comprising: receiving, after storing the accumulated delta snapshot, a message indicating that the system is to deploy a previous version of the intent policy model to the device; identifying, based on the message, a previous deployment time at which the system deployed the previous version of the intent policy model to the device; and generating, based on the data structure and the previous deployment time, a rollback deployment snapshot. 8. The method of claim 7 , wherein generating the rollback deployment snapshot comprises: identifying a portion of the data structure associated with the previous deployment time; and generating, based on the accumulated delta snapshot included in the portion of the data structure, the rollback deployment snapshot. 9. The method of claim 7 , further comprising: generating, based on the rollback deployment snapshot, device-level rollback configuration information for the device; and providing the device-level rollback configuration information to the device, wherein providing the device-level rollback configuration information permits the previous version of the intent policy model to be deployed on the device. 10. A non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising: one or more instructions that, when executed by one or more processors of a system, cause the system to: identify an intent policy model associated with an initial time; update a data structure to cause the data structure to include one or more portions, wherein each portion of the data structure is associated with a start time and an end time, and each portion includes: a first delta snapshot that indicates one or more first changes to the intent policy model from the initial time to the start time associated with the portion; and one or more additional delta snapshots that respectively indicate one or more incremental changes to the intent policy model at times from the start time and to the end time associated with the portion of the data structure; identify, based on a message indicating that the system is to deploy a previous version of the intent policy model to a device, a previous deployment time at which the system deployed the previous version of the intent policy model to the device; and generate, based on the data structure and the previous deployment time, a rollback deployment snapshot. 11. The non-transitory computer-readable medium of claim 10 , wherein the one or more instructions further cause the system to: receive, after updating the data structure, a message indicating that the system is to deploy an updated version of the intent policy model at a deployment time to the device; identify, based on the message, a previous deployment time at which the system deployed a previous version of the intent policy model to the device; and generate, based on the data structure, the previous deployment time, and the deployment time, a differential deployment snapshot. 12. The non-transitory computer-readable medium of claim 11 , wherein the one or more instructions, that cause the system to generate the differential deployment snapshot, cause the system to: identify a first portion of the data structure associated with the previous deployment time; identify a second portion of the data structure associated with the deployment time; and generate, based on at least one of the one or more additional delta snapshots included in the first portion of the data structure and at least one of the on
based on delta files · CPC title
characterised by the use of retention policies (retention policies for HSM systems G06F16/185) · CPC title
Management of the data involved in backup or backup restore · CPC title
by rolling back to previous configuration versions · CPC title
involving simulating, designing, planning or modelling of a network · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.