It would be a pretty niche application, though, I'd think. No doubt somebody could write a cute little GUI that 'acted' like Explorer and let you do the moves / renames / etc and then generated such a script. If you do it via script, just use relative paths in your script and then you'll have a script suitable to run w/o modification on the remote copies. It's sub-optimal, but if you're not going to pay for something that uses the filesystem change journal you're going to have to implement the functionality yourself. You could 'capture' your actions by way of doing the initial moves / renames via script, then running that script on the remote machines. (Somebody who knows more about it than me should comment about that.) I don't see where it's ever been added back into the product. The DFS Replication service is included in Windows Vista, but the 'PC to PC Sync' feature that would use it was cut from Vista RTM.

Windows Server 2003 R2 and Windows Server 2008 can do this. It monitors the NTFS change journal and uses the uniquely assigned file numbers to track renames / moves of files. Microsoft DFS replication will do what you're talking about.

Personally, I'd go with the robocopy option. run it once to replicate, then run it again and it will only copy over the files that have changed.ģ.) If you use HP in a large corporate setting and have a vendor agreement or something set up with them, check into HP StorageWorks Storage Mirroring, however it's a bit heavy-handed for two windows folders.Ĥ.) Finally, there's also, (beta warning! Beta warning!) Windows Live Mesh, but it's. (A big bonus with this is that it will do incremental mirroring, i.e. Here's a script that I shamelessly copied from somewhere, (why re-invent the wheel, eh? :) that I used when migrating large amounts of data from one share to another. 1.) DFS folder replication will work, there's a tutorial here and here's the MS webpage.Ģ.) Robocopy in mirroring mode will work as well, but it won't key off the fact that a file has changed.

Syncback server