Actually, in netbios mode, you only need one copy on the source machine, but - this is the least efficient way to operate, but the most simple to configure. Barely any improvement over Robocopy in this mode, all due to the network traffic needed to analyze the remote files.
Put a copy of Unison.exe on the remote (anywhere) and create a shortcut in the users startup folder that runs <path>UNISON -socket 1758. This starts a Unison listener on port 1758 (you could use pretty much any available port)
On the source system, you can run
unison <path> socket://<host>:1758/<path> -prefer <path> -batch
This becomes a very efficient method, as the originating command briefly communicates a request to the remote to generate a report of files in the specified "root" (path). This report is returned to the originating system, where it compares the list with one it generated locally, determining which files need to be updated (in which direction). It then begins sending the update.
The remote site accepts the files into temporary locations, and only after completely receiving and verifying them does it overwrite the local file, making the sync process both safe and recoverable.
The "prefer" tells unison which file to take if changes are detected on both systems. It's use is up to you - I generally force one system over the other.
I set up unison to run as a system service using SrvAny, and push files to many small servers at remote branches every hour throughout the day.
Glenn
_________________________
Actually I
am a Rocket Scientist!
