Installing and upgrading to HP Insight Software 6.3 on Windows Server 2008 R2 Failover Cluster with SQL Server 2008 for high availability

So f tw a r e

The software needed:

• Microsoft W indows Server 20 08 R2 Enterprise, which includes

– Fa ilove r Clustering

– Microsoft Distributed Tra nsa ction Coordina tor (DTC)

• Microsoft SQL Server 2008 Enterprise with Service Pack 1

• HP Insight Softwa re 6 .3 DVD # 1 a nd DVD # 2

• Update DVD, if installing Insight Software 6.3 update

• Additional softwa re a s specified in “Requirements for non-OS software and Supported browsers” in

the

HP Insight Softwa re 6 .3 Support Ma trix

• ProLiant Support Pack (PSP) 8.50 or higher. To download PSPs for your OS and server model, go to

http://welcome.hp.com/country/us/en/support.html

Sto r a g e

The storage disks needed along with the drive letters used for the examples in this white paper:

• Two private disks, one for each ProLiant system’s boot drive, disk C:

• One shared disk for the cluster witness, disk W:

• O ne shared disk for Microsoft Distributed Tra nsa ction Coordinator, disk T:

• One shared disk for Microsoft SQ L Server 2008, disk S:

• One shared disk for the Insight Software progra m files, disk V:

HP recommends that SAN storage be used for boot disks as well as shared disks. See the document

Booting HP ProLiant servers from a storage area network, and also go to

http:/ / h18004.www1.hp.com/ storage/ networking/ bootsan.html.

In testing for this white pa per, the disks for the cluster witness a nd Distributed Tra nsa ction Coordina tor

were sized at 1 GB each.

TIPS:

Create the shared disks W:, T:, S:, and V: on the SAN and present them to

the cluster nodes, but do not “online”, “initialize” or “create” a volume for

any disk until instructed to do so in the section Creating the Failover Cluster

below.

The SAN “ snapclone” feature provides a convenient way to create restore

points that can be used with backup schemes and to facilitate the

reinstallation of software if needed.

Supporting Systems

It is assumed that an existing Active Directory domain infrastructure and DN S services suitable for

hosting the cluster are available.

Netw ork

Microsoft Failover Clusters require that each virtual server in a cluster have a unique static IP address

and network name registered in the DNS. For the configuration described in this white paper, four

static IP addresses are required for the four virtual servers described below. An additional two static IP

addresses are needed for the physical nodes.