vSphere 6.7 U1 Support

[andrew.penniman]

KB2443 has listed vCenter 6.7 U1 as unsupported for an annoyingly long time. That article claims that 6.7 U1 will be supported with VBR 9.5 Update 4. I don't suppose anybody has an inkling of when Update 4 might be released, eh?

I am trying really, really hard to stay on 6.5 but with holidays and the all-important ski season coming up, my maintenance windows will very soon disappear for a while. I am debating whether to upgrade to ESXi/vCenter 6.7 U1 and implement the VEEAM workaround or stick with 6.5 and until VEEAM supports it. I get itchy and uncomfortable running non-current hypervisors....

https://www.veeam.com/kb2443

[andrew.penniman]

KB2443 has listed vCenter 6.7 U1 as unsupported for an annoyingly long time.

Wait, was 6.7 U1 really just released on the 16th?! I can hardly call that "unsupported for an annoyingly long time" and I apologize to the Veeam team for saying so. My sense of time seems to be off...

[evilaedmin]

Wait, was 6.7 U1 really just released on the 16th?! I can hardly call that "unsupported for an annoyingly long time" and I apologize to the Veeam team for saying so. My sense of time seems to be off...

Same here! It was "prematurely" announced at VMworld in August.

I believe VMware customers should give feedback to their account teams that it is NOT acceptable that major partners such as Veeam do not have access to prerelease code, or early access to GM code, in order to support releases on Day 1.

[jamerson]

Hi guys
the reg edit does works fine for us, however the speed during the backup drops from 140MB/S til 7MB/S.
any suggestions why? before the update we could pick 140MB till 220MB.

VEEAM is 9.5.0.1922 thank you

[Trelor]

KB2443 has listed vCenter 6.7 U1 as unsupported for an annoyingly long time. That article claims that 6.7 U1 will be supported with VBR 9.5 Update 4. I don't suppose anybody has an inkling of when Update 4 might be released, eh?

I am trying really, really hard to stay on 6.5 but with holidays and the all-important ski season coming up, my maintenance windows will very soon disappear for a while. I am debating whether to upgrade to ESXi/vCenter 6.7 U1 and implement the VEEAM workaround or stick with 6.5 and until VEEAM supports it. I get itchy and uncomfortable running non-current hypervisors....

https://www.veeam.com/kb2443

I sat in on a session for Update 4 for Veeam @ VMworld in August they said Q4; either November of December (Two presenters one was November the Other December). However the features that they demoed during the session are worth the wait....just wait and see .

[Gostev]

@Jamerson we did not observe this in our lab nor had similar reports from other customers, so please contact support for the investigation.

[jamerson]

@Gostev i've got it sourted out, after the update the VEEAM was confused and the ISCI drive letter was changed from F to E which caused the database confusion.
i end up creating a new job and the speed i s back to 240MB/S
Thank you

[Frosty]

I'm also hanging on and waiting for VBR v9.5 U4, so I can pair it with vSphere v6.7 U1.
I know others have been happy with the Regedit workarounds, but I prefer to avoid such things.

[danswartz]

Feeling very stupid here, but when I try entering 6.7.1 = 6.7 as the data for the new key, I get an error from regedit that "Data of type MULTI_REG_SZ cannot contain empty strings". What am I missing?

EDIT: after putting quotes around the above string and retrying, I still get the error from regedit, but now the backup works?

[Gostev]

Quotes are not needed for sure. I just checked on my Windows 10 desktop and I am not getting this error - see if you get the same error on any other computer?

[jc_virtual]

hi i have the same error from regedit Server 2012R2
after reboot the Server Backup is working fine !
Thank you very mutch!

[feky777]

No quotes needed. Put new line after string and it should be fine. No error then.

[abarhorst]

For planning purposes, do we have a rough timeline for completion of full regression testing? For us, the benefits from U1 are worth the slight risk with Veeam, if the regression testing passes.

[danswartz]

By new line, do you mean \n? If so, it would be nice if either of the posts telling what to do had said so. That said, this must be a bug in regedit, as I did get the error pop-up, yet the avoidance seems to take effect.

[jamerson]

@danswartz you error is if you copy a space in the code. Windows correct it though.
just make sure to restart the VEEAM service so the VEEAM would see the new reg code.
otherwise just reboot the server.

[danswartz]

that's good to know, but it shouldn't have been posted with spaces in it, no?

[jamerson]

@danswartz its not about the spaces been posted, you've had probably copied the spaces. its not a big deal at all.
Windows does correct that though.

[Novox]

Is the "6.7.1 = 6.7" supposed to include spaces or not? My windows doesn't "correct" this to have no spaces, and on another site

https://nolabnoparty.com/en/veeam-backu ... -update-1/

, the workaround is described without spaces.

Thank you,
~Bill

[Gostev]

It does not matter, as spaces will be stripped out.

[Novox]

With the registry workaround, I am unable to add a new 6.7 U1 host.

I receive the error:


What might be wrong?

Thank you.

[Gostev]

This error is unrelated to the API compatibility issue discussed in this thread, so please contact support for troubleshooting.

[Novox]

Will do, thank you.

Update... jumbo frames on the VM host was making Veeam angry.

[ahmad-1234]

you can solve these problem by adjusting the combatability of the VM in the job to (13) instead of (14) by adjusting the vmx file
these step will be temporally until veeam finished with update 4.

[mentalinc]

Is there a known workaround for Ubuntu 18.04 LTS?

[Gostev]

Sorry, what are you talking about?

[mentalinc]

Sorry I missed the words " on the backup server".
Thought the regedit needed to be made on all endpoints.
All working ignore the Ubuntu request

[whysyn]

Hello Gostev,

Any update on regression testing since 19 October? We're holding off on updating all of our customer's vSphere environments until Veeam officially supports 6.7 U1, but some customers are getting antsy about not being on the latest version (and we all know there's no arguing technical merits with a customer who wants something shiny!).

Thanks!

[evilaedmin]

I don't mean to derail your argument, but full support for the HTML5 client and no more flash, isn't just shiny!

[jamerson]

VMware has released a new build ESXi-6.7.0-20181104001 (Build 10764712) is this reg confi will works with this patches?

[Gostev]

Any update on regression testing since 19 October? We're holding off on updating all of our customer's vSphere environments until Veeam officially supports 6.7 U1, but some customers are getting antsy about not being on the latest version (and we all know there's no arguing technical merits with a customer who wants something shiny!).

We did not find any issues in our own labs yet, however we have a number of active support cases under investigation from customers who already upgraded, so I would not recommend updating right now unless your customers want to potentially join that crowd (which is actually great for us, as we do need early adopters to find those corner case issues anyway).