Systems and methods for synchronizing computer systems through an intermediary file system share or device

• US 20050223047A1
• Filed: 07/12/2004
• Published: 10/06/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, Pohlmann, Nils H., Thomas, Michael W., Shah, Darshatkumar
• Granted Patent: US 7,401,104 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

The invention is directed to systems and methods for the synchronization of two clients both utilizing a common storage platform (e.g., the new storage platform of the related inventions) to synchronize through an intermediary that is not using the same common storage platform (e.g., instead using a legacy storage platform that does not itself support synchronization for the new storage platform). Data is synchronized using the existing capabilities of the intermediary but where the data structure of the clients is preserved. An “adapter” is used to enable a client to interact with an intermediary by compensating for the intermediaries inability to preserve the data structure elements inherent to the client'"'"'s storage platform. Specific embodiments are directed to either or both upload-syncing data from a client to a intermediary and/or download-syncing data from an intermediary to a client. Certain additional embodiments are further directed to compaction of data on the intermediary.

Claims

1. A method for synchronizing at least two computer systems utilizing a common storage platform (e.g., WinFS) (each a “

client”

) through an intermediary computer system having a different storage platform (e.g., Win32) (the “

intermediary”

), said method comprising the utilization of a synchronization-through-intermediary (STI) adapter resident on each client and interfacing each client to said intermediary.

2. The method of claim 1 wherein said synchronization is utilized to support a data-sharing operation.

3. The method of claim 1 wherein said synchronization is utilized to support an end-user roaming.

4. The method of claim 1 wherein each said common storage platform is an Item-based storage platform.

5. The method of claim 4 wherein a change enumeration for a client is serialized as at least one file stored on said intermediary (each a “

sync file”

).

6. The method of claim 5 wherein said at least one file comprises, for a single serialization, at least one or more of the following:

a change data file (CDF) for change data (CD), a prerequisite knowledge file (PKF) for prerequisite knowledge (PK), and a learned knowledge file (LKF) for learned knowledge (LK).

7. The method of claim 5 wherein said synchronization comprises a send sync operation between a first client and said intermediary, said send sync operation comprising:

determining learned knowledge for the intermediate;

if said first client has changes that are not reflected in said intermediate'"'"'s learned knowledge, preparing a set of necessary changes for said intermediary;

serializing said set of necessary changes and writing same to said intermediary; and

8. The method of claim 7 wherein said send sync operation further comprises:

acquiring write mode process locks; and

releasing write mode process locks.

9. The method of claim 5 wherein said synchronization comprises a receive sync operation between a first client and said intermediary, said receive sync operation comprising deserializing a set of necessary changes from the intermediary and applying same to said client.

10. The method of claim 9 wherein said receive sync operation further comprises:

acquiring read mode process locks; and

releasing read mode process locks.

11. The method of claim 5 wherein said synchronization comprises a compaction operation between a first client and said intermediary, said compaction operation comprising:

executing a successful receive sync operation without releasing said read mode process locks;

deleting all sync files; and

executing a full send sync operation.

12. A system for synchronizing at least two computer systems utilizing a common storage platform (e.g., WinFS) (each a “

client”

) through an intermediary computer system having a different storage platform (e.g., Win32) (the “

intermediary”

), said system comprising at least one subsystem for utilizing a synchronization-through-intermediary (STI) adapter resident on each client for interfacing each client to said intermediary.

13. The system of claim 12 further comprising at least one subsystem whereby said synchronization is utilized to support a data-sharing operation.

14. The system of claim 12 further comprising at least one subsystem whereby said synchronization is utilized to support a end-user roaming.

15. The system of claim 12 further comprising at least one subsystem whereby each said common storage platform is an Item-based storage platform.

16. The system of claim 15 further comprising at least one subsystem whereby a change enumeration for a client is serialized as at least one file stored on said intermediary (each a “

sync file”

).

17. The system of claim 16 further comprising at least one subsystem whereby said at least one file comprises, for a single serialization, at least one or more of the following:

a change data file (CDF) for change data (CD), a prerequisite knowledge file (PKF) for prerequisite knowledge (PK), and a learned knowledge file (LKF) for learned knowledge (LK).

18. The system of claim 16 further comprising at least one subsystem whereby said synchronization comprises a send sync operation between a first client and said intermediary, said send sync operation comprising:

determining learned knowledge for the intermediate;

if said first client has changes that are not reflected in said intermediate'"'"'s learned knowledge, preparing a set of necessary changes for said intermediary;

serializing said set of necessary changes and writing same to said intermediary; and

19. The system of claim 18 further comprising at least one subsystem whereby said send sync operation further comprises:

acquiring write mode process locks; and

releasing write mode process locks.

20. The system of claim 16 further comprising at least one subsystem whereby said synchronization comprises a receive sync operation between a first client and said intermediary, said receive sync operation comprising deserializing a set of necessary changes from the intermediary and applying same to said client.

21. The system of claim 20 further comprising at least one subsystem whereby said receive sync operation further comprises:

