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

Technical white paper | HP Insight Management 7.3
8. Perform validation and final configuration steps.
Option 3: Installing a patch after installing a major Insight Management release
The main body of this whitepaper describes installing Insight Management in a cluster. It also discusses applying an
incremental update, if applicable, and any applicable Insight Management Software Patches after Insight Management
release install. The steps from the main body of the white paper are summarized as follows:
1. Create a two-node Failover Cluster with Microsoft Distributed Transaction Coordinator and Microsoft SQL Server
Enterprise installed.
2. Install Insight Management 7.3 on the primary system, with secondary node powered down to avoid unintentional
failover. Immediately afterwards, install the Insight Management 7.3 incremental update, if applicable, on the primary
system.
3. Install Insight Management 7.3 on the secondary system with primary node powered down. Immediately afterwards,
install the Insight Management 7.3 incremental update, if it was installed on the primary system.
4. Power on the primary system and wait for it to come up online.
5. Move the Insight Management resources over to the primary system. Wait for the HP SIM group resources to come
online.
6. Install the Insight Management Software Patches following the patch instructions on the primary system, if applicable.
7. After the patch installation is completed on the primary system, move the Insight Management resources over to the
secondary system. Wait for the HP SIM group resources to come online.
8. Install the Insight Management Software Patches on the secondary system if the Insight Management Software
patches have been installed on the primary system.
Note:
For patch updates requiring only a registry update on secondary system, follow the instructions as described in the patch.
9. Perform validation.
Appendix E: Migrating an Insight Management 7.3 Windows 2012 Cluster
or a 7.3 Windows 2012 Standalone Server to a Windows 2012 Cluster
This appendix provides an overview of the steps to migrate an Insight Management 7.3 Windows 2012 Cluster or a 7.3
Windows 2012 Standalone Server, called the Source system, to a new Windows 2012 cluster, called the Target system.
The source standalone server may be in a domain or in a workgroup. The target cluster will always be in a domain. It
contains references to documents with detailed migration steps.
See the section Migration support matrix for Cluster CMS in the Data Migration of an existing Microsoft Windows CMS to
a new Insight Management 7.3 system white paper to find out the supported migration configurations.
Migration overview
The following steps are a high level overview of the migration procedure for Insight Management running in a two-node
Failover Cluster. For exact migration steps, follow the Data Migration of an existing Microsoft Windows CMS to a new
Insight Management 7.3 system white paper.
Set up a separate target Windows Server 2012 cluster with the same patch level of Insight Management 7.3 installed on it
as is installed on the source. Then use the Insight Management migration tools to migrate Insight Management data from
the source Windows Server 2012 7.3 cluster or Standalone Server to the target Windows Server 2012 7.3 cluster in the
same domain.
The detailed migration steps include steps for migrating a cluster in the Data migration of an existing Microsoft Windows
CMS to a new Insight Management 7.3 system white paper. The steps are summarized as follows.
1. Follow the instructions in the main body of this document to create the new Windows 2012 cluster.
A. Install the new cluster in the same Windows domain as the source cluster or the source standalone (if standalone
server is setup in a domain). In 7.3, the Data Migration Tool also supports migration from a source Standalone
Server in a workgroup to a target Insight Management cluster with local SQL Server or with SQL Server installed on
another cluster in the same domain.
56