Migration process overview
BMC provides an out-of-the-box migration toolkit that helps you to migrate data from TrueSight Capacity Optimization to BMC Helix Continuous Optimization. Before starting the migration, you must understand the end-to-end process for migrating the data.
The following image provides an overview of the process:
The following table provides a sequence to migrate your data:
Task | Action | Role | Reference |
|---|---|---|---|
1 | 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. | Capacity Planner | |
2 | Assess your source environment and plan for migration. | BMC professional services | NA |
3 | Prepare your environment for migration:
| System administrator | |
4 | Run the migration tool to migrate data. Monitor the status of the migration and logs by using the Migrator system task in BMC Helix Continuous Optimization. Check if this task is completed successfully. 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. | System administrator | |
5 | Validate data and perform post migration tasks. The data is migrated in two phases. 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. | System administrator |
Example scenario
Apex Global is running TrueSight Capacity Optimization 20.02, which gives insights to optimize the use of their current IT resources and plan for future demands. Alan is an administrator for Apex Global and performs all administrative tasks, such as deploying the product components, integrating data sources, and managing system tasks.
The current deployment of TrueSight Capacity Optimization in Apex Global is:
Apex Global now wants to move to BMC Helix Continuous Optimization that is a cloud-based capacity management solution.
After assessing their current deployment, including product customizations and business requirements, Alan needs to do the following tasks to prepare the environment for migration:
- Register for BMC Helix Continuous Optimization and activate the product.
- Download the Remote ETL Engine from BMC Helix Continuous Optimization and install it in his on-premises environment so that it can communicate with the TrueSight Capacity Optimization Database server during migration of the time series data.
- Download the migration toolkit from BMC Helix Continuous Optimization and copy it on the host computer on which the TrueSight Capacity Optimization Application Server is installed.
For details on performing these tasks, see Preparing-for-migration.
After completing the premigration tasks, the deployment of Capacity Optimization is:
Alan now runs the migration tool to migrate the on-premises data to the cloud-based solution. For details, see Running-the-migration-tool.
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. Depending on the size of entities and configurations, this task might take from a few minutes to a couple of hours to be completed. After this task is completed successfully, Alan finds everything configured in BMC Helix Continuous Optimization, such as hierarchy, analysis, models, and ETL configurations with all data sources. However, the historical data is not migrated in this phase.
In phase 2, Helix Remote ETL Engine schedules a set of data migrator ETLs created in phase 1 to migrate the historical data from TrueSight Capacity Optimization. After this data migrator ETL task completes the first run, Alan can see all configuration data and performance data for the last 7 days, as these ETLs migrate data for 7 days at a time. If required, Alan can configure this duration for the data to be migrated in each batch in the Days to extract property in the data migrator ETL.
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. After this task is completed, Alan finds all configurations and historical data along with new time series data in BMC Helix Continuous Optimization.
