Page 1 of 5

vSphere 6.7 U1 Support

Posted: Oct 16, 2018 8:43 pm
by Gostev
Folks, just a heads up!

We're seeing consistent backup failures after installing Update 1 in our first test lab. Judging on the error, it looks like VMware has possibly introduced some breaking API change which affects our transport selection logic, so this does not look like something minor - and will likely affect 100% of our users.

I will update after devs had a chance to investigate this issue, and QC tests the update in more labs - but for now, please do avoid installing this update just to be on a safe side.

Official support KB article > KB2784

Thanks!

[UPDATE] October 17th
The issue has been fully understood, so I am documenting it here until the KB article is updated.

Symptons
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.

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

Code: Select all

Value: VMwareOverrideApiVersion
Type: Multi-String Value (REG_MULTI_SZ)
Data: 6.7.1 = 6.7
Important
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 all 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).

[UPDATE] October 19th
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. I will provide another update once the full regression testing cycle completes.

Re: vSphere 6.7 U1 Support

Posted: Oct 17, 2018 12:57 pm
by ngreen
Thanks for the warning. Would be useful to identify if it's ESXi or vCenter related (or both). Ideally we'd like to update to vCenter 6.7 U1 to get the fully featured HTML5 client, even if we left the hosts on ESXi 6.7 GA.

Re: vSphere 6.7 U1 Support

Posted: Oct 17, 2018 1:03 pm
by mwvme
I reproduced this issue with only vCenter updated and hosts still at 6.7. You need to wait, unfortunately.

Michael

Re: vSphere 6.7 U1 Support

Posted: Oct 17, 2018 1:22 pm
by tka
ESXi 6.7 U1 with "old" vCenter works - at least with SAN transport.

Re: vSphere 6.7 U1 Support

Posted: Oct 17, 2018 1:28 pm
by Trelor
How are you running a version of vCenter that is behind ESXI that is not even supported

Re: vSphere 6.7 U1 Support

Posted: Oct 17, 2018 1:30 pm
by mwvme
I upgraded my vCenter, which is in fact the correct order, and I did not update my hosts yet. So this is all legit.

Michael

Re: vSphere 6.7 U1 Support

Posted: Oct 17, 2018 1:36 pm
by tka
Trelor wrote:
Oct 17, 2018 1:28 pm
How are you running a version of vCenter that is behind ESXI that is not even supported
Yes, in this case it is supported to run vCenter 6.7 with ESXi 6.7 u1:
https://www.vmware.com/resources/compat ... matrix.php

Re: vSphere 6.7 U1 Support

Posted: Oct 17, 2018 2:07 pm
by tka
I did an Update via VCSA Installer wizard from 6.5 to 6.7 u1 today and veeam failed afterwards.

Re: vSphere 6.7 U1 Support

Posted: Oct 17, 2018 2:18 pm
by stefanbrun
I did an upgrade from VCenter 6.7 to 6.7 U1 via the VCSA web updater.
Updatet also the ESXi hosts from 6.7 to 6.7 U1.

Tested backup via VCenter and ESXi direct, on both tests same problem.

Re: vSphere 6.7 U1 Support

Posted: Oct 17, 2018 2:26 pm
by Gostev
Updated the original post with the workaround.

Re: vSphere 6.7 U1 Support

Posted: Oct 17, 2018 2:46 pm
by stefanbrun
Thx Gostev, workaround does the job.

Re: vSphere 6.7 U1 Support

Posted: Oct 17, 2018 2:47 pm
by Gostev
Super, glad to hear that :D

P.S. In case you're as fast as one of my colleagues, please note that the registry key location was off originally, but is corrected now.

Re: vSphere 6.7 U1 Support

Posted: Oct 17, 2018 3:39 pm
by ddenson
I can confirm that the workaround is working for us also. Thank you!
Gostev wrote:
Oct 16, 2018 8:43 pm
Workaround
Create the following registry value under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication key on the backup server:

Code: Select all

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

Re: vSphere 6.7 U1 Support

Posted: Oct 17, 2018 4:17 pm
by rendest
We can confirm it works (upgrade both VCSA and ESX to 6.7u1 in lab)

Re: vSphere 6.7 U1 Support

Posted: Oct 17, 2018 8:05 pm
by jorgedlcruz
Tried on the Home Lab, working like a charm.

Thank you Anton!