30 października 2011 15:46
This scenario envisions 3 replicas - A, B, and C. Both A and C sync to B, but not to each other.
On all replicas, file 123.txt is a previously synced copy of the same file.
On replica A, file 123.txt is modified on January 1 by a user while A is offline and unable to sync. On replica C, file 123.txt is modified on January 2 by a user while C is offline and unable to sync. On January 3, replica A comes online and syncs file 123.txt with replica B. On January 4, replica C comes online and syncs file 123.txt with replica B.
What will happen when replica C syncs 123.txt with replica B?
When syncing with replica C, is the copy of 123.txt synced by replica A to replica B considered as modified earlier or later than the replica C copy of 123.txt? As shown, 123.txt was last modified by a user on replica A on January 1, before the modification on replica C on January2. However, the replica A copy was last synced to replica B on January 3, after the user modification to 123.txt on replica C. Is the synced file originally from replica A considered "modified" on replica B, and thus, "newer" than the copy of the file on replica C? Note, no changes have been made to 123.txt on replica B, other that what the sync introduces.
- Zmodyfikowany przez bill28 31 października 2011 00:13
30 października 2011 16:44Właściciel
Is this question for the File Sync Provider (or Sync Toy)?
31 października 2011 00:04
Hmm .. I thought the answer would be the same, so now I am curious of the difference. However, my question was with respect to the File Sync Provider.
3 listopada 2011 05:09Właściciel
You should confirm this with SyncToy, but I think you are right that A will be the winner here.
The Sync Framework itself does not know about "Last Modified Time" - it leaves the resolution up to the sync application. The File Sync Provider choses to use Last Modified Time to resolve conflicts.