System and method to achieve an uninterrupted file level backup using a pass-through snapshot engine

US11188248B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11188248-B2
Application numberUS-202016775221-A
CountryUS
Kind codeB2
Filing dateJan 28, 2020
Priority dateJan 28, 2020
Publication dateNov 30, 2021
Grant dateNov 30, 2021

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A pass-through snapshot engine records lifecycle data and chronological status of files or objects, in one or more pass-through snapshots during a backup. If there is an abort, the pass-through snapshot engine freezes the pass-through snapshot(s) and terminates the backup. To restart after the abort, the pass-through snapshot engine sends one or more pass-through snapshots to the backup agent. The backup agent restarts the backup, and enforces states of lifecycle and chronology to files or objects, and discards files or objects that have already been backed up to the target device, in accordance with the one or more pass-through snapshots.

First claim

Opening claim text (preview).

What is claimed is: 1. A pass-through snapshot engine for backups, comprising: a memory; and one or more processors, to: record, in a pass-through snapshot in the memory, life cycle data that indicates completed portions of processes for backing up each file or object scheduled for backing up by a backup agent using an operational buffer during a backup; record, in the pass-through snapshot in the memory, chronological data that indicates all interactions, after the backup has started, with each file or object scheduled for the backing up in a target device during the backup; freeze the pass-through snapshot in the memory and terminate the backup, responsive to an abort of the backup prior to completion; and send one or more pass-through snapshots to the backup agent so that the backup agent restarts the backup, enforces states of lifecycle and chronology to files or objects and discards files or objects that have already been backed up to the target device, in accordance with the one or more pass-through snapshots, to restart after the abort. 2. The pass-through snapshot engine for backups of claim 1 , wherein the one or more processors are further to: initialize a zero file in the memory, as a placeholder for pass-through snapshots comprising the life cycle data, responsive to the backup agent indicating receiving a backup request. 3. The pass-through snapshot engine for backups of claim 1 , wherein the one or more processors are further to: delete the one or more pass-through snapshots, responsive to a request from the backup agent in acknowledgment of completion of a write, which completes the backup, by the target device. 4. The pass-through snapshot engine for backups of claim 1 , wherein the life cycle data is received by the pass-through snapshot engine from the backup agent. 5. The pass-through snapshot engine for backups of claim 1 , wherein the chronological data is received by the pass-through snapshot engine from the operational buffer. 6. The pass-through snapshot engine for backups of claim 1 , wherein the restart does not start from a beginning of the backup. 7. The pass-through snapshot engine for backups of claim 1 , wherein the backup agent utilizes the one or more pass-through snapshots to understand a current batch of files or objects that have to be consumed for an immediate write operation resulting in an uninterrupted backup session. 8. A method for backups, using pass-through snapshots, comprising: recording, in a pass-through snapshot in a memory, life cycle data that indicates completed portions of processes for backing up each file or object scheduled for backing up by a backup agent using an operational buffer during a backup session; recording, in the pass-through snapshot in the memory, chronological data that indicates all interactions, after the backup session has started, with each file or object scheduled for backing up in a target storage device during the backup session; freezing the pass-through snapshot in the memory and terminating the backup session, responsive to an abort of the backup session prior to completion; sending one or more pass-through snapshots to the backup agent; and restarting the backup session after the abort, with the backup agent enforcing states of lifecycle and chronology to files or objects and discarding files or objects that have already been backed up to the target storage device, in accordance with the one or more pass-through snapshots. 9. The method for backups, using pass-through snapshots, of claim 8 , further comprising: initializing a zero file in the memory, as a placeholder for pass-through snapshots comprising the life cycle data, responsive to the backup agent indicating receiving a backup request. 10. The method for backups, using pass-through snapshots, of claim 8 , further comprising: deleting the one or more pass-through snapshots, responsive to a request from the backup agent in acknowledgment of completion of a write, which completes the backup session, by the target storage device. 11. The method for backups, using pass-through snapshots, of claim 8 , further comprising: sending the life cycle data from the backup agent to a pass-through snapshot engine. 12. The method for backups, using pass-through snapshots, of claim 8 , further comprising: sending the chronological data from the operational buffer to a pass-through snapshot engine. 13. The method for backups, using pass-through snapshots, of claim 8 , wherein the restart does not start from a beginning of the backup session. 14. The method for backups, using pass-through snapshots, of claim 8 , further comprising: utilizing, by the backup agent, the one or more pass-through snapshots to understand a current batch of files or objects that have to be consumed for an immediate write operation resulting in an uninterrupted backup session. 15. A non-transitory computer-readable medium having instructions thereupon which, when executed by a processor, cause the processor to: record, in a pass-through snapshot, life cycle data that indicates completed portions of processes for backing up each file or object scheduled for backing up by a backup agent using an operational buffer during a backup; record, in the pass-through snapshot, chronological data that indicates all interactions, after the backup has started, with each file or object scheduled for backing up in a target device during the backup; freeze the pass-through snapshot and terminate the backup, responsive to an abort of the backup prior to completion; and send one or more pass-through snapshots to the backup agent so that the backup agent restarts the backup, enforces states of lifecycle and chronology to files or objects and discards files or objects that have already been backed up to the target device, in accordance with the one or more pass-through snapshots, to restart after the abort. 16. The non-transitory computer-readable medium of claim 15 , wherein the instructions further cause the processor to: initialize a zero file, as a placeholder for pass-through snapshots comprising the life cycle data, responsive to the backup agent indicating receiving a backup request. 17. The non-transitory computer-readable medium of claim 15 , wherein the instructions further cause the processor to: delete the one or more pass-through snapshots, responsive to a request from the backup agent in acknowledgment of completion of a write, which completes the backup, by the target device. 18. The non-transitory computer-readable medium of claim 15 , wherein the instructions further cause the processor to receive the life cycle data from the backup agent. 19. The non-transitory computer-readable medium of claim 15 , wherein the instructions further cause the processor to receive the chronological data from the operational buffer. 20. The non-transitory computer-readable medium of claim 15 , wherein instructions further cause the processor to utilize the one or more pass-through snapshots to understand a current batch of files or objects that have to be consumed for an immediate write operation resulting in an uninterrupted backup session.

Assignees

Inventors

Classifications

  • G06F3/065Primary

    Replication mechanisms · CPC title

  • G06F3/0619Primary

    in relation to data integrity, e.g. data losses, bit errors · CPC title

  • Single storage device · CPC title

  • Using snapshots, i.e. a logical point-in-time copy of the data · CPC title

  • Saving storage space on storage systems · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11188248B2 cover?
A pass-through snapshot engine records lifecycle data and chronological status of files or objects, in one or more pass-through snapshots during a backup. If there is an abort, the pass-through snapshot engine freezes the pass-through snapshot(s) and terminates the backup. To restart after the abort, the pass-through snapshot engine sends one or more pass-through snapshots to the backup agent. …
Who is the assignee on this patent?
Emc Ip Holding Co Llc
What technology area does this patent fall under?
Primary CPC classification G06F3/065. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Nov 30 2021 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 1 related publication on this page (citations in our corpus or others sharing the same primary CPC).