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

Product Name : HP Insight Recovery software

Product Version : 6.3

Status : Successful

----------------------------------------------------------

Product Name : HP Operations Orchestration software [HP Insight

Dynamics infrastructure orchestration]

Product Version : 6.3.0

Status : Successful

----------------------------------------------------------

Export is successful. The exported data file is C:/Program

Files/HP/Systems Insight Manager/data/configdata-export\Products.zip

C:\>

Importing the data to the target CMS

The import utility checks for installed software dependencies and imports the data in a predefined order. As

part of the import operation, some data from the export operation is replaced with data to match the target

system, such as the CMS name and IP address. This enables a migration to a new CMS with a different host

name and IP address. Other environmental changes might occur for the CMS, such as a local or remote

database. The initial installation of the Insight Software on the target CMS configures database connections

and any other local disks and /or file systems needed for the import operation.

After the import process completes, additional manual steps must be performed in order to ensure the

managed environment is consistent with the imported data on the target CMS.

If the new CMS has not been configured and Insight Software is not installed and started on the new CMS

system, perform the steps in the Configuring the target CMS for migration section before proceeding with the

following steps.

Note:

The import operation replaces the configuration data on the system where the

import is done.

Step 1: Ensuring the target CMS is prepared for an import operation

1. Review the “Before you begin”.

2. Ensure the steps in the Configuring the target CMS for migration section have been performed.

3. Ensure the steps in the Exporting the source CMS configuration data section have been performed.

Note:

The target CMS system must not be one of the managed systems on the source

CMS, and instead must be a new system. Deleting the target system from the

source CMS does not work if the target system was ever licensed for any product.

Note:

All the scheduled tasks running in the target CMS must be disabled before the

import operation. After successful import operation, re-enable all the scheduled

tasks in the target CMS.