HP Insight Management 7.3 DMT White Paper

Introduction
The Insight Management data migration tools (DMT) provide an easy mechanism to migrate an existing Insight
Management central management server (CMS) from one system environment to another. These tools are designed to
relocate a CMS to a new hosted environment when there is a need to change the underlying hardware or operating
system of the CMS without losing any of the customized data located on the CMS. The data migrated to the target CMS
environment include the configuration information such as system credentials, tasks, collections, licenses, and addresses
for supplemental management servers; plus management database information, which includes discovered systems,
performance data, and profiles.
Migration involves export and import operations. First, the export operation runs on the source CMS, which generates a
large compressed zip file containing configuration data from the existing CMS database. Then, the import operation
decompresses this data and imports it on the new, or target, CMS. The target CMS can be hosted either on a new system
in the infrastructure or on the same system.
From 6.2 releases, data migration supports the Highly Available MSCS Cluster CMS. Steps for Non-Cluster CMS and
Cluster CMS are documented in the same white paper. By default all the steps in the document are applicable for both,
unless explicitly mentioned as Non-Cluster CMS or Cluster CMS.
Note: No additional parameters are required for exporting a Cluster CMS, but two additional parameters are required for
importing.
Note: HP recommends that a separate server be used for the target CMS. However, you can use the same server as the
source and target CMS when new hardware is not available; the target CMS must not be a Cluster CMS, and the OS needs
to be reinstalled from a 32-bit version to a 64-bit version. You must have a unique hostname and IP for the target CMS if
it is a cluster.
The migration utility does not copy any program executable or OS-level configurations. For example, an OS username
and password are not copied by the migration utility. Therefore, Insight Management 7.3 must be installed on the target
CMS before performing the import. Any existing Insight Management configuration data on the target CMS is overwritten
with source CMS information when the data is imported.
Scenarios where the migration utility applies when moving from an older SQL server version or Windows Server version
to a newer version include:
• Moving from a 32-bit OS installation to a 64-bit OS installation on a new hardware system
• Moving from an older 64-bit system to a newer and faster 64-bit system
• Moving from a 32-bit OS installation to a 64-bit OS installation on the same hardware system
Migration support matrix
Table 1. Insight Management 7.3 DMT support matrix
Supported
Versions
<Source CMS
Version>

<Target CMS
version>
HP Systems Insight
Manager
HP Insight Control HP Matrix OE HP Virtual Connect
Enterprise Manager
5.3.1  7.3 Not Supported Not Supported Not Supported Not Supported
6.0  7.3 Not Supported Not Supported Not Supported Not Supported
6.1  7.3 Not Supported Not Supported Not Supported Not Supported
6.2  7.3 Not Supported Not Supported Not Supported Not Supported
6.3  7.3 Supported Not Supported Not Supported Supported
7.0  7.3 Supported Not Supported Not Supported Supported
7.1  7.3 Supported Not Supported Not Supported Supported
7.2  7.3 Supported Not Supported Not Supported Supported
7.3  7.3 Supported Supported Supported Supported
4