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

Technical white paper | HP Insight Management 7.3
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:
– HP Insight Control server deployment and Insight Remote Support Advanced
– HP Vulnerability and Patch Management Pack
– 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 (or Microsoft Windows Server 2012 R2 Standard OS
or Microsoft Windows Server 2008 R2 Enterprise Edition SP1), including processor, memory, networking, and disk
space. See the section “Management servers in a high availability environment” 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:
– All system components (server, storage, HBA, MPIO, etc.) have been certified under the Windows Server Logo Program
for Windows Server 2012. See the following Microsoft website: http://www.windowsservercatalog.com/
– The fully configured solution must pass the Validate test in the Failover Cluster Manager.
Using a CMS cluster as part of a federated CMS environment
A federated CMS environment relates specifically to HP Matrix infrastructure orchestration. In a federated CMS environment
multiple CMS servers cooperatively share the responsibility for managing a larger number of resources than can be
managed by a single server. A federated CMS environment is comprised of one Primary CMS and up to four Secondary CMSs.
A CMS cluster may be part of a federated CMS environment as follows:
• The Primary CMS must be the first CMS cluster in a federated environment.
• After the Primary CMS is a cluster, any Secondary CMS may also be a cluster.
• Each clustered CMS resides in a different Windows cluster.
• There may be both standalone and clustered CMSs in a federation.
Table 1 lists the Insight Management components that are supported in a CMS cluster and are required, optional, or
prohibited when a CMS cluster is part of a federated environment.
Components supported in a highly available environment
Table 1. Insight Management components supported in a highly available environment
5