Challenge
Note: This is a temporary workaround against this specific error. The release vehicle for the official out-of-the-box support for vSphere 6.7 U1 will be Veeam Backup & Replication v9.5 Update 4.
For more information regarding Veeam Backup & Replication and vSphere compatibility please refer to https://www.veeam.com/kb2443
After updating vCenter to 6.7U1, processing of all VMs fails with "Object reference not set to an instance of an object."
Cause
The issue is triggered by an update to the vSphere API version in vCenter 6.7 U1.Solution
Create the following registry value on the Veeam Backup and Replication server.Please, note that value and data fields should not contain any spaces.
Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
Value: VMwareOverrideApiVersion
Type: Multi-String Value (REG_MULTI_SZ)
Data: 6.7.1=6.7
Value: VMwareOverrideApiVersion
Type: Multi-String Value (REG_MULTI_SZ)
Data: 6.7.1=6.7
After creating the registry value above, you must 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).