Method for managing multiple file states for replicated files

• US 8,010,491 B2
• Filed: 02/28/2003
• Issued: 08/30/2011
• Est. Priority Date: 02/28/2003
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Liu, Hai, Rayson, Steven James, Edelstein, Noah, Saliba, Hani, Antonoff, Lauren
• Primary Examiner(s): Cottingham; John R.
• Assistant Examiner(s): Pham; Michael
• Application Number:
  US10/376,873
• Publication Number:
  US 20040172424A1
• Time in Patent Office: 3,105 Days
• Field of Search: 707/201, 707/203, 707/204, 707/1, 707/10, 707/8, 707/638, 707/609, 707/610, 707/640, 707/695, 717/170
• US Class Current: 707/638
• CPC Class Codes: G06F 16/10 File systems; File servers

Abstract

A server file replication technique is implemented with three local copies of a replicated file. First, a shadow file is a copy of the last known good version of the file on the server. Second, a local copy is the user'"'"'s working copy. Whatever changes the user has made to the file are stored in the local copy. Third, a rollback file is a copy made of the local copy if the local copy changes (for example, when conflicts are resolved or the server version is copied to the local copy.) Different states exist, based on whether these copies contain differences from each other and from the server version, and based on the user'"'"'s use of the document. These states guide what is done to maintain the local copies and whether conflict resolution is required.

Claims

1. A method for file replication of a master file on a first computer accessible by a plurality of other computers, comprising:

replicating a local copy of said master file and an accompanying shadow copy of said master file on each of at least several of the plurality of other computers;

permitting access to each local copy for modification; and

updating each shadow copy when said master file changes.

2. The method of claim 1, where said method further comprises:

storing a versioning state associated with said replication,

and where said step of permitting access to said local copy for modification comprises;

changing said versioning state when said local copy is modified.

3. The method of claim 2, where said step of changing said versioning state when said local copy is modified comprises:

setting said versioning state to a modified state indicating that said local copy has been modified.

4. The method of claim 1, where said method further comprises:

storing a versioning state associated with said replication;

and where said step of updating said shadow copy when said master file changes comprises;

changing said versioning state when said updating occurs.

5. The method of claim 1, where said step of updating said shadow copy when said master file changes comprises:

detecting that said local copy has been modified; and

resolving conflicts between said local copy and said updated shadow copy.

6. The method of claim 5, where said method further comprises:

storing a versioning state associated with said replication;

and where said step of resolving conflicts between said local copy and said updated shadow copy comprises;

changing said versioning state to a conflicted state indicating that a conflict exits.

7. The method of claim 5, where said step of resolving conflicts between said local copy and said updated shadow copy comprises:

presenting a conflict interface;

accepting a conflict resolution command; and

implementing said conflict resolution command.

8. The method of claim 7, where said implementation of conflict resolution commands comprises:

determining if a change should be made to said master file; and

communicating said change to be made to said first computer.

9. The method of claim 8, where said step of communicating said change to be made to said first computer comprises:

generating difference information regarding differences between said local copy and said master file; and

communicating said difference information to said master file.

10. The method of claim 1, where said step of updating said shadow copy when said master file changes comprises:

storing said local copy as a rollback copy; and

updating said local copy with said shadow copy.

11. The method of claim 10, where said step of storing said local copy as a rollback copy comprises:

presenting a rollback interface;

accepting a rollback command; and

displaying said rollback copy in response to said rollback command.

12. The method of claim 10, where said method further comprises:

storing a versioning state associated with said replication;

and where said step of storing said local copy as a rollback copy comprises;

changing said versioning state to a rollback available state.

13. The method of claim 10, further comprising:

tracking whether the local copy has been accessed since a previous rollback;

and where said step of storing said local copy as a rollback copy comprises;

storing said local copy as a rollback copy only if said local copy has been accessed since the previous rollback.

14. A system for replication of a master file, the system comprising a first computer and a plurality of other computers, said master file located on the first computer, said first computer at least intermittently operably connected to the plurality of other computers, each of at least several of the plurality of other computers comprising:

local copy storage for storing a local copy of said master file;

shadow copy storage for storing a shadow copy of said master file;

a local copy modification module for permitting access to said local copy for modification; and

a shadow copy updating module for updating said shadow copy storage when said master file changes.

15. The system of claim 14, at least a subset of the plurality of other computers further comprising:

versioning state storage for storing a versioning state associated with said replication,

and where said local copy modification module changes said versioning state when said local copy is modified.

16. The system of claim 15, where said local copy modification module sets said versioning state to a modified state indicating that said local copy has been modified.

17. The system of claim 14, where the at least a subset of the plurality of other computers further comprises:

versioning state storage for storing a versioning state associated with said replication;

and where said shadow copy updating module changing said versioning state when said updating occurs.

18. The system of claim 14, where shadow copy updating module comprises:

local copy modification detection module for detecting that said local copy has been modified; and

conflict resolution module for resolving conflicts between said local copy and said updated shadow copy.

19. The system of claim 18, where the at least a subset of the plurality of other computers further comprises:

versioning state storage for storing a versioning state associated with said replication;

and said conflict resolution module changes said versioning state to a conflicted state indicating that a conflict exits.

20. The system of claim 18, where said conflict resolution module comprises:

conflict interface module for presenting a conflict interface;

conflict resolution input module for accepting a conflict resolution command; and

conflict resolution implementation for implementing said conflict resolution command.

21. The system of claim 20, where said conflict resolution implementation comprises:

change determination module for determining if a change should be made to said master file; and

first computer change communication module for communicating said change to be made to said first computer.

22. The system of claim 21, where said first computer change communication module comprises:

difference generation module for generating difference information regarding differences between said local copy and said master file; and

first computer communication module for communicating said difference information to said master file.

23. The system of claim 14, where said shadow copy updating module comprises:

rollback storage for storing said local copy as a rollback copy; and

local copy update module for updating said local copy with said shadow copy.

24. The system of claim 23, where said local copy update module comprises:

a rollback interface presentation module presenting a rollback interface;

rollback command acceptance module accepting a rollback command; and

rollback copy display for displaying said rollback copy in response to said rollback command.

25. The system of claim 23, where at least a subset of the plurality of other computers further comprises:

versioning state storage for storing a versioning state associated with said replication;

and where said rollback storage changes said versioning state to a rollback available state.

26. The system of claim 23, at least a subset of the plurality of other computers further comprising:

local copy access tracking module for tracking whether the local copy has been accessed;

and where said rollback storage for storing said local copy as a rollback copy comprises;

local copy access logic for storing said local copy as a rollback copy only if said local copy has been accessed.

27. A method for replicating a master file on a server processor onto a plurality of client processors, the method comprising:

storing a local copy of the master file on each of the plurality of client processors;

storing a shadow copy of the master file on each of the plurality of client processors;

permitting each of the plurality of client processors to access their local copy for modification;

updating the shadow copy on each of the plurality of client processors when the master file changes, wherein the updated shadow copy is indicative of a most recent version of the master file on the server processor by, the step of updating the shadow copy on each of the plurality of client processors comprising;

storing a local copy as a rollback copy only if the local copy has been

accessed since a previous rollback; and

updating the local copy with the shadow copy; and

generating versioning states indicative of versions of each of the master file, the plurality of local copies, and the plurality of shadow copies;

storing the generated versioning states; and

utilizing the stored versioning states to determine a current state of at least one of the master file, a local copy, and a shadow copy.