Blogcast: Virtual Server 2005 R2 Host Clustering How To - Part 5 of 5
If you watched the demonstration blogcast of Virtual Server 2005 R2 I posted up at the weekend, yesterday, I ripped the environment apart to build it again from scratch so you can see how I built it.
The last part of this mini series is where we setup the networking on the Virtual Machine guest we are making highly available through host clustering. In my scenario, I deviate from the whitepaper on host clustering as the network cards between my two hosts are different. In the whitepaper, you place the .vnc file for the network on the shared drive. I also show you once more what happens during unplanned downtime by power-cycling one of the nodes in the cluster.
So that's all you need to know about host based clustering using Virtual Server 2005 R2 in conjunction with Windows Server 2003 Clustering Services. Have fun, and please let me know if you found this useful!
Previous parts:
Comments
Anonymous
January 01, 2003
Here's a good question emailed to me yesterday. If you seen the Virtual Server 2005 R2 Host Clustering...Anonymous
January 01, 2003
Microsoft have released today 4 new whitepapers for Microsoft Virtual Server. They all are about ~20Anonymous
January 01, 2003
Virtual Server 05 R2 es gratis, tambien es importante el entranemiento para completar la oferta....aqui...Anonymous
January 01, 2003
I've sent this out to several folks that wanted to learn more about VS.  Here are a few resources...Anonymous
December 22, 2005
Question sir...I watched your entire videos relating to the Virtual Server R2 HostClustering and noticed that the cluster nodes are laptop and desktop. I'm no cluster expert, but I though cluster nodes are "suppose" to be identical. I'd like to this to my small client's setup due to hardware differences / costs. Basically, with what you did is okay to do...although I know not recommended or best practices cluster still will work for non-similar hardware (host hardware). Thanks - great technical BLOG.Anonymous
December 23, 2005
The comment has been removedAnonymous
March 07, 2006
John, how do you put multiple servers in the havm.vbsAnonymous
March 07, 2006
Brian - it should be exactly the same as building a cluster of more machines - havm.vbs is simply the failover script. If you have look at technet for info on building clusters, that's the process to follow. havm.vbs won't care regardless of number of nodes.
Cheers,
John.Anonymous
March 08, 2006
I guess I was a little vague. I actually meant how can I, if I can, attach multiple vmc's to one script.Anonymous
March 13, 2006
Unfortunately, as far as I'm aware that isn't possible using the script as it stands - I would test it, but have no demo kit available. When you configure the script resource, you specify the name of the VM it is failing over. With a little tweaking, you could in theory have multiple parameters with names of multiple VMs, but this would deviate from the supported script - and I re-iterate, I haven't tested this. The supported solution would be to have multiple groups, one per virtual machine.
Cheers,
John.Anonymous
March 20, 2006
Jon, before we went to host clustering for virtual server, we had our virtual's set up to boot at intervals. Is there any way to tell the havm.vbs script to delay the resume of a machine after the resource comes online?Anonymous
March 30, 2006
The comment has been removedAnonymous
July 19, 2006
John,
In response to the Havm.vbs posted by Brian, would it matter if you copied havm.vbs to same directory and renamed it to havm2.vbs and associated the second VS to havm2.vbs (VS1 to havm.vbs and VS2 to havm2.vbs), which would allow for both VS's to run using the same scripted commands in files with different names?