Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have two servers using MS NLB for IIS and this is working great.

I have a D:\Websites\ directory on both servers that contain the html, css, aspx, and images etc. I would like to have the D:\Websites\ directory on ServerA be replicated to D:\Websites\ on ServerB. I don't need any snyc, just a brute copy/replace from ServerA -> ServerB.

What is the best way to achieve this?

share|improve this question
up vote 3 down vote accepted

Robocopy is probably the best choice for a simple copy.

robocopy src dst /mir
share|improve this answer
Should I set this up as a scheduled task on ServerA? – Nate Jul 2 '09 at 20:49
Yes, unless you really want to sit there and run it manually. :) – John Gardeniers Jul 2 '09 at 22:23
Thanks for the witty sarcasm John ;) – Nate Aug 5 '09 at 22:42

You could use Distributed File System, but it's probably overkill.

We just use Robocopy + batch file + scheduled tasks to copy this from 1 server to 3 others. Robocopy is available for Server 2003 as part of the Resource Kit tools, or built-in to Server 2008.

share|improve this answer

Seems better to be using features built into IIS, that it was designed to use, than using a bunch of extra points of failure, like Scheduled Tasks, and Scripts etc.

You could share the folder on ServerA, and then change ServerB IIS settings for the site so that the Home Directory is set to "A share located on another computer" - which you would then point back to the share on ServerA

If redundancy is a concern, you could move the data to a different server altogether, share it, then do as I mentioned above to both ServerA and ServerB.

Just thinking out loud!

alt text

share|improve this answer
I thought about this, but I chose robocopy since I trust a scheduled task as a point of failure more than a network file server. – Nate Aug 5 '09 at 22:41

I like Super Flexible File Synchronizer for this because it has built in logging and email notification for failure.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.