Configuration replication for system recovery and migration

• US 20080126856A1
• Filed: 08/18/2006
• Published: 05/29/2008
• Est. Priority Date: 08/18/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Watson, Eric B., Fishman, Neil Scott, Levidow, Bjorn Benjamin
• Granted Patent: US 7,571,349 B2
• Time in Patent Office: Days
• US Class Current: 714/19
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 11/1482 by means of middleware or OS functionality
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases

Abstract

Aspects of the subject matter described herein relate to system state changes. In aspects, a state change monitor detects a state change, determines whether the state change is within a set of state changes that are monitored, and, if so, logs data regarding the state change. The data and any other data needed to rollback the state change is exported to other nodes. The other nodes may store the data for rollback or migration purposes and/or adjust their operation so that they may operate correctly in view of the state change.

Claims

1. A computer-readable medium having computer-executable instructions for executing in an networked environment, comprising:

detecting a state change on a first node of a configuration set, wherein the configuration set includes a plurality of nodes for which at least one state change of the first node has a potential for causing incorrect operation of at least the first node or a second node of the configuration set;

determining whether the state change is within a set of state changes for which monitoring is selected;

extracting data associated with the state change, the data including information about a state that existed before the state change that allows a rollback or recovery to the state; and

exporting the data to at least one other node of the plurality of the nodes.

2. The computer-readable medium of claim 1, wherein the incorrect operation comprises an inability to access a resource in the networked environment that was accessible immediately prior to the state change.

3. The computer-readable medium of claim 1, wherein the incorrect operation comprises erroneously ceasing to provide a service by two or more previously cooperating components of at least one node of the configuration set.

4. The computer-readable medium of claim 1, wherein determining whether the state change is within a set of state changes for which monitoring is selected comprises consulting a dependencies store that indicates a state change and entities affected by the state change.

5. The computer-readable medium of claim 4, wherein entities affected by the state change comprise one or more network appliances, routers, firewalls, clients, servers, or services accessible through the networked environment.

6. The computer-readable medium of claim 1, wherein the set of state changes for which monitoring is selected comprises state indicated by a system administrator.

7. The computer-readable medium of claim 1, wherein the set of state change for which monitoring is selected comprises state hard-coded in a software component.

8. The computer-readable medium of claim 1, further comprising:

restoring the first node to a previous state;

importing the data from the at least one other node;

applying the data to the first node to configure the node to a state that existed just prior to the state change; and

providing information regarding the state that existed just prior to the state change to any nodes affected by the state change.

9. A method implemented at least in part by a computer, the method comprising:

creating a dependencies data structure that includes data regarding a plurality of state changes, wherein the data associates at least one entity potentially affected by a state change with the state change;

receiving an indication that a user has requested to cause the state change;

notifying the user of the at least one entity potentially affected by the state change;

receiving a user confirmation or cancellation regarding causing the state change;

if a user confirmation is received, allowing the state change; and

if a user cancellation is received, cancelling the state change.

10. The method of claim 9, further comprising using the dependencies data structure to determine what state changes are monitored by a state change monitor.

11. The method of claim 9, wherein the dependencies data structure is automatically updated in response to the at least one entity becoming connected to or disconnected from a network connecting a plurality of entities.

12. The method of claim 9, further comprising exporting data regarding the state change from a first entity to a second entity, wherein the data includes a timestamp corresponding to a time at which the state change occurred, an identifier identifying an entity upon which the change occurred, and information to rollback the state change.

13. The method of claim 9, further comprising notifying all affected entities regarding the state change and updating the affected entities in response to the state change such that the affected entities are able to continue communicating with an entity upon which the state change occurred.

20. The apparatus of claim 13, wherein the entity and the dependencies data structure are located on a network external to the other entities and wherein the data exporter is further arranged to export the data regarding state changes to at least one of the other entities in response to a request from the at least one of the other entities.

14. In a computing environment, an apparatus, comprising:

a state change monitor arranged to monitor selected changes to system state and to log information in a log data structure in response thereto;

a dependencies data structure including a state field that indicates a state of an entity and an associated dependencies field that indicates at least one other entity potentially affected by a change of the state; and

a data exporter arranged to export data regarding state changes to other entities.

15. The apparatus of claim 14, wherein the information comprises one or more of a timestamp corresponding to a time at which a change occurred, an identifier that identifies a user who caused the change to occur, an identifier that identifies a node upon which the change occurred, and data to rollback to a state that existed just prior to the change.

16. The apparatus of claim 14, wherein the data indicates network information that allows the other entities to communicate with the entity.

17. The apparatus of claim 14, further comprising a data extractor arranged to read the log data structure and derive additional data therefrom, wherein the additional data includes information to rollback state changes.

18. The apparatus of claim 17, wherein the additional data includes an identification of entities affected by each state change.

19. The apparatus of claim 14, wherein the system state includes one or more of a variable, a file, a directory and its subdirectories, one or more entries in a registry, and one or more entries in a database.