Efficient data rehydration

• US 8,849,878 B1
• Filed: 09/30/2011
• Issued: 09/30/2014
• 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, Ravan, Daniel, Varma, Venu
• Primary Examiner(s): Chen, Susan
• Application Number:
  US13/250,557
• Time in Patent Office: 1,096 Days
• Field of Search: 707/624, 707/642, 707/646, 707/89, 707/9, 711/117, 703/23, 705/50, 370/255
• US Class Current: 707/823
• 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 efficient data rehydration that minimizes an amount of data transferred, comprising:

a server for receiving a restore list indicating a data set comprising a full synthetic backup or a clone of data at a client system, wherein;

the restore list is created by checking files when the files are coalesced as the files are added to the restore list, wherein coalescing comprises merging adjacent files to reduce retrieve file calls and an uncoalesced restore list is never created;

the data at the client system is backed up at a previous time and stored at one or more backup storage nodes; and

the full synthetic backup or the clone is generated after the previous time using only data stored at the one or more backup storage nodes without communicating with or retrieving data from the client system; and

one or more reader device managers for reading, using a processor, a data set comprising the full synthetic backup or the clone indicated by the restore list from the one or more backup storage nodes, wherein;

the restore list comprises a plurality of storage locations and lengths that indicate data chunks or segments from the client system that have been previously backed up and stored as part of a full or as an incremental backup session on at least a first backup storage node; and

the one or more backup storage nodes include at least one full backup session and one or incremental backup sessions.

2. A system as in claim 1, wherein the restore list comprises a coalesced restore list.

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

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

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

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

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

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

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

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

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

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

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

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

15. A system as in claim 1, wherein the one or more backup storage nodes include one or more incremental backup sessions that are generated and stored after a full backup session with respect to time.

16. A system as in claim 15, wherein the full backup session is located generated and stored between at least two incremental backup sessions with respect to time.

17. A system as in claim 1, further comprising a writer device manager for transferring the data set comprising the full synthetic backup or the clone to at least one of the one or more backup storage node.

18. A system as in claim 17, further comprising a verifier for verifying, using the computer processor, the transfer of the data set comprising the full synthetic backup or the clone to the at least one backup storage node.

19. A system as in claim 18, wherein the verifier verifies the transfer of the data set including by calculating a checksum for the transferred data set.

20. A method for efficient data rehydration that minimizes an amount of data transferred, comprising:

receiving a restore list indicating a data set comprising a full synthetic backup or a clone of data at a client system, wherein;

the restore list is created by checking files when the files are coalesced as the files are added to the restore list, wherein coalescing comprises merging adjacent files to reduce retrieve file calls and an uncoalesced restore list is never created;

the data at the client system is backed up at a previous time and stored at one or more backup storage nodes; and

the full synthetic backup or the clone is generated after the previous time using only data stored at the one or more backup storage nodes without communicating with or retrieving data from the client system; and

reading, using a processor, a data set comprising the full synthetic backup or the clone indicated by the restore list from the one or more backup storage nodes, wherein;

the restore list comprises a plurality of storage locations and lengths that indicate data chunks or segments from the client system that have been previously backed up and stored as part of a full or as an incremental backup session on at least a first backup storage node; and

the one or more backup storage nodes include at least one full backup and one or more incremental backup sessions.

21. A computer program product for efficient data rehydration that minimizes an amount of data transferred, the computer program product being embodied in a tangible and non-transitory computer readable storage medium and comprising computer instructions for:

receiving a restore list indicating a data set comprising a full synthetic backup or a clone of data at a client system, wherein;

the restore list is created by checking files when the files are coalesced as the files are added to the restore list, wherein coalescing comprises merging adjacent files to reduce retrieve file calls and an uncoalesced restore list is never created;

the data at the client system is backed up at a previous time and stored at one or more backup storage nodes; and

the full synthetic backup or the clone is generated after the previous time using only data stored at the one or more backup storage nodes without communicating with or retrieving data from the client system; and

reading a data set comprising the full synthetic backup or the clone indicated by the restore list from the one or more backup storage nodes, wherein;

the restore list comprises a plurality of storage locations and lengths that indicate data chunks or segments from the client system that have been previously backed up and stored as part of a full or as an incremental backup session on at least a first backup storage node; and

the one or more backup storage nodes include at least one full backup and one or more incremental backup sessions.