acquiring read mode process locks; and

releasing read mode process locks.

22. The system of claim 16 further comprising at least one subsystem whereby said synchronization comprises a compaction operation between a first client and said intermediary, said compaction operation comprising:

executing a successful receive sync operation without releasing said read mode process locks;

deleting all sync files; and

executing a full send sync operation.

23. A computer-readable medium comprising computer-readable instructions for synchronizing at least two computer systems utilizing a common storage platform (e.g., WinFS) (each a “

client”

) through an intermediary computer system having a different storage platform (e.g., Win32) (the “

intermediary”

), said computer-readable instructions comprising instructions for the utilization of a synchronization-through-intermediary (STI) adapter resident on each client and interfacing each client to said intermediary.

24. The computer-readable instructions of claim 23 further comprising instructions whereby said synchronization is utilized to support a data-sharing operation.

25. The computer-readable instructions of claim 23 further comprising instructions whereby said synchronization is utilized to support a end-user roaming.

26. The computer-readable instructions of claim 23 further comprising instructions whereby each said common storage platform is an Item-based storage platform.

27. The computer-readable instructions of claim 26 further comprising instructions whereby a change enumeration for a client is serialized as at least one file stored on said intermediary (each a “

sync file”

).

28. The computer-readable instructions of claim 27 further comprising instructions whereby said at least one file comprises, for a single serialization, at least one or more of the following:

a change data file (CDF) for change data (CD), a prerequisite knowledge file (PKF) for prerequisite knowledge (PK), and a learned knowledge file (LKF) for learned knowledge (LK).

29. The computer-readable instructions of claim 27 further comprising instructions whereby said synchronization comprises a send sync operation between a first client and said intermediary, said send sync operation comprising:

determining learned knowledge for the intermediate;

if said first client has changes that are not reflected in said intermediate'"'"'s learned knowledge, preparing a set of necessary changes for said intermediary;

serializing said set of necessary changes and writing same to said intermediary; and

30. The computer-readable instructions of claim 29 further comprising instructions whereby said send sync operation further comprises:

acquiring write mode process locks; and

releasing write mode process locks.

31. The computer-readable instructions of claim 27 further comprising instructions whereby said synchronization comprises a receive sync operation between a first client and said intermediary, said receive sync operation comprising deserializing a set of necessary changes from the intermediary and applying same to said client.

32. The computer-readable instructions of claim 31 further comprising instructions whereby said receive sync operation further comprises:

acquiring read mode process locks; and

releasing read mode process locks.

33. The computer-readable instructions of claim 27 further comprising instructions whereby said synchronization comprises a compaction operation between a first client and said intermediary, said compaction operation comprising:

executing a successful receive sync operation without releasing said read mode process locks;

deleting all sync files; and

executing a full send sync operation.

34. A hardware control device for synchronizing at least two computer systems utilizing a common storage platform (e.g., WinFS) (each a “

client”

) through an intermediary computer system having a different storage platform (e.g., Win32) (the “

intermediary”

), said hardware control device comprising means for the utilization of a synchronization-through-intermediary (STI) adapter resident on each client and interfacing each client to said intermediary.

35. The hardware control device of claim 34 further comprising means whereby said synchronization is utilized to support a data-sharing operation.

36. The hardware control device of claim 34 further comprising means whereby said synchronization is utilized to support a end-user roaming.

37. The hardware control device of claim 34 further comprising means whereby each said common storage platform is an Item-based storage platform.

38. The hardware control device of claim 37 further comprising means whereby a change enumeration for a client is serialized as at least one file stored on said intermediary (each a “

sync file”

).

39. The hardware control device of claim 38 further comprising means whereby said at least one file comprises, for a single serialization, at least one or more of the following:

a change data file (CDF) for change data (CD), a prerequisite knowledge file (PKF) for prerequisite knowledge (PK), and a learned knowledge file (LKF) for learned knowledge (LK).

40. The hardware control device of claim 38 further comprising means whereby said synchronization comprises a send sync operation between a first client and said intermediary, said send sync operation comprising:

determining learned knowledge for the intermediate;

if said first client has changes that are not reflected in said intermediate'"'"'s learned knowledge, preparing a set of necessary changes for said intermediary;

serializing said set of necessary changes and writing same to said intermediary; and

41. The hardware control device of claim 40 further comprising means whereby said send sync operation further comprises:

acquiring write mode process locks; and

releasing write mode process locks.

42. The hardware control device of claim 38 further comprising means whereby said synchronization comprises a receive sync operation between a first client and said intermediary, said receive sync operation comprising deserializing a set of necessary changes from the intermediary and applying same to said client.

43. The hardware control device of claim 42 further comprising means whereby said receive sync operation further comprises:

acquiring read mode process locks; and

releasing read mode process locks.

44. The hardware control device of claim 38 further comprising means whereby said synchronization comprises a compaction operation between a first client and said intermediary, said compaction operation comprising:

executing a successful receive sync operation without releasing said read mode process locks;

deleting all sync files; and

executing a full send sync operation.