Consistent backup failures after installing vSphere 6.7 U1

KB ID: 2784
Product: Veeam Backup & Replication;Veeam Backup & Replication Cloud Edition
Last Modified: 2018-11-08


After updating vCenter to 6.7U1, processing of all VMs fails with "Object reference not set to an instance of an object".


The issue is triggered by an update to the vSphere API version in vCenter 6.7 U1.


Create the following registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the Veeam Backup and Replication server:

Please, note that value and data fields should not contain any spaces.

Value: VMwareOverrideApiVersion
Type: Multi-String Value (REG_MULTI_SZ)
Data: 6.7.1=6.7 

Then reboot the Veeam Backup and Replication server.

More Information

This is a temporary workaround against the specific error, which will allow the jobs to complete successfully. Overriding VMware API version may potentially cause issues with other Veeam functionality, because we don't know the specific API changes that made VMware increment the API version. We're working with VMware to obtain these details while continuing to test vSphere 6.7 U1 with the workaround applied.

The release vehicle for the official out-of-the-box support for vSphere 6.7 U1 will be our next release (Update 4). We'll be able to determine supportability of vSphere 6.7 U1 with the workaround applied after full regression testing cycle is done against the U1 GA code (usually takes 3-4 weeks).

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.3 out of 5 based on 129 ratings

Couldn't find what you were looking for?

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

Request new content