Systems and methods for the utilization of metadata for synchronization optimization

• US 20050256907A1
• Filed: 08/27/2004
• Published: 11/17/2005
• Est. Priority Date: 08/21/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Novik, Lev, Talius, Tomas, Wu, Yunxin, Zhou, Shaoyu
• Granted Patent: US 8,046,424 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/1787 Details of non-transparently synchronising file systems
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: Y10S 707/99955 Archiving or backup

Abstract

Various embodiments of the present invention are directed to synchronization utilizing one or more optimizations through the utilization of metadata. For several embodiments of the present invention, one method for optimizing synchronization is to reduce the overhead required for said synchronization by having each peer only tracking changes for itself and other peers within its change community (or communities) (a.k.a., “Intra-Community-Only Change Tracking Optimization”). For certain embodiments of the present invention, another method for optimizing synchronization is to not create synchronization overhead until required. For numerous embodiments of the present invention, yet another method for optimizing synchronization is to minimize redundant use of a partner'"'"'s unique global ID—a large and cumbersome number—and to instead maintain a table that cross-references each partner (and its unique global ID) with a smaller and much less cumbersome partner key.

Claims

1. A method for synchronizing at least three computer systems (comprising a first peer, a second peer, and a third peer) in at least two synchronization communities (a first sync community and a second sync community) where said a first peer is a member of said first sync community but is not a member of said second sync community, and where said second peer is a member of said second sync community but is not is not a member of said first sync community, and where said third peer is a member of both said first sync community and said second sync community, said method comprising the utilization of an Intra-Community-Only Change Tracking Optimization such that said first peer in said first sync community does not track changes made by said second peer in said second sync community and said second peer in said second sync community does not track changes made by said first peer in said first sync community.

2. The method of claim 1 wherein said at least three computer systems utilize a item-based storage platform.

3. The method of claim 1 wherein said Intra-Community-Only Change Tracking Optimization is provided by a common item-based storage platform utilized by said at least three computer systems.

4. A method for synchronizing at least two computer systems where changes are synchronized via change units and associated metadata, said method comprising the utilization of a Just-In-Time Sync-Overhead Optimization wherein said change units are created only after a corresponding entity is designated for synchronization.

5. The method of claim 4 wherein said at least two computer systems utilize a item-based storage platform.

6. The method of claim 4 wherein said Just-In-Time Sync-Overhead Optimization is provided by a common item-based storage platform utilized by said at least two computer systems.

7. A method for synchronizing a first computer system with a second computer system where changes from said first computer system are at least in part identified by a global identification number unique to said first computer system, said method comprising the utilization of a Partner Key Table Optomization whereby said second computer system utilizes a table to cross-references said first computer system'"'"'s global identification number with a partner key utilized by said second computer system to uniquely identify said first computer system.

8. The method of claim 7 wherein said at least two computer systems utilize a item-based storage platform.

9. The method of claim 7 wherein said Just-In-Time Sync-Overhead Optimization is provided by a common item-based storage platform utilized by said at least two computer systems.

10. A method for synchronizing at least two computer systems, said method comprising the utilization of a Multi-Level Change Tracking Optomization comprising at least a first level of tracked changes and a second level of tracked changes whereby conducting a single check for changes at a first level precludes the need for conducting at least two checks for changes at a second level.

11. The method of claim 10 further comprising the utilization of a Last Update Optimization whereby, when a first sync entity tracked at said first level of tracked changes, and which has at least one change, is updated to reflect at least one change received from a second sync entity tracked at said first level of tracked changes, that said first level of tracked changes continues to reflect the need for said second sync entity to be updated with said at least one change from said first sync entity.

12. The method of claim 11 wherein said at least two computer systems utilize a item-based storage platform.

13. The method of claim 11 wherein said Just-In-Time Sync-Overhead Optimization is provided by a common item-based storage platform utilized by said at least two computer systems.

14. A system for synchronizing at least three computer systems (comprising a first peer, a second peer, and a third peer) in at least two synchronization communities (a first sync community and a second sync community) where said a first peer is a member of said first sync community but is not a member of said second sync community, and where said second peer is a member of said second sync community but is not is not a member of said first sync community, and where said third peer is a member of both said first sync community and said second sync community, said system comprising at least one subsystem for the utilization of an Intra-Community-Only Change Tracking Optimization such that said first peer in said first sync community does not track changes made by said second peer in said second sync community and said second peer in said second sync community does not track changes made by said first peer in said first sync community.

15. The system of claim 14 further comprising at least one subsystem whereby said at least three computer systems utilize a item-based storage platform.

16. The system of claim 14 further comprising at least one subsystem whereby said Intra-Community-Only Change Tracking Optimization is provided by a common item-based storage platform utilized by said at least three computer systems.

17. A system for synchronizing at least two computer systems where changes are synchronized via change units and associated metadata, said system comprising at least one subsystem for the utilization of a Just-In-Time Sync-Overhead Optimization wherein said change units are created only after a corresponding entity is designated for synchronization.

18. The system of claim 17 further comprising at least one subsystem whereby said at least two computer systems utilize a item-based storage platform.

