MULTI-CLIENT CLUSTER-BASED BACKUP AND RESTORE

• US 20080168111A1
• Filed: 02/28/2008
• Published: 07/10/2008
• Est. Priority Date: 04/20/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Lyon, James M.
• Granted Patent: US 7,447,857 B2
• Time in Patent Office: Days
• US Class Current: 707/204
• CPC Class Codes: G06F 11/1453 using de-duplication of the data
• CPC Class Codes: G06F 11/1456 Hardware arrangements for backup
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: Y10S 707/99953 Recoverability
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

Backup and restore technology comprising a backup engine, one or more client backup modules coupled to the backup engine via a backup protocol, and a backup database coupled to the backup engine, the backup database including a set of clusters, the set of clusters forming one or more backups, wherein each cluster of the set of clusters is unique such that single-instance storage across clients is achieved.

Claims

1. A backup system comprising:

a backup engine;

a backup protocol configured to couple a client backup module to the backup engine;

a backup database coupled to the backup engine, the backup database comprising a first set of clusters, the first set of clusters forming one or more backups, wherein each cluster of the first set of clusters is unique such that single-instance storage across clients is achieved;

a processor; and

a memory operatively connected to the processor, the memory having computer-executable instructions that when executed by the processor provide;

the backup engine configured to;

receive from the client backup module a set of current cluster hashes, wherein each one of the set of current cluster hashes is calculated based on a corresponding one of a plurality of clusters of one or more storage devices, and wherein each one of the set of current cluster hashes uniquely identifies the corresponding one of the plurality of clusters;

reduce the set of current cluster hashes to include only those not already stored in the backup database, resulting in a reduced set of cluster hashes;

receive from the client backup module a reduced set of clusters of the plurality of clusters identified by the reduced set of cluster hashes; and

store in the backup database the reduced set of clusters, wherein each cluster stored in the backup database is unique, wherein single instance storage in the backup database is provided.

2. The backup system of claim 1 wherein the backup database further includes a first set of cluster hashes, each cluster hash of the first set of cluster hashes associated with one cluster of the first set of clusters.

3. The backup system of claim 1, wherein:

the backup database includes a first set of file record hashes, the first set of file record hashes corresponding to a backup; and

the backup engine further configured to provide to the client backup module the first set of file record hashes, wherein the set of current cluster hashes corresponds to a list of potentially changed clusters based at least in part on comparing the first set of file record hashes to a second set of file record hashes.

4. The backup system of claim 1, wherein the set of current cluster hashes further:

is calculated based at least in part on a modified current in-use cluster list;

the modified current in-use cluster list is based on a fix-up list and a current in-use cluster list; and

the current in-use cluster list excludes clusters marked as not-in-use.

5. The backup system of claim 1 wherein the first set of clusters does not include clusters marked as not-in-use.

6. The backup system of claim 1 wherein the first set of clusters does not include clusters associated with ephemeral files.

7. The backup system of claim 6 wherein the ephemeral files include at least one of temporary data, temporary internet files, virtual memory cache files, page files, swap files, and hibernation files.

8. The backup system of claim 1, the backup engine further configured to include a recoverable commit operation during the store in the backup database operation.

9. The backup system of claim 1, the set of current cluster hashes calculated using a hashing function that calculates a fixed size hash value from an arbitrarily long input value, wherein the input value is cluster data.

10. A computer-readable medium encoded with computer-executable instructions embodying a backup system comprising a backup engine, the backup engine configured to:

communicate with a client backup module via a backup protocol;

communicate with a backup database, the backup database comprising a first set of clusters, the first set of clusters forming one or more backups, wherein each cluster of the first set of clusters is unique such that single-instance storage across clients is achieved;

receive from the client backup module a set of current cluster hashes, wherein each one of the set of current cluster hashes is calculated based on a corresponding one of a plurality of clusters of one or more storage devices, and wherein each one of the set of current cluster hashes uniquely identifies the corresponding one of the plurality of clusters;

reduce the set of current cluster hashes to include only those not already stored in the backup database, resulting in a reduced set of cluster hashes;

receive from the client backup module a reduced set of clusters of the plurality of clusters identified by the reduced set of cluster hashes; and

store in the backup database the reduced set of clusters, wherein each cluster stored in the backup database is unique, wherein single instance storage in the backup database is provided.

11. The computer readable medium of claim 10 wherein the backup database further includes a first set of cluster hashes, each cluster hash of the first set of cluster hashes associated with one cluster of the first set of clusters.

12. The computer readable medium of claim 10, wherein:

the backup database includes a first set of file record hashes, the first set of file record hashes corresponding to one of the one or more backups; and

the backup engine further configured to provide to the client backup module the first set of file record hashes, wherein the set of current cluster hashes corresponds to a list of potentially changed clusters based at least in part on comparing the first set of file record hashes to a second set of file record hashes.

13. The computer readable medium of claim 10, wherein the set of current cluster hashes further:

is calculated based at least in part on a modified current in-use cluster list;

the modified current in-use cluster list is based on a fix-up list and a current in-use cluster list; and

the current in-use cluster list excludes clusters marked as not-in-use.

14. The computer readable medium of claim 10 wherein the first set of clusters does not include clusters marked as not-in-use.

15. The computer readable medium of claim 10 wherein the first set of clusters does not include clusters associated with ephemeral files.

16. The computer readable medium of claim 15 wherein the ephemeral files include at least one of temporary data, temporary internet files, virtual memory cache files, page files, swap files, and hibernation files.

17. The computer readable medium of claim 10, the backup engine further configured to include a recoverable commit operation during the store in the backup database operation.

18. The computer readable medium of claim 10, the set of current cluster hashes calculated using a hashing function that calculates a fixed size hash value from an arbitrarily long input value, wherein the input value is cluster data.

19. A restore system comprising:

a backup engine;

a backup protocol configured to couple a client backup module to the backup engine;

a backup database coupled to the backup engine, the backup database comprising a first set of clusters, the first set of clusters forming one or more backups, wherein each cluster of the first set of clusters is unique such that single-instance storage across clients is achieved;

a processor; and

a memory operatively connected to the processor, the memory having computer-executable instructions that when executed by the processor cause the backup engine to;

receive a request from the client restore module for a range of cluster data, wherein each one of the range of cluster data uniquely corresponds to a cluster of a storage device;

send to the client restore module, for each cluster in the range of clusters requested, a message; and

wherein the message includes an indication of a condition of the cluster data.

20. The restore system of claim 19, wherein the indication of the condition of the cluster data is selected from the list comprising:

at least a portion of the requested cluster contents is unavailable,

at least a portion of the requested cluster contents was not included in the backup for some reason, and

valid cluster data for at least a portion of the requested cluster contents.