Application of a differential dataset to a data store using sequential change sets

• US 9,460,184 B2
• Filed: 02/20/2014
• Issued: 10/04/2016
• Est. Priority Date: 10/18/2011
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Lasky, Michael, Ryan, Matthew
• Primary Examiner(s): TRUONG, CAM Y T
• Application Number:
  US14/185,003
• Publication Number:
  US 20140172791A1
• Time in Patent Office: 957 Days
• Field of Search: 707/624
• US Class Current: 1/1
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1471 involving logging of persistent data for recovery
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/275 Synchronous replication

Abstract

Systems and methods are described herein for creating, maintaining and applying a dataset that can be used to synchronize multiple instances of a data store. The dataset includes a sequentially-ordered sequence of change sets associated with the data store, wherein each change set includes zero or more entries that specify how the state of certain entities in the data store have changed since state changes represented by a previous change set in the sequence were applied to the data store. When a new change set is added to the dataset, any entries in any previously-added change sets dealing with the entities identified in the new change set are removed. Consequently, the dataset provides a concise and complete representation of all the state changes that have occurred to the data store since a known origin state.

Claims

1. A computer-implemented method for synchronizing a local instance of a data store with at least one remote instance of the data store, comprising:

comparing a local version of a dataset, that includes a first sequentially-ordered list of change sets associated with the local instance of the data store, to a shared version of the dataset, that includes a second sequentially-ordered list of change sets associated with the at least one remote instance of the data store, to identify one or more new change sets that are included in the shared version of the dataset and are not included in the local version of the dataset, the one or more new change sets comprising a set of operations that represent how a state of a corresponding set of entities in the local instance of the data store must be changed to bring the local instance of the data store into synchronization with the at least one remote instance of the data store, and the one or more new change sets having been automatically modified to ensure that only a single operation is included in the set of operations for each entity in the corresponding set of entities; and

applying the one or more new change sets to the local instance of the data store in the order in which the one or more new change sets appear in the second sequentially-ordered list, the applying the one or more new change sets to the local instance of the data store comprising;

performing, by using a computer system, one or more add, modify or delete operations included in the one or more new changes set with respect to one or more corresponding entities in the local instance of the data store.

2. The method of claim 1, wherein the method is performed upon determining that the shared version of the dataset is a more recently-updated version of the dataset than the local version of the dataset.

3. The method of claim 1, further comprising:

obtaining the shared version of the dataset from one of a file sharing system, a networked server, a Web service, or a cloud-based service.

4. The method of claim 1, further comprising:

overwriting the local version of the dataset with the shared version of the dataset or updating the local version of the dataset based on the shared version of the dataset.

5. The method of claim 1, wherein the shared version of the dataset comprises one of a plurality of shared versions of the dataset that can each be accessed to synchronize an instance of the data store to a desired change state.

6. The method of claim 1, wherein each version of the dataset comprises a file that includes a sequentially-ordered list of change sets associated with the data store.

7. The method of claim 1, wherein each version of the dataset comprises a database that stores change sets associated with the data store.

8. The method of claim 1, wherein the local instance of the data store includes one or more entities that represent one or more user settings associated with a program.

9. A system comprising:

a file sharing system that maintains a shared version of a dataset; and

a client machine that maintains a local version of the dataset and a local instance of a data store, the client machine including at least one processor that is configured to;

obtain the shared version of the dataset from the file sharing system;

compare the local version of the dataset, that includes a first sequentially-ordered list of change sets associated with the local instance of the data store, to the shared version of the dataset, that includes a second sequentially-ordered list of change sets associated with at least one remote instance of the data store, to identify one or more new change sets that are included in the shared version of the dataset and are not included in the local version of the dataset, the one or more new change sets comprising a set of operations that represent how a state of a corresponding set of entities in the local instance of the data store must be changed to bring the local instance of the data store into synchronization with the at least one remote instance of the data store, and the one or more new change sets having been automatically modified to ensure that only a single operation is included in the set of operations for each entity in the corresponding set of entities; and

apply the one or more new change sets to the local instance of the data store in the order in which the one or more new change sets appear in the second sequentially-ordered list, the applying the one or more new change sets to the local instance of the data store including performing one or more add, modify or delete operations included in the one or more new change sets with respect to one or more corresponding entities in the local instance of the data store.

10. The system of claim 9, wherein the at least one processor of the client machine is further configured to overwrite the local version of the dataset with the shared version of the dataset or update the local version of the dataset based on the shared version of the dataset.

11. The system of claim 10, wherein the at least one processor of the client machine is further configured to perform the following in response to determining that the local instance of the data store has been modified subsequent to the overwriting of the local version of the dataset with the shared version of the dataset or the updating of the local version of the dataset based on the shared version of the dataset:

add a further new change set to the local version of the dataset; and

provide the local version of the dataset that includes the further new change set to the file sharing system.

12. The system of claim 9, wherein the at least one processor of the client machine is configured to perform the obtaining, comparing, and applying operations only upon determining that the shared version of the dataset is a more recently-updated version of the dataset than the local version of the dataset.

13. The system of claim 9, wherein the shared version of the dataset comprises one of a plurality of shared versions of the dataset that can be accessed to synchronize an instance of the data store to a desired change state.

14. The system of claim 9, wherein each version of the dataset comprises a file that includes a sequentially-ordered list of change sets associated with the data store.

15. The system of claim 9, wherein each version of the dataset comprises a database that stores change sets associated with the data store.

16. The system of claim 9, wherein the local instance of the data store includes one or more entities that represent one or more user settings associated with a program.

17. A device comprising:

a processing unit;

a memory communicatively connected to the processing unit, the memory storing instructions that are executable by the processing unit to perform operations, the operations including;

comparing a local version of a dataset, that includes a first sequentially-ordered list of change sets associated with a local instance of a data store, to a shared version of the dataset, that includes a second sequentially-ordered list of change sets associated with at least one remote instance of the data store, to identify one or more new change sets that are included in the shared version of the dataset and are not included in the local version of the dataset, the one or more new change sets comprising a set of operations that represent how a state of a corresponding set of entities in the local instance of the data store must be changed to bring the local instance of the data store into synchronization with the at least one remote instance of the data store, and the one or more new change sets having been automatically modified to ensure that only a single operation is included in the set of operations for each entity in the corresponding set of entities; and

applying the one or more new change sets to the local instance of the data store in the order in which the one or more new change sets appear in the second sequentially-ordered list, the applying the one or more new change sets to the local instance of the data store comprising;

performing one or more add, modify or delete operations included in the one or more new change sets with respect to one or more corresponding entities in the local instance of the data store.

18. The device of claim 17, wherein the operations further include:

obtaining the shared version of the dataset from one of a file sharing system, a networked server, a Web service, or a cloud-based service.