Discussions specific to the VMware vSphere hypervisor
Gostev
Veeam Software
Posts: 23099
Liked: 2913 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

vSphere 6.7 U1 Support

Post by Gostev » Oct 16, 2018 8:43 pm 7 people like this post

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.

ngreen
Novice
Posts: 5
Liked: never
Joined: Jun 15, 2017 2:48 pm
Full Name: Neil Green
Contact:

Re: vSphere 6.7 U1 Support

Post by ngreen » Oct 17, 2018 12:57 pm

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.

mwvme
Veeam Software
Posts: 122
Liked: 24 times
Joined: Dec 05, 2015 10:19 pm
Full Name: Michael White
Location: Calgary, Alberta Canada
Contact:

Re: vSphere 6.7 U1 Support

Post by mwvme » Oct 17, 2018 1:03 pm 1 person likes this post

I reproduced this issue with only vCenter updated and hosts still at 6.7. You need to wait, unfortunately.

Michael
Michael White
Field Product Manager
https://notesfrommwhite.net
@mwVme

tka
Novice
Posts: 5
Liked: 2 times
Joined: Apr 04, 2014 6:24 am
Full Name: Tim
Location: Cologne, Germany
Contact:

Re: vSphere 6.7 U1 Support

Post by tka » Oct 17, 2018 1:22 pm 1 person likes this post

ESXi 6.7 U1 with "old" vCenter works - at least with SAN transport.

Trelor
Influencer
Posts: 12
Liked: 3 times
Joined: Apr 27, 2015 6:02 pm
Contact:

Re: vSphere 6.7 U1 Support

Post by Trelor » Oct 17, 2018 1:28 pm

How are you running a version of vCenter that is behind ESXI that is not even supported

mwvme
Veeam Software
Posts: 122
Liked: 24 times
Joined: Dec 05, 2015 10:19 pm
Full Name: Michael White
Location: Calgary, Alberta Canada
Contact:

Re: vSphere 6.7 U1 Support

Post by mwvme » Oct 17, 2018 1:30 pm 2 people like this post

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
Michael White
Field Product Manager
https://notesfrommwhite.net
@mwVme

tka
Novice
Posts: 5
Liked: 2 times
Joined: Apr 04, 2014 6:24 am
Full Name: Tim
Location: Cologne, Germany
Contact:

Re: vSphere 6.7 U1 Support

Post by tka » Oct 17, 2018 1:36 pm 1 person likes this post

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

tka
Novice
Posts: 5
Liked: 2 times
Joined: Apr 04, 2014 6:24 am
Full Name: Tim
Location: Cologne, Germany
Contact:

Re: vSphere 6.7 U1 Support

Post by tka » Oct 17, 2018 2:07 pm

I did an Update via VCSA Installer wizard from 6.5 to 6.7 u1 today and veeam failed afterwards.

stefanbrun
Service Provider
Posts: 23
Liked: 3 times
Joined: Apr 26, 2011 7:36 am
Full Name: Stefan Brun | MSupport Networks AG
Location: Lengnau, Switzerland
Contact:

Re: vSphere 6.7 U1 Support

Post by stefanbrun » Oct 17, 2018 2:18 pm

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.

Gostev
Veeam Software
Posts: 23099
Liked: 2913 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: vSphere 6.7 U1 Support

Post by Gostev » Oct 17, 2018 2:26 pm 1 person likes this post

Updated the original post with the workaround.

stefanbrun
Service Provider
Posts: 23
Liked: 3 times
Joined: Apr 26, 2011 7:36 am
Full Name: Stefan Brun | MSupport Networks AG
Location: Lengnau, Switzerland
Contact:

Re: vSphere 6.7 U1 Support

Post by stefanbrun » Oct 17, 2018 2:46 pm

Thx Gostev, workaround does the job.

Gostev
Veeam Software
Posts: 23099
Liked: 2913 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: vSphere 6.7 U1 Support

Post by Gostev » Oct 17, 2018 2:47 pm

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.

ddenson
Lurker
Posts: 1
Liked: 1 time
Joined: Sep 10, 2013 4:12 pm
Full Name: Drew Denson
Location: Madison, Wisconsin
Contact:

Re: vSphere 6.7 U1 Support

Post by ddenson » Oct 17, 2018 3:39 pm 1 person likes this post

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

rendest
Influencer
Posts: 19
Liked: 5 times
Joined: Feb 01, 2017 8:36 pm
Full Name: Stef
Contact:

Re: vSphere 6.7 U1 Support

Post by rendest » Oct 17, 2018 4:17 pm

We can confirm it works (upgrade both VCSA and ESX to 6.7u1 in lab)

jorgedlcruz
Veeam Software
Posts: 153
Liked: 63 times
Joined: Jul 17, 2015 6:54 pm
Full Name: Jorge de la Cruz Mingo
Contact:

Re: vSphere 6.7 U1 Support

Post by jorgedlcruz » Oct 17, 2018 8:05 pm

Tried on the Home Lab, working like a charm.

Thank you Anton!

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 35 guests