Migrating a Web Server to IIS 5.0

Assessing Hardware Requirements

The first thing you must do is decide what type of hardware to use for the migration, and then obtain it and set it up. There are four different approaches to migration, and each one has a different implication for deployment hardware. This section describes the pros and cons of each approach and the hardware required. Subsequent sections give more information about performing the migration steps mentioned here.

1. Migrate to a clean installation of Windows 2000 Server and IIS 5.0.  Perform a clean installation of Windows 2000 Server and IIS 5.0 on a computer other than the production Web server. Migrate settings, content, and applications from the production Web server to the new IIS 5.0 server. Test and debug the new server before deploying it and taking the old production Web server offline.

   Hardware needed: A second computer is required, in addition to the existing production Web server.

   Pros: You can opt to put new, updated hardware in place at the same time you perform the migration. You also avoid taking your production Web server offline until the new server is tested and deployed. Following deployment, if problems arise with the new server that didn’t appear during testing, you can use the original server as a backup.

   Cons: You might need new hardware. However, the cost will be at least partly offset by the time saved conducting the migration as well as troubleshooting any problems that occur during the migration.

   Recommendation: This method is highly recommended because it has the least likelihood of resulting in unforeseen problems. Because of the difficulty in conducting a cross-platform migration on a single computer, this is the only approach recommended for migrating a UNIX-based Web server to IIS 5.0.

2. Migrate a duplicate of a Windows NT–based Web server.  If you’re migrating from a computer running Microsoft® Windows® NT, you can use this approach: On a second computer, install the same software as exists on the production Web server, and then use the Windows 2000 Server Setup Wizard in order to upgrade to Windows 2000 Server and IIS 5.0. Migrate Web configuration settings, content, and applications to the new Web server. Test and debug the new server before deploying it and taking the old production Web server offline.

   Hardware needed: A second computer is required, in addition to the existing production Web server.

   Pros: You can opt to put new, updated hardware in place at the same time you perform the migration. You also avoid taking your production Web server offline until the new server is tested and deployed. Following deployment, if problems arise with the new server that didn’t appear during testing, you can use the original server as a backup.

   Cons: You might need new hardware. However, the cost will be at least partly offset by the time saved conducting the migration as well as troubleshooting any problems that occur during the migration.

   Recommendation: This approach is acceptable, but it requires the preliminary step of installing the software on the new server. It is only feasible for a migration from a Windows NT–based server.

3. Migrate a mirror of a Windows NT–based Web server.  If you’re migrating from a computer running Windows NT, you can use this approach: Create a mirror image of the current production Web server (operating system, software, configuration settings, and content) on a second computer. Then use the Windows 2000 Server Setup Wizard to upgrade it to Windows 2000 Server and IIS 5.0. Migrate Web configuration settings, content, and applications to the new Web server. Test and debug the new server before deploying it and taking the old production Web server offline.

   Hardware needed: For this approach to be successful, you need hardware exactly duplicating that of your existing server.

   Pros: You avoid taking your production Web server offline until the new server is deployed. Following deployment, if problems arise with the new server that didn’t appear during testing, you can use the original server as a backup.

   Cons: All hardware on the second system must exactly duplicate the original server, so you forego having the option to upgrade your hardware at the same time you migrate or upgrade the Web server.

   Recommendation: This method is fine if you don’t need to upgrade your hardware, and it’s far less risky than the next approach described. It is only feasible for a migration from a Windows NT–based server.

4. Migrate the production Web server.  Take your production Web server offline. If it’s already running Windows NT Server, use the Windows 2000 Server Setup Wizard to upgrade it to Windows 2000 Server with IIS 5.0. For a new installation, install Windows 2000 Server on a primary disk partition, which may require reformatting and repartitioning of the hard disk. Migrate Web configuration settings, content, and applications to IIS ‘in place’ on the production Web server. Test and debug the server before deploying it.

   Hardware needed: No new hardware is required.

   Pros: There is no hardware cost.

   Cons: Migrating a production Web server is extremely risky. You must take the server offline, and it will not be available to users until you complete all migration tasks, testing, and debugging.

   Recommendation: This method is not recommended.

© 1997-1999 Microsoft Corporation. All rights reserved.