Users Guide
36 Implementing High Availability in Hyper-V
4
Make sure that all the devices on the server have the latest supported
drivers from
http://support.dell.com
. Download the device drivers for
Windows Server 2008 x64.
NOTE: Dell does not support device drivers that are downloaded from 3rd
party vendors. Only use drivers from http://support.dell.com.
5
Configure the network connections and storage connections as planned.
NOTE: Make sure that the appropriate MPIO software for the storage array
has been installed on the nodes.
NOTE: For Node and Disk Majority configuration of the Failover cluster, make
sure that the shared LUN (minimum 500 MB) that will be used as the witness
disk is configured as shared storage for all servers.
Configure the Failover Clustering Feature and Hyper-V Role
1
Install the Failover Clustering feature on all the Windows Server 2008
servers that will be part of the Hyper-V Host Cluster. The feature can be
enabled using the
Add Feature
wizard in
Server Manager
.
2
The Failover Clustering feature in Windows Server 2008 provides a new
capability that allows administrators to run a validation check on the
planned configuration to identify potential issues before actually creating
the failover cluster. Open the
Failover Cluster
console on any of the
systems, run the
Validate a Configuration
wizard, and make sure that the
configuration with all the nodes meets all the requirements for a Windows
Failover Cluster.
NOTE: It is strongly recommended that all errors and warnings reported by
the validation wizard are addressed before proceeding with configuring the
failover cluster.
3
After all the requirements have been verified to be met, use the
Failover
Cluster Management
console to create the failover cluster.
4
Enable the
Hyper-V Role
on each of the nodes of the failover cluster.
NOTE: For information on enabling the Hyper-V Role, refer to the Dell
Solutions Overview Guide for Microsoft Hyper-V.
5
Configure the Virtual Networks as planned on each Hyper-V server. Make
sure that Virtual Networks are created with the exact same names on all
the servers in the Hyper-V Host Cluster. For example, if any one cluster
node has a virtual network called
TestNetwork
, all the Hyper-V hosts in