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

We have about 150 websites on one of our servers. We want to move that websites to another server with all of their content, databases, DNS, FTP and application pool users etc.

Current OS is Windows Server 2008 R2 Web edition and the new one will be the same. Most of websites are Dotnetnuke sites. How can we move whole websites with minimum effort?

Our database server is SQL Server 2008 R2 Web Edition and IIS version is IIS 7.5.

share|improve this question
How is your IIS version 7 when 7.5 ships with 2008 R2? – MDMarra Oct 5 '11 at 13:43
hmm okay, I'll correct that thanks for notice. – zforx Oct 5 '11 at 13:52
It's not clear from your question. Are all of the DBs located on the same server as the websites or a different one? – GregD Oct 5 '11 at 13:59
Yes all of the DBs are located on the same server as the websites. – zforx Oct 5 '11 at 14:40

Unfortunately, "minimal" in this case still involves some effort.

  • Migrating the apps and databases / data should be relatively straightforward. Apps you just redeploy on the new environment(s), and Data / DB's you just export / import. Here is a link to a guide for IIS configuration export and migration:

  • DNS is standard to set up

  • The primary points of pain will occur when you go to migrate FTP & application pool users.

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.