How to move websites and SQL databases from Windows 2003 server to new Windows 2008 server

I am in a tight position here.  The data center that my production server (Windows 2003) is sitting in will be shutting down in a week.  In preparation for this, my hosting company built me a new Windows 2008 server in another one of their nearby data centers.  It's up and running and ready to go.  It has been for some time.  I was originally going to have the personal who developed the website and databases to help me with this migration.  I can't seem to contact him now.  I'm a little desperate to make this happen quickly.  I need to transfer (probably via FTP) all of my existing websites (and their SQL databases) from the old server to the new server.  This is the first time I've seen 2008 and its IIS.  It looks a bit different from the IIS that I'm running on the old server (I don't know what version -- it doesn't say).  Both servers are running MS SQL 2008.  Can someone please guide me through this process?
Who is Participating?
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.

Here is a step by step for site migration:

The major concerns here would be any issues between connecting to datasource etc once you start the sql migration.  If you are able to name your sql server to match the naming convention of the current sql server or mimic any of the datasource settings currently in the datacenter you are leveraging it will make your migration much easier.

Please go through your checklist several times before you begin.
Emmanuel AdebayoGlobal Windows Infrastructure Engineer - ConsultantCommented:

First thing you need to do is to configure your IIS7/7.5 to function well on yiur new Windows 2008 Server.

Install IIS features from Server Manager.
1. Click Start -> All Programs -> Administrative Tools -> Server Manager.
 2. In the Server Manager window, scroll down to Roles Summary, and then click Add Roles
Follow the on screen display
3. Select Web Server (IIS) on the Select Server Roles page. An introductory page will open with links for further information.
4. Select the IIS services to be installed on the Select Role Services page. Add only the modules necessary. In this case, ASP.NET is selected, and a description of ASP.NET appears in the right pane. Once desired modules are added, click Next.
5. Add any required role services.
6. IIS is now installed with a default configuration for hosting ASP.NET on Windows Server. Click Close to complete the process.

7. Confirm that the Web server works by using http://localhost.



Add a website by using the UI
1.Open IIS Manager. •For Windows Server 2012, on the Start page click the Server Manager tile, and then click OK. In the Server Manager, click the Tools menu, and then click Internet Information Services (IIS) Manager.
•For Windows 8, on the Start page type Control Panel, and then click the Control Panel icon in the search results. On the Control Panel screen, click System and Security, click Administrative Tools, and then click Internet Information Services (IIS) Manager.

2.In the Connections pane, right-click the Sites node in the tree, and then click Add Website.
3.In the Add Website dialog box, enter a friendly name for your website in the Site name box.
4.If you want to select a different application pool than the one listed in the Application Pool box, click Select. In the Select Application Pool dialog box, select an application pool from the Application Pool list and then click OK.
5.In the Physical path box, enter the physical path of the website's folder, or click the browse button (...) to navigate the file system to find the folder.
6.If the physical path that you entered in the previous step is to a remote share, click Connect as to specify credentials that have permission to access the path. If you do not use specific credentials, select the Application user (pass-through authentication) option in the Connect As dialog box.
7.Select the protocol for the website from the Type list.
8.. If you must specify a static IP address for the website (by default, this is set to All Unassigned), enter the IP address in the IP address box.
9.Enter a port number in the Port text box.
10.Optionally, enter a host header name for the website in the Host Header box.
11.If you do not have to make any changes to the site, and you want the website to be immediately available, select the Start Web site immediately check box.
12.Click OK.
13. Test your site by browsing on to it locally.

Setup FTP
Go to the IIS Manager and right click FTP, select create FTP and follow the onscreen display.

Now that your IIS and FTP are fully configured you now need to perform the following on your existing Server?

Backup your webserver content directory and copy the backup to you new webserver directory or use ftp to copy the data across

Install and Configure your SQL Database
Backup your SQL server and dump the db on to your SQL and configure the database with necessary permission.
Test to ensure you can connect to the database using odbc

Test your web application
Test your web application to ensure that it is connecting to the database and all features are functioning as expected.

Plan for the migration/cut off from the existing server
Schedule the migration
Plan with your hosting provider when you want to cut over so that they can repoint your DNS (I normally plan this for weekend as it sometimes take about 48 or 72hrs for full dns propagation)

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
lrbarriosAuthor Commented:
Thanks all for the help.  For the most part, it was fairly painless.  My sites are up and running.  The biggest problem that I am dealing with is trying to transfer a 126GB database file from the old server (in the old data center) to the new server (in the new data center) across the public Internet.  Slow-going and prone to interruptions.  I've broken up the file (using 7zip) into 700MB chuncks -- a total of 157 files.  If there are any corrupted files on the destination, I will just create PAR2 recovery files for those files using the original source files still on the old server.  Then I'll only need to transfer the PAR2 files (which will be much smaller).  Hoping this works.  Fingers crossed.  Thanks again.
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
Microsoft IIS Web Server

From novice to tech pro — start learning today.