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

20
Prerequisite steps are:
1.
The Insight Software and SQL cluster applications must
be running on the node where the import
utility will run. Ensure that the other node in the cluster is powered off before running the import
utility.
2.
Use Failover Cluster Manager to take the Insight Software cluster application offline. Then bring
only the
disk, file server, network name, and IP address resources in the Insight Software
application online.
Step 5: Running the import utility on the target CMS
The import utility is a command
-
line interface (CLI) tool that must be run from a standard command
p
rompt on a Windows operating system. The import utility must be executed by a user that has OS
-
level administrative privileges, and ideally be the same user who installed the Insight Software on the
target CMS. In addition, if Insight Dynamics Global Workl
oad Manager is installed, the same user
must also have SQL Server administrative rights to the database.
The import
CLI
command is
mximport [
-
f<filename>] [
-
p password]
Where the parameters are listed in the following:
-
f
—
O
ptional
.
C
an be used to specify a
different filename or path for the export archive. The default
file name is
Products.zip
and is placed in the
<SIM Install Path>
\
data
\
configdata
-
import
directory
on the source CMS.
-
p
—
O
ptional
.
Enables
the password to be passed in on the command line for
non
-
interactive
operations such as a script.
This must be the same password that was used to encrypt the exported
file.
If
–
p is not specified
,
the user
is
prompted to enter the password
. HP recommends not specifying
–
p on the command line for greater secu
rity
.
Parameters applicable only for Cluster CMS
–
v
—
Mandatory. Used to specify the Cluster IP also known as the
MSCS cluster virtual server IP
address
of target CMS.
–
n
—
Mandatory. Used to specify the Cluster Name/Host Name also known as the
Cluster name
is the
MSCS cluster virtual server name
of the target CMS. If Cluster Name/Host Name is not available then
pass Cluster IP.
Cluster CMS example
mximpo
rt
–
f
<File Name>
–
p <password>
–
v <Cluster
CMS
IP>
-
n <Cluster
CMS
Name>
For example,
mximport
–
f c:
\
export.zip
–
p somepassword
–
v {IP address}
–
n
hpcluster
Non
-
Cluster CMS example
mximport
–
f
<File Name>
–
p
<password>
For example
mximport
–
f c:
\
export.zip
–
p somepassword
In both examples
, the export archive file is read from the root directory of
the
C:
drive and is called
export.zip
. Since the password was provided, the user is not prompted for the password.
1.
Sign in to the source CMS with OS
-
level administrative privileges. Make sure this is the same user
who installed the Insight Software.