File Deduplication using Copy-on-Write Storage Tiers

• US 20090204650A1
• Filed: 11/11/2008
• Published: 08/13/2009
• Est. Priority Date: 11/15/2007
• Status: Abandoned Application

• Current Assignee: RPX Corporation
• Original Assignee: Attune Systems, Inc. (F5 Incorporated)
• Inventors: Wong, Thomas K., Vogel, Ron S.
• Application Number:
  US12/268,575
• Publication Number:
  US 20090204650A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/1744 using compression, e.g. sparse files

Abstract

A method and apparatus for removing duplicated data in a file system utilizing copy-on-write storage tiers. A synthetic namespace is created via file virtualization, and is comprised of one or more file systems. Deduplication is applied at the namespace level and on all of the file systems comprising the synthetic namespace. A set of storage policies selects a set of files from the namespace that become the candidates for deduplication. The entire chosen set is migrated to a Copy-On-Write (COW) storage tier. This Copy-On-Write storage tier may be a virtual storage tier that resides within another physical storage tier (such as tier-1 or tier-2 storage). Each file stored in a Copy-On-Write storage tier is deduped, regardless of whether there is any file with identical contents in the set or in the COW storage tier. After deduplication, the deduped file becomes a sparse file where all the files storage space is reclaimed while all the file'"'"'s attributes, including size, remain. A copy of each file that is deduped is left as a mirror copy and is stored in a mirror server. If two mirror copies have identical contents, only one mirror copy will be stored in the mirror server. Read access to a file in the COW storage tier (COW file) is redirected to its mirror copy if the file is deduped. When the first write to a COW file is received, the mirror copy stored in the mirror server is copied as the contents of the COW file, and the association from the COW file to its mirror copy is discarded. Thereafter, access to the “un-deduped” file will resume normally from the COW file.

Claims

1. A method of deduplicating files from a primary storage tier by a file virtualization appliance in a file storage system, the method comprising:

associating a number of files from the primary storage tier with a copy-on-write storage tier having a designated mirror server; and

deduplicating the files associated with the copy-on-write storage tier, such deduplicating including;

storing in the designated mirror server a single copy of the file contents for each duplicate and non-duplicate file associated with the copy-on-write storage tier;

deleting the file contents from each deduplicated file in the copy-on-write storage tier to leave a sparse file; and

storing metadata for each of the files, the metadata associating each sparse file with the corresponding single copy of the file contents stored in the designated mirror server.

2. A method according to claim 1, wherein associating a number of files from the primary storage tier with a copy-on-write storage tier comprises:

maintaining the copy-on-write storage tier separately from the primary storage tier; and

migrating the number of files from the primary storage tier to the copy-on-write storage tier.

3. A method according to claim 2, wherein maintaining the copy-on-write storage tier separately from the primary storage tier comprises creating a synthetic namespace for the copy-on-write storage tier using file virtualization, the synthetic namespace associated with a number of file servers, and wherein migrating the number of files from the primary storage tier to the copy-on-write storage tier comprises migrating a selected set of files from the synthetic namespace to the copy-on-write storage tier.

4. A method according to claim 1, wherein associating a number of files from the primary storage tier with a copy-on-write storage tier comprises:

marking the number of files as being associated with the copy-on-write storage tier, wherein the copy-on-write storage tier is a virtual copy-on-write storage tier.

5. A method according to claim 1, wherein associating a number of files from the primary storage tier with a copy-on-write storage tier comprises:

maintaining a set of storage policies identifying files to be associated with the copy-on-write storage tier; and

associating the number of files with the copy-on-write storage tier based on the set of storage policies.

6. A method according to claim 1, wherein storing in the designated mirror server a single copy of the file contents for each duplicate and non-duplicate file associated with the copy-on-write storage tier comprises:

determining whether the file contents of a selected file in the copy-on-write storage tier match the file contents of a previously deduplicated file having a single copy of file contents stored in the designated mirror server; and

when the file contents of the first selected file do not match the file contents of any previously deduplicated file, storing the file contents of the selected file in the designated mirror server.

7. A method according to claim 6, wherein determining whether the file contents of a selected file in the copy-on-write storage tier match the file contents of a previously deduplicated file having a single copy of file contents stored in the designated mirror server comprises:

comparing a hash value associated with the selected file to hash values associated with the single copies of file contents for the previously deduplicated files stored in the designated mirror server.

8. A method according to claim 1, further comprising:

purging unused mirror copies from the designated mirror server.

9. A method according to claim 8, wherein purging unused mirror copies from the designated mirror server comprises:

suspending file deduplication operations;

identifying mirror copies in the designated mirror server that are no longer in use;

purging the unused mirror copies from the designated mirror server; and

