Windows IT Pro is the leading independent community for IT professionals deploying Microsoft Windows server and client applications and technologies.
  
  
  Advanced Search 


May 2005

Virtual Server 2005 Cluster Setup Kit

Here's all you need to build a virtualized Windows Server 2003 cluster
RSS
Subscribe to Windows IT Pro | See More Clustering and Load Balancing Articles Here | Reprints | Or get the Monthly Online Pass—only $5.95 a month!
SideBar    VM Configuration Summary

One of the most useful features of Microsoft Virtual Server 2005 is its full support for Windows server OSs and for creating clusters in virtual machines (VMs). Using Virtual Server 2005 to create a cluster is easier than you might think. I'll walk you through the process, and you'll soon have a virtualized Windows Server 2003, Enterprise Edition cluster up and running.

Windows 2003 Clusters
Microsoft Clustering Services (MSCS) is the software that enables clustering on various Windows server OSs. MSCS lets multiple systems, called nodes, work together and provide the image of single server as a unit, or cluster, to clients. If one cluster node fails, the node's workload is automatically transferred to the remaining cluster nodes. We'll use Virtual Server 2005 to create and configure a Windows 2003 cluster whose servers are implemented as VMs and are connected to a virtual, shared cluster-storage device. I set up this cluster by using an HP ProLiant ML350 with dual Xeon 3.2 GHz EM64T processors, 2GB of RAM, and 144GB (4 × 36GB) of disk storage. The Web-exclusive sidebar "VM Configuration Summary" at http://www.windowsitpro.com, InstantDoc ID 45902 sums up the details of the sample cluster configuration.

Our sample cluster has two nodes. Each node requires two IP addresses. One address is used for internal communications between the cluster nodes. This internal network passes the cluster heartbeat—essentially a signal that tells each cluster node that the other server is active and available—between nodes. The other address lets external networked systems on your LAN access the cluster.

Creating the Shared Quorum Disk
A key cluster characteristic is the shared storage that the cluster quorum uses. The quorum disk doesn't need to be large—50MB is all the space typically required for a test setup. However, if you're planning to add cluster resources, you'll want to configure a larger quorum disk (100MB to 500 MB), depending on the number of resources you'll add.

To create the shared quorum disk, open Virtual Server Web Administrator by entering the URL http://server:1024/virtualserver/vswebapp.exe?view=1, where server is the name of your Virtual Server 2005 system. Then, to create the virtual hard drive to use for the quorum, click Virtual Disks (in Web Administrator's left frame), Create, Fixed Size Virtual Hard Disk. Virtual Server 2005 doesn't support using a dynamically expanding disk as a cluster's quorum drive, so you must select the Fixed Size Virtual Hard Disk option. Doing so displays a screen like that in Figure 1.

Next, assign a name and directory to the virtual hard disk that will act as the cluster quorum. In Figure 1, you can see that I named my quorum MyClusterQuorum and created it in the Shared Virtual Machines subdirectory, which all the VMs can access. In this way, both cluster nodes can easily access the shared quorum disk.

Configuring the First Node
Your next step is to create the VMs that will serve as the two cluster nodes. To create the first node's VM, click Virtual Machines, Create, which displays the page that Figure 2, shows. In the Virtual machine name field, enter the VM's name (I named it Node1). Next, specify how much memory to allocate to the VM. 256MB, the minimum RAM recommended for a test Windows server installation, is adequate for a test cluster environment.

Now you must create a new dynamically expanding virtual hard disk, which is where Node1's OS will be stored. I used the default size of 16GB. This virtual hard disk isn't shared between the nodes as the quorum drive is.

To let the cluster access your external network, in the Virtual network adapter section you specify External Network, which indicates that the VM will be connected to the host system's external network (in our example, the external network uses an HP NC7761 Gigabit adapter). Virtual Server 2005 gives you two networking options: Internal and External. Internal networks can access only other VMs; external networks can use the host adapter to access your physical network. Although the completed cluster configuration will use both networking types, for now you should select just the external option, then click Create to create the VM.

At this point, we've created a VM named Node1 that has 256MB of RAM, a 16GB IDE virtual hard disk, an IDE CD-ROM device (which Virtual Server adds automatically), and a network interface that's bridged through your host's NIC.

Adding the Quorum to Node1
Now we need to add the shared quorum drive to Node1. Click the Master Status link, then hover the mouse over Node1. Make sure Node1 is powered off and select Edit Configuration from the pop-up window. Before adding the quorum drive, you must set up a SCSI adapter. To do so, in Node1's properties, select the SCSI Adapters option, then click Add SCSI Adapter >> to display the adapter properties page. For SCSI adapter ID, use the default value of 7. Select the Share SCSI bus for clustering check box and click OK.

Next, you'll add to the SCSI adapter the shared hard drive that will be the cluster's quorum drive. To do so, select Node1 on the Web Administrator page, then click Edit Configuration. Click the Hard Disks link, then click Add Disk >>. On the Virtual Hard Disk Properties screen, you should see the dynamically expanding virtual hard drive listed as Virtual hard disk 1 and several blank entry boxes for Virtual hard disk 2—which is where you'll add the information for the shared quorum drive. In the Virtual hard disk 2 section, enter the path to the shared disk (quorum disk) that you created earlier in the Fully qualified path to file box. There's no way to browse for the file, so you must type the path accurately. I used the path C:\Documents and Settings\All Users\Documents\Shared Virtual Machines\MyClusterQuorum.vhd (the default path). To minimize typing, you might want to create these objects close to the root. Then, for Virtual hard disk 2, select SCSI 0 ID 0 for the attachment and click OK. The completed adapter properties should appear similar to the page that Figure 3 shows.

