Microsoft KB Archive/248025

= How to configure clustered IIS virtual servers on Windows 2000 Advanced Server =

Article ID: 248025

Article Last Modified on 10/26/2007

-

APPLIES TO


 * Microsoft Windows 2000 Advanced Server

-



This article was previously published under Q248025



SUMMARY
''This article provides a brief overview of load balancing and clustering to configure a Microsoft Internet Information Services (IIS) Web site. This article also provides step-by-step instructions that describe how to configure IIS virtual servers on Microsoft Windows 2000 Advanced Server cluster nodes.''



SUMMARY
You can use either load balancing or clustering to configure a highly available IIS Web site. Load balancing is effective for high traffic Web sites that receive many hits per day. Clustering is an effective solution for reduced traffic Web sites where the site must be available. In a cluster configuration, two computers use a shared hard disk and appear to the user as a single site.

This article describes how to configure IIS virtual servers on Windows 2000 Advanced Server cluster nodes.



MORE INFORMATION
Note Before you configure your cluster, confirm that the Microsoft Cluster service and Microsoft IIS 5.0 are correctly installed on both computers in the cluster. Also, confirm that the computers are connected to the same shared hard disk. You can install the Cluster service on Microsoft Windows 2000 Advanced Server-based and Microsoft Windows 2000 Datacenter Server-based domain controllers or member servers.

Before you install IIS server instances on a server that runs the Cluster service, make sure that the Cluster service is installed correctly and that failover works.

We only support running MSDTC on cluster nodes as a clustered resource. Running MSDTC in stand-alone mode on a cluster is not a recommended or a supported configuration. Using MSDTC in as a non-clustered resource on an MSCS cluster is a problematic configuration because transactions can be orphaned and data corruption can occur if a cluster failover occurs.

To configure an IIS clustered site, follow these steps:

Note You must follow steps 1 through 23 to create the Web resource correctly.  On the first node in the cluster, click Start, click Run, type Comclust.exe, and then click OK. You can ignore the message that says that component load balancing will not be installed.

This step configures MSDTC on both nodes and installs the MSDTC resource group on the server that runs the Cluster service.

MSDTC resource installation for IIS virtual servers is required when Web programs are using transaction mode or calling MSDTC-related programs. IIS Virtual Server Instance does not require MSDTC resource dependency if the Web sites are not using transactions. Repeat step 1 on each node in the cluster. On one of the nodes in the cluster, click Start, click Run, and then type the following, where  is the drive letter for the shared drive, and   is the name of the folder for the Web folder that you want to use:



By default, the MSDTC resource is always added to the default Cluster group when Comclust.exe is run. However, you can install MSDTC on another group that depends on non-quorum disks. This leaves the default Cluster group intact.

If you remove the quorum disk resource or move the quorum disk resource from the group, Comclust.exe moves the MSDTC resource to another group. You can also modify the properties of the MSDTC resource so that the dependency can be changed from the quorum disk to another disk and then moved to another disk group. In the folder that you created in step 3, create two new files that are named Default.asp and Default.htm. Click Start, point to Programs, point to Administrative Tools, and then click Cluster Administrator. Right-click the non-quorum disk group that you want to use, click New, click Resource, and then type a name and description for the resource. Under Resource Type, click IP Address, and then click Next.</li> On the Possible Owners screen, click any node that you do not want to have available to the disk resource if a failure occurs, click Remove, and then click Next.</li> On the Dependency screen, click the disk resource, click Add, and then click Next.</li> Type an Internet Protocol (IP) address for the virtual server. Use a different IP address for each virtual server. Click to clear the Enable NetBIOS check box if your situation requires this configuration. In the Network box, click Public Cluster Connection, and then click Finish.</li> Create an IP address resource for an IIS virtual server in the disk group that is using the non-quorum disk in Cluster Administrator. Use a different IP address for each virtual server. Follow steps 6 through 9 for each virtual server instance. Set this IP address resource to depend on the MSDTC resource and the shared disk resource that you have chosen to hold Web site contents.</li> Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.</li> Right-click your computer name, click New, click Web Site, and then click Next.</li> Type a description of the Web site, and then click Next.</li> Type the IP address that you specified in step 9, type the port settings for the site, type the host header information if you use host headers, and then click Next.</li> In the Path box, type the location of the folder that you created in step 3, and then click Next.</li> Under Allow the following, click to select the access permissions that you want, and then click Next.</li> Click Finish.</li> Click Start, point to Programs, point to Administrative Tools, and then click Cluster Administrator.</li> Right-click the disk group for the IP address that you created in step 9, click New, and then click Resource.</li> Type a name and a description for the virtual server instance, click IIS Server Instance, and then click Next.</li> On the Possible Owners screen, remove any servers that you do not want to host the virtual server, and then click Next.</li> Click Disk Resource, click IP Address Resource, click Add, and then click Next..</li> <li>Click the virtual server that you created in Internet Services Manager, and then click Finish.</li> <li>(This step is optional.) On the domain name system (DNS) server, add a host entry that maps the IIS virtual server network name to the IP address that is provided for this Web site. Now the IIS virtual server instance is ready on node A. You can manually move the group to node B and create a new Web site. To do this, use the Microsoft Management Console (MMC) on node B, and then type the same folder path and IP address. Alternatively, you can use the IISSYNC utility to synchronize the two nodes automatically.

For additional information about how to run IISSYNC on Windows 2000 Advanced Server, click the following article number to view the article in the Microsoft Knowledge Base:

249603 Using IISSYNC to synchronize clustered Web sites on Windows 2000 Advanced Server

</li> <li>After you follow the procedure that is described in steps 1 through 23, test the IIS virtual Web server from a client browser by accessing the DNS name of the Web site. For example, if the IIS virtual server has the network name "MyWeb" and the DNS entry maps the corresponding IP to "MyWeb.Microsoft.com" for this site, type the following in a browser window to view the default page:

http://myweb.microsoft.com

If no DNS entry is specified in step 7, you can use the IP address to directly access the clustered Web site to test it. Before you use the browser to test the IIS virtual Web server, use the PING protocol at a command prompt to check the IP address for the cluster Web site to make sure that the IP configuration on the network is correct.</li></ol>

Additional information about MSDTC installation
IISSync requires MSDTC to synchronize the metabases between the cluster nodes. By default, MSDTC is installed in the Cluster group and can remain there. For additional information about how to move MSDTC to the group that owns the IIS server instance, click the following article number to view the article in the Microsoft Knowledge Base:

243204 Microsoft Distributed Transaction Coordinator (MSDTC) recovery techniques in Windows 2000 Cluster Server

<div class="references_section">