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

8
Step
5
: Creating space for new/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 products that are installed. T
he 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
on
the remote database server
for the import operation.
Configuring the t
arget 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 loss of
data, complete 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 the remote database is
extra
cted 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: Selecting new host name and IP address for a new system as the
target CMS
A new CMS requires a n
ew host name and IP address,
so
it
must
be
configure
d
in the OS.
Step 2: (Optional) Upgrading memory and firmware on the target CMS
system
Verify hardware requirements for Insight Software 6.1 at
http:
//www.hp.com/go/insightsoftware/docs
and ensure the new CMS is properly configured.
Step 3: Installing and pre
-
configuring the target CMS
1.
Install a supported version of Windows operating system on the target CMS which meets
Insight Software 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 the 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 location in the infrastructure.
3.
Using Windows utilities, join the Win
dows 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 database software is running a version supported by Insight Softw
are v6.
2
.