Part 1. Server 8 Beta Hyper-V Cluster Build

Below are the steps taken to build a Windows Server 8 Beta (build 8250) failover cluster for hyper-v virtualization.  My servers have already had the following performed:

  • Joined to domain
  • NIC Team configured with default settings
  • Hyper-v role installed
  • Failover Clustering feature has been installed on each of the two nodes
  • Virtual Switch created and setup to tag management traffic with the proper vlanID (only 2 nics available in lab)
  • Storage has been provisioned and zoned to each of the two clustered nodes.

Upon launching the Failover Cluster Manager tool, the familiar FCM console appears. To create a new cluster, select “Create Cluster…” in the actions pane.

The yet again familiar “Create Cluster Wizard” appears allowing us to build our new cluster. Select Next to continue.

In the “Select Servers” screen of the wizard, add the two (or more) nodes that will make up the cluster and select “Next” to proceed.

It’s always a good idea to ensure the cluster can be supported by Microsoft and validation of the cluster is one way to ensure everything required is in place. Leave the default of Yes selected and click “Next” to proceed to invoke the validation wizard.

It’s worth it to note that during my validation tests the “List All Running Processes” task took almost 10 minutes. Have patience and once completed select next to continue.

After the validation wizard has successfully been completed, we are taken to the “Access Point for Administering the Cluster” screen. This seems to be new to Server 8 but the end result is the same as in 2008/R2 clustering in that we are creating a cluster core object for managing the cluster. My settings are configured as below. An additional static IP is best for this cluster object.

Selecting “Next” will take the wizard to the final confirmation screen summarizing the cluster name and IP address and also the nodes that will be part of the new cluster. Note that I am also unchecking the box at the bottom which states to “Add all eligible storage to the cluster”. I have not come across this before and will test the purpose of this in a different environment with different storage.

After successful completion of the new cluster, the system will automatically connect to the new “Access point for Administration” or cluster object. It should display similar to the below screen shot.

In Part 2 of Server 8 Hyper-V Clustering. I will bring shared storage (CSV) into the newly created cluster for storage of highly available virtual machines.

Any thoughts?