What-If VM Deployment Planning for Hyper-V (manual resource entry)
This report calculates the number of additional VMs that your existing infrastructure (Hyper-V storage and clusters) can support before the resource utilization reaches the specified threshold value.
The What-If VM Deployment Planning for Hyper-V (manual resource entry) report evaluates total capacity of your infrastructure and provides estimation of how many sample VMs of a certain profile can be added without causing the specified resource utilization threshold to be breached. In this report, you can specify parameters for the VM profile manually.
The report analyzes historical performance data for the specified period in the past, calculates the performance utilization trend and applies it to the forecast horizon. Calculation of additional VM sets is based on the predicted future performance of the sample VM(s) and the predicted virtual infrastructure capacities.
To make a prediction for the vCpuCount counter, the report analyzes the current vCpuCount value, not historical performance data.
Performance Data From: defines a date in the past starting from which historical performance data will be used for calculating the performance utilization trend. The report analyzes historical performance data starting from this date to the current date (data collection period).
To make a forecast, the report must use historical performance data for at least 72 hours.
Forecast Horizon: defines the forecast period. The calculated performance utilization trend is applied to the time period that starts from the current date to the forecast horizon date.
The date in the Forecast Horizon field must be a date in future.
Scope: defines a list of Groups or Objects that will be analyzed in the report (by default, the Veeam Hyper-V Hosts Group and Veeam Hyper-V Cluster Disks Group are selected).
Objects of the Veeam Hyper-V Hosts Group and Veeam Hyper-V Cluster Disks Group are described with different related metrics. That is why, to evaluate your Hyper-V infrastructure properly, mind the following:
Threshold: CPU Utilization (%): defines the CPU usage threshold as a percentage of total cluster CPU resources.
Threshold: Used Memory (%): defines the used memory threshold as a percentage of total cluster memory resources.
Threshold: Storage Volume Free Space: defines the free space threshold as a percentage of total available volume space.
Threshold: Storage IOPS: defines storage IOPS threshold.
To identify the IOPS limit at which your storage device may experience abnormal latency, you can use the Hyper-V Storage Performance Profile Analysis report.
Threshold: vCPUs per Core: defines the threshold for vCPU cores per a single instance of the physical CPU core.
VM COUNT: defines the number of VMs to include in the profile.
VM config - vCPU COUNT: defines the number vCPUs in the sample VM.
VM config - CPU GHz: defines CPU frequency in the sample VM.
VM config - Memory GB: defines the amount of memory used by the sample VM.
VM config - IOPS: defines the number of IOPS completed on disks on the sample VM.
VM config - Storage GB: defines the number of storage space allocated to the sample VM.
VM config - Resource usage %: defines average planned usage of the resources specified for the sample VM(s).
Specify the following VM profile: 5 VMs, 3 GHz CPU, 4 GB memory, 250 disk IOPS. Assume that resource usage for these VMs will not exceed 85%. Forecast how many sets of VMs of the specified profile can be added to your storage taking into storage capacity. Make sure that the free space threshold will not breach 20% within the next 30 days. Use the historical performance data for the previous month for report analysis.
- Open the What-If VM Deployment Planning for Hyper-V (manual resource entry) report.
- From the Performance Data From list, select Previous Month > First Day.
- From the Forecast Horizon list, select a date in future (30 days from today).
- In the Scope section, exclude Veeam Hyper-V Hosts Group from the report scope (select the group and click Remove) to search for available storage only.
- In the VM COUNT field, enter 5.
- In the VM config - CPU GHz field, enter 3.
- In the VM config - Memory GB field, enter 4.
- In the VM config - IOPS field, enter 250.
- In the VM config - Resource usage % field, enter 85.
- In the Threshold: Storage Volume Free Space field, enter 20.
- Click Run to view the report.
The Virtual Infrastructure Described table will provide an overview for all volumes included in the report scope: total number of volumes and total storage capacity.
The Sample Workload Described table will provide an overview for the profile of virtual machines: total number of VMs, total CPUs, total CPU usage, memory usage and storage usage and number of IOPS.
The Constraining Resource per Each Object table will provide the following details for every volume and disk:
Name of the volume/disk.
Resource for which the specified threshold will be breached first within the forecast period.
For example, both CPU Utilization (%) and Used Memory (%) thresholds will be breached within the forecast period and the CPU Usage (%) is reported to be breached first. In this case, the report will display CPU Usage as the constraining resource. However, the Recommendations will be provided both for CPU Utilization and Used Memory resources.
Number of additional VMs of the specified profile that your storage will be able to support on the forecast horizon date (that is, at the end of the forecast period).
Report details will provide in-depth forecast information for every volume and disk included in the report scope.
The Performance Forecast section will show a details table for each analyzed storage resource:
Name of the analyzed resource.
Specified threshold value.
Total storage capacity.
Predicted amount of free space left on the storage after the new VM sets are added.
The report provides both absolute value and relative value (as a percentage of total capacity).
VM Sets that Can Be Added
Number of additional VMs of the specified profile that the storage will be able to support on the forecast horizon date (that is, at the end of the forecast period).