Accuracy levels of Migration Simulation

The following table explains the accuracy levels that are associated with the resizing recommendations for the proposed or target instances in the Migration Simulation results page. You can use the information in the Probable reason and Probable resolution columns to understand the cause of the levels and the actions that you can take to improve them.

About the accuracy levels

If you have selected Utilization-based migration strategy, each proposed target instance in the migration simulation results page displays an Accuracy icon that indicates the accuracy or reliability of the proposed configuration. For more information about the Utilization-based strategy, see Strategies for migration simulation.

The Accuracy icon can have one of the following values:

Icon - Accuracy level

- Very Low

- Low

- Medium

- High

- Very High

Icon/ Accuracy level	UI message	Probable reason	Probable resolution
- Very Low	At least one mandatory configuration metric is not available. Simulation is performed based on the other available configuration metrics.	One or more required configuration metrics of the source server are not available. In most cases, the storage related metric is unavailable.	In Workspace, navigate to the source server and in the Metrics tab, verify whether the configuration metrics are available. If the configuration metrics are not available, verify whether the ETL modules are correctly configured to import them. For more information about the ETL modules, see the corresponding section in Collecting data.
- Low	Although utilization-based strategy was selected, simulation is based on lift-and-shift strategy because at least one mandatory utilization metric is not available.	One or more utilization metrics of the source server are not available. Only configuration metrics are available.	In Workspace, navigate to the source server and in the Metrics tab, check whether utilization metrics are available. If the metrics are not available, check whether the ETL modules are correctly configured to import them. For more information about the ETL modules, see the corresponding section in Collecting data.
- Medium	Although balanced behavior was selected, simulation is based on aggressive behavior because detailed statistics for hourly data samples are not available for the server.	The CPU_UTILMHZ_HM metric is missing. Utilization metrics of the source server are collected at hourly granularity. About CPU_UTILMHZ_HM metric The CPU_UTILMHZ_HM metric is the CPU utilization value (expressed in MHZ) that is calculated by using granular samples that the Continuous Optimization Agent collects. For balanced behavior, the 90^th percentile value of CPU utilization is considered. For conservative behavior, the 95^th percentile value of CPU utilization is considered.	For VMware vSphere: Use the VMware - vCenter E xtractor Service ETL module to import data. For other supported cloud providers and technologies: Install the Continuous Optimization Agent on the source server for data collection and use the BMC - TrueSight Capacity Optimization Gateway VIS files parser to import data.
- Medium	Although conservative behavior was selected, simulation is based on aggressive behavior because detailed statistics for hourly data samples are not available for the server.
- Medium	Simulation is not considering CPU benchmark because it is not available.	The estimated CPU benchmark (SPECint_rate2006) value is not available for the source VM.	In Workspace, navigate to the source server and in the Reference Benchmark section of the Summary tab, verify whether the benchmark details are displayed or not. If not, verify the status of the last run of the BenchmarkAlignment system task. To do so, in Administration, click ETL and System tasks > System tasks, and review the status of the BenchmarkAlignment task. If the BenchmarkAlignment task status shows a Warning or Error message: Check whether any of the following configuration metrics are missing for the source server: `CPU_MHZ` `CPU_NUM` OR `CPU_MAX_PROCESSORS` `(CPU_VENDOR` & `CPU_MODEL)` OR (`HW_MODEL` & `HW_VENDOR)` `(OS_FAMILY` OR `OS_TYPE)¹` `^{1 - Optional metrics. Used if available.}` Add the missing metrics and run the BenchmarkAlignment task again. Go to Step 1. If the required benchmark is still not available, update the benchmark catalog. For more information, see Updating benchmark data.
- High	Although balanced behavior was selected, simulation is based on 15 minutes detail samples. Detailed statistics for hourly data samples are not available for the server.	The CPU_UTILMHZ_HM metric is missing. Utilization metrics of the source server are collected at 15-minutes granularity. Information: The accuracy level is High as compared to the earlier scenarios because the 15-minute data samples are available as compared to hourly granularity. About CPU_UTILMHZ_HM metric The CPU_UTILMHZ_HM metric is the CPU utilization value (expressed in MHZ) that is calculated by using granular samples that the Continuous Optimization Agent collects. For balanced behavior, the 90^th percentile value of CPU utilization is considered. For conservative behavior, the 95^th percentile value of CPU utilization is considered.	For VMware vSphere: Use the VMware - vCenter E xtractor Service ETL module to import data. For other supported cloud providers and technologies: Install the Continuous Optimization Agent on the source server for data collection and use the BMC - TrueSight Capacity Optimization Gateway VIS files parser to import data.
	Although conservative behavior was selected, simulation is based on 15 minutes detail samples. Detailed statistics for hourly data samples are not available for the server.
	Simulation is based on aggressive behavior, as requested.	The metrics that are required for the selected behavior are available and the recommendation is generated as expected.	No action is required.
- Very High	Simulation is based on balanced behavior, as requested.	The metrics that are required for the selected behavior are available and the recommendation is generated as expected.	No action is required.
	Simulation is based on conservative behavior, as requested.

Accuracy levels of Migration Simulation

Comments