Method and system for migrating computer state

• US 7,210,131 B2
• Filed: 10/01/2001
• Issued: 04/24/2007
• Est. Priority Date: 10/01/2001
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Negreanu, Calin, Schmidt, Jim
• Primary Examiner(s): Dam; Tuan
• Assistant Examiner(s): Fowlkes; Andre R
• Application Number:
  US09/968,623
• Publication Number:
  US 20030074386A1
• Time in Patent Office: 2,031 Days
• Field of Search: 713/1, 713/2, 713/100, 717168-178, 707/203
• US Class Current: 717/137
• CPC Class Codes: G06F 9/4451 User profiles; Roaming

Abstract

A system and method for migrating state data from a source computing platform to a destination platform, such as for migrating state data from one computer to another computer. Pluggable modules collect state on a source platform and transport it to temporary storage as state objects that are independent of any particular destination platform. For example, a state object may contain the information that represents a file on a source machine, while another state object may contain a piece of registry data on that machine. At the source platform, modules provide state data gathering and analysis that collect the data into the state objects. A transport module transports the data to storage accessible to the destination. At the destination, the state objects are applied by pluggable modules to the destination platform. The object data can be adjusted, translated and/or merged with destination state data as appropriate for the destination platform.

Claims

1. A system for migrating state data from a source platform to a destination platform, comprising, on the source platform:

1) a migration application program operable to be executed on the source platform and on the destination platform, where the migration application program is capable of determining whether it is executing on the source platform or the destination platform;

2) a source state migration engine separate from and invoked by the migration application program;

3) a gather module called by a migration application program via the source state migration engine to gather source state data from the source platform; and

4) at least one transport module called to write the source state data to a temporary storage selected by the migration application program via the source state migration engine, such that the source state data is stored in an abstracted form independent of the source platform and independent of the destination platform, the at least one transport module being selected by the migration application program via the source state migration engine based on a capability of the at least one transport module; and

on the destination platform

1) the migration application program;

2) a destination state migration engine invoked by the migration application program based on a determination by the migration application that the migration application is executing on the destination platform;

3) a transport module called to read the source state data from the storage; and

4) an operation module called to apply the source state data to at least one storage location accessible to the destination platform.

2. The system of claim 1 wherein at the source platform, the gather module and the transport module are called by the source state migration engine.

3. The system of claim 2 wherein the gather module is called by the source state migration engine in response to a call from the migration application program.

4. The system of claim 2 wherein the transport module is selected and called by the source state migration engine in response to at least one call from the migration application program.

5. The system of claim 1 wherein at the destination platform, the transport module and the operation module are called by the destination state migration engine.

6. The system of claim 1 wherein the source state migration engine includes a set of at least one interface via which the gather module and the transport module exchange information with the source state migration engine module.

7. The system of claim 1 wherein at the source platform, the gather module comprises a source state data gather module.

8. The system of claim 7 further comprising, at the source platform, a source analyze module that analyzes state data gathered by the source state data gather module.

9. The system of claim 1 wherein at the source platform, the gather module collects information from a registry.

10. The system of claim 1 wherein at the source platform, the gather module collects at least one file.

11. The system of claim 1 wherein the state data is gathered into a state object set comprising at least one state object.

12. The system of claim 11 wherein the gather module collects information from registry information and file information, and wherein the state object set includes at least one registry state object for maintaining the registry information and least one file state object for maintaining the file information.

13. The system of claim 11 wherein the state object set includes at least one engine state object.

14. The system of claim 13 wherein the state object set includes another type of state object, and further comprising, at the source platform, an extensible type module that is called by the source state migration engine to abstract information into the other type of state object.

15. The system of claim 14 further comprising, at the destination platform, an extensible type module that is called by the destination state migration engine to recover the information abstracted at the source platform.

16. The system of claim 1 wherein at the source platform, the gather module comprises a virtual computer gather module that gathers state data into a virtual computer format that is capable of being edited.

17. The system of claim 16 further comprising, at the destination platform, a source state data gather module that gathers state data from the virtual computer format.

18. The system of claim 17 further comprising, at the destination platform, an analyze module that analyzes state data gathered by the source state data gather module of the destination platform.

19. The system of claim 1 further comprising, at the destination platform, a destination state data gather module that gathers destination state data corresponding to the destination platform.

20. The system of claim 19 further comprising, at the destination platform, an analyze module that analyzes the destination state data gathered by the destination state data gather module.

21. The system of claim 19 further comprising, at the destination platform, a combine state module that merges the source state data and the destination state data.

22. The system of claim 1 wherein the operation module changes at least some of the source state data when called to apply the source state data.

23. A computer-implemented method, comprising,

gathering at least one set of state data from a source platform;

identifying associated state data from the source platform, the associated state data containing information that changes a setting of at least one state data in the set of state data gathered from the source platform;

determining an associated state data from the identified associated state data to be migrated from the source platform based on a setting associated with the identified associated state data;

abstracting the associated state data from the determining step into a format that is independent of the source platform and independent of any destination platform;

transporting the abstracted state data into a storage accessible by a destination platform;

recovering the state data from the storage at the destination platform; and

applying at least some of the recovered state data at the destination platform such that the destination platform has available thereto at least some of the state data from the source platform in a format that is suitable for the destination platform.

24. The method of claim 23 wherein abstracting the state data comprises writing the state data into a state object.

