Installing and upgrading HP Insight Management 7.0 on Windows Server 2008 R2 Failover Clusters

• A client accesses the Insight Management CMS through its virtual server. Clients connect to

Systems Insight Manager, and thereby Insight Management, through Systems Insight Manager’s

client access point. Network traffic addressed to the virtual server is received by the Systems

Insight Manager service, wherever it is running in the cluster. Thus, a client has no need to know

on which system Systems Insight Manager is running.

• Likewise, Insight Management uses the client access point of the Microsoft SQL Server 2008 R2

virtual server to connect to a Microsoft SQL Server 2008 R2 database instance, because

Microsoft SQL Server 2008 R2 is installed as a clustered service.

• The databases used by the Insight Management reside in a Microsoft SQL Server 2008 R2

database instance. Other data files are stored on the Insight Management shared disk.

• Figure 1 shows the Failover Cluster with a virtual server for Insight Management and another for

clustered SQL Server 2008 R2. In this document, the preferred system for running Insight

Management is called the primary system. The system on which SQL Server 2008 R2 normally

runs is called the secondary system.

Figure 1: Relationships among HP SIM, Insight Management, SQL Server 2008 R2, and the cluster disks

Insight Management virtual server

HP SIM IP address: 16.92.155.186

SQL Server 2008 R2 virtual server

IP address: 16.92.155.185

Failover Cluster primary system

IP Address: 16.92.155.179

Failover Cluster secondary system

IP Address: 16.92.155.180

SQL Server instance files

Insight Management files

Local connection

Remote connection

S: on shared storage V: on shared storage

Failover Cluster virtual server

IP Address: 16.92.155.183

The cluster monitors the Insight Management and Microsoft SQL Server 2008 R2 clustered services. If

a clustered service fails, the cluster automatically presents its shared storage to the other system,

moves the virtual server, and restarts the failed service there.