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

6
Step 4: Creat
ing
space for n
ew/target CMS system

Ensure at least
2
0GB free disk space exists for the export file on both the source and
target
CMS if Insight Dynamics is installed.
The
file size
might
vary
,
depending on the number of
discovered systems and on the Insight
S
oftware pro
ducts that are installed. The file can be much
smaller, 50MB, if just HP SIM is installed with several hundred system
s
.

If there is a remote database server,
you must have
2
0GB space in the temp
orary
directory
o
n
the remote database server
for the import o
peration.
Configuring the target CMS for migration
If the target CMS is to be the same physical system as the source CMS,
you will need to complete the
export process on the CMS before installing and configuring the target CMS. To avoid a los
s
of
data, co
mplete the steps defined in the
Exporting the source CMS
configuration data
section before
proceeding with
the setup process for the target CMS
.
If the source CMS system uses a remote database,
then
the data from t
he remote database
is
extracted as part of the export
process.
After
the export
operation
has completed, the remote
database can then be reconfigured for use with the target CMS
.
Step 1:
S
elect
ing
new host name and IP address
for a new system as the
target
CMS
A
new CMS installed on a new Windows system requires a new host name and IP address, so
you
must
configure this in the OS.
Step 2:
(Optional) U
pgrad
ing
memory
and firmware on the target CMS
system
Verify hardware requirements for Insight Software 6.0
at
http://www.hp.com/go/insightsoftware/docs
and ensure the new CMS is properly configured.
Step 3: Install
ing
and pre
-
configur
ing
the target CMS
1.
Install a supported version of Windows operating sys
tem on the
target CMS which meets
Insight S
oftware requirements
.
–
The target system must not have
its UTC system time set
earlier than the source.
For example,
ensure the system time is synchronized for the source and
target
CMS
.
–
The target CMS OS must be t
he same
locale
as the source CMS
.
–
The target CMS must either be on the same LAN as the source CMS
,
or it must have access to all
the managed systems reachable by the source CMS
.
–
The target CMS must have the same DNS configuration settings as the source CMS
.
At a
minimum, the target CMS must be able to resolve the same set of
forward and reverse DNS
lookups
supported by the source CMS
.
2.
Configure the target CMS with a new host name and IP address, and
then
add this new host
to the network at the desired locat
ion in the infrastructure
.
3.
Using Windows utilities, join the Windows domain and configure the set of OS usernames
and passwords on the target CMS
,
which include all usernames and passwords
defined for use
by Insight Software on the
source
CMS.
4.
Ensure the d
atabase software is running a version supported by Insight Software v6.0.