HP Insight Management 7.3 DMT White Paper

Technical White Paper | HP Insight Management 7.3
• The target CMS is the same physical system as the source CMS when the target CMS is a cluster CMS.
• Importing into the target CMS in a workgroup (for example, x) from the remote SQL server in the
workgroup (for example, y) is not supported.
Table 11. Insight Management components that do not support migration
HP Insight Management component Notes
HP Insight Remote Support software Remote support data must be reconfigured on the target
CMS. For example, all systems requiring remote support
must be re-imported.
HP Version Control Repository Manager
(VCRM)
This component uses a separate migration tool.
HP Insight Control server deployment
(RDP)
Manual steps required are listed in this white paper that
assist in migrating RDP jobs and scripts.
HP Insight Vulnerability and Patch
Manager software
This software is not supported by Insight Software 6.x.
Requirements
• The import operation can only be performed on a CMS with Insight Management version 7.3. When performing
the import operation, the Administrator must log in using the same credentials that were used to install Insight
Management v7.3 on the target CMS.
• The same OS user names and credentials defined for use by Insight Management on the source CMS must also
be defined on the target CMS.
• The target CMS must have a fresh installation of Insight Management 7.3.
• If Matrix OE is installed, you must ensure that you have at least 20 GB free space for the export file on both the
source and target CMS. File size might vary, depending on the number of discovered systems and on the Insight
Management products that are installed. The file can be much smaller, 50 MB, if just HP SIM is installed with
several hundred systems. If you are using a remote database server, you must have 20 GB space (varies based
on installed products) in the temporary directory on the remote database for the import operation.
Before you begin
The data migration process enables the target CMS to be hosted on a new system in the infrastructure or on the existing
system after an OS upgrade. In either instance, critical OS-level information must be configured on the target CMS. HP
recommends that the target CMS to be hosted on a different system. When hosting on a different system, the installation
and configuration of the OS and the installation of HP Insight Management on the target CMS must be completed before
exporting data or shutting down the source CMS. Completing these installation and configuration steps on the target CMS
system reduces the total time the CMS is unavailable for management operations.
Important:
If you have customized an application, workflow, or script that asynchronously issues Insight Management requests, then
you must temporarily disable this functionality to avoid generating Insight Management requests during the HP Insight
Management/ HP Systems Insight Manager upgrade process.
Step 1: Choosing the appropriate time for CMS migration
The migration might take 2 to 8 hours, depending on the number of systems managed, the number of Insight
Management components being migrated, and whether a separate target CMS host is used. The CMS is not available for
management activities during this migration process, and therefore the configuration of the managed environment must
remain unchanged during the migration process. HP recommends performing the migration at a time when changing the
configuration of the managed environment is not expected or required. Limited feedback is sent to the command-line
interface.
13