Several years ago, I became really frustrated with Windows' off line drive function. You know the one where if you have network drives and you want access to the data when off line, you can ask Windows to make them available and it would sync them with local copies kept on your laptop hard drive. That way, when you are connected on the office network, you are working on the network version, and when on the road, you are working on the off line local copy, and any changes in either direction would be synchronised the next time you were back on the office network.
If it really worked like that, it would be perfect. The problem was though that in Windows 2000 and then later Windows XP, it never did really work. Sometimes it was just as promised, but more often than not I would be in another location and find that my local copy was somehow not available, or there would be large chunks of data missing, or the version available off line would be a least a few weeks out of date, even if I had been in the office recently.
At the time I tracked down fsync, by Vico Biscotti, which is a small command line utility for synchronising two folders from left to right, no more and no less. I then wrote a bunch of simple batch files using notepad to sync my network folders onto local directories on my hard drive, and then another set to sync them back. This worked very well, and never missed a beat. I would run one fsync batch file every time I left the network, and another one every time I rejoined.
It worked so well in fact that I had forgotten about it actually, and when I received my last laptop with Windows 7, I decided to try off line folders within Windows again, seeing as the rest of Windows 7 works so much better than most previous versions of Windows.
The first few months went well. Each time I needed them, the off line folders appeared to work as expected. Then one day, as luck would have it, just when I needed something really important, it wasn't there. I had experienced some syncing issues which I somehow didn't notice, until it was too late. Then there was another time, where I was on the network, checking out some of our customer profile files, and they appeared to be out of date. I was about to chastise some of our staff for not keeping the details current, when suddenly I noticed that my computer was using the offline copies rather than the live ones, even though I was connected to the network. That was the final straw.
I was stupid though. I started googling through various sync applications and tried several of them. They all seemed ok, but I kept coming across various issues, the main one being that they were often overly complicated. It was not always clear how directories missing on one side were going to affect directories on the other, and while it was possible to have version control etc, this was way more than I needed.
Thankfully it suddenly hit me, and I tracked down fsync again. It has had a couple of minor revisions since I had last downloaded it, but it is still just as simple and effective as it ever was. It still has all the same options to run in silent mode without prompting, and determining what overwrites and what doesn't etc. Most importantly though, it just gets the job done.
It is a command line utility so it is best suited for those like me who want to run a basic batch file or script unattended. If you need a GUI showing the source and destination folders etc, fsync is not for you. Also, I suggest you test your batch file first to make sure you are copying just what you want, and it is handling the deleting of missing directories on your target side as per your requirements. You don't want to accidentally wipe out any data you want to keep. Once you have the script doing just what you want though, you can save it and then just run it every time you need to, knowing it will work as expected every time.
I now have my off line folder system working just how I want it again with my work laptop, and I am now making full use of fsync at home to maintain backups of our media library from our media NAS onto our general backup NAS. Yes, I have two NAS's on our home network, geeky I know, but well worthwhile.
Later.