Veeam Home | Support | Downloads
Management Pack 8.0 for Veeam Backup & Replication User Guide

Veeam Management Pack Help Center  > Veeam MP for Backup & Replication User Guide >  Release Notes > Known Issues and Limitations

Known Issues and Limitations

Previous page Print this Topic

Table of contents

This section lists issues known in MP 8.0 – Update 3 for Veeam Backup & Replication.

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. To resolve the issue, download and install an update rollup for your Ops Mgr version:

Update Rollup 2 — for System Center 2016 Operations Manager.

Update Rollup 12 — for System Center 2012 R2 Operations Manager.

Backup Job RPO compliance monitor does not work for SureBackup jobs

The Veeam Backup: Job RPO Compliance monitor is designed to track jobs which produce restore points. SureBackup jobs perform verification of restore points that have already been created. That is why the monitor will ignore SureBackup jobs, and will stay in the ‘Green’ state when tracking their results.

VM Backup Status report incorrectly displays some backup job states

The Backup Status dataset rule collects the results of backup job sessions. In case the rule captures the “in-Progress” state, the VM Backup Status report will mark this state with a warning. The “in-Progress” job state may indicate poor performance of the Veeam Backup configuration database or other performance issues on the backup server.

Backup Job RPO compliance monitor is in Healthy state although last successful restore point is older than 3 months

The Veeam Backup: Job RPO Compliance monitor is designed to track job history for successfully created restore points for the previous 3 months.

It is not recommended to use the monitor to track jobs that are scheduled to run with a 3-month interval or rarely. If you enable the monitor for such a job, as soon as a restore point is created, the monitor will generate an alert stating either that the job is disabled, or that the job schedule is incorrectly configured to meet the desired RPO.

For Veeam Backup & Replication 9.0, the issue has been resolved.

Limitations for Veeam Backup & Replication 7.0

Veeam MP uses Veeam Backup & Replication API for data collection and reporting. Since Veeam Backup & Replication 7.0 API does not support some Veeam Backup & Replication features, the following Veeam MP 8.0 reports and monitors will not work with Veeam Backup & Replication 7.0:

Configuration Tracking and Alert Correlation report

Job Configuration Change Tracking report

Delegated Restore Permissions Overview report

Veeam Backup: Job transport mode status monitor

Veeam Backup: Job RPO Compliance monitor

WMI class for Veeam backup servers 7.0 lacks the following properties:

Configuration DB Protection (Backup) Enabled

Configuration DB SQL Server Edition

For this reason, Veeam MP will not be able to collect and display these backup server properties in the Ops Mgr console.

Protected VMs report may show incorrect data

The Protected VMs report shows all VMs as unprotected though backup data has been collected successfully. This is a known report limitation since the same vCenter servers have to be both connected to Veeam Backup & Replication console and displayed in the Veeam UI under the same unique address (it is recommended to use FQDN in both cases).

To resolve the issue, remove the connection to the vCenter server in the Veeam UI and add it again with the same name as it appears in the Veeam Backup & Replication console.

‘_Total Instance’ value of ‘CPU Used %’ metric for Veeam backup proxy exceeds 100%

The Veeam Backup Proxy CPU Used % rule collects the performance metric CPU Used % as a total of average CPU usage for all processes running on the Veeam backup proxy server. When the backup proxy is overloaded, the _Total instance may be reported to be higher than 100%.

VM Configuration Assessment Report may show false-positive result for vmdk file size test

If a VM has a large volume (more than 2TB), but the volume is distributed among several VMDK files, the VM Configuration Assessment Report may incorrectly report this volume as having a potential backup issue.

VM Configuration Assessment Report may not show problematic 2TB disk in vmdk file size test

In some cases, the VM Configuration Assessment Report may not indicate a potential issue for large vmdk files, although Veeam Backup & Replication will not be able to back up these files. This behavior is observed when a 2TB vmdk disk resides on VMFS version 4 or earlier, and the VM is registered in vSphere hosts 5.5 or later.

Job sessions that failed before VMs enumeration are excluded from Veeam Backup Reports

If a backup or replication job fails before initiating the VM backup routine, there is no way to get the precise list of VMs that the job should process. Such failed sessions cannot be associated with any VMs and are excluded from from Veeam Backup Reports.

Restore Operator Activity report does not list all types of restore operations

Veeam Backup & Replication does not have audit for all types of restores that users can perform. Because of that, certain types of restore operations, such as restores from SAN snapshots and U-AIR wizard-driven restores will not be visible in the Restore Operator Activity report.

For Veeam Backup & Replication 9.0, the issue has been resolved.

State of re-initialized monitors for all backup jobs is Green

When a Veeam backup server goes down, the WMI namespace on this server cannot be accessed. As a result, Veeam MP for Backup discovery will groom all backup jobs managed by this server. When the server is back online, Ops Mgr will rediscover jobs for this server and re-initialize monitors for the jobs.

The state of re-initialized monitors for the backup jobs will be Green even if the jobs previously finished with errors or warnings.

Table of contents