I have blogged before about using the Microsoft Mesh software for keeping multiple computers in sync so that I can pick up any of my machines and pick up exactly where I left off with all of my most important (actually all of them) files with me regardless of which machine I have in front of me. I also use it to ensure that if I do lose any of these machines then I am safe in my knowledge that I have access to all (almost to be pedantic) of my files still.
Well this week I moved one of my netbooks over to Windows 7 which because it had XP meant that it was a clean install. Of course, as part of the installation I set up Microsoft Mesh and selected the normal folders to pull down onto the machine. Well three days later, the sync had not finished and was looking like it was stalled. A quick check through the logs showed an error WinError 18, with the associated text missing file. Checking around I found that the Live Desktop was at 5GB used (which it was not before) and this immediately sprang an idea in my head. Mesh is pretty dumb at times.
It has always been the case that you could setup sync and exceed your online storage and just ignore it. In fact, Paul Thurrott blogged about it in the early days but what was missed was the effect of exceeding your storage, something that I only saw when I also checked my Broadband data usage through my ISP’s nice dashboard. When the online storage is full, Mesh continues to attempt to sync and in this approach it uses bandwidth over and over again so it creates network traffic needlessly. This is a bit poor, particularly when this also seems to hit the processor usage of the machines involved.
Removing the online data store usage of Live stopped the whole repeated sync and suddenly everything is happy again. The world is good, and I am no longer frustrated with the never ending sync.
So come on Microsoft, fix Mesh and give it better behaviour when online storage is exceeded. Additionally, why do you keep it at 5GB? What is wrong with integrating this with the 25GB Live Skydrive?
Pingback: Meshing around | Blog of a Long Distance Worker Tech | Long Distance Dial