This section lists issues known in Veeam MP for Microsoft Hyper-V.
Microsoft Operations Management Suite compatibility issues
Under rare circumstances, Operations Manager connected to Microsoft Operations Management Suite may cause Veeam MP objects to become unmonitored. This behavior will be accompanied by 1215 events written into the Operations Manager log. This is a known Microsoft compatibility issue, and Microsoft is currently working on the solution.
If you encounter the issue, we recommend that you contact Veeam Support.
Capacity Planning for Azure Hybrid Cloud report output may list some VMs twice
Two Microsoft Azure VM sizes — A10 and D13 — are almost identical besides a small difference in the hardware specifications. If a VM fits both sizes, the Capacity Planning for Azure Hybrid Cloud report output will show the VM twice.
Absent Path property in the Traffic Lights widget
Supporting SQL stored procedures on the SQL back-end have been significantly re-factored by Microsoft and now work more reliably and much faster, however the current version lacks path information. Even if you configure the Traffic Lights widget to display the Path property, dashboards will still show no data for it.
In a future release, Veeam will improve the Traffic Lights widget architecture to display Path properties regardless of data obtained from the supported SQL stored procedures.
Drill-down option may not work in Capacity Planning for Azure Cloud report
The Capacity Planning for Azure Cloud report included in the Veeam Capacity Planning for Hybrid Clouds MP provides an opportunity to click numbers in the output table to drill down to the list of VMs that matches profiles and to check performance data for these VMs. However, if the number of VMs is too big (>200), the drill-down option will not work and you will get the following error: ‘The value of parameter 'Object' is not valid. (rsInvalidParameter). Invalid URI: The Uri string is too long.’
This is a known MS SQL Server 2012 SP1 issue.
Non-default collation settings for SQL cause Data Warehouse errors after import of Veeam MP
If you are using a non-default SQL Collation that is not supported by OpsMgr, after installation of Veeam MP you may receive errors, such as: ‘Cannot resolve the collation conflict between ‘SQL collation’, ‘SQL_Latin1_General_CP1_CI_AS’ and ‘Latin1_General_CI_AS’ in the equal to operation.’
This is not a Veeam MP issue, although it is exposed by the reporting features in Veeam MP. The root cause is an unsupported configuration for the OpsMgr Data Warehouse DB.
To avoid this issue, make sure that the supported collation is specified for Ops Mgr and Data Warehouse databases when installing Ops Mgr. It is also required that the collation is configured identically between the following databases and the SQL instance(s) in which they reside:
For existing installations it may be required to port/reinstall Ops Mgr to use a supported SQL collation configuration.
For a list of collations supported by Ops Mgr, see:
|•||Ops Mgr 2012 SP1 system requirements at technet.microsoft.com/en-us/library/jj656654.aspx|
|•||Ops Mgr 2012 R2 system requirements at technet.microsoft.com/en-us/library/dn249696.aspx|
Hyper-V on Microsoft Windows Nano Server is not supported
Veeam Management Pack currently does not support Hyper-V working on a highly minimized Microsoft Windows Nano OS. This operating system requires a separate agent and a separate set of core management packs currently not included In the Veeam MP.
Windows and Hyper-V containers are not supported
Veeam Management Pack currently does not support monitoring and alerting for Container objects on Windows Server 2016.
Performance metric overrides may cause Veeam MP monitors to work incorrectly
If you set an override for a Veeam MP performance metric in a way that the specified data collection time interval exceeds the Ops Mgr time range configured to collect dependent metrics, the corresponding Veeam MP monitor will not be able to work correctly, and all dependent metrics will return zero values.
To avoid the issue, configure the performance metric override correctly taking into account the Ops Mgr data collection time range, or configure overrides for the performance metric and its dependent metrics at the same time. For more information, see section Troubleshooting.
Veeam MP disk metrics are collected only for VHD(X) type of virtual hard disk
Currently Hyper-V API is not able to correctly expose per-VM disk usage for a VHDs attached to a specific VM. That is why in case a virtual machine uses the VHDs (VHD Set) type of virtual hard disk, Ops Mgr will not be able to collect disk metric values for the VHDs, and the Used Storage GB metric will return zero values.
Configuration Change Tracking and Alert Correlation report displays GUID toVM name as a change
Veeam MP discovers Hyper-V virtual machines using several sources (cluster resources, storage device, Hyper-V resources and, if necessary, SCVMM namespace). Not all of these sources contain the display name of a virtual machine. That is why, in case of mismatched discovery timings, for a short period of time the VM may be represented with its GUID in the Ops Mgr console.
The Configuration Tracking and Alert Correlation report, which is designed to capture such changes, cannot tell the difference between this change and the real change of the VM name. That is why, the report will consider GUID to VM name as a real VM name change, and will include this change in the output table.
VM Net and Disk Traffic Analysis dashboard does not show Net Used and Disk Time statistics
The VM Net and Disk Traffic Analysis dashboard shows empty % Net Used, % Disk Time widget.
Importing Hyper-V Task Manager VMM plug-in without restart may cause SCVMM console to crash
After you import the Hyper-V Task Manager plugin, you need to restart the SCVMM console. Veeam Task Manager for Hyper-V can be launched for Host and Cluster objects. That is why, if you try to select a non-supported object (for example, a VM) right after importing the plugin, without restarting SCVMM console, the console may crash.
Last successful backup property of Hyper-V VMs with crash-consistent backups is always empty
Some backup solutions, including Veeam Backup & Replication, can perform crash-consistent Hyper-V backups. When you create such backups, the Last Successful Backup VM property is not updated.
If you use Veeam Backup & Replication and want to get an up-to-date list of all protected VMs and their current properties, import MP for Veeam Backup & Replication and use the Protected VMs report included in the MP. For more information on MP for Veeam Backup & Replication, see the MP for Veeam Backup & Replication User Guide.
Hyper-V Integration Services are required for full-featured monitoring
Some data will be missing if a Hyper-V VM does not have Integration Services installed. For example , the Veeam HyperV: VM Power State monitor will not be able to display power state correctly. As recommended by Microsoft, Hyper-V Integration Services should be installed in all VMs where the guest OS supports it.
Integration Services monitor may generate errors for an unresponsive VM
A heavily loaded virtual machine may not be able to respond in a timely manner. In this case, the Veeam HyperV: VM Integration Services Status monitor script will write errors to the Ops Mgr log.
Rebooting renamed VMs
After a VM is renamed, it should be restarted to ensure that Hyper-V can correctly report VM name and its metric values. Additionally, some performance metrics for the VM will not be fed into the Ops Mgr until the VM is rebooted.
Error Count metric shows high values for SCSI disc attached to a VM
When the Hyper-V host does not correctly process a command that the guest OS sent to the SCSI device, it will increase the Error Count metric value although the command is valid and not necessarily an error. This is a known issue for Hyper-V environment.
VMs are temporarily represented with GUIDs instead of VM names
Hyper-V VMs are discovered by several rules — these rules target Hyper-V host resources and cluster resources. In some cases, the cluster resources discovery can run prior to the main Hyper-V host resources discovery. As a result, VM objects may be temporarily represented with IDs (VM GUIDs) instead of VM names. When all discovery is completed, the issue will be resolved.
GUIDs shown for VMs residing on offline storage
Under some circumstances, VMs can be removed from Hyper-V Manager inventory while the storage remains offline (for example, the storage became inaccessible for a long term).
When Veeam MP discovers such offline volumes, it identifies remaining VMs and shows VM GUIDs in Ops Mgr. To resolve the issue, bring the storage volume online, clean VM files completely and initialize re-discovery on the volume.
Inaccurate performance statistics for VMs with the same name
If two or more VMs on a Hyper-V host have the same VM name, the Hyper-V Task Manager may show inaccurate performance statistics data for such VMs. This is because Microsoft performance metric logging makes it impossible to map metrics when VMs have the same name.
VMs with static memory report zero memory usage
For VMs with static memory, Hyper-V will not send memory usage data to the PerfMon classes. As a result, such VMs will have zero memory usage in Ops Mgr.
Ops Mgr reports problems with unloading workflows when all VMs on a host stopped
When all VMs on a Hyper-V host are stopped, events 10103 will be written to the Ops Mgr event log on the Hyper-V host: ‘In PerfDataSource, could not resolve counter instance [CounterName]. Module will not be unloaded. One or more workflows were affected by this.’
When all VMs are stopped, Hyper-V server unloads all PerfMon classes, and Ops Mgr PerfMon module cannot access data.
Hyper-V host local volumes with 0 VMs do not appear in Ops Mgr console
Local disks and volumes on Hyper-V hosts will be discovered only if there are VMs on these volumes. This discovery behavior is by design.
NFS Storage not supported
The current Veeam Hyper-V MP version supports Local Storage, Cluster Shared Volumes and SMB Shares only. NFS Shares are not supported.
VM pass-through disks not included in total VM storage metric
The size of the pass-through disks is not taken into account when the Used Storage metric value for a VM is calculated.
Virtual Machines. Idle VMs report does not show Down Time data
The Virtual Machine. Idle VMs report output tables show ‘n/a’ values in the Down Time (%) column.
Traffic lights and Top N dashboard widgets do not show data, although infrastructure topology is already discovered and performance metrics are available
After installation or upgrade, Traffic Light and Top N dashboard widgets will show no data until performance statistics are aggregated in the Ops Mgr data warehouse. In general, the initial aggregation takes about 4 hours. This behavior is by design.
VM Uses Storage property mismatch for VMs and volumes with multiple mount paths
If a VM is migrated from a volume that has several mount paths, the Used Storage property for the VM may be reported incorrectly. For the volume that has multiple mount paths, Veeam Hyper-V MP is able to collect only the last path value. This value may differ from the path value stored in the VM properties. For this reason, the relations between the VM, CSV and Host Disk may be displayed incorrectly.
Used Storage GB reported as zero for unavailable CSV
If a Clustered Shared Volume is unavailable (failed status), the Used Storage GB metric will be reported as zero.
Unauthorized Access exception in Management Server log
If the Run As account configured for the Veeam Hyper-V MP SCVMM Connection Account (Read-only) profile does not have sufficient permissions, ‘Unauthorized Access’ exceptions will be written to the event log on the Management Server.
In the Ops Mgr agent event log on the SCVMM server, you will see an exception similar to this: ‘Cannot connect to SDK. Check Veeam Hyper-V MP SCVMM Connection Account (Read-only) Profile. It must contain account with sufficient access rights.’
The issue will be resolved as soon as you configure the Veeam Hyper-V MP SCVMM Connection Account. For details, see Appendix A. Configuring Run As Account for SCVMM Discovery.