Installing and upgrading HP Insight Management 7.2 Update 2 on Windows Server 2012 Failover Clusters

Technical white paper | HP Insight Management 7.2

The software listed above reflects the preferred supported versions. For Windows Server and SQL Server products, these

earlier versions are also supported:

• Microsoft Windows Server 2008 R2 Enterprise, with or without SP1. The hotfix download described in

http://support.microsoft.com/kb/978527 is required when SP1 is not installed. If you are installing Insight

Management 7.2.x on a Microsoft Windows Server 2008 R2 cluster, follow the Insight Management installation

instructions from the 7.1. version of this whitepaper. See Using Failover Cluster Manager to create resources for the

Insight Management clustered service section onward in the 7.2 version of this whitepaper to know more about the

changes in the post Insight Management installation configuration procedure.

• Microsoft SQL Server 2008 Enterprise with SP3

• Microsoft SQL Server 2008 R2 Enterprise with SP1 or SP2

NOTE: Microsoft SQL Server 2008 R2 Enterprise SP1 is not supported with Insight Management release 7.2.2 and onward.

Storage

The following storage disks with drive letters are 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:

• One shared disk for Microsoft Distributed Transaction Coordinator, disk T:

• One shared disk for Microsoft SQL Server, disk S:

• One shared disk for the Insight Management program files, disk V:

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

Configuration Guide, and also see Boot from SAN.

In testing for this white paper, the disks for the cluster witness and Distributed Transaction Coordinator were sized at 1 GB

each.

Tip:

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 Creating the Failover Cluster.

Supporting Systems

It is assumed that an existing Active Directory domain infrastructure and DNS services suitable for hosting the cluster are

available. Multi-site clusters are not supported.

If the Insight Management SQL instance is to be hosted in another cluster, that cluster must be in the same domain as the

Insight Management cluster.

Network

Microsoft Failover Clusters require that each virtual server in a cluster have a unique 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

following four virtual servers. An additional two static IP addresses are needed for the physical nodes.

1. Failover Cluster virtual server and the client access point

Function: To act as the virtual server IP address and name for the Failover Cluster software

Suggested action: Windows management tools use this address to get the status and manage the Failover Cluster

software. In addition, Systems Insight Manager uses this address to discover the Failover Cluster. For the examples

discussed in this white paper, the IP address is 15.199.242.161 and the name is CMS-C16-CLUSTER.

2. Systems Insight Manager and Insight Management virtual server and the client access point

Function: To act as the virtual server IP address and name for Systems Insight Manager and Insight Management

You specify this name and address to connect to Systems Insight Manager through your browser.