Can anyone tell me how much overhead network load there is on Windows file replication, and back it up with any of the theory of how/when it creates traffic? We have several geographically distributed web servers and the web team is wanting to use replication to keep the website files up to date. The network team on the other hand says that this will create excessive traffic even though the files (<20MB) are only updated once or twice a week. The desire for replication is to deploy the files once and then know that they will be copied to the other servers.
We are specifically looking at the file replication available in Windows Server, not a 3rd party product.
In the end, does Windows File Replication have much traffic between updates, or does it wait until it has an update then pushes that data to the other servers?
We are running Windows 2008 64-bit with servers in 2 domains, but both domains are in the same forest.