Step-By-Step Guide: Configuring Hyper-V and Failover Clustering for Windows Server 2008 R2 on the HP ProLiant DL980, rev 1

• Consider using multipath I/O software: In a highly available storage fabric, you can deploy

failover clusters with multiple host bus adapters by using multipath I/O software. This provides the

highest level of redundancy and availability. For Windows Server 2008 R2, the multipath solution must

be based on Microsoft Multipath I/O (MPIO). HP usually supplies an MPIO device-specific module

(DSM) for the storage, although Windows Server 2008 R2 includes one or more DSMs as part of the

operating system.

Important

This Host bus adapters and multipath I/O software can be very version

sensitive. If you are implementing a multipath solution for your cluster, choose

the correct adapters, firmware, and software for Windows Server 2008 R2.

Software Requirements for Using Hyper-V and Failover Clustering

Software requirements for using Hyper-V and the Failover Cluster feature are described below.

• All the servers in a failover cluster must run the x64-based version of Windows Server 2008 R2.

(Nodes within a single failover cluster cannot run different versions.)

• All the servers should have the same software updates (patches) and service packs.

• Windows Server 2008 R2 Enterprise or Windows Server 2008 R2 Datacenter must be used for the

physical computers. These servers must run the same version of Windows Server 2008 R2, including

the same type of installation. That is, both servers must be either a full installation or a Server Core

installation.

• If you do not want to install Windows Server 2008 R2 Enterprise or Windows Server 2008 R2

Datacenter on the test virtual machine, you will need the installation media for the operating system.

The instructions in this guide assume that you will install Windows Server 2008 R2 on the virtual

machine.

Network Infrastructure and Domain Account Requirements

You will need the following network infrastructure for a two-node failover cluster and an administrative

account with domain permissions, described below.

• Network settings and IP addresses: When you use identical network adapters for a network,

also use identical communication settings on these adapters (such as speed, duplex mode, flow control,

and Media Type). Also, compare the settings between the network adapter and the switch it connects

to and make sure that no settings are in conflict.

• DNS: The servers in the cluster must be using Domain Name System (DNS) for name resolution.

The DNS dynamic update protocol can be used.

• Domain role: All servers in the cluster must be in the same Active Directory domain.

• Domain controller: We recommend that your clustered servers be member servers. If they are, you

need an additional server that acts as the domain controller in the domain that contains your failover

cluster.

• Clients: As needed, you can connect one or more networked clients to the failover cluster that you

create, and observe the effect on a client when you move or fail over the highly available virtual

machine from one cluster node to the other.

• Account for administering the cluster: When you first create a cluster or add servers to it, you

must be logged on to the domain with an account that has administrator rights and permissions on all

servers in that cluster. The account does not need to be a Domain Admins account, but can be a