enabling file deduplication operations.

10. A method according to claim 9, wherein identifying mirror copies in the designated mirror server that are no longer in use comprises:

identifying mirror copies in the designated mirror server that are no longer associated with existing files associated with the copy-on-write storage tier.

11. A method according to claim 10, wherein identifying mirror copies in the designated mirror server that are no longer associated with existing files in the copy-on-write storage tier comprises:

constructing a list of hash values associated with existing files in the copy-on-write storage tier; and

for each mirror copy in the designated mirror server, comparing a hash value associated with the mirror copy to the hash values in the list of hash values, wherein the mirror copy is deemed to be an unused mirror copy when the hash value associated with the mirror copy is not in the list of hash values.

12. A method according to claim 1, further comprising:

receiving from a client an open request for a specified file associated with the copy-on-write storage tier;

when the specified file is a non-deduplicated file;

creating a copy-on-write file handle for the specified file;

marking the copy-on-write file handle as ready; and

returning the copy-on write file handle to the client;

when the specified file is a deduplicated file having a mirror copy of the file contents stored in the designated mirror server;

opening the specified file;

creating a copy-on-write file handle for the specified file;

marking the copy-on-write file handle as not ready;

returning the copy-on write file handle to the client;

when the open request is for read;

obtaining a mirror file handle for the mirror copy from the designated mirror server;

associating the mirror file handle with the copy-on-write file handle;

opening the mirror copy;

marking the copy-on-write handle as ready, if the open mirror copy is successful; and

marking the copy-on-write handle as ready with error, if the open mirror copy is unsuccessful; and

when the open request is for update;

filling the contents of the specified file from the mirror copy of the file contents stored in the designated mirror server; and

marking the copy-on-write handle as ready.

13. A method according to claim 12, wherein the mirror file handle for the mirror copy is obtained from the designated mirror server based on hash values associated with the specified file and the mirror copy.

14. A method according to claim 12, wherein the contents of the specified file are filled from the copy of the file contents stored in the designated mirror server by a background task.

15. A method according to claim 12, further comprising:

receiving from the client a file request including the copy-on-write file handle;

when the copy-on-write file handle is marked as not ready;

suspending the file request until the contents of the specified file have been refilled from the mirror copy;

marking the copy-on-write file handle as ready if the contents of the specified file have been refilled successfully; and

marking the copy-on-write file handle as ready with error if the contents of the specified file have been refilled unsuccessfully;

when the copy-on-write file handle is marked as ready with error, returning an error indication to the client;

when the file request is a read operation and the copy-on-write file handle is associated with a mirror file handle;

using the mirror file handle to retrieve data from the mirror copy stored in the designated mirror server; and

returning the data to the client;

when the file request is a read operation and the copy-on-write file handle is not associated with a mirror file handle;

using the copy-on-write file handle to retrieve data from the file; and

returning the data to the client;

when the file request is a write operation, using the copy-on-write file handle to write data to the file in the copy-on-write storage tier; and

otherwise sending the file request to the file virtualization appliance.

16. A file virtualization appliance for deduplicating files from a primary storage tier in a file storage system, the file virtualization appliance comprising:

a network interface for communication with the file servers; and

a processor coupled to the network interface and configured to associate a number of files from the primary storage tier with a copy-on-write storage tier having a designated mirror server and to deduplicate the files associated with the copy-on-write storage tier, such deduplicating including;

storing in the designated mirror server a single copy of the file contents for each duplicate and non-duplicate file associated with the copy-on-write storage tier;

deleting the file contents from each deduplicated file in the copy-on-write storage tier to leave a sparse file; and

storing metadata for each of the files, the metadata associating each sparse file with the corresponding single copy of the file contents stored in the designated mirror server.

17. A file virtualization appliance according to claim 16, wherein the processor is configured to associate a number of files from the primary storage tier with a copy-on-write storage tier by maintaining the copy-on-write storage tier separately from the primary storage tier and migrating the number of files from the primary storage tier to the copy-on-write storage tier.

18. A file virtualization appliance according to claim 17, wherein the processor is configured to maintain the copy-on-write storage tier separately from the primary storage tier by creating a synthetic namespace for the copy-on-write storage tier using file virtualization, the synthetic namespace associated with a number of file servers, and wherein migrating the number of files from the primary storage tier to the copy-on-write storage tier comprises migrating a selected set of files from the synthetic namespace to the copy-on-write storage tier.

19. A file virtualization appliance according to claim 16, wherein the processor is configured to associate a number of files from the primary storage tier with a copy-on-write storage tier by marking the number of files as being associated with the copy-on-write storage tier, wherein the copy-on-write storage tier is a virtual copy-on-write storage tier.

