Migrating data from ProactiveNet or Infrastructure Management


In the process of upgrading from ProactiveNet or TrueSight Infrastructure Management 9.6.00.002 to TrueSight Infrastructure Management 11.0, you need to migrate data (or move data) from ProactiveNet or TrueSight Infrastructure Management to TrueSight Presentation Server. 

Migration can be done in one of the following ways:

  • During the upgrade (by using the upgrade installer) 
  • Post upgrade (by running the command-driven migration utility).
Best practice

If you plan to migrate a large volume of data, it is recommended that you perform the migration post upgrade by using the migration utility. Doing so can help reduce the downtime required for completing the migration.

Note

Migrating data post upgrade requires you to manually register TrueSight Infrastructure Management with TrueSight Presentation Server.

The following information can help you understand the concept, methods, and process of migrating data to the TrueSight Presentation Server:

Migration process

The following tabs provide a high-level overview of the migration process for each of the migration methods.


The following diagram provides a high-level overview of the migration process when you want to migrate data post upgrade (by using the migration utility).

migration workflow using migration utility.png

Summary of steps for migrating data with the migration utility


The following diagram provides a high-level overview of the migration process when you want to migrate data during the upgrade (by using the upgrade installer).

migration workflow.png

Summary of steps for migrating data with the upgrade installer


Types of data moved during migration

During migration the following types of data are moved from ProactiveNet or TrueSight Infrastructure Management to TrueSight Presentation Server and Remedy Single Sign-On.

Remedy Single Sign-On is used as an authentication and user management mechanism for TrueSight Presentation Server. Therefore, the user management data is migrated to Remedy Single Sign-On.

Note

Post migration, users are created in Remedy Single Sign-On with randomized passwords.

As an admin, you need to log on to Remedy Single Sign-On to set a temporary password for all the migrated users and then ask the respective users to reset the temporary password.

Migration sequence

It is recommended that you migrate user management data before migrating policies. 

You do not require to follow a sequence for migrating files.

Migration requirements


Before you migrate data, ensure that the following requirements are met:

  • Remedy Single Sign-On is up and running.
  • TrueSight Presentation Server is up and running and integrated with Remedy Single Sign-On.
  • You have administrator privileges for accessing TrueSight Presentation Server and Remedy Single Sign-On.
  • The Central Monitoring Administration repository is the same for both ProactiveNet or TrueSight Infrastructure Management 9.6.00.002 and TrueSight Presentation Server 11.0. 

Migrating data by using the migration utility

The following sections provide information about running the migration utility post-upgrade.

Running the migration commands

  1. Navigate to the following location:

    Platform

    Directory location

    Windows

    <InstallationDirectory>\pw\pronto\lib\Datamigrator\

    Linux

    <InstallationDirectory>/pw/pronto/lib/Datamigrator/

  2. Depending on the type of data that you want to migrate, run the following commands:

    • To migrate policies and thresholds, run one of the following commands:

      Command syntax for Windows

      migration.bat export_policies -d <directoryName> -presentation_host <presentationHostName> -presentation_port <presentationPort> -presentation_username <adminUserName> -presentation_passwd <adminPassword> -presentation_protocol <presentationProtocol> -sso_tenant <tenantName>

      Command syntax for Linux

      ./migration.sh export_policies -d <directoryName> -presentation_host <presentationHostName> -presentation_port <presentationPort> -presentation_username <adminUserName> -presentation_passwd <adminPassword> -presentation_protocol <presentationProtocol> -sso_tenant <tenantName>
    • To migrate user management data, run one of the following commands:

      Note

      During the migration, authorization profiles are created in Remedy Single Sign-On, with the same name and permissions as the user groups.

      Command syntax for Windows

      migration.bat export_users -sso_host <ssoHostName> -sso_port <ssoPort> -sso_user <adminUserName> -sso_passwd <ssoPassword> -sso_tenant <tenantName> -sso_protocol <ssoProtocol> -presentation_host <presentationHostName> -presentation_port <presentationPort> -presentation_username <adminUserName> -presentation_passwd <adminPassword> -presentation_protocol <presentationProtocol>

      Command syntax for Linux

      ./migration.sh export_users -sso_host <ssoHostName> -sso_port <ssoPort> -sso_user <adminUserName> -sso_passwd <ssoPassword> -sso_tenant <tenantName> -sso_protocol <ssoProtocol> -presentation_host <presentationHostName> -presentation_port <presentationPort> -presentation_username <adminUserName> -presentation_passwd <adminPassword> -presentation_protocol <presentationProtocol>

    • To migrate files, run one of the following commands:

      Command syntax for Windows

      migration.bat export_files -file_list_xml <filePath.xml> -presentation_host <presentationHostName> -presentation_port <presentationPort> -presentation_username <adminUserName> -presentation_passwd <adminPassword> -presentation_protocol <presentationProtocol> -sso_tenant <tenantName>

      Command syntax for Linux

      ./migration.bat export_files -file_list_xml <filePath.xml> -presentation_host <presentationHostName> -presentation_port <presentationPort> -presentation_username <adminUserName> -presentation_passwd <adminPassword> -presentation_protocol <presentationProtocol> -sso_tenant <tenantName>

    For more information about the parameters used in the preceding commands, see Parameter definitions.

 

Parameter definitions

The following table lists the parameters used while running the migration commands.

 

Importing the repository files

You need to ensure that the repository used with ProactiveNet or TrueSight Infrastructure Management 9.6.00.002 is also used with TrueSight Presentation Server 11.0.

To do this, proceed in one of the following ways:

  • If you have only the base or extended repositories and do not have any custom KMs or monitoring solutions, import the repository via the TrueSight console. You need to import the repository zipped file used with ProractiveNet 9.6.00.002. As an alternative, you can download the repository files from the EPD site
    For more information, see Importing the Infrastructure Management repository.
  • If you have custom KMs or monitoring solutions that you want to migrate to the TrueSight Presentation Server, manually copy the repository files used with ProractiveNet (or TrueSight Infrastructure Management) 9.6.00.002 to the following target location and then restart the TrueSight Presentation Server.

    Target location: <Presentation-Server-installation-directory>\TrueSightPServer\truesightpserver\modules\cma\pproxy>

    Usually, the source location can be <Infrastructure-Management-installation-directory>\pw\pproxy.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*