Data migration of an existing MS Windows CMS to a new Insight Software 6.0 system

5
Before you begin
The data migration process
enables
the target CMS to be hosted on a new system in the infrastructure
or on the existi
ng system after an OS upgrade.
In either
instance
, critical OS
-
level information
must
be
configured on the target
C
MS.
HP recommends for 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
reduce
s
the total time the CMS is unavaila
ble for management operations.
Step 1: Choos
ing
the appropriate time for CMS migration
The migration
m
ight
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 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, so
let the export process proceed and give it plenty of time.
Step 2: Collect
ing
OS level user names and passwords from old CMS
The
same
OS user names and credentials defined for use by Insight Software on t
he 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.
Step
3
:
Sav
ing
any customer created scripts or executables
The migration utility
does not
export or import
non
-
HP cr
eated scripts or other executables.
These files
will need to be copied to the target CMS after the import operation has successfully completed.
C
opy the following data to a safe location
that will be accessible after the import on the target CMS
has been
completed.

C
ustom scripts, executables
,
or other
non HP Insight Software
files created on the source CMS
.
For instance
,
there might be a command
-
line tool that needs to be saved.
You will be instructed
to copy t
hese files to the same location on the targ
et CMS after the import
has completed
.

T
he
Install PSP
directory
—
this
directory is created during the
Initial PSP Install task and is
found under the Systems Insight Manager directory.
You will be instructed to copy this directory to
the System Insight Ma
nager directory on the target CMS after the import has completed.

O
ther configurations
on the source CMS that are necessary for the execution of script, for
instance,
a storage device
may
contain additional data or repositories
, if so the target CMS will
n
eed to be configured to use the same or similar storage device
.
Note:
The safe location is mentioned several times in this document. If the source
CMS is to be retained and not used as the target CMS,
then
the source
CMS itself can be the safe location. Th
ese files can then be copied later,
directly from the source CMS. If the target CMS is also the source CMS,
then locate some shared storage that can host the copies of the various
customer
-
specific files noted in this document.