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

10
Suggested action:
Microsoft Distributed Transaction Coordinator is installed with Microsoft SQL
Server 2008. In the examples discussed in this white paper, the IP address is
16.92.155.184
an
d the name is
CMS
-
C2
-
DTC
.
Another two static IP addresses and names are needed for the primary and secondary systems.
5.
Failover Cluster primary system IP address and name
Function:
To serve as the TCP/IP address and name of the specific Microsoft Windows se
rver
host.
Suggested action:
Any software that references system
-
specific functions uses this address to
connect to this system. In the examples discussed in this white paper, the IP address is
16.92.155.179
and the name is
CMS
-
C2
-
N1
.
6.
Failover Cluster sec
ondary system IP address and name
Function:
To serve as the TCP/IP address and name of the specific Microsoft Windows server
host.
Suggested action:
Any software that references system
-
specific functions uses this address to
connect to this system. For the
examples discussed in this white paper, the IP address is
16.92.155.180
and the name is
CMS
-
C2
-
N2
.
The
16.
network referenced above is the public network used by clients to access cluster services.
Failover Clustering also requires that a private network b
e implemented for exchanging the cluster
heartbeat. The Failover Cluster primary and secondary systems will also have static IP addresses on
the private network. In this white paper, the
10.
network is used as the private network.
If you are implementing s
hared storage with an iSCSI SAN, in addition to the above network
resources you will
need
an additional dedicated network adaptor on each
cluster
system
and
,
possibly
IP addresses for the target.
The target is the storage controller to which the cluster sy
stems
c
onnect to access SAN resources.
Cluster configuration
Figure 1
demonstrates how to configure a cluster for enhanced performance once all components are
installed. In this active
-
active configuration, load is distributed by r
unning Insight Software and SQL
Server on different systems.
The purpose of the primary system is to run the
Systems Insight Manager
service and other Insight
Software components.
The purpose of the secondary system is to run the Microsoft SQL Server 2008
processes and to
handle remote Microsoft SQL Server commands.
Set up the failover environment
This section covers setting up the cluster environment in preparation for installing SQL Server 2008
and Insight Software. At this time Windows 2008 R2
Enterprise should be installed on the primary
and secondary systems, the public and private networks should be configured on each, the systems
should be members of the domain which is to host the cluster, and all other network and storage
resources describ
ed above should have been provisioned and are available.
Administrator credentials used by this white paper
R
eview the credential requirements for the person who creates the cluster and configures cluster
services. Refer to
Failover Cluster Step
-
by
-
Step Gu
ide: Configuring Accounts in Active Directory
at