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

6
Requirements

The imp
ort operation can only be performed on a CMS with Insight Software version 6.1. When
performing the import operation, the Administrator must login using the same credentials that
were used to install Insight Software
v6
.1 on the target CMS.

The same OS us
er 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.
1
.

I
f Insight Dynamics is installed
, you must
e
nsure
that you have
at least 20
GB free space for the
export file on both the source and
target
CMS.
F
ile size
might
vary
,
depending on the number of
discovered system
s
and
on the Insight S
oftware products that are installed. The file can be much
smaller, 50MB, if just HP SIM
is installed with several hundred system
s
. If
you are using
a remote
database server,
you must have 20GB
(varies based on installed products)
space in the
temp
orary
directory
on the remote database
for the import operation.
Before you begin
The data migrat
ion 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 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 Software 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, in your environment, you have customized an application, workflow or
script to asynchronously issue
Insight Software requests, you must
temporarily disable this functionality to avoid generating Insight Software
requests during the HP Insight Software/ HP Systems Insight Manager
upgrade process.
Step 1: Choos
ing
the appropriate time for CMS migration
Th
e migration might take 2 to 8 hours, depending on the number of systems managed, the number of
Insight Software components being migrated, and whether a separate target CMS host is used. The
CMS is not available for management activities during this migrat
ion 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 requi
red. Limited feedback is sent to the command line interface, so
let the export process proceed and give it plenty of time.
Step 2: Collecting OS level user names and passwords from old CMS
The
same
OS user names and credentials defined for use by Insight
Software on the source CMS must
also be defined on the targe
t CMS. If domain accounts are used, ensure the target system has joined
the Windows domain.