Windows File Replication load

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.
LVL 4
SkipFireAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

adiloadiloCommented:
you should use DFS and not FRS , DFS will allow you to limit network traffic and split bandwith between all locations . it also allows you to scheduele the replication time and direction of replication etc ....  a 20 MB replication will not affect a network ,only if it is run frequently .

http://technet.microsoft.com/en-us/library/cc732863(WS.10).aspx
0
SkipFireAuthor Commented:
Being on an infrequent schedule may minimize traffic, but it also goes against the web team's requirement of nearly immediate.  The goal is to deploy once and have it almost immediately update on all servers, not wait for what would average out to several minutes before it starts to copy.  Unidirectional replication would be fine, but not every 15 minutes.  There is concern about even 5 minutes.
0
adiloadiloCommented:
with DFS content update will be immediate , if you have a fast connection . if no fast connection is available then  you may have to dedicate a separate tunnel for  traffic between server IIS servers . you can also limit replication  to only replicate when a file or folder is updated . you should create a webfarm between iis servers .
Please read this article , it will explain further .

http://weblogs.asp.net/owscott/archive/2006/06/07/DFS-for-Webfarm-Usage---Content-Replication-and-Failover.aspx
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.