×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
BMC TrueSight Operations Management 11.0 ... Upgrading Upgrading the Infrastructure Management components

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:

Related topics

Upgrading the Infrastructure Management components

Migrating the configuration of Infrastructure Management cells

Troubleshooting an Infrastructure Management upgrade

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

    Summary of steps for migrating data with the migration utility

    Task Resource
    Install Remedy Single Sign-On Installing Remedy SSO

    Install TrueSight Presentation Server

    		 Installing the Presentation Server

    Upgrade the ProactiveNet or TrueSight Infrastructure Management server

    Note: In a multiple-server deployment, you need to upgrade the child server before upgrading the central server.

    		 Upgrading the Infrastructure Management Server

    Manually register TrueSight TrueSight Infrastructure Management with TrueSight Presentation Server

    		 Adding and editing components Open link

    Import the repository

    		 Importing the repository files
    Run the migration utility Migrating data by using the migration utility
    Upgrade the Integration Service and remote cells Upgrading the Integration Service


    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

    Summary of steps for migrating data with the upgrade installer

    Task Resource
    Install Remedy Single Sign-On Installing Remedy SSO 

    Install TrueSight Presentation Server

    		 Installing the Presentation Server 
    Import the repository Importing the repository files 

    Upgrade the ProactiveNet or TrueSight Infrastructure Management server

    Note: In a multiple-server deployment, you need to upgrade the child server before upgrading the central server.

    		 Upgrading the Infrastructure Management Server 
    Upgrade the Integration Service and remote cells Upgrading the Integration Service


    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.

    Type of dataMigration destination

    Policies and thresholds

    Monitoring policies, blackout policies, staging policies, time frames, Integration Service clusters, and global thresholds

    TrueSight Presentation Server

    User management data

    Users and user groups 

    		Remedy Single Sign-On

    Roles and objects, which includes views, monitors, groups, CIs, components folders, event folders, and reports 

    Note: Service Level Objects (SLOs) are not migrated.

    TrueSight Presentation Server

    Files
    Installation packages (also known as deployable packages)

    TrueSight Presentation Server

    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:

      PlatformDirectory 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.

    ParameterDescription

    -presentation_host

    Host name of the TrueSight Presentation Server.

    -presentation_port

    Port corresponding to the TrueSight Presentation Server host name.

    -presentation_username

    User name (with super admin role) that must be used for accessing the TrueSight Presentation Server.

    -presentation_passwd

    Password corresponding to the user name used for accessing the TrueSight Presentation Server.

    -presentation_protocol

    Optional, default HTTPS

    Protocol to be used while connecting with the TrueSight Presentation Server.

    The default value is HTTPS.

    -d

    Full path to the directory (including the directory name) that contains the exported policies to be imported into the TrueSight Presentation Server.

    Typically, the <ProactiveNet-Installation-Directory>/pw/pronto/lib/Datamigrator/exported_policies directory is expected to contain the policies.

    -sso_hostHost name of Remedy Single Sign-On.
    -sso_portPort corresponding to the Remedy Single Sign-On host name.
    -sso_userUser name (with administrator privileges) that must be used for accessing Remedy Single Sign-On.
    -sso_passwdPassword corresponding to the user name used for accessing Remedy Single Sign-On.

    -sso_tenant

    Optional, default *

    Tenant under which data must be migrated.

    This tenant (created in Remedy Single Sign-On) is used for accessing TrueSight Presentation Server. In other words, this tenant is that with which TrueSight Infrastructure Managementis registered with TrueSight Presentation Server.

    Note: The default value is *. If you are using the default tenant (*), do not provide this parameter.

    -sso_protocol

    Optional, default HTTPS

    Protocol to be used while connecting with Remedy Single Sign-On.

    The default value is HTTPS.

    Note: Specifying this parameter is necessary only while migrating user management data by running the export_users migration option.

    -file_list_xml

    Path to the file containing information about the files that need to be migrated.

    By default, the value is <ProactiveNet-Installation-Directory>pw\pronto\lib\DataMigrator\conf\files_to_export.xml. 


    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.

    Was this page helpful? Yes No Submitting... Thank you
    Last modified by Mukta Kirloskar on Jan 10, 2018
    task proactivenet infrastructure_management migration migration_utility upgrading

    Comments

    Log in or register to comment.

    Performing the post-upgrade steps after upgrading from ProactiveNet or Infrastructure Management
    Upgrading the Infrastructure Management components in high availability cluster mode
    © Copyright 2015-2018 BMC Software, Inc. © Copyright 2013-2018 BladeLogic, Inc.
    Legal notices

    Powered by Atlassian Confluence and Scroll Viewport

    © Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.