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

White paper | HP Insight Management 7.2
11 | March 2013
1
By using the Insight Installer’s Customize button, components from this table can be selected for
installation.
2
This component may require special configuration to run in a CMS cluster as described later in
this whitepaper.
3
An existing remote installation of HP Insight Control server deployment may be used, but neither
HP Insight Control server deployment, HP Insight Control server deployment SIM Integration
module, nor HP Insight Control server deployment Quiesce SIM Plugin may be installed in a cluster.
See the HP Insight Management 7.2 Installation and Configuration Guide for details on how to
reuse an existing installation of HP Insight Control server deployment.
4
HP Matrix infrastructure chargeback and HP Matrix infrastructure bursting connecter (optional)
services are also installed when HP Matrix infrastructure orchestration is selected.
5
HP Matrix recovery management is supported on the Primary and the Remote Site is managed
only by the Primary CMS in a Federated CMS configuration.
Note:
No components other than those described in this white paper are supported in a CMS cluster.
Specifically, the following are not supported: HP Operations Orchestration, HP Vulnerability and
Patch Management Pack, HP Command View, VMware vCenter, and VMware vSphere.
Description of the Insight Management high availability
solution
Insight Management components run on HP ProLiant servers in a Microsoft Windows Server
environment using Microsoft SQL Server. HP requires the use of physical servers (not virtual
machines) to set up a Failover Cluster environment for the CMS. Installing Insight Management as
a clustered service increases its availability. The cluster monitors the resources that comprise the
clustered service. When a failure is detected the cluster can restart an individual resource or move
the entire service to another system (node). The cluster allows an administrator to vacate all the
clustered services from the system so, for example, it can be shut down for maintenance.
Additionally, more efficient use can be made of compute capacity when the Microsoft SQL Server
and the Insight Management clustered services are placed on different systems.
This white paper describes the steps to install Insight Management on a Microsoft Windows Server
2012 Standard Failover Cluster with Microsoft SQL Server 2012. See the HP Insight Management
Support Matrix for details on the hardware and software installation requirements for Insight
Management. This and other Insight Management documents can be found at
http://www.hp.com/go/insightmanagement/docs.
The relationship between the Microsoft SQL Server instance and Insight Management is shown in
Figure 1.
• A Failover Cluster defines virtual servers. A virtual server has a unique static client-facing
network name and IP address that is registered with the DNS. This unique name and IP
address is called a client access point. The virtual server associates the client access
point with a group of resources, for example Windows services that, at any time, run on
only one of the cluster’s systems. The group of resources is called a clustered service.
• A client accesses the Insight Management CMS through its virtual server. Network traffic
addressed to the virtual server is received by the Insight Management CMS wherever it is
running in the cluster. A client never needs to know on which physical system it is
running.