Data migration of an existing Microsoft Windows CMS to a new Insight Management 7.0 system

16
Configuring the target CMS for migration
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 uses a remote database, then the data from the 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.
IMPORTANT:
If the target CMS is to be the same physical system as the source CMS, you
must complete the export process on the CMS before installing and
configuring the target CMS.
Note:
The target CMS cannot be the same physical system as the source CMS
when the target CMS is a cluster CMS.
Step 1: (Optional) Upgrading memory and firmware on the target CMS system
Verify hardware requirements for Insight Management 7.0 at
http://www.hp.com/go/insightmanagement/docs and ensure the new CMS is properly configured.
Step 2: Installing and pre-configuring the target CMS
1. Install a supported version of the Windows operating system that meets Insight Management
requirements on the target CMS.
The target system must not have the 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. For more details, see the notes
for the Migration support matrix.
The target CMS must either be on the same LAN as the source CMS, or it must have access to all
of 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 the new host to the
network at the desired location in the infrastructure. You can also reuse the source CMS host name
and IP address for the target CMS. Before reusing the source CMS hostname and IP address,
remove the source CMS from the network to avoid conflicts.
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 Management on the source CMS.
4. Ensure the database software is running a version supported by Insight Management v7.0.
Step 3: Installing Insight Management version 7.0 on the target CMS
• Only the installation of Insight Management is needed, no additional discovery.
• If the same remote database server is to be used, either a new instance must be configured or the
old database must be dropped for Insight Management to install.