Image recovery from volume image files

US11243850B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11243850-B2
Application numberUS-201916543848-A
CountryUS
Kind codeB2
Filing dateAug 19, 2019
Priority dateDec 23, 2013
Publication dateFeb 8, 2022
Grant dateFeb 8, 2022

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 system for image recovery comprises an input interface and a processor. The input interface is configured to receive a block backup volume that can be mounted. The processor is configured to determine a merged chain map by consolidating one or more incremental chain maps and to store an image using the merged chain map and a volume map.

First claim

Opening claim text (preview).

What is claimed is: 1. A system, comprising: an input interface configured to receive a block backup volume that can be mounted; and a processor configured to: determine a merged chain map by consolidating a plurality of chain maps, wherein to determine the merged chain map includes iteratively selecting one chain map of the plurality of chain maps, and for each block in the selected one chain map based at least in part on an order from most recent to oldest, placing the block in the merged chain map according to a determination of whether the merged chain map already comprises the block; and use the merged chain map in connection with recovery of a volume image file. 2. The system of claim 1 , wherein the merged chain map comprises information indicating a location of a most recent version of data stored at each block address in the volume image file. 3. The system of claim 1 , wherein the plurality of chain maps correspond to a plurality of incremental chain maps. 4. The system of claim 1 , wherein the placing the block in the merged chain map according to a determination of whether the merged chain map already comprises the block comprises: determining whether the merged chain map already comprises the block; in response to determining that the merged chain map does not comprise the block, placing the block in the merged chain map; and in response to determining that the merged chain map comprises the block, skipping writing the block from the selected one chain map to the merged chain map. 5. The system of claim 1 , wherein the recovery of the volume image file is further based at least in part on a most recent full backup. 6. The system of claim 1 , wherein the plurality of chain maps correspond to a plurality of incremental chain maps and the merged chain map indicates the changes to the full backup that exist in the plurality of incremental chain maps before the changes are applied to the full backup in connection with a data recovery process. 7. The system of claim 1 , wherein the plurality of chain maps correspond to a plurality of incremental chain maps, and the plurality of incremental chain maps correspond to one or more incremental backups. 8. The system of claim 1 , wherein to recover the volume image file comprises storing the image using the merged chain map and the volume map and mounting the merged chain map and reading a file from the mounted merged chain map. 9. The system of claim 1 , wherein the plurality of chain maps correspond to a plurality of incremental chain maps, and the block backup volume includes the plurality of incremental chain maps. 10. The system of claim 1 , wherein the block backup volume includes a volume map, the volume map being used in connection with recovering the volume image file. 11. The system of claim 10 , wherein the volume map comprises sparse file metadata. 12. The system of claim 1 , wherein the block backup volume includes backup data. 13. The system of claim 12 , wherein the backup data comprises the backup. 14. The system of claim 12 , wherein the backup data comprises one or more incremental backups. 15. The system of claim 1 , wherein the merged chain map is used to copy blocks from the block backup volume to a target volume. 16. The system of claim 1 , wherein the plurality of chain maps correspond to a plurality of incremental chain maps, and to determine the merged chain map comprises consolidating the plurality of incremental chain maps by determining a set of up-to-date blocks indicated in the plurality of incremental chain maps and storing indicators to the set of up-to-date blocks in the merged chain map. 17. The system of claim 1 , wherein to recover the volume image file comprises storing an image using the merged chain map and a volume map, the storing the image comprising retrieving and storing the set of up-to-date blocks. 18. The system of claim 17 , wherein each block in the set of up-to-date blocks comprises a most recent stored version of a data block from an appropriate stored full or incremental backup. 19. The system of claim 18 , wherein the appropriate stored full or incremental backup is determined using the merged chain map. 20. The system of claim 17 , wherein in response to determining that the merged chain map indicates that the data is not changed at an address, a data block is stored at the address in the image from a full backup. 21. The system of claim 1 , wherein the plurality of chain maps correspond to a plurality of incremental chain maps, and to determine the merged chain map comprises: create the merged chain map, wherein the merged chain map is created as a merged empty chain map; and copy changes indicated in the plurality of incremental chain maps to the empty merged chain map to form the merged chain map. 22. The system of claim 21 , wherein to copy changes indicated in the plurality of incremental chain maps to the empty merged chain map comprises: copy the changes indicated in the plurality of incremental chain maps to corresponding blocks of the merged chain map. 23. The system of claim 1 , wherein an empty block of the merged chain map is indicative that a most up-to-date information for the block is represented in the full backup. 24. The system of claim 1 , wherein the plurality of chain maps correspond to a plurality of incremental chain maps, and a determination that the merged chain map already comprises the block is indicative of the merged chain map comprising more recent data from another one of the plurality of incremental chain maps. 25. A computer program product, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for: receiving a block backup volume that can be mounted; determining a merged chain map by consolidating a plurality of chain maps, wherein determining the merged chain map includes iteratively selecting one chain map of the plurality of chain maps a merged chain map by consolidating a plurality of chain maps, wherein to determine the merged chain map includes iteratively selecting one chain map of the plurality of chain maps, and for each block in the selected one chain map based at least in part on an order from most recent to oldest, placing the block in the merged chain map according to a determination of whether the merged chain map already comprises the block, and for each block in the selected one chain map, placing the block in the merged chain map according to a determination of whether the merged chain map already comprises the block; and using the merged chain map in connection with recovery of a volume image file. 26. A method, comprising: receiving a block backup volume that can be mounted; determining, using a processor, a merged chain map by consolidating a plurality of chain maps, wherein determining the merged chain map includes iteratively selecting one chain map of the plurality of chain maps a merged chain map by consolidating a plurality of chain maps, wherein to determine the merged chain map includes iteratively selecting one chain map of the plurality of chain maps, and for each block in the selected one chain map based at least in part on an order from most recent to oldest, placing the block in the merged chain map according to a determination of whether the merged chain map already comprises the block, and for each block in the selected one chain map, plac

Assignees

Inventors

Classifications

  • Distributed file systems · CPC title

  • Timestamp · CPC title

  • Backup restoration techniques · CPC title

  • involving logging of persistent data for recovery · CPC title

  • Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion (error detection or correction of the data by redundancy in operations or in hardware G06F11/14, G06F11/16) · 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 US11243850B2 cover?
A system for image recovery comprises an input interface and a processor. The input interface is configured to receive a block backup volume that can be mounted. The processor is configured to determine a merged chain map by consolidating one or more incremental chain maps and to store an image using the merged chain map and a volume map.
Who is the assignee on this patent?
Emc Ip Holding Co Llc
What technology area does this patent fall under?
Primary CPC classification G06F11/1469. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Feb 08 2022 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 2 related publications on this page (citations in our corpus or others sharing the same primary CPC).