Installing HP Insight Software 6.1 Update 1 on Windows Server 2008 R2 Failover Clusters with SQL Server 2008 for high availability

9
When
testing for this white paper, the disks for the cluster witness and Distributed Transaction
Coordinator 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
put online
, initiali
ze,
or create a volume for
any disk until instructed to do so in the section Create the Failover Cluster
below.
T
he 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 infrastru
cture and DNS services suitable for
hosting the cluster are available.
Network
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 describe
d in this white paper, four
static IP addresses are required for the four virtual servers described below.
1.
Failover Cluster virtual server and access point
Function:
To act as the virtual server IP address and name for the Failover Cluster software.
Sugge
sted action:
Windows management tools use this address to get 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 a
ddress is
16.92.155.183
and the name is
CMS
-
C2
-
CLUSTER
.
2.
Systems Insight Manager
and Insight Software virtual server and access point
Function:
To act as the virtual server IP address and name for
Systems Insight Manager
and
Insight software. You specify t
his name and address to connect to
Systems Insight Manager
through your browser.
Suggested action:
All SNMP devices that report their events to
Systems Insight Manager
should
use this IP address and name for the location of the Event Consolidator, the SNMP Trap
Destination. The host defined for the WMI Mapper proxy should use this name and IP address
unless the WMI Mapper service runs on a system that is not a cluster m
ember and the WMI
Mapper is not installed as part of Insight Software. For the examples discussed in this white
paper, the IP address is
16.92.155.186
and the name is
CMS
-
C2
-
HPSIM
.
3.
Microsoft SQL Server 2008 virtual server and access point
Function:
To act
as the virtual server IP address and name for the Microsoft SQL Server 2008
Enterprise database software. This software is used to extract, manipulate, or back up the Insight
Software and
Systems Insight Manager
databases.
Suggested action:
The
Systems Ins
ight Manager
Open Database Connectivity (ODBC) data
source uses this virtual server IP address and name as the location where the CMS
Systems Insight
Manager
Data Source Name (DSN) points. In the examples discussed in this white paper, the IP
address is
16.92.155.185
and the name is
CMS
-
C2
-
SQLSVR
.
4.
Microsoft Distributed Transaction Coordinator virtual server and access point
Function:
To act as the virtual server IP address and name for the Microsoft Distributed
Transaction Coordinator service. This servic
e coordinates transactions that are distributed across
a cluster.