Techniques for performing incremental data backups

Patent metadata

Field	Value
Publication number	US-11449389-B2
Application number	US-201715841283-A
Country	US
Kind code	B2
Filing date	Dec 13, 2017
Priority date	Jun 2, 2017
Publication date	Sep 20, 2022
Grant date	Sep 20, 2022

Abstract

The embodiments set forth techniques for performing incremental backups of a source file system volume (FSV) managed by a source computing device. According to some embodiments, the source computing device can be configured to generate a current snapshot of the source FSV, where the current snapshot complements a previous snapshot of the source FSV (e.g., established during a previous backup). In some cases, to free up storage space, the data for files belonging to the source FSV can be stripped from the previous snapshot (where metadata for the files remains intact). Next, the source computing device can generate, within a destination storage device, a second snapshot of a destination FSV (that corresponds to the source FSV). In turn, the source computing device identifies changes made to the source FSV based on the current snapshot and the previous snapshot, and reflects the changes within the second snapshot of the destination FSV.

First claim

What is claimed is:

1. A method for performing a backup of a source file system volume (FSV) associated with a source computing device, the method comprising, at the source computing device:
in response to identifying that an amount of available storage space is insufficient for generating a current snapshot:
removing, from a previous snapshot, data for files of the source FSV to establish a sufficient amount of available storage space for generating the current snapshot, such that the previous snapshot includes metadata for files within the source FSV but does not include the data for the files within the source FSV;

generating the current snapshot of the source FSV, wherein the current snapshot complements the previous snapshot of the source FSV;
generating, within a destination storage device, a second snapshot of a destination FSV, wherein the source FSV corresponds to the destination FSV;
identifying changes that have been made to the source FSV based on the current snapshot and the previous snapshot; and
reflecting the changes within the second snapshot of the destination FSV.

2. The method of claim 1 , further comprising:
excluding at least one file from the backup based on its type, and/or location within the source FSV.

3. The method of claim 1 , wherein identifying the changes comprises:
identifying a change to a source file that occurred between the current snapshot and the previous snapshot, wherein a size of the source file satisfies a threshold;
obtaining (i) a first physical block map for the source file based on the current snapshot, and (ii) a second physical block map for the source file based on the previous snapshot;
identifying, based on the first physical block map and the second physical block map, at least one block that has changed within the source file;
identifying a destination file that corresponds to the source file; and
reflecting the change to the at least one block within the destination file.

4. The method of claim 3 , wherein reflecting the change to the at least one block within the destination file comprises:
cloning the destination file to establish a cloned destination file;
reflecting the change to the at least one block within the cloned destination file; and
renaming the cloned destination file in accordance with the destination file.

5. The method of claim 1 , further comprising, prior to identifying that the amount of available storage space is insufficient for generating the current snapshot:
generating the previous snapshot, wherein the previous snapshot includes both (i) the metadata for files within the source FSV, and (ii) data for the files within the source FSV; and
generating the destination FSV based on the previous snapshot of the source FSV.

6. The method of claim 1 , wherein the data for files of the source FSV comprises binary comprises binary data of actual file contents.

7. The method of claim 1 , further comprising:
generating a third destination snapshot of the destination FSV to finalize the backup.

8. At least one non-transitory computer readable storage medium configured to store instructions that, when executed by at least one processor included in a source computing device, cause the source computing device to perform a backup of a source file system volume (FSV) associated with the source computing device, by carrying out steps that include:
in response to identifying that an amount of available storage space is insufficient for generating a current snapshot:
removing, from a previous snapshot, data for files of the source FSV to establish a sufficient amount of available storage space for generating the current snapshot, such that the previous snapshot includes metadata for files within the source FSV but does not include the data for the files within the source FSV;

generating the current snapshot of the source FSV, wherein the current snapshot complements the previous snapshot of the source FSV;
generating, within a destination storage device, a second snapshot of a destination FSV, wherein the source FSV corresponds to the destination FSV;
identifying changes that have been made to the source FSV based on the current snapshot and the previous snapshot; and
reflecting the changes within the second snapshot of the destination FSV.

9. The at least one non-transitory computer readable storage medium of claim 8 , wherein the steps further include:
excluding at least one file from the backup based on its type, and/or location within the source FSV.

10. The at least one non-transitory computer readable storage medium of claim 8 , wherein identifying the changes comprises:
identifying a change to a source file that occurred between the current snapshot and the previous snapshot, wherein a size of the source file satisfies a threshold;
obtaining (i) a first physical block map for the source file based on the current snapshot, and (ii) a second physical block map for the source file based on the previous snapshot;
identifying, based on the first physical block map and the second physical block map, at least one block that has changed within the source file;
identifying a destination file that corresponds to the source file; and
reflecting the change to the at least one block within the destination file.

11. The at least one non-transitory computer readable storage medium of claim 10 , wherein reflecting the change to the at least one block within the destination file comprises:
cloning the destination file to establish a cloned destination file;
reflecting the change to the at least one block within the cloned destination file; and
renaming the cloned destination file in accordance with the destination file.

12. The at least one non-transitory computer readable storage medium of claim 8 , wherein the steps further include, prior to identifying that the amount of available storage space is insufficient for generating the current snapshot:
generating the previous snapshot, wherein the previous snapshot includes both (i) the metadata for files within the source FSV, and (ii) data for the files within the source FSV; and
generating the destination FSV based on the previous snapshot of the source FSV.

13. The at least one non-transitory computer readable storage medium of claim 8 , wherein the data for files of the source FSV comprises binary comprises binary data of actual file contents.

14. The at least one non-transitory computer readable storage medium of claim 8 , wherein the changes are identified based on an event log associated with the source FSV.

15. A source computing device configured to perform a backup a source file system volume (FSV) associated with the source computing device, the source computing device comprising:
at least one processor; and
at least one memory configured to store instructions that, when executed by the at least one processor, cause the source computing device to:
in response to identifying that an amount of available storage space is insufficient for generating a current snapshot:
remove, from a previous snapshot, data for files of the source FSV to establish a sufficient amount of available storage space for generating the current snapshot, such that the previous snapshot includes metadata for files within the source FSV but does not include the data for the files within the source FSV;

generate the current snapshot of the source FSV, wherein the current snapshot complements the previous snapshot of the source FSV;
generate, within a destination storage device, a second snapshot of a destination FSV, wherein the source FSV corresponds to the destination FSV;
ide

Assignees

• Apple Inc

Inventors

• Cisler Pavel
• Sokolov Pavel
• Giampaolo Dominic B
• Weiss Eric A
• Wolf Christopher A

Classifications

• G06F16/166

  File name conversion · CPC title

• G06F11/1451 Primary

  by selection of backup contents · CPC title

• G06F2201/84

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

• G06F16/128

  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

• G06F16/1727

  Details of free space management performed by the file system (saving storage space on storage systems G06F3/0608; management of blocks in storage devices G06F3/064) · CPC title