Data migration of an existing Microsoft Windows CMS to a new Insight Software 6.3 system

• The source CMS with Insight Software 3.x/6.0 installed and the target CMS with standalone Systems
Insight Manager installed.
• The source CMS with standalone Systems Insight Manager and the target CMS with Insight Control or
Insight Dynamics 3.x/6.0 installed.
• The source CMS as a 64-bit system and the target CMS as a 32-bit system.
• The target CMS system is managed by the source CMS.
• The source and target systems are members of different Windows domains.
• The target CMS and the remote SQL server are members of workgroups.
• The target CMS is the same physical system as the source CMS when the target CMS is a cluster CMS.
• HP Insight Dynamics orchestration does not support migration of primary or secondary Federated CMS
when source and target CMS’s have different FQDN’s.
• Data migration is not supported, if Target Cluster CMS is configured with Remote Database.
• In 6.3, HP Insight Orchestration released federated CMS support. In 6.3 installations, the federated CMS
will be enabled by default. In HA environment, the federated CMS is not supported, thus, the migration
from a federated primary CMS to a cluster configuration is not supported in 6.3. HP Support can
assist in converting federated CMS to a non-federated CMS and thus enabling a migration to a cluster
configuration (non-federated to non-federated scenario). For further assistance, contact HP support for this
EA: PI 45268.
For more information on IO federated CMS, please refer the following link
http://www.hp.com/go/matrixoe/docs
Table 8: Insight Software components that do not support migration
HP Insight software component Notes
HP Insight Remote Support software
Remote support data must be re-configured on the target CMS. For
example, all systems requiring remote support must be re-imported.
HP Version Control Repository Manager
(VCRM)
Uses 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
Not supported by Insight Software 6.x
Requirements
• The import operation can only be performed on a CMS with Insight Software version 6.3. When performing
the import operation, the Administrator must login using the same credentials that were used to install
Insight Software v6.3 on the target CMS.
• The same OS user names and credentials defined for use by Insight Software on the source CMS must also
be defined on the target CMS.
• The target CMS must have a fresh installation of Insight Software 6.3.
• If Insight Dynamics is installed, you must ensure that you have at least 20GB 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 Software products that are installed. The file can be much smaller, 50MB, if just HP SIM
is installed with several hundred systems. If you are using a remote database server, you must have 20GB
(varies based on installed products) space in the temporary directory on the remote database for the import
operation.