Combined computer backup, disaster recovery and migration in a shared environment

• US 20060036895A1
• Filed: 08/13/2004
• Published: 02/16/2006
• Est. Priority Date: 08/13/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Henrickson, David L.
• Granted Patent: US 7,392,423 B2
• Time in Patent Office: Days
• US Class Current: 714/4
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1469 Backup restoration techniques

Abstract

Computer tools and methods novelly combine periodic backup and restore features with migration features to transfer the components of a failed system to a new system, which new system may be dissimilar to the old system. As well as backing up and transferring critical data files during the disaster recovery operation, the present invention also transfers, inter alia, applications, user states, hardware settings, software settings, user preferences and other user settings, menus, and directories. In another aspect of the present invention, a network of shared end-user computers periodically backs up each individual end-user computer to a central instrumentality, in a novel manner to reduce storage and time requirements. That is, redundancies for the end-user computer backup files are eliminated or greatly reduced by only making reference to but not storing components that are generic to the system, and further for each previously stored component, only storing differential or incremental information, unless predefined conditions are met. In yet another aspect of the present invention, remote end-users upload, via a wide area network such as the Internet, backup information to a central location. In the case of end-user computer failure, backup and migration information can be delivered to a new machine by means such as mailing a storage medium (e.g., compact disc), and downloading from the Internet.

Claims

1. An information backup and transfer method, said method comprising:

a) networking a plurality of end-user computers to at least one host computer;

b) via each end-user computer, periodically cataloging the contents of the end-user computer, as well as the state of each component, and transferring components of the end-user computer to said host computer;

c) via said host computer, periodically backing up components from said end-user computers in a plurality of end-user computer backup profiles;

d) via said host computer, storing and cataloging components which are generic to a plurality of end-user computers;

e) prior to storing a component in an end-user computer profile, noting in said end-user computer profiles, particular generic components that are cataloged on the end-user computers;

f) comparing the state of cataloged end-user components with the state of corresponding generic components;

g) for each end-user computer, storing in said end-user computer profiles those components that are not generic;

h) for each end-user computer, storing in said end-user computer profiles differential backup indicia corresponding to the differences between the host computer version of generic components and the end-user computer version of generic components; and

i) via said host computer, recreating and transferring backup components from a failed end-user computer to a different computer based upon said end-user computer profiles.

2. The method of claim 1, wherein said end-user catalog also comprises for each component, indicia of the differences between the current state of the component versus the previously backed up state of the component.

3. The method of claim 1, wherein step g) further comprises storing in said end-user computer profiles, along with each component, an indication of the change in the previously stored component.

4. The method of claim 3, further comprising overwriting a stored component with a new version of the stored component when a predetermined condition is met.

5. The method of claim 4, wherein said predetermined condition comprises the passage of a predetermined amount of time since a stored component was initially stored.

6. The method of claim 4, wherein said predetermined condition comprises a predetermined amount of change to the stored component.

7. The method of claim 1, wherein said stored components comprise indicia corresponding to a user state.

8. The method of claim 1, wherein said stored components comprise user-specific settings.

9. The method of claim 1, wherein said stored components comprise hardware-specific settings.

10. The method of claim 1, wherein said stored components comprise menus or directories.

11. An information backup and transfer system, said system comprising:

a plurality of end-user computers; and

at least one host computer networked to said end-user computers;

each said end-user computer being adapted to periodically catalog the contents of the end-user computer, as well as the state of each component, and transfer components of the end-user computer to said host computer;

said host computer being adapted to;

periodically back up components from said end-user computers in a plurality of end-user computer backup profiles;

store and catalog components which are generic to a plurality of end-user computers; and

prior to storing a component in an end-user computer profile, noting in said end-user computer profiles, particular generic components that are cataloged on the end-user computers;

said host computer further comprising;

a comparator adapted to compare the state of cataloged end-user components with the state of corresponding generic components; and

a re-creator adapted to recreate and transfer backup components from a failed end-user computer to a different computer based upon said end-user computer profiles;

wherein said host computer is further adapted to, for each end-user computer, store in said end-user computer profiles those components that are not generic, and for each end-user computer, store in said end-user computer profiles differential backup indicia corresponding to the differences between the host computer version of generic components and the end-user computer version of generic components.

12. The system of claim 11, wherein said end-user catalog also comprises for each component, indicia of the differences between the current state of the component versus the previously backed up state of the component.

13. The system of claim 11, wherein said end-user computers are further adapted to transfer to said host computer, along with each component, an indication of the change in the previously stored component.

14. The system of claim 13, wherein said host computer is further adapted to overwrite a stored component with a new version of the stored component when a predetermined condition is met.

15. The system of claim 14, wherein said predetermined condition comprises the passage of a predetermined amount of time since a stored component was initially stored.

16. The system of claim 14, wherein said predetermined condition comprises a predetermined amount of change to the stored component.

17. The system of claim 11, wherein said stored components comprise indicia corresponding to a user state.

18. The system of claim 11, wherein said stored components comprise user-specific settings.

19. The system of claim 11, wherein said stored components comprise hardware-specific settings.

20. The system of claim 11, wherein said stored components comprise menus or directories.