Release Notes for Veeam Management Pack 8.0 Update 6

Veeam Management Pack for Microsoft System Center
Last Modified:


Release Notes for Veeam Management Pack 8.0 Update 6.

NOTE: The Veeam Management Pack 8.0 Update 6 cumulative patches for Veeam Backup & Replication monitoring and VMware vSphere 7.0 monitoring are available through kb2940 and kb3112 correspondingly.


Please confirm you are running Veeam Management Pack 8.0 prior to installing this update. You can check this in Operations Manager console under Administration | Management Packs, the build number should be or later.

To install the update, import the management packs through Operations Manager console > Administration > Management Packs > Import Management Packs.

To obtain Veeam MP 8.0 for System Center - Update 6, please download it here.

NOTE: It is important that you update Veeam Management Pack Core Services to Support TLS 1.2 Protocol for Update 6.


New in This Release

  • Additional Hypervisor support vSphere 6.7. VMware vSphere 4.0 and later (including vSphere 6, vSphere 6.5, vSphere 6.7, vSphere 6.7 U1, vSphere 6.7 U2 and vSphere 6.7 U3) 
  • Monitoring SQL Transaction Log Backup Job. Veeam MP separately monitors SQL Transaction Log Backup jobs running inside backup jobs with the enabled application-aware processing option. For this purpose, Veeam MP includes a new Veeam SQL Transaction Log Backup Jobs view and Veeam Backup: SQL Transaction Log Job Status monitor.
  • Improved performance of Morning Coffee Dashboards. In previous versions, Morning Coffee Dashboards tended to load slowly for large-scale environments. In Veeam MP 8.0 Update 6, the performance of Morning Coffee Dashboards has been significantly improved.
  • A new metric for Veeam VMware Collector. Due to the Ops Mgr Health Service (Monitoring Agent Service) limitations that appear when a Veeam VMware Collector processes a large amount of data, it is required to distribute monitoring load among multiple Veeam VMware Collectors in large environments. To assess the monitoring load on Veeam VMware Collectors more precisely, Veeam MP provides a new % Object Monitoring Load metric.
Resolved Issues
  • No monitoring for Hyper-V hosts that exceeded the license limit. Veeam MP license limits the number of Hyper-V hosts enabled for monitoring in Ops Mgr. Earlier, if the number of licensed Hyper-V hosts was exceeded and new hosts were added to the Ops Mgr infrastructure, Ops Mgr automatically stopped monitoring the old infrastructure and started monitoring the newly added hosts. In Veeam MP 8.0 Update 6, the issue was resolved, and Ops Mgr continues monitoring the old infrastructure.
  • Ops Mgr event log shows excessive BackupCopyJobSessionFinished events. In previous versions, the Ops Mgr event log contained a large number of 3101 events caused by errors in the backup copy job status collection process. In Veeam MP 8.0 Update 6, the issue was resolved.
Known Issues and Limitations
  • Collector Autodeploy limitations. If you use the Collector Auto-Deployment feature to automatically deploy Veeam VMware Collectors on Management Servers, keep in mind that it will install clear 8.0 version without patches. When the installation completes, run the ISO\Update\VeeamMP80_Update6.exe installation file on each Veeam Collector to install patches.  
  • Veeam MP for Hyper-V stops collecting storage metrics. If storage migrates to another volume, the storage performance collection will halt and Veeam MP will stop collecting the following metrics: Storage IOPS, Storage KB Total/sec, Storage Flush Count and Storage Error Count. Note that this issue does not affect migration between hosts. To work around the issue, restart the Ops Mgr agent after storage migration.

More Information

Should you have any questions, contact Veeam Support.

Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.


Rate the quality of this KB article: 
4 out of 5 based on 6 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text: