Data migration preserving storage efficiency
US-2016088080-A1 · Mar 24, 2016 · US
US11550665B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11550665-B2 |
| Application number | US-201715721311-A |
| Country | US |
| Kind code | B2 |
| Filing date | Sep 29, 2017 |
| Priority date | Jun 2, 2017 |
| Publication date | Jan 10, 2023 |
| Grant date | Jan 10, 2023 |
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.
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.
Opening claim text (preview).
What is claimed is: 1. A method for retaining clone relationships between files when performing file copy operations in order to preserve available storage space, the method comprising: receiving a request to copy a first file and a second file from a source storage device to a destination storage device, wherein a first clone relationship exists between the first and second files; identifying that the destination storage device supports file cloning capabilities; and performing, on the destination storage device: (1) a file copy operation that causes a copy of the first file to be established at the destination storage device as a third file, and (2) a file cloning operation that causes a clone of the third file to be established at the destination storage device as a fourth file, wherein: the fourth file contains only a subset of data of the third file such that a second clone relationship exists between the third and fourth files that is the same as the first clone relationship between the first and second files. 2. The method of claim 1 , wherein: the first clone relationship is a perfect clone relationship when extents referred to by the first and second files are identical in nature, and the first clone relationship is a partial clone relationship when at least one physical block overlap exists between extents of the first and second files. 3. The method of claim 1 , wherein the second clone relationship is the same as the first clone relationship when the third and fourth files are cloned in the same manner as the first and second files. 4. The method of claim 1 , where the subset of data comprises information that refers to at least one extent that is shared between the third and fourth files. 5. The method of claim 1 , wherein the request is generated in response to: receiving a selection of the first and second files in a user interface (UI); and receiving a copy command associated with the first and second files. 6. The method of claim 5 , wherein the copy command is issued in conjunction with receiving, at a user interface (UI) element that represents the destination storage device, a drop event from a drag of the selection of the first and second files. 7. The method of claim 5 , wherein the copy command is issued in conjunction with (1) (i) receiving a second selection of a copy UI element/a third selection of a paste UI element within a context menu displayed in association with the selection, or (2) detecting (i) a first hotkey that corresponds to the copy command and (ii) a second hotkey that corresponds to a paste command. 8. At least one non-transitory computer readable storage medium configured to store instructions that, when executed by a processor included in a computing device, cause the computing device to retain clone relationships between files when performing file copy operations in order to preserve available storage space, by carrying out steps that include: receiving a request to copy a first file and a second file from a source storage device to a destination storage device, wherein a first clone relationship exists between the first and second files; identifying that the destination storage device supports file cloning capabilities; and performing, on the destination storage device: (1) a file copy operation that causes a copy of the first file to be established at the destination storage device as a third file, and (2) a file cloning operation that causes a clone of the third file to be established at the destination storage device as a fourth file, wherein: the fourth file contains only a subset of data of the third file such that a second clone relationship exists between the third and fourth files that is the same as the first clone relationship between the first and second files. 9. The non-transitory computer readable storage medium of claim 8 , wherein: the first clone relationship is a perfect clone relationship when extents referred to by the first and second files are identical in nature, and the first clone relationship is a partial clone relationship when at least one physical block overlap exists between extents of the first and second files. 10. The non-transitory computer readable storage medium of claim 8 , wherein the second clone relationship is the same as the first clone relationship when the third and fourth files are cloned in the same manner as the first and second files. 11. The non-transitory computer readable storage medium of claim 8 , where the subset of data comprises information that refers to at least one extent that is shared between the third and fourth files. 12. The non-transitory computer readable storage medium of claim 8 , wherein the request is generated in response to: receiving a selection of the first and second files in a user interface (UI); and receiving a copy command associated with the first and second files. 13. The non-transitory computer readable storage medium of claim 12 , wherein the copy command is issued in conjunction with receiving, at a user interface (UI) element that represents the destination storage device, a drop event from a drag of the selection of the first and second files. 14. The non-transitory computer readable storage medium of claim 12 , wherein the copy command is issued in conjunction with (1) (i) receiving a second selection of a copy UI element/a third selection of a paste UI element within a context menu displayed in association with the selection, or (2) detecting (i) a first hotkey that corresponds to the copy command and (ii) a second hotkey that corresponds to a paste command. 15. A computing device configured to retain clone relationships between files when performing file copy operations in order to preserve available storage space, the computing device comprising a processor configured to cause the computing device to carry out steps that include: receiving a request to copy a first file and a second file from a source storage device to a destination storage device, wherein a first clone relationship exists between the first and second files; identifying that the destination storage device supports file cloning capabilities; and performing, on the destination storage device: (1) a file copy operation that causes a copy of the first file to be established at the destination storage device as a third file, and (2) a file cloning operation that causes a clone of the third file to be established at the destination storage device as a fourth file, wherein: the fourth file contains only a subset of data of the third file such that a second clone relationship exists between the third and fourth files that is the same as the first clone relationship between the first and second files. 16. The computing device of claim 15 , wherein: the first clone relationship is a perfect clone relationship when extents referred to by the first and second files are identical in nature, and the first clone relationship is a partial clone relationship when at least one physical block overlap exists between extents of the first and second files. 17. The computing device of claim 15 , wherein the second clone relationship is the same as the first clone relationship when the third and fourth files are cloned in the same manner as the first and second files. 18. The computing device of claim 15 , where the subset of data comprises information that refers to at least one extent that is shared between the third and fourth files. 19. The computing device of claim 15 , wherein the request is generated in response t
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
Solving problems relating to consistency · CPC title
Details of user interfaces specifically adapted to file systems, e.g. browsing and visualisation, 2d or 3d GUIs (query results presentation G06F16/156) · 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
Management of the data involved in backup or backup restore · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.