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

ManualsBrandsHP ManualsSoftwareHP Systems Insight Manager 4.x Linux Software

Note:

The i

mport

process will

clear

the

data on the

target

system

and database

before it actually imports

any

data into the

target

CMS

Note:

f the target CMS had been previously discovered by the source CMS that

record will be removed,

and the

original CMS record will remain intact

The original CMS record

will be renamed

to that of the target

and the IP

addresses will be updated

Figure 2:

Console output of

import tool operation

>mximport

: HPSIM Data Import Tool Launcher :

Lookup HPSIM InstallPath (x86)

HPSIM InstallPath: C:

rogram Files

Systems Insight Manager

Lookup succeeded

Data encryption password:

Is Database Remote (y/n) ? y

The following steps are needed to perform only if the target CMS is

configured with a remote SQL server database.

1. The source CMS, targe

t CMS, and the remote SQL server must be in the

same Windows domain.

2. The folder, configdata

import, under <HPSIM installation

directory>

Systems Insight Manager

data on the target CMS must be shared

with full permissions granted to the database server f

or the user running

the import tool. The share name must be the default, configdata

import

3. The SQL service account must be configured to run as a domain user or

administrator user that would have access to the configdata

import share

named above.

4. The

xp_cmdshell must be enabled on the remote database.

a. For SQL 2005, open SQL Surface Area Configuration, select the

Database instance used for the installation, select xp_cmdshell and click

the check box to enable.