19. The system of claim 17 further comprising at least one subsystem whereby said Just-In-Time Sync-Overhead Optimization is provided by a common item-based storage platform utilized by said at least two computer systems.

20. A system for synchronizing a first computer system with a second computer system where changes from said first computer system are at least in part identified by a global identification number unique to said first computer system, said system comprising at least one subsystem for the utilization of a Partner Key Table Optomization whereby said second computer system utilizes a table to cross-references said first computer system'"'"'s global identification number with a partner key utilized by said second computer system to uniquely identify said first computer system.

21. The system of claim 20 further comprising at least one subsystem whereby said at least two computer systems utilize a item-based storage platform.

22. The system of claim 20 further comprising at least one subsystem whereby said Just-In-Time Sync-Overhead Optimization is provided by a common item-based storage platform utilized by said at least two computer systems.

23. A system for synchronizing at least two computer systems, said system comprising at least one subsystem for the utilization of a Multi-Level Change Tracking Optomization comprising at least a first level of tracked changes and a second level of tracked changes whereby conducting a single check for changes at a first level precludes the need for conducting at least two checks for changes at a second level.

24. The system of claim 23 further comprising at least one subsystem for the utilization of a Last Update Optimization whereby, when a first sync entity tracked at said first level of tracked changes, and which has at least one change, is updated to reflect at least one change received from a second sync entity tracked at said first level of tracked changes, that said first level of tracked changes continues to reflect the need for said second sync entity to be updated with said at least one change from said first sync entity.

25. The system of claim 24 further comprising a subsystem whereby said at least two computer systems utilize a item-based storage platform.

26. The system of claim 24 further comprising a subsystem whereby said Just-In-Time Sync-Overhead Optimization is provided by a common item-based storage platform utilized by said at least two computer systems.

27. A computer-readable medium comprising computer-readable instructions for synchronizing at least three computer systems (comprising a first peer, a second peer, and a third peer) in at least two synchronization communities (a first sync community and a second sync community) where said a first peer is a member of said first sync community but is not a member of said second sync community, and where said second peer is a member of said second sync community but is not is not a member of said first sync community, and where said third peer is a member of both said first sync community and said second sync community, said computer-readable instructions comprising instructions for an Intra-Community-Only Change Tracking Optimization such that said first peer in said first sync community does not track changes made by said second peer in said second sync community and said second peer in said second sync community does not track changes made by said first peer in said first sync community.

28. The computer-readable instructions of claim 27 further comprising instructions whereby said at least three computer systems utilize a item-based storage platform.

29. The computer-readable instructions of claim 27 further comprising instructions whereby said Intra-Community-Only Change Tracking Optimization is provided by a common item-based storage platform utilized by said at least three computer systems.

30. A computer-readable medium comprising computer-readable instructions for synchronizing at least two computer systems where changes are synchronized via change units and associated metadata, said computer-readable instructions comprising instructions for a Just-In-Time Sync-Overhead Optimization wherein said change units are created only after a corresponding entity is designated for synchronization.

31. The computer-readable instructions of claim 30 further comprising instructions whereby said at least two computer systems utilize a item-based storage platform.

32. The computer-readable instructions of claim 30 further comprising instructions whereby said Just-In-Time Sync-Overhead Optimization is provided by a common item-based storage platform utilized by said at least two computer systems.

33. A computer-readable medium comprising computer-readable instructions for synchronizing a first computer system with a second computer system where changes from said first computer system are at least in part identified by a global identification number unique to said first computer system, said computer-readable instructions comprising instructions for a Partner Key Table Optomization whereby said second computer system utilizes a table to cross-references said first computer system'"'"'s global identification number with a partner key utilized by said second computer system to uniquely identify said first computer system.

34. The computer-readable instructions of claim 33 further comprising instructions whereby said at least two computer systems utilize a item-based storage platform.

35. The computer-readable instructions of claim 33 further comprising instructions whereby said Just-In-Time Sync-Overhead Optimization is provided by a common item-based storage platform utilized by said at least two computer systems.

36. A computer-readable medium comprising computer-readable instructions for synchronizing at least two computer systems, said computer-readable instructions comprising instructions for the utilization of a Multi-Level Change Tracking Optomization comprising at least a first level of tracked changes and a second level of tracked changes whereby conducting a single check for changes at a first level precludes the need for conducting at least two checks for changes at a second level.

37. The computer-readable instructions of claim 36 further comprising instructions whereby at least one subsystem for the utilization of a Last Update Optimization whereby, when a first sync entity tracked at said first level of tracked changes, and which has at least one change, is updated to reflect at least one change received from a second sync entity tracked at said first level of tracked changes, that said first level of tracked changes continues to reflect the need for said second sync entity to be updated with said at least one change from said first sync entity.

38. The computer-readable instructions of claim 37 further comprising instructions whereby said at least two computer systems utilize a item-based storage platform.

39. The computer-readable instructions of claim 37 further comprising instructions whereby said Just-In-Time Sync-Overhead Optimization is provided by a common item-based storage platform utilized by said at least two computer systems.