25. The method of claim 23, wherein one of the migratable objects comprises a registry entry in a registry on the source platform, and a value stored in the registry entry is analyzed to determine if it indicates a dependency on another migratable object.

26. The method of claim 23 further comprising, selecting a transport from among a plurality of transports capable of transporting the state data into the storage.

27. The method of claim 23 further comprising, gathering destination state data at the destination, and merging at least some of the destination state data with the state data recovered from the storage.

28. The method of claim 23 further comprising, translating at least some of the state data recovered from the storage to correspond to the destination platform.

29. The method of claim 23 wherein at least some of the state data contains a file, and wherein applying at least some of the state data at the destination platform includes creating a file corresponding thereto accessible to the destination platform.

30. The method of claim 23 wherein at least some of the state data contains a setting, and wherein applying at least some of the state data at the destination platform includes recreating the setting at a location accessible to the destination platform.

31. The method of claim 30 wherein recreating the setting comprises writing information to a registry.

32. The method of claim 23 further comprising communicating with an extensible type module to access at least some of the state data.

33. A system for collecting state data from a source platform for use in configuring a destination platform, comprising:

a state migration engine;

a gather module that gathers source state data from the source platform in response to a call from the state migration engine, where the gather module further identifies associated state data from the source platform, the associated state data containing information that changes a setting of at least one gathered state data and determines an associated state data from the identified associated state data to be migrated from the source platform, and where the gather module is caused to be invoked by a migration application program configured to be capable of executing on the destination platform to manage migrating the source state data to the destination platform; and

a transport module that writes the source state data gathered by the gather module to a storage, the transport module operating in response to a call from the state migration engine, the source data written in an abstracted format independent of the source platform and independent of any destination platform.

34. The system of claim 33 wherein the gather module is called by the state migration engine in response to a call from the migration application program.

35. The system of claim 33 wherein the transport module is a selectable component, and wherein the transport module selected and called by the state migration engine in response to at least one call from the migration application program.

36. The system of claim 33 wherein the gather module includes a source state data gather module.

37. The system of claim 36 further comprising a source analyze module that analyzes state data gathered by the source state data gather module.

38. The system of claim 33 wherein the gather module collects information from a registry.

39. The system of claim 33 wherein the gather module collects at least one file.

40. The system of claim 33 wherein the data is gathered into a state object set comprising at least one state object.

41. The system of claim 40 wherein the state object set includes at least one registry state object that maintains registry information and at least one file state object that maintains file information.

42. The system of claim 40 wherein the state object set includes at least one engine state object.

43. The system of claim 40 wherein the state object set includes another type of state object, and further comprising an extensible type module that is called by the state migration engine to abstract information into the other type of state object.

44. The system of claim 33 further comprising at least one mechanism configured to read the state data from the storage and apply the state data to the destination platform.

45. A system for configuring a destination platform with state data collected from a source platform, comprising:

a migration application configured to be capable of performing migration on the source platform and on the destination platform;

a state migration engine separate from and invoked by the migration application;

at least one transport module, selected by the migration application via the state migration engine, that reads source state data from a storage in response to a call from the state migration engine, the source state data stored in an abstracted format independent of the source platform and independent of any destination platform; and

an operation module that applies the source state data to at least one storage location accessible to the destination platform by performing at least one of filtering or content editing, the transport module operating in response to a call from the state migration engine.

46. The system of claim 45 wherein the source state data comprises virtual computer data gathered into a virtual computer format that is capable of being edited, and further comprising, a state data gather module that gathers state data from the virtual computer format.

47. The system of claim 46 further comprising, an analyze module that analyzes the state data gathered by the state data gather module.

48. The system of claim 45 further comprising, a destination state data gather module that gathers destination state data corresponding to the destination platform.

49. The system of claim 48 further comprising, an analyze module that analyzes the destination state data gathered by the destination state data gather module.

50. The system of claim 48 further comprising, a combine state module that merges the source state data and the destination state data.

51. The system of claim 45 wherein the operation module changes at least some of the source state data when called to apply the source state data.

52. The system of claim 45 further comprising at least one mechanism configured to gather the source state data from the source platform and store the source state data in the storage.

53. A computer program product, comprising, a computer-readable storage medium having executable code thereon comprising:

a first computer instruction for reading at least one set of state data and at least one set of associated state data from a source platform, wherein the at least one set of associated state data changes a setting of at least one state data in the at least one set of state data and identifying the at least one set of associated state data to be migrated from the source platform;

a second computer instruction for abstracting the state data into a predetermined format to obtain abstracted state data that is independent of the source platform and independent of any destination platform, any destination program operating in an environment incompatible with the environment in which the source platform is operating; and

a third computer instruction for writing the abstracted state data to a storage medium.

54. A computer program product, comprising, a computer-readable storage medium having executable code thereon comprising:

a first computer instruction for directing a gather module via a source state migration engine to read abstracted state data representative of a state of a source platform wherein a format of said abstracted state data is platform independent, where a migration application program determines whether it is running on the source platform or on a target platform, and where the first computer instruction is invoked by the migration application program in response to the migration application program'"'"'s determination that it is running on the target platform, the source state migration engine being separate from and invoked by the migration application program; and

a second computer instruction for applying at least some of the abstracted state data at a target platform such that the target platform has available thereto at least some of the state data from the source platform in a format that is suitable for the second platform.