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

6
Table 4:
Insight Software 6.2 DMT type (32/64
-
bit) and database support matrix for
a Cluster CMS
Source CMS System
Target CMS System
Components
CMS OS
Type
Database
CMS OS
Type
Database
HP Systems Insight
Manager / HP
Insight Dynamics /
HP Insight Control
Virtual Connect
Enterprise
Manager
Windows
Server 2003
R2 Enterprise
32
-
bit OS
SQL Server 2005
Enterprise SP3
Windows Server 2008 2
Enterprise 64
-
bit OS
SQL Server 2008
Enterprise SP1
Note:
If the source CMS Insight Software version is earlier than 6.2,
you must
upgrade to 6.2 first and then perform data migration.
For more details about the Cluster CMS, see:

Installing and upgrading to HP Insight Software 6.2 o
n Windows Server 2003 R2 MSCS for high
availability

Installing and upgrading to HP Insight Software 6.2 on Windows Server 2008 R2 Failover Clusters
with SQL Serv
er 2008 for high availability

Deploying HP SIM 6.x on MSCS clusters on Windows 2003 with SQL Server 2005 SP3 White
Paper

Deploying HP SIM 6.x on MSCS clusters on Windows 2008 with SQL Server 2005 White Paper
Scenarios not supported

The source and target CMS and the database server with different log in credentials.

The source
CMS with Insight Software 3.x/6.0 installed and the target CMS with standalone
Systems Insight Manager installed.

The source CMS with standalone Systems Insight Manager and the target CMS with Insight Control
or Insight Dynamics 3.x/6.0 installed.

The sour
ce CMS as a 64
-
bit system and the target CMS as a 32
-
bit system.

A multi
-
named target CMS with a remote database where the database server cannot communicate
to all target CMS IP subnets.

The target CMS system is managed by the source CMS.

The source and t
arget systems are members of different Windows domains.

The target CMS and the remote SQL server are members of workgroups.

The target CMS is the same physical system as the source CMS when the target CMS is a cluster
CMS.