https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyNzg0IiwiaGFzaCI6IjlkNTk1NmQ1LWQ3MGQtNGVkYy1hOTg3LTRhMTk0YWIzNzlhOSJ9
1-800-691-1991 | 9am - 8pm ET
EN

Consistent backup failures after installing vSphere 6.7 U1

Challenge

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

The issue affects only Veeam Backup & Replication 9.5 Update 3a.
Please upgrade to Veeam Backup & Replication 9.5 Update 4, it works fine with 6.7 U1 out of the box, no additional steps needed.
 
NOTE: The displayed version in vSphere is not 6.7.1 for Update 1. The only way to verify the version is by the build number.
The version can be verified by checking the build number in the following VMware KB Articles.
ESX\ESXi Hosts - https://kb.vmware.com/s/article/2143832
vCenter Servers - https://kb.vmware.com/s/article/2143838?lang=en_US

 

More information

Veeam Backup & Replication support for VMware vSphere: https://www.veeam.com/kb2443

KB ID:
2784
Product:
Veeam Backup & Replication, Veeam Cloud Connect
Version:
9.5.0.1922
Published:
2018-10-17
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
1 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later