Microsoft Windows Server 2003 Deployment Kit—Deploying Microsoft Internet Information Services (IIS) 6.0 [Electronic resources] نسخه متنی

Completing the Migration

At this point in the process, you have migrated your Web sites and applications to the target server and configured the IIS 6.0 properties to settings on the source server. Now you need to verify that the migration completed successfully, capture the current configuration of the target server, and enable client access to the target server. After you complete these last steps, your migration is complete. Figure 6.9 illustrates the process for completing the migration to IIS 6.0.

Figure 6.9: Completing the Migration to IIS 6.0

Verifying That the Web Sites and Applications Migrated Successfully

Before deploying the target server to a production environment, verify that the Web site content and configuration information migrated successfully by completing the following steps:

Review the system log in Windows Server 2003 on the target server to determine whether any of the Web sites did not start.

IIS 6.0 creates entries in the system log when a Web site fails to start for any reason. Search the System log on the target server for to determine if any errors occurred. For more information about how to troubleshoot Web sites that fail to start, see "Troubleshooting" in IIS 6.0 Help, which is accessible from IIS Manager.

Verify that the Web site content migrated to the target server.

Compare the files and folders for each Web site on the target server with the original files and folders on the source server to determine whether the Web site content has been migrated correctly. Ensure that the number and size of the files and folders on the target server approximates the number and size of the same files on the source server.

Verify that the Web site configuration migrated to the target server.

View the Web site configuration information for a random sampling of the Web sites that were migrated. Compare the Web site configuration on the target server with the corresponding Web site configuration on the source server. Ensure that the configuration for the Web sites has been migrated correctly.

Perform functional testing of the migrated Web sites and applications to ensure that the Web sites and applications behave as expected.

You can find possible causes of application failure by reviewing the Windows Server 2003 and IIS 6.0 Migration Tool logs and application configuration, but the only way to accurately assess whether your Web sites and applications migrated successfully is to perform functional testing. Functional testing is designed to ensure that Web sites and applications are functioning correctly in the most common usage scenarios (for example URLs and inputs).

Procedures for performing functional testing of Web sites and applications are beyond the scope of this chapter. For more complete information about general testing, see the MSDN Online link on the Web Resources page at [http://www.microsoft.com/windows/reskits/webresources], and search for "testing".

Backing Up the Target Server

Before you enable client access to the target server, perform a complete image backup of the target server. Performing this image backup provides you with a point-in-time snapshot of the Web server. If you need to restore the target server in the event of a failure, you can use this backup to restore the Web server to a known configuration.

For more information about how to back up the Web server, see "Back Up and Restore the Web Server to a File or Tape" in "IIS Deployment Procedures" in this book.

Enabling Client Access

After you have migrated your Web sites from the source server to the target server, you are ready to enable client access to the Web sites on the target server while maintaining the DNS entries to the source servers. After a period of time that meets your business needs, you can remove the DNS entries that point to the Web sites on the source server.

Enable client access to the Web sites that are on the target server by completing the following steps:

Create the appropriate DNS entries for the Web sites and applications running on the target server.

For more information about how to create DNS entries for your Web sites and applications see "Managing resource records" in Help and Support Center for Windows Server 2003.

Monitor client traffic to determine whether clients are successfully accessing the target server.

For more information about how to monitor client traffic to Web sites on the target server, see "Monitor Active Web and FTP Connections" in "IIS Deployment Procedures" in this book.

Establish a monitoring period, such as a few hours or a day, to confirm that clients accessing Web sites on the target server are experiencing response times and application responses that meet or exceed your requirements.

Remove the DNS entries that are pointing to the Web sites and applications on the source server.

For more information about how to remove DNS entries for your Web sites and applications, see "Managing resource records" in Help and Support Center for Windows Server 2003.

Prevent new clients from accessing the Web sites on the source server by pausing the Web sites on the source server.

For more information about how to pause Web sites on the source server, see "Pause Web or FTP Sites" in "IIS Deployment Procedures" in this book.

Monitor client traffic to the Web sites on the source server to determine when clients are no longer accessing the source server.

For more information about how to monitor client traffic to Web sites on the source server, see "Monitor Active Web and FTP Connections" in "IIS Deployment Procedures" in this book.

When clients are no longer accessing the Web sites on the source server, decommission the hardware for the source server.