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

White paper | HP Insight Management 7.2
8 | March 2013
Introduction
The HP Insight Management media set provides an installer to quickly and accurately deploy,
configure, integrate, and update HP Insight Management products. For more information about
the individual components delivered with HP Insight Management, visit
http://www.hp.com/go/insightmanagement/docs.
Summary of the Insight Management high availability
solution
These are the high-level characteristics and constraints of the high availability solution for an
Insight Management CMS. HP has tested the configuration as described and recommended.
• An Insight Management CMS cluster is built from specific Windows Server and SQL
Server components as detailed in the Software section. These components are a subset
of those supported for single-server CMS configurations.
• The SQL Server instance used by the CMS must run either in the same cluster with the
Insight Management CMS, or in a remote Windows cluster that is a member of the same
Windows domain as the CMS cluster.
• The following applications may not run in the CMS cluster:
o HP Insight Control server deployment and Insight Remote Support Advanced
o HP Vulnerability and Patch Management Pack
o HP Command View, HP Operations Orchestration, VMware vCenter, and similar
applications
• The CMS cluster is a two-node cluster that consists of two identical HP Proliant servers
(that is, physical servers, not virtual machines) and attached shared storage. HP
recommends SAN shared storage. HP recommends SAN boot for the two cluster nodes.
Each server must satisfy the hardware and recommended requirements for Insight
Management and the Microsoft Windows Server 2012 Standard OS, including processor,
memory, networking, and disk space. See the section “Management servers” in HP
Insight Management Support Matrix.
• Each server requires a minimum of two dedicated network adapter: one for a public
(client-facing) network and another for a private cluster network. Each server requires a
third dedicated adapter if iSCSI is used.
• An Active Directory domain infrastructure and DNS services suitable for hosting the
cluster are required, but they cannot run on either of the two cluster nodes.
• The CMS cluster is a single-site cluster.
• The CMS cluster is active-active. The Insight Management CMS and SQL Server may run
concurrently on different nodes of the cluster.
• The CMS cluster meets the requirements for Microsoft cluster support: