The reason I suggested Unison over Robocopy is that it is better suited for WAN replication.
Robocopy must read/evaluate the remote files to determine what to copy - this puts a heavy load on your communcation circuits. We've saturated a 256K frame link using Robocopy to sync a folder containing only about two dozen Windows hotfixes.
Unison, on the other hand, is a form of client-server synchronization. You "install" Unison (put the executable anywhere in the path) on both systems. Running it on one launches a copy on the remote - they exchange information about the files to be synchronized, so the majority of the work is done without network traffic. Based on the information transferred during setup, the program knows which files to transfer, and in what direction. It's more difficult to set up the first time, but you'll replicate more quickly without overloading the WAN links. Using Unison, we've been able to replicate our entire software repository between sites without saturating the network.
Glenn
_________________________
Actually I
am a Rocket Scientist!
