Method and system for backing up and restoring data of a node in a distributed system

• US 7,249,281 B2
• Filed: 07/28/2003
• Issued: 07/24/2007
• Est. Priority Date: 07/28/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Johnson, Gregory C., Shirley, Brett A.
• Primary Examiner(s): Baderman; Scott
• Assistant Examiner(s): ASSESSOR, BRIAN J
• Application Number:
  US10/628,806
• Publication Number:
  US 20050028026A1
• Time in Patent Office: 1,457 Days
• Field of Search: 714/6, 714/13, 714/15
• US Class Current: 714/15
• CPC Class Codes: G06F 11/1453 using de-duplication of the data
• 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
• CPC Class Codes: G06F 2201/82 Solving problems relating to consistency ensuring consistency in mirrored systems G06F11/2064
• CPC Class Codes: G06F 2201/84 Using snapshots, i.e. a logical point-in-time copy of the data

Abstract

A method and system for backing up and restoring a data set on a node of a distributed system prevents conflicts in data replication caused by restoration from backup data. Before a node is backed up, state data of the data set of the node are set to mark the data set as “backed up.” The data set also stores a lowest serial number for uncommitted changes. A snapshot of the data set, including the state data, of the node is then taken to provide a backup copy. When the backup copy is later used to restore the data set of the node, the “backed up” value of the state data of the restored data set serves as a notification to the replication server of the node that the data set has been restored, so that the replication server will switch to a new Node ID for labeling new changes for replication to other nodes in the distributed system.

Claims

1. A computer-readable medium having computer executable instructions for performing steps for backing up and restoring a data set of a node in a distributed system, comprising:

initiating a back up operation of an original data set, the original data set having state data indicating that the original data set is original data rather than backup data;

before making a backup copy of the original data set, changing the state data of the original data set to indicate that the original data set is backup data

after changing the state data of the original data set, taking a snapshot of the contents of the original data set, including the state data indicating that the original data set is backup data, to generate a backup copy, the contents of the original data set including a plurality of changes each identified by a replication identification number of the node and a serial number; and

after taking the snapshot, resetting the state data of the original data set to again indicate that the original data set is original data rather than backup data.

2. A computer-readable medium as in claim 1, having further computer-executable instructions for performing the steps of:

restoring the original data set using the backup copy;

detecting that the state data of the restored data set indicates that the data set backup data;

in response to the detecting, changing the replication identification number of the node from an old value used before the backup operation to a new value.

3. A computer-readable medium as in claim 2, having further computer-executable instructions for performing the step of storing into the original data set a lowest uncommitted serial number that corresponds to a lowest one of the serial numbers of changes made to the original data set that are not yet committed prior to taking the snapshot.

4. A computer-readable medium as in claim 3, having further computer-readable instructions for performing the step of requesting a second node in the distributed system to replicate changes that have the old value of the replication identification number of the node and serial numbers equal or higher than said lowest uncommitted serial number.

5. A computer-readable medium as in claim 2, having further computer-executable instructions for performing the step of storing in the original data set, prior to taking the snapshot, a next serial number to be assigned to a new change to the original data set.

6. A computer-readable medium as in claim 1, wherein the replication identification number of the node is a computed Globally Unique Identifier (GUID).

7. A computer-readable medium as in claim 1, wherein the distributed system is a directory service system and the data set of the node contains directory data.

22. A computer-readable medium as in claim 1, wherein the state data is a collective value for the original data set.

23. A computer-readable medium as in claim 1, wherein the distributed system is Active Directory.

8. A method for backing up and restoring contents of a data set of a node in a distributed system, comprising:

initiating a back up operation of an original data set, original the data set having state data indicating that the original data set is original data rather than backup data;

before making a backup copy of the original data set, changing state data of the original data set to indicate that the original data set backup data;

after changing the state data of the original data set, taking a snapshot of the contents of the original data set, including the state data indicating that the original data set is backup data, to generate a backup copy, the contents of the data set including a plurality of changes each identified by a replication identification number of the node and a serial number; and

after taking the snapshot, resetting the state data of the original data set to again indicate that the original data set is original data rather than backup data.

9. A method as in claim 8, further including the steps of:

restoring the original data set using the backup copy;

detecting that the state data of the restored data set indicates that the data set is backup data; and

in response to the detecting, changing the replication identification number of the node from an old value used before the backup operation to a new value.

10. A method as in claim 9, further including the step of storing into the original data set a lowest uncommitted serial number that corresponds to a lowest one of serial numbers of changes made to the original data set that are not yet committed prior to taking the snapshot.

11. A method as in claim 10, further including the step of requesting a second node in the distributed system to replicate changes that have the old value of the replication identification number of the node and serial numbers equal to or higher than said lowest uncommitted serial number.

12. A method as in claim 9, further including the step of storing in the original data set, prior to talking the snapshot, a next serial number to be assigned to a new change to the original data set.

13. A method as in claim 8, further including the step of setting the replication identification number of the node as a computed Globally Unique Identifier (GUID).

14. A method as in claim 8, wherein the distributed system is a directory service system and the data set of the node contains directory data.

15. A computer system for acting as a node in a distributed system, the computer system comprising:

a data manager for maintaining a data set containing a plurality of changes each identified by a replication identification number of the node and a serial number, the original data set having state data indicating that the original data rather than backup data;

a replication server for replicating changes made to the original data set to other nodes in the distributed system;

a backup server for generating a backup copy of the original data set, the backup server being programmed to;

(i) cause the state data of the original data set to be set to indicate that the original data set is backup data before making a backup copy of the original data set, (ii) after changing the state data of the original data set, take a snapshot of the contents of the original data set, including the state data indicating that the data set is backup data, to generate the backup copy of original data set, and (iii) cause the state data of the original data set to be reset after taking the snapshot to again indicate that the original data set is original data rather than backup data.

16. A computer system as in claim 15, wherein the replication server is programmed to detect, after the original data set is restored from the backup copy, that the state data of the restored data set indicates that the restored data set is backup data and change the replication identification number of the node from an old value used before the snapshot to a new value.

17. A computer system as in claim 16, wherein the replication server is further programmed to store into the original data set a lowest uncommitted serial number that corresponds to a lowest one of serial numbers of changes made to the original data set that are not yet committed prior to taking the snapshot.

18. A computer system as in claim 17, wherein the replication server is further programmed to request a second node in the distributed system to replicate changes that have the old value of the replication identification number of the node and serial numbers equal or higher than said lowest uncommitted serial number.

19. A computer system as in claim 16, wherein the replication server is further programmed to store in the original data set, prior to taking the snapshot, a next serial number to be assigned to a new change to the original data set.

20. A computer system as in claim 15, wherein the replication identification number of the node is a computed Globally Unique Identifier (GUID).

21. A computer system as in claim 15, wherein the distributed system is a directory service system and the data set of the node contains directory data.