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 on the Veeam Backup and Replication server. You must be on Veeam 9.5 Update 3a
Please, note that value and data fields should not contain any spaces.
Type: Multi-String Value (REG_MULTI_SZ)
After creating the registry value above, you must reboot the Veeam Backup and Replication server.
More information regarding this workaround can be found here: https://forums.veeam.com/vmware-vsphere-f24/vsphere-6-7-u1-support-t54673.html
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).
All auto-tests of Update 3a with the workaround enabled have completed successfully, so all base Veeam Backup & Replication functionality is now confirmed to work with vSphere 6.7 U1. The forum post above will be updated once the full regression testing cycle completes.
Please be aware that we’re making changes which will restrict access to product updates for users without an active contract.