Efficient data rehydration

• US 9,633,065 B2
• Filed: 08/22/2014
• Issued: 04/25/2017
• Est. Priority Date: 09/30/2011
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Inventors: Bachu, Kiran K., Varma, Venu, Ravan, Daniel
• Primary Examiner(s): Chen, Susan
• Application Number:
  US14/466,756
• Publication Number:
  US 20150052366A1
• Time in Patent Office: 977 Days
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 21/602 Providing cryptographic facilities or services
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

A system for an efficient data rehydration comprises a server, one or more reader device managers, a writer device manager, and a verifier. The server is for receiving a restore list comprising a plurality of storage locations and lengths for performing a data rehydration. The one or more reader device managers is for reading a data set indicated by the restore list by reading the plurality of storage locations for the lengths from one or more storage nodes. The plurality of storage locations and lengths indicate chunks from a client system stored as part of a full or as an incremental backup session on a storage device attached to a storage node. The writer device manager is for transferring the data set to a save node. A verifier is for verifying transfer of the data set.

Claims

1. A system for an efficient data rehydration comprising:

an interface configured to receive a restore list comprising a plurality of storage locations and lengths for performing a data rehydration; and

a computer processor configured to;

retrieve, from one or more storage nodes, a data set indicated by the restore list, wherein the plurality of storage locations and lengths indicate chunks from a client system stored as part of a full or as an incremental backup session on a storage device attached to a storage node of the one or more storage nodes, wherein the restore list is created by coalescing files as they are added to the restore list, wherein coalescing comprises merging the files in the event that the files reside at adjacent points in the full or the incremental backup session;

transfer the data set to a save node; and

verify the transfer of the data set.

2. A system as in claim 1, wherein the performing the data rehydration is part of generating a full synthetic backup.

3. A system as in claim 1, wherein the performing the data rehydration is part of generating a clone.

4. A system as in claim 1, wherein the processor is further configured to determine whether the files are encrypted.

5. A system as in claim 4, wherein the processor is further configured to receive an encryption key associated with the files.

6. A system as in claim 5, wherein the files are decrypted before transferring the data set using the encryption key.

7. A system as in claim 1, wherein the processor is further configured to determine whether the files are compressed.

8. A system as in claim 7, wherein the processor is further configured to receive a compression key associated with the files.

9. A system as in claim 8, wherein the files are decompressed before transferring the data set using the compression key.

10. A system as in claim 1, wherein the processor is further configured to determine whether the files are deduplicated.

11. A system as in claim 10, wherein the processor is further configured to receive deduplication information associated with the files.

12. A system as in claim 11, wherein the files are undeduplicated before transferring the data set using the deduplication information.

13. A system as in claim 1, wherein the processor is further configured to in the event that the dataset is to be encrypted, encrypt the data set before transfer.

14. A system as in claim 1, wherein the processor is further configured to in the event that the data set is to be compressed, compress the data set before transfer.

15. A system as in claim 1, wherein the processor is further configured to in the event that the data set is to be deduplicated, deduplicate the data set before transfer.

16. A method for efficient data rehydration, comprising:

receiving, using an interface, a restore list comprising a plurality of storage locations and lengths for performing a data rehydration;

retrieving, using a computer processor, from one or more storage nodes, a data set indicated by the restore list, wherein the plurality of storage locations and lengths indicate chunks from a client system stored as part of a full or as an incremental backup session on a storage device attached to a storage node of the one or more storage nodes, wherein the restore list is created by coalescing files as they are added to the restore list, wherein coalescing comprises merging the files in the event that the files reside at adjacent points in the full or the incremental backup session;

transferring the data set to a save node; and

verifying transfer of the data set.

17. A computer program product for efficient data rehydration, the computer program product being embodied in a tangible computer readable storage medium and comprising computer instructions for:

receiving, using an interface, a restore list comprising a plurality of storage locations and lengths for performing a data rehydration;

retrieving, using a computer processor, from one or more storage nodes, a data set indicated by the restore list, wherein the plurality of storage locations and lengths indicate chunks from a client system stored as part of a full or as an incremental backup session on a storage device attached to a storage node of the one or more storage nodes, wherein the restore list is created by coalescing files as they are added to the restore list, wherein coalescing comprises merging the files in the event that the files reside at adjacent points in the full or the incremental backup session;

transferring the data set to a save node; and

verifying transfer of the data set.