Veeam One v7 R2 update

KB ID:
1841
Product:
Veeam ONE
Version:
7.0
Published:
Last Modified:
2014-05-20

Challenge

Release Notes for Veeam One v7 R2 update

Cause

Please confirm you are running version 7.0.0.876 prior to installing this update. You can check this under Help | About in Veeam ONE Monitor Client.
After upgrading, your build will be version 7.0.0.919.

This update should be applied to remote systems with the Veeam ONE Monitor Client, as well as the Veeam ONE server.

Solution

New Features
 
VMware
 
  • vSphere 5.5 support
  • vCloud Director 5.5 support.

Microsoft
 
  • Windows Server 2012 R2 Hyper-V and free Hyper-V Server 2012 R2 support
  • Support for Windows Server 2012 R2 and Windows 8.1 as guest virtual machines (VMs)
  • Support for System Center 2012 R2 Virtual Machine Manager (VMM)
  • Support for the installation of Veeam ONE and its components on Windows Server 2012 R2 and Windows 8.1

Resolved issues:
 
 
Monitor Client 
 
  • Refresh of the performance and alarms data takes too much time in large virtual infrastructure deployments.
  • Frequent infrastructure tree updates in large deployments makes Monitor Client slow and less responsive.

Veeam Backup & Replication Integration
 
  • Monitored Veeam backup servers are in disconnected state after upgrade to Veeam ONE v7.
  • Alarms for vPower NFS datastores cannot be suppressed.
  • Alarms for verified by a SureBackup job VMs cannot be suppressed.
  • Historical information about VM backup tasks cannot be retrieved from the backup server.
  • Veeam backup server could not be monitored by Veeam ONE server installed on non-English locales after deleting any backup job from the Veeam backup server.

Hyper-V
 
  • Snapshot size and snapshot age alarms are triggered for VMs with differencing disks.
  • Memory usage widget shows memory available counter on the summary of the Hyper-V hosts.

Email Notifications
 
  • Veeam ONE server sends email notifications for resolved warning alarms, ignoring the configured policy to notify about errors only.

Monitoring Engine
 
  • Veeam ONE Monitor service fails with the following error message “Fatal error at thread exit if FLS callback not freed” in the debug log.

Reporting Engine
 
  • Monthly report scheduling set for the last day does not work.
  • All URL triggered performance reports that have past interval as a predefined parameter display wrong reporting interval.
  • Saved performance reports using past time reporting intervals are triggered with "Date From" - "Date To" parameter. 
  • VMs with low CPU Ready metric are ignored in the Undersized VMs report.

Object Categorization
 
  • Grouping expressions with nested expressions using “IndexOf”, “<”, “>” and other operators cannot be processed.

Known issues:
 
 
Reporter
 
  • Reports generated via direct links are not displayed in Internet Explorer 11. To workaround this issue, add Veeam ONE website to trusted sites.
  • Veeam ONE website is not displayed. To workaround this issue, add Veeam ONE website to trusted sites.
  • VM Uptime report shows no data for historical time intervals after the upgrade to Veeam ONE v7 R2. This is caused by the switch to the new VM uptime monitor that improves report accuracy.

Monitor
 
  • Host disk alarms are reset to default thresholds after the upgrade. The list of affected alarms is the following: 
VMware vSphere:
  • Host disk SCSI aborts
  • Host disk bus resets
  • Host disk read latency
  • Host disk write latency
Microsoft Hyper-v server:
  • Host average disk queue length

More Information

To obtain the patch, please download it here.

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

OK

Rate the quality of this KB article: 
4.3 out of 5 based on 26 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:

Submit