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

12
Step 4: Creating space for new target CMS system
• Ensure at least 20GB 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 Software products that are installed. The file can be much smaller, 50MB, if only Systems Insight
Manager is installed with several hundred systems.
• If there is a remote database server, you must have 20GB space in the temporary directory on the remote
database server for the import operation.
Step 5: Upgrading to version 6.3 or installing migration software
If the target CMS has the Insight Control or the Insight Dynamics suite installed from the Insight Software
DVD version pre 6.3 installed, you must upgrade to Insight Software v6.3 prior to starting the migration
process.
• The Insight Software DVD 3.0 or 3.1 contains Insight Dynamics-VSE v4.1.x, which does not support a
direct migration to the Insight Software v6.3 setup, and therefore must be upgraded to v6.0 first and then to
v6.3. The version of Insight Dynamics that is installed on the source CMS can be verified through the
source CMS console HelpAbout menu.
• Upgrade the source CMS to Insight Software v6.3, making sure to include the Insight Dynamics version 6.3
suite. For detailed steps on how to upgrade from 3.x to 6.3, see the Insight Software Installation and
Configuration Guide or the Matrix Update Guide found at
• If you are migrating Insight Software from a Cluster CMS, follow the instructions in
http://www.hp.com/go/insightsoftware/docs .
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.
Note:
Operating system administrative privileges are required for the signed in user on
the source CMS.
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 Software 6.3 at http://www.hp.com/go/insightsoftware/docs and ensure
the new CMS is properly configured.