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

Step 2: Installing and pre-configuring the target CMS
1. Install a supported version of Windows operating system that meets Insight Software 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 refer notes at
“
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. The user can also reuse the source CMS’s host
name and IP address for target CMS. Before reusing the source CMS’s 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 operating system user
names 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 Software v6.3.
Step 3: Installing Insight Software version 6.3 on the target CMS
• Only the installation of Insight Software 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 Software to install.
Follow the instructions in the Insight Software Installation and Configuration Guide, Chapter 2, to install
the same software products that exist on the source CMS. The configuration guide can be found at
http://www.hp.com/go/insightsoftware/docs.
• The post-installation configuration of the target CMS listed in Chapter 3 of the configuration guide do not
have to be performed.
• If you are migrating Insight Software from a Cluster CMS, follow the instructions in
Installing and
upgrading to HP Insight Software 6.3 on Windows Server 2008 R2 MSCS for high availability to upgrade
the source cluster to Insight Software version 6.3. The new cluster must be installed as a different cluster in
the same Windows domain as the old cluster. The steps under Complete and validate the installation do not
have to be performed.
Step 4: Launching the console on the target CMS
Log in to the Systems Insight Manager GUI and verify the expected software is installed through
HelpAbout. No additional configuration of the CMS is necessary.
Exporting the source CMS configuration data
Before the export operation can be performed, you must perform several steps to prepare the source CMS,
such as quiescing the Insight Software. If the target CMS and the source CMS are on different servers, to
reduce downtime, Insight Software must be installed on the target CMS prior to exporting the source CMS
configuration data. For additional details, see Before you begin and Configuring the target CMS for migration
in this white paper.
The export operation compresses and encrypts all configuration data related to Insight Software into a single
zip file.
IMPORTANT:
Changes must not be made to the managed environment after an export operation
has been completed. If changes must be made prior to importing, another export
must be run. Insight Software attempts to resynchronize to the environment when
possible.