The report analyzes configuration of the Hyper-V infrastructure against a set of recommended settings and best practices, identifies clusters, hosts and\or VMs that are configured inefficiently and verifies problem areas to help mitigate issues and prepare VMs for backup with Veeam Backup & Replication.
- Verification Results chart displays the share of failed and passed verification tests, and tests that completed with warnings.
- Assessment Criteria table lists criteria used in the report to assess the Hyper-V infrastructure, and shows the assessment results.
- Optimization tables show detailed assessment result for each criterion and provides recommendations on how to improve infrastructure configuration.
The report takes into account the following criteria when analyzing Hyper-V configuration:
Hosts use same CPU vendors/models
The report analyzes cluster configuration to make sure clusters include hosts with CPUs of the same vendors.
A cluster that includes hosts with CPUs from different vendors may not operate correctly when you perform some tasks in Veeam Backup & Replication. For example, migration or restore of VMs to a host with a different processor may fail as some applications only run on processors of a specific vendor.
Hosts are updated equally
The report verifies that hosts in a cluster have the same Hyper-V version installed.
When hosts in a cluster have different Hyper-V versions installed, it may cause compatibility issues and unexpected errors.
Storage controllers are of the same vendors
The report analyzes cluster configuration to verify that storage controllers installed on hosts are of the same vendor.
If you have storage controllers of different vendors on hosts in a cluster, you may experience unexpected errors and failures.
The report analyzes cluster configuration to verify whether NIC cards within a cluster are of the same vendor.
Incompatible NIC cards may cause issues during backup and restore operations in a cluster.
Host is not running on a balanced power plan
The report analyzes host configuration to verify whether hosts in the infrastructure are running on a balanced power plan.
The Balanced power plan is the default power plan in Windows operating systems. However, to increase host efficiency, you are recommended using the High Performance power plan.
No RDP printers mapped
The report analyzes your infrastructure to verify that there are no RDP mapped printers on hosts.
Printers mapped via RDP may not work efficiently and may cause unexpected errors and failures. You can disable RDP printer mapping through a group policy.
Virtual CPUs/Logical CPUs ratio
The report analyzes the infrastructure to verify that maximum vCPU per host CPU core ratio is below the specified value. The default ratio is 8.
If CPU configuration is not balanced, VMs may not obtain enough processor resources. For information on how to measure processor performance, see Microsoft MSDN article.
The report analyzes the infrastructure to determine whether snapshots on VMs are not saved to Local Disk (C).
Snapshot redirection may slow down VM backup. For better backup experience with Veeam Backup and replication, make sure there are no redirected checkpoints.
Integration Services state
The report analyzes your infrastructure to verify that all Integration Services on VMs in the infrastructure are enabled.
Integration Services participate in application-aware image processing during backup in Veeam Backup & Replication. To use application-aware image processing efficiently, enable Integration Services.
Hyper-V VSS Requestor state
The report analyzes the infrastructure to identify the state of VSS Requestor on VMs.
If VSS Requestor is not started on a VM, this may cause issues during backup as VSS services will not be able to create a shadow copy and prepare data for backup.
If the state of VSS Requestor on a VM is Started/Automatic or Started/Automatic (Delayed Start), the report will show the Success verification result. In other cases, the verification result will be Warning.
No Checkpoints used
The report analyzes the virtual infrastructure to find VMs with existing checkpoints.
To use Veeam Changed Block Tracking for incremental backup, you must remove snapshots.
No VMs on datastores with less than 10% of free space
The report analyzes the Hyper-V infrastructure to find datastores that have less than 10% of free space.
During backup Veeam Backup & Replication triggers a checkpoint that is normally stored next to VM files on the source datastore. To eliminate the problem of datastores running low on free space during backup, it is required that the free space is more than 10%.
This report shows a list of clusters, hosts and VMs in your virtual environment that could experience potential issues during backup, gets guidance on how to resolve these issues.
Scope (VI): defines a virtual infrastructure level and its sub-components to analyze in the report.
Business View object(s): defines Veeam ONE Business View groups to analyze in the report. The parameter options are limited to objects of the Cluster type.
Assessment type: defines types of objects to analyze in the report.
Max vCPU per Host CPU core ratio: defines the threshold for the maximum number of vCPU cores per a single instance of the physical CPU core.