Techniques for preserving clone relationships between files

Patent metadata

Field	Value
Publication number	US-11989095-B2
Application number	US-202218063655-A
Country	US
Kind code	B2
Filing date	Dec 8, 2022
Priority date	Jun 2, 2017
Publication date	May 21, 2024
Grant date	May 21, 2024

Abstract

The described embodiments set forth techniques for preserving clone relationships between files at a computing device. In particular, the techniques involve identifying clone relationships between files in conjunction with performing operations on the files where it can be beneficial to preserve the clone relationships. The operations can include, for example, preserving clone relationships between files that are being copied from a source storage device (that supports file cloning) to a destination storage device that supports file cloning. Additionally, the operations can include preserving clone relationships when backing up and restoring files between a source storage device (that supports file cloning) and a destination storage device that does not support file cloning. In this manner, the various benefits afforded by the clone relationships between files can be retained even as the files are propagated to destination storage devices that may or may not support file cloning.

First claim

What is claimed is:

1. A method for retaining clone relationships between files when performing backup and restore operations, the method comprising:
receiving a request to back up at least two source files from a source storage device to a destination storage device, wherein the at least two source files are members of a clone relationship;
establishing, within the destination storage device, destination files that correspond to the at least two source files; and
updating metadata associated with each destination file to reflect the clone relationship.

2. The method of claim 1 , wherein, when the clone relationship is a perfect clone relationship, establishing the destination files comprises:
identifying a first source file of the at least two source files;
copying data of the first source file from the source storage device to the destination storage device to establish a first destination file;
for each subsequent source file of the at least two source files:
establishing a subsequent destination file at the destination storage device as a hard-link to the first destination file, and

establishing metadata for at least one of the destination files, wherein the metadata indicates that the destination files are perfect clones.

3. The method of claim 2 , further comprising:
receiving a second request to restore the destination files to a second destination storage device;
identifying the first destination file based on the metadata;
copying the first destination file to the second destination storage device to establish a restored file; and
based on the metadata, and for each subsequent destination file of the destination files:
establishing a subsequent restored file at the second destination storage device as a clone of the restored file.

4. The method of claim 1 , wherein, when the clone relationship is a partial clone relationship, establishing the destination files comprises:
for each source file of the at least two source files:
copying data of the source file from the source storage device to the destination storage device to establish a respective destination file, and
populating (i) block map information, and (ii) timestamp information associated with the source file into metadata associated with the respective destination file.

5. The method of claim 4 , further comprising:
receiving a second request to restore the destination files to a second destination storage device;
identifying a first destination file based on the block map information populated in the metadata associated with the destination files;
copying the first destination file to the second destination storage device to establish a restored file; and
based on the block map information, and for each subsequent destination file of the destination files:
establishing a subsequent restored file at the second destination storage device, wherein the partial clone relationship between the subsequent restored file and at least one other restored file remains intact.

6. The method of claim 5 , wherein an order by which the subsequent restored files are established at the second destination storage device is based on the timestamp information included in the metadata associated with the destination files.

7. The method of claim 1 , further comprising, prior to establishing, within the destination storage device, destination files that correspond to the at least two source files:
identifying file sizes associated with the at least two source files; and
verifying that the destination storage device includes enough free space to store the destination files.

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 computing device, cause the computing device to retain clone relationships between files when performing backup and restore operations, by carrying out steps that include:
receiving a request to back up at least two source files from a source storage device to a destination storage device, wherein the at least two source files are members of a clone relationship;
establishing, within the destination storage device, destination files that correspond to the at least two source files; and
updating metadata associated with each destination file to reflect the clone relationship.

9. The at least one non-transitory computer readable storage medium of claim 8 , wherein, when the clone relationship is a perfect clone relationship, establishing the destination files comprises:
identifying a first source file of the at least two source files;
copying data of the first source file from the source storage device to the destination storage device to establish a first destination file;
for each subsequent source file of the at least two source files:
establishing a subsequent destination file at the destination storage device as a hard-link to the first destination file, and

establishing metadata for at least one of the destination files, wherein the metadata indicates that the destination files are perfect clones.

10. The at least one non-transitory computer readable storage medium of claim 9 , wherein the steps further include:
receiving a second request to restore the destination files to a second destination storage device;
identifying the first destination file based on the metadata;
copying the first destination file to the second destination storage device to establish a restored file; and
based on the metadata, and for each subsequent destination file of the destination files:
establishing a subsequent restored file at the second destination storage device as a clone of the restored file.

11. The at least one non-transitory computer readable storage medium of claim 8 , wherein, when the clone relationship is a partial clone relationship, establishing the destination files comprises:
for each source file of the at least two source files:
copying data of the source file from the source storage device to the destination storage device to establish a respective destination file, and
populating (i) block map information, and (ii) timestamp information associated with the source file into metadata associated with the respective destination file.

12. The at least one non-transitory computer readable storage medium of claim 11 , wherein the steps further include:
receiving a second request to restore the destination files to a second destination storage device;
identifying a first destination file based on the block map information populated in the metadata associated with the destination files;
copying the first destination file to the second destination storage device to establish a restored file; and
based on the block map information, and for each subsequent destination file of the destination files:
establishing a subsequent restored file at the second destination storage device, wherein the partial clone relationship between the subsequent restored file and at least one other restored file remains intact.

13. The at least one non-transitory computer readable storage medium of claim 12 , wherein an order by which the subsequent restored files are established at the second destination storage device is based on the timestamp information included in the metadata associated with the destination files.

14. The at least one non-transitory computer readable storage medium of claim 8 , wherein the steps further include, prior to establishing, within the destination storage device, destination files that correspond to the at least two source files:
identifying file sizes associated with the at least two source f

Assignees

• Apple Inc

Inventors

• Cisler Pavel
• Wolf Christopher A
• Vandereyken Loic E
• Weiss Eric A

Classifications

• G06F11/1448 Primary

  Management of the data involved in backup or backup restore · CPC title

• G06F3/0486

  Drag-and-drop · CPC title

• G06F11/1469

  Backup restoration techniques · CPC title

• G06F16/11

  File system administration, e.g. details of archiving or snapshots (error detection or correction of the data by redundancy in operations G06F11/14) · 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