Migration process for TrueSight Operations Management and TrueSight Capacity Optimization to BMC Helix Operations Management and BMC Helix Capacity Optimization

1 - Analyze the environment and create an upgrade plan

1. Obtain and run the health check tool.

2. Analyze the environment.

   1. Identify the data that would be easier to recreate rather than migrate.
      Use the upgrade evaluation questionnaire to evaluate your environment.

   2. Identify the tasks that must be done before the migration.

   3. Evaluate SaaS versus on-premises deployment.

1. Create an upgrade plan based on your evaluation.
   The upgrade plan will contain information about the data that you want to migrate to BMC Helix Operations Management.

• Health check tool: TrueSight Operations Management Health Check Tool 

• Planning the upgrade: Upgrade evaluation questionnaire

• SaaS versus on-premises evaluation: Upgrading TrueSight Operations Management to BMC Helix Operations Management

2 - Deploy the product

Based on your evaluation, deploy the SaaS version of the product.

3 - Run migration tools

1. Migrate pconfig rules in TrueSight Operations Management to monitoring policies within TrueSight Operations Management. You can then migrate the policies to BMC Helix Operations Management.

2. Migrate policies in TrueSight Operations Management to BMC Helix Operations Management.

3. Manage the BMC Helix Operations Management environment.

4. Migrate PATROL Agents from TrueSight Operations Management to BMC Helix Operations Management.

5. Migrate event data from TrueSight Operations Management to BMC Helix Operations Management.

• Migrating pconfig rules

• Migrating monitoring policies

• Migrating and upgrading PATROL Agents

• Managing the BMC Helix Operations Management environment

• Migrating event data to BMC Helix Operations Management

4 - Validate in the QA or non-production environment

1. Validate the migrated data by performing the following tasks:

   1. Define the timelines and owners of each migration task.

   2. Keep the acceptance criteria and checklist ready.

   3. Depending on the experience of validation in the QA environment, change the migration plan.

2. Test the migrated data.

None

5 - Implement in the production environment

1. Launch BMC Helix Operations Management.

2. Go live with the product.

1 - Review key considerations

Review the key considerations to learn about the type of data that is migrated and the features that are discontinued in BMC Helix Continuous Optimization.

Key considerations for migration

2 - Analyze the environment and plan for migration

Analyze your source environment and plan for migration.

NA

3 - Prepare for the migration

Prepare your environment for migration:

1. Register for BMC Helix Continuous Optimization and activate the product.

2. Download the Remote ETL Engine from BMC Helix Continuous Optimization and generate the API keys and tenant ID that are required during the Remote Engine Installation. Install it on the TrueSight Capacity Optimization environment so that it can communicate with the Database server during the migration of the historical data.

3. Download the migration toolkit from BMC Helix Continuous Optimization and copy it to the host computer on which the TrueSight Capacity Optimization Application Server is installed. You need to generate API keys and the tenant ID that are required while you run the migration tool on the Application Server.

Preparing for migration

4 - Run the migration tool 

Run the migration tool to migrate data and monitor the progress and status of the migration. 

You can run the Migration tool by using the proxy server to create an additional layer of security. Setting up a proxy server is optional. 

Running the migration tool

5 - Validate data in BMC Helix Continuous Optimization

Validate data and perform post-migration tasks.

The data is migrated in two phases.
In phase 1, the migration tool extracts all configurations, such as the definition of entities, relationships, tags, analysis, models, external DB connections, entity catalogs, and ETL configurations, and migrates this data to BMC Helix Continuous Optimization. During the same phase, the tool also creates a set of data migrator ETLs in BMC Helix Continuous Optimization. Depending on the size of entities and configurations, this phase might take from a few minutes to a couple of hours to be completed. All ETL configurations with various data sources (for example, vSphere and AWS) in the source environment are reconfigured on Remote ETL Engines in BMC Helix Continuous Optimization. 

In phase 2, the Remote ETL Engine of  BMC Helix Continuous Optimization schedules a set of data migrator ETLs created in phase 1 to migrate the historical data from the source environment. During the first run of each migration ETL, all configuration metrics data, with the first batch of performance metrics data, is migrated. In subsequent runs of these ETLs, the remaining performance metrics data is migrated in batches. Depending on the size of the historical data, it might take from a few hours to a couple of days to completely migrate the historical data. 

Running the migration tool