Adding the Internal Network to Node1
You're now ready to add the second virtual NIC that will connect the two cluster nodes. Click the Edit Configuration option for Node1. Click the Network Adapters link, then click Add Network Adapter >>. You'll see the Node1 Network Adapter Properties page, which Figure 4 shows. In the Connected to drop-down box, select Internal Network and click OK. You're now finished configuring the VM for the first cluster node.

Configuring the Second Node
Leave Node 1 powered off and start the configuration process for the second cluster node, Node2. Configuring Node2 is nearly the same as configuring Node1—with two important differences. First, the Node2 VM requires a unique name. Second, the virtual SCSI adapter requires a unique SCSI ID for accessing the shared quorum disk. To create the Node2 VM, click Virtual Machines, Create. Doing so displays the Create Virtual Machine page that Figure 5 shows.

Enter Node2 for the VM name, then fill out the rest of the page exactly as you did for Node1. Select the Create a new virtual hard disk option and create a dynamically expanding virtual hard disk. Leave the Size entry at the default value of 16GB. To let Node2 access the external network, in the Virtual network adapter section specify External Network. You've now created a second VM named Node2 that has 256MB of RAM, a 16GB IDE virtual hard disk, an IDE CD-ROM device, and one NIC that accesses your external network.

Adding the Quorum to Node2
Leave Node2 powered off. To add the shared quorum drive, you must first add a virtual SCSI adapter to Node2, then add the shared quorum drive to the SCSI adapter. To add the SCSI adapter, select Node2, then click Edit Configuration. Click the SCSI Adapters link, then click Add SCSI Adapter >>. On the Node2 SCSI Adapter Properties page, select the Share SCSI bus for clustering check box. In the SCSI adapter ID drop-down list, select 6 (i.e., a different value than you specified for Node1). After you've selected the values, click OK.

Next, you'll add to the SCSI adapter the virtual hard drive that will serve as the shared quorum. Select Node2's Edit Configuration option, then click the Hard Disks link. The Virtual hard disk 1 section should show the virtual hard disk that was created with the VM. To add the shared virtual disk, click the Add Disk >> button, then fill out the virtual hard disk information for Virtual hard disk 2. For Virtual hard disk 2, enter the path to the shared quorum disk in the Fully qualified path to file field. This is the same path that you used for Node1. Next, in the Attachment drop-down box, select the value SCSI 0 ID 0. The completed virtual disk configuration will look like that in Figure 3.

Adding the Internal Network to Node2
The next step is to add to Node2 the second virtual NIC, which is the internal network that will connect the two cluster nodes. On the Web Administrator page, edit the Node2 configuration. Click the Network Adapters link, then click Add Network Adapter >>. In the Connected to drop-down box for Virtual network adapter 2, select Internal Network and click OK. The internal-network configuration values for Node2 will look exactly like those you entered for Node1 in Figure 4. Figure 6 shows the completed Node2 configuration. After you've configured the Node2 VM, be sure to leave Node2 powered off so that it doesn't interfere with subsequent configuration of the Node1 quorum drive.

   Previous  [1]  2  Next 


Interact! The Straight Story on Virtual Server

Learning Path Size up competing virtualization products:
"“Virtual-Server Face-Off"


Find out more about Virtual Server 2005 and clustering:
"Using Microsoft Virtual Server 2005"


Get detailed information about deploying a Windows cluster node as a domain controller (DC):
"Windows 2000 and Windows Server 2003 cluster nodes as domain controllers"


Learn more about Virtual Server 2005:
"Microsoft Virtual Server 2005"


Top Viewed ArticlesView all articles
Kon-Boot Lets You Bypass Logon for Windows and Linux

Kon-Boot looks like a very interesting tool since it can get you into a system without having to logon first. ...

Google to Take On Windows with New OS

It's official: Google will compete head-to-head with Microsoft's dominant Windows OS with a new system called Google Chrome OS. Based on the Google Chrome browser and not its previous OS effort, the smart phone-based Android system, Google Chrome OS will ...

Q. How can I continually check a performance counter from Windows PowerShell?

...


Windows OSs Whitepapers Why SaaS is the Right Solution for Log Management

Related Events WinConnections and Microsoft® Exchange Connections

Don't Miss Windows Server 2008 Virtual Event

Check out our list of Free Email Newsletters!

Windows OSs eBooks Understanding and Leveraging Code Signing Technologies

A Guide to Windows Certification and Public Keys

SQL Server Administration for Oracle DBAs

Related Windows OSs Resources Introducing Left-Brain.com, the online IT bookstore
Looking for books, CDs, toolkits, eBooks? Prime your mind at Left-Brain.com

Discover Windows IT Pro eLearning Series!
Clear & detailed technical information and helpful how-to's, all in our trademark no-nonsense format

Test Drive IT Solutions and Get Free Music Downloads
Solve your toughest IT problems with these free downloads and receive 5 free music downloads!


Windows IT Pro Home Register FAQ for Windows WinInfo News
Europe Edition About Us Contact Us/Customer Service Media Kit Affiliates / Licensing  
SQL Server Magazine Office & SharePoint Pro DevProConnections IT Job Hound
Left-Brain.com Technology Resource Directory asp.netPRO ITTV Windows SuperSite 
 
 Windows IT Pro is a Division of Penton Media Inc.
 © 2009 Penton Media, Inc. Terms of Use | Privacy Statement | Reprints and Licensing