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

20
Step 2: Configuring remote database access for the import operation to the
target CMS
The following steps must be performed only if the target CMS is configured with a remote SQL server
database. This configuration enables the remote SQL server to have access to import the database information
that is embedded in the export file with the SQL server BCP tools. When the import operation is complete on
the target CMS, remove or disable this file sharing.
Note:
In case target CMS is cluster CMS with remote database, then export zip file
should be placed in custom folder (for example “c:\dmt”) on local drive of target
CMS server instead of configdata-import. For example, in local c: drive
create a folder “dmt” and place the export.zip in it  “c:\dmt\export.zip”. Set
permissions on “dmt” folder similar to configdata-import as mentioned in below
steps.
1. The source CMS, target CMS and the remote SQL server must be in the same Windows domain.
Migration is not supported if they are in workgroups.
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 for the user running the import tool. The share name must be the default,
configdata-import.
Note:
Accessibility of shared folder verification can be done as follow,
For example, if we have target system 15.1.1.20 and remote database system
15.1.1.40. Then “configdata-import” (or custom) directory on target system
should be shared and from remote database system 15.1.1.40 it should be
accessible. Basically “configdata-import” should be accessible when we type the
following URL is explorer \\5.1.1.20\configdata-import
” on remote database
system.
Note:
If you encounter issues during import, set permissions to full control for
Everyone.
3. The SQL service account must be configured to run as a domain user or administrator user that has
access to the configdata-import share named previously.
4. On the target CMS, set folder permissions on the <HPSIM installation
directory>\Systems Insight Manager\data\configdata-import to full control for
authenticatedUsers.
5. The temporary directory, C:\temp, must be present at the remote database server. This directory is
generally provided by the Windows operating system.
6. 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.
b. For SQL 2008, open Microsoft SQL Server Management Studio, select the database
instance used for install, then right click and select Facets. Select Surface area
Configuration from the pull-down box and set XPCmdShellEnabled to true.
Note:
You must disable xp_cmdshell and stop sharing once the import process is
complete.