EFFICIENT DATA REHYDRATION

• US 20150052366A1
• Filed: 08/22/2014
• Published: 02/19/2015
• Est. Priority Date: 09/30/2011
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: EMC Corporation (Dell Technologies Inc.)
• Inventors: Bachu, Kiran K., Varma, Venu, Ravan, Daniel
• Granted Patent: US 9,633,065 B2
• Time in Patent Office: Days
• US Class Current: 713/189
• 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:

a server for receiving a restore list comprising a plurality of storage locations and lengths for performing a data rehydration;

one or more reader device managers 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, 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;

a writer device manager for transferring the data set to a save node; and

a verifier for verifying 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 restore list comprises a coalesced restore list.

5. A system as in claim 1, wherein the server is for determining that the files are encrypted.

6. A system as in claim 5, wherein the server is for receiving an encryption key associated with the files.

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

8. A system as in claim 1, wherein the server is for determining that the files are compressed.

9. A system as in claim 8, wherein the server is for receiving a compression key associated with the files.

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

11. A system as in claim 1, wherein the server is for determining that the files are deduplicated.

12. A system as in claim 11, wherein the server is for receiving deduplication information associated with the files.

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

14. A system as in claim 1, wherein in the event that the dataset is to be encrypted, encrypting the data set before transfer.

15. A system as in claim 1, wherein in the event that the data set is to be compressed, compressing the data set before transfer.

16. A system as in claim 1, wherein in the event that the data set is to be deduplicated, deduplicating the data set before transfer.

17. A method for efficient data rehydration, comprising:

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

retrieving, on one or more source storage nodes, a data set indicated by the restore list, wherein the restore list indicates the plurality of storage locations and lengths storing chunks from a client system that were stored as part of a full or as an incremental backup session on a storage device attached to a storage node;

transferring the data set to a save node; and

verifying transfer of the data set.

18. 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 a restore list comprising a plurality of storage locations and lengths for performing a data rehydration;

retrieving, on one or more source storage nodes, a data set indicated by the restore list, wherein the restore list indicates the plurality of storage locations and lengths storing chunks from a client system that were stored as part of a full or as an incremental backup session on a storage device attached to a storage node;

transferring the data set to a save node; and

verifying transfer of the data set.