Troubleshooting issues with the migration of min and max values of entities

When you migrate data from TrueSight Capacity Optimization to BMC Helix Continuous Optimization by using the migration toolkit provided in versions earlier than 23.3.02, the minimum (min) and maximum (max) values for metrics of the entities created in TrueSight Capacity Optimization are not imported to BMC Helix Continuous Optimization. This issue causes a data validation discrepancy between the TrueSight and Helix environments. Perform the troubleshooting steps provided in this topic to import the missing data to BMC Helix Continuous Optimization for effective and accurate visibility into capacity planning. 

Related topics

Running-the-migration-tool

Migrating-to-BMC-Helix-Continuous-Optimization

Scenario

Apex Global company is using TrueSight Capacity Optimization to manage the capacity of their infrastructure. They plan to move to the SaaS version of this product, BMC Helix Continuous Optimization. Alan is an administrator at Apex Global company. He performs the data migration by using the out-of-the-box migration toolkit provided by BMC Helix Continuous Optimization in versions earlier than 23.3.02. After the migration is complete, he observes that for the entities created in TrueSight Capacity Optimization, only average values are migrated to BMC Helix Continuous Optimization and minimum and maximum values are unavailable. The missing values cause a data validation discrepancy between TrueSight and Helix environments. 

He then performs the troubleshooting steps and re-runs the data migrator ETL in BMC Helix Continuous Optimization version 23.3.02. After the migration is complete, he can see min and max values in BMC Helix Continuous Optimization.

Issue symptoms

The imported entities show only the average (avg) values. The min and max values are missing.

Issue scope

This issue occurs after migrating data from TrueSight Capacity Optimization to BMC Helix Continuous Optimization.

Resolution

Perform the following steps. 

Important

To import the missing values for the selected entities, perform all steps. To import the missing values for all entities, skip steps 1 and 2. However, for a faster ETL run, we recommend that you perform all steps and re-run the ETL for selected entities instead of all entities. 

  1. Prepare a text file with a list of selected system types for which you want to import the missing min and max values.
    1. Log in to the host computer of the Remote ETL Engine that is running the data migrator ETL. 
    2. Create a text file and include a list of required system types:
      • Use the entity prefix for the system type. For example, sys:gm:vmw for Virtual Machine - VMware.
        You can also use regular expressions, for example, sys:gm:.*. or sys:.*.:vmw.
        For details on the system types, see System types.           
      • Add an entry for each system type on a separate line. Make sure that delimiters are not added between system types. 

  2. Modify the run configuration of the data migrator ETL to read this text file. 
    1. Log in to BMC Helix Continuous Optimization.
    2. Select Administration > ETL & System tasks > ETL tasks.
    3. On the ETL tasks page, click the name of the data migrator ETL.
    4. In the Run configurations table, click Edit this run configuration edit_simulation_icon.png.

      Migrator_ETL_run_config.png

    5. In the Run configuration tab, click the You can manually edit ETL properties from this page link. 
    6. In the Add new property field at the bottom of the page, type the name of the property as extract.filter.enttypes.file and click Add. 
    7. Locate the new property in the list of properties, type a path to a text file that contains a list of selected system types, and click Save.

      Migrator_ETL_prop.png

  3. Modify or delete the last counter value.
    1. On the data migrator ETL details page, click Lastcounter.
    2. In the Status details table, do one of the following actions:
      • Click Delete all lastcounters to delete all last counter values.
      • Click Edit Lastcounter to change the last counter value to the start date of the migration so that data from that week onwards will be migrated.
  4. Click Run active configuration to re-run the data migrator ETL.
    After this data migrator ETL task completes at least one run, you can see the reimported data for the last 7 days because this ETL migrates data for 7 days at a time.
  5. Verify the ETL run and imported data.
    1. To verify whether the ETL ran successfully:
      1. On the data migrator ETL details page, review the Run History table. 
      2. In the Last exit column, verify that the status is OK.
      3. In the # loaded entities column, verify that the entities are loaded in each run. 
    2. To verify that the minimum and maximum values are imported: 
      1. In the left pane of the Workspace tab, expand the relevant domain name and click the entity type for which you reimported the data: for example, Virtual Machine - VMware.   
      2. Click on the entity and select the Metrics tab. 
      3. For the required metric, run the Quick analysis. For details, see Using-the-Quick-analysis-tool. 
      4. Edit the analysis and click Advanced. 
      5. Expand the Statistics selection, select Statistics as MIN and MAX, and click Save. 
      6. Verify the minimum and maximum values on the chart. 


 

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