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

Technical white paper | HP Insight Management 7.2
48
B. References section.
C. Use the backup tool of your choice to make a full backup of the cluster including the Insight Management, SQL
Server, cluster witness, and Distributed Transaction Coordinator shared disks. It is recommended to take a full
backup in case of failure. It is required to create a backup of the Insight Management and SQL Server shared disks
to complete the upgrade. For information on how to back up and restore the disks, see the white paper, Backing
up and Restoring HP Insight Management Central Management Server (Windows), that is specific to your pre-
upgrade release.
2. Install any prerequisites for the new software on both cluster nodes.
Review the Insight Management installation requirements listed in the HP Insight Management 7.2 Support
Matrix, especially the Requirements for non-OS software and Supported browsers; and also review the
HP
Insight Management 7.2 Preinstallation Worksheet. Make sure the components listed are installed on each
node. Verify the installation of these components on each node by running the HP Insight Management Advisor
and enabling the Pre-Install Items option from the HP Insight Management Installer menu.
Note:
If the Insight Advisor test sqlcheck produces the error Caught DBConnection exception: 1700 with Message: SQL server does
not exist or access denied, proceed. This error may be ignored.
Be sure to install any new prerequisite .NET software before continuing with the HP Insight Management installation.
Allowing the HP Insight Management Installer to install .NET software during the installation process will restart the
clustered services disrupting access to the shared disk resulting in an unsuccessful installation.
3. Upgrade the primary system.
A. Make sure the primary system is running and the secondary system is shut down.
B. Log into the primary system with the same administrator credentials that you configured for the Insight
Management service account credentials.
C. Use Failover Cluster Manager to take the Insight Management service offline. In this paper, the Insight
Management service is called cms-c16-matrix.
D. Use Failover Cluster Manager to bring only the Server Name and Disk Drives resources in the Insight Management
(cms-c16-matrix) service online on the primary system.
E. Use Failover Cluster Manager to verify that the SQL Server service is online on the primary system.
F. Run Administrative Tools Services. Start the following Insight Management services in the order listed, skipping
any service not found in your system. The services installed in your system depend on your Insight Management
release and your installed components:
i. Pegasus WMI Mapper
ii. HP Systems Insight Manager
iii. OpenSSH Server
iv. HP Version Control Repository Manager
v. HP Insight Control server migration Application Service
vi. HP Insight Control server migration Web Service
vii. HP Insight Control virtual machine management
viii. HP Application Discovery
ix. HP Global Workload Manager Central Management Server
x. HP Agentless Data Collector Service
xi. HP Agentless Collection for Linux Systems
xii. HP Capacity Advisor Data Service
xiii. HP Extensible Storage & Server Adapter