20. A file virtualization appliance according to claim 16, wherein the processor is configured to associate a number of files from the primary storage tier with a copy-on-write storage tier by maintaining a set of storage policies identifying files to be associated with the copy-on-write storage tier and associating the number of files with the copy-on-write storage tier based on the set of storage policies.

21. A file virtualization appliance according to claim 16, wherein the processor is configured to store a single copy of the file contents for each duplicate and non-duplicate file associated with the copy-on-write storage tier by determining whether the file contents of a selected file in the copy-on-write storage tier match the file contents of a previously deduplicated file having a single copy of file contents stored in the designated mirror server and when the file contents of the first selected file do not match the file contents of any previously deduplicated file, storing the file contents of the selected file in the designated mirror server.

22. A file virtualization appliance according to claim 21, wherein the processor is configured to determine whether the file contents of a selected file in the copy-on-write storage tier match the file contents of a previously deduplicated file having a single copy of file contents stored in the designated mirror server by comparing a hash value associated with the selected file to hash values associated with the single copies of file contents for the previously deduplicated files stored in the designated mirror server.

23. A file virtualization appliance according to claim 16, wherein the processor is further configured to purge unused mirror copies from the designated mirror server.

24. A file virtualization appliance according to claim 23, wherein the processor is configured to purge unused mirror copies from the designated mirror server by suspending file deduplication operations;

identifying mirror copies in the designated mirror server that are no longer in use;

purging the unused mirror copies from the designated mirror server; and

enabling file deduplication operations.

25. A file virtualization appliance according to claim 24, wherein the processor is configured to identify mirror copies in the designated mirror server that are no longer in use by identifying mirror copies in the designated mirror server that are no longer associated with existing files associated with the copy-on-write storage tier.

26. A file virtualization appliance according to claim 25, wherein the processor is configured to identify mirror copies in the designated mirror server that are no longer associated with existing files in the copy-on-write storage tier by constructing a list of hash values associated with existing files in the copy-on-write storage tier and for each mirror copy in the designated mirror server, comparing a hash value associated with the mirror copy to the hash values in the list of hash values, wherein the mirror copy is deemed to be an unused mirror copy when the hash value associated with the mirror copy is not in the list of hash values.

27. A method according to claim 16, wherein the processor is further configured to process open requests for files associated with the copy-on-write storage tier, such processing of open requests comprising:

receiving from a client an open request for a specified file associated with the copy-on-write storage tier;

when the specified file is a non-deduplicated file;

creating a copy-on-write file handle for the specified file;

marking the copy-on-write file handle as ready; and

returning the copy-on write file handle to the client;

when the specified file is a deduplicated file having a mirror copy of the file contents stored in the designated mirror server;

opening the specified file;

creating a copy-on-write file handle for the specified file;

marking the copy-on-write file handle as not ready;

returning the copy-on write file handle to the client;

when the open request is for read;

obtaining a mirror file handle for the mirror copy from the designated mirror server;

associating the mirror file handle with the copy-on-write file handle;

opening the mirror copy;

marking the copy-on-write handle as ready, if the open mirror copy is successful; and

marking the copy-on-write handle as ready with error, if the open mirror copy is unsuccessful; and

when the open request is for update;

filling the contents of the specified file from the mirror copy of the file contents stored in the designated mirror server; and

marking the copy-on-write handle as ready.

28. A method according to claim 27, wherein the processor is configured to obtain the mirror file handle for the mirror copy from the designated mirror server based on hash values associated with the specified file and the mirror copy.

29. A method according to claim 27, wherein the processor is configured to fill the contents of the specified file from the copy of the file contents stored in the designated mirror server using a background task.

30. A method according to claim 27, wherein the processor is further configured to process file requests, such processing of file requests comprising:

receiving from the client a file request including the copy-on-write file handle;

when the copy-on-write file handle is marked as not ready;

suspending the file request until the contents of the specified file have been refilled from the mirror copy;

marking the copy-on-write file handle as ready if the contents of the specified file have been refilled successfully; and

marking the copy-on-write file handle as ready with error if the contents of the specified file have been refilled unsuccessfully;

when the copy-on-write file handle is marked as ready with error, returning an error indication to the client;

when the file request is a read operation and the copy-on-write file handle is associated with a mirror file handle;

using the mirror file handle to retrieve data from the mirror copy stored in the designated mirror server; and

returning the data to the client;

when the file request is a read operation and the copy-on-write file handle is not associated with a mirror file handle;

using the copy-on-write file handle to retrieve data from the file; and

returning the data to the client;

when the file request is a write operation, using the copy-on-write file handle to write data to the file in the copy-on-write storage tier; and

otherwise sending the file request to the file virtualization appliance.