vSphere 6.7 U1 Support

[edvJB]

Dear Sirs and Madam

would this workaround work also for VCenter 6.7 U2 ?
Yesterday we upgraded to version: Version 6.7.0.20000

I tried to set the string in registry: 6.7.2 = 6.7

But seems not to be working.
Does it make sense to file a support case?

Sincerely
Denis

[wishr]

Hi Denis,

Is it build 10244745? If so, then it's a Full Patch for vCenter Server Appliance 6.7 Update 1. Please review the posts above, especially one of the users confirmed the workaround does the job in a similar environment.

Could you please let us know what errors you are getting? If those differ from the one mentioned on the first page of this thread it's definitely recommended to open a support case. Btw, Have you tried to reboot the B&R server after applying the workaround as suggested in the KB article?

Regards,
Fedor

[foggy]

When will be the Update 4 release date?

It should be shipped in a few weeks, as stated above.

[lazman]

Few weeks??? We have been waiting for 2 months! If they wait a little longer, another update comes out!
I installed a test VM with Windows Server 2019, when the VM is turned on VEEAM can not back it up. Is windows 2019 supported or should we wait for the update 4? This is the error that shows:

Code: Select all

"Failed to create VM snapshot. Error: CreateSnapshot failed, vmRef vm-12857, timeout 1800000, snName VEEAM BACKUP TEMPORARY SNAPSHOT, snDescription Please do not delete this snapshot. It is being used by Veeam Backup., memory False, quiesce True
Error: An error occurred while quiescing the virtual machine. See the virtual machine's event log for details."

[wishr]

Hi Lazman,

Windows Server 2019 support is also coming in Update 4, as per our 90 days platform support commitment.

Thanks!

[Gostev]

Few weeks??? We have been waiting for 2 months! If they wait a little longer, another update comes out!

Trust me, we too miss the good old days when vSphere updates were merely cumulative bug fix roll ups, and were supported by the shipping release automatically, without us having to do anything at all... because as soon as we have to make changes, the corresponding code has to wait for the immediate release vehicle.

[DonZoomik]

Few weeks??? We have been waiting for 2 months! If they wait a little longer, another update comes out!
I installed a test VM with Windows Server 2019, when the VM is turned on VEEAM can not back it up. Is windows 2019 supported or should we wait for the update 4? This is the error that shows:

Code: Select all

"Failed to create VM snapshot. Error: CreateSnapshot failed, vmRef vm-12857, timeout 1800000, snName VEEAM BACKUP TEMPORARY SNAPSHOT, snDescription Please do not delete this snapshot. It is being used by Veeam Backup., memory False, quiesce True
Error: An error occurred while quiescing the virtual machine. See the virtual machine's event log for details."

This is not likely a Veeam issue (occurs on normal snapshots as well), I've hit the same problem in testing and it's either inbox VSS writers or bad cooperation between Windows and VMware VSS provider.
Keep in mind that Windows Servers 2019 is not supported by VMware either.

[raudi]

Windows Server 2019 is supported starting with vSphere 6.5 to 6.7U1.

https://www.vmware.com/resources/compat ... _Guide.pdf

Page 137

And Version 6.7.0.20000 is Update 1...

Kind regards
Stefan

[DonZoomik]

Well it seems that it's today's news as I checked HCL just a few days ago and it was still in "Tech preview" phase.
Either way, I saw this timeout error on so far only test WS2019Core box. Inbox writers time out even via ordinary VMware snapshot request. I didn't try diskshadow for comparison though.

[ngreen]

We have a couple of test Windows Server 2019 VMs (GUI not core) and they are backing up just fine. VMs are running the latest VMware Tools 10.3.5 - no official word on 2019 support in the release notes, but might be worth upgrading the tools to test.

[DonZoomik]

Tools are already at 10.3.5...

[jamerson]

Is this version ESXi-6.7.0-20181104001-standard (Build 10764712) supported on the 3a ?
VMWare has released this 2018-11-09

Thank you

[wishr]

Hi Julien,

Yes, it is since it's the main branch.

Thanks

[NightBird]

Are you sure ? Because it’s post U1 build number so esx base contain U1 code too

[kmile]

Experienced the issue recently. Applied the registry as per the KB but did not work! The KB says in bold "Please, note that value and data fields should not contain any spaces."

I then checked this forum and the registry code here has spaces i.e. 6.7.1 = 6.7

Rebooted the server again and all good this time. I think the KB article needs to be corrected to say that the spaces are needed.

Hopefully, this will help someone.

Thanks,
Kamil

[wishr]

Hi NightBird,

VMware Express Patches for 6.7 GA version do not include previous Updates bits. 6.7 GA and 6.7 Updates are two different independent branches in terms of patches releases (while updates may include previous EPs, though). Build versions do not indicate any dependencies between those two. As Gostev mentioned, B&R U3a does support patched VMware 6.7 GA versions that currently exist.

Example:
ESXi 6.5 U1 Express Patch 4 - this is an EP for 6.5 U1
ESXi 6.5 EP 11 - this is an EP for 6.5 GA version
--
ESXi 6.7 U1 - Update 1 itself
ESXi 6.7 EP 05 - EP for 6.7 GA branch
No EPs yet for U1

Reference: https://kb.vmware.com/s/article/2143832

If it was an express patch for U1 then yes - we would probably not recommend installing it as of now keeping in mind the U1 API changes, but since it's an EP for the GA version you are safe to install it.

@Kamil, thanks for sharing the information - we'll take a look at that internally.

Thanks

[Yuya]

We run ESXi 6.7 on VMwareWorkstation 15 Player for verification purposes and we are running CentOS 7 as the guest OS.
An error occurred when installing Veeam Backup Free 9.5.0.1922 on a physical PC of Windows 10 Pro and backing up.
"Processing CentOS 7 Error: Object reference not set to object instance"
What are the possible causes?

I added the registry key with reference to the following KB and restarted, but it does not improve.
https://www.veeam.com/kb2784

Veeam: 9.5.0.1922
VMware: 6.7.0 Update 1 (Build 10302608)

[wishr]

Hi Yura,

Please make sure you've pressed Enter after entering the key value, so the pointer will jump to the next line and stay here, then press OK, then reboot the B&R server. If that won't help could you please try the key value with spaces before and after the "=" sign (please also ensure the pointer location as mentioned above), then reboot the server again and let us know the result.

Look forward to your reply!

BR,
Fedor

[NightBird]

Thanks for this clarification but I'm not totally agree with you.

ESX 6.7 EP05 apply to 6.7U1 too, for example to remediate the security issue of vmxnet3.

[lywwing]

Hi,
I am use Veeam Backup & Replication 9.5.0.1922, only backup VM guest which guest in local datastore get above error, if the guest located in SAN disk, no such error.
ESXi 6.7.0U1 "VMware ESXi, 6.7.0, 10302608"and vCenter 6.7.0 "version 6.7.0.20000"

Regards
Thanks...KEN

[wishr]

ESX 6.7 EP05 apply to 6.7U1 too, for example to remediate the security issue of vmxnet3.

Hi,

Yes, the EP5 patch remediates the vmxnet3 issue, but it does not include any API changes introduced by Update 1. So in our case, you can go ahead and update environments having a 6.7 GA version to EP5.

Thanks

[Alex Uryumtsev]

I am use Veeam Backup & Replication 9.5.0.1922, only backup VM guest which guest in local datastore get above error, if the guest located in SAN disk, no such error.
ESXi 6.7.0U1 "VMware ESXi, 6.7.0, 10302608"and vCenter 6.7.0 "version 6.7.0.20000"

Hi Ken,

It seems that you have faced with technical issue and it is hard to find out the root cause within the forum.

I would highly recommend you to contact our support team as they can investigate your log files.

If you have any questions left, let me know.

Alex

[DGrinev]

I am use Veeam Backup & Replication 9.5.0.1922, only backup VM guest which guest in local datastore get above error, if the guest located in SAN disk, no such error.
ESXi 6.7.0U1 "VMware ESXi, 6.7.0, 10302608"and vCenter 6.7.0 "version 6.7.0.20000"

Hey,

It's a known issue which is described in the existing big discussion here.
You will find a solution in the first post or if you contact the support team, they can help you to apply the fix. Thanks!

[Yuya]

Please make sure you've pressed Enter after entering the key value, so the pointer will jump to the next line and stay here, then press OK, then reboot the B&R server. If that won't help could you please try the key value with spaces before and after the "=" sign (please also ensure the pointer location as mentioned above), then reboot the server again and let us know the result.

Hi Fedor,

I tried these, but it did not resolve.

This is a screenshot of the registry.
Is there a problem?
https://imgur.com/6TJiLfw

Thanks,
Yuya

[wishr]

Hi Yuya,

That's strange.

Could you please give 6.7.1=6.7 one more try (without spaces)? Once again, please make sure to press enter before pressing OK, then restart the B&R server.

If that does not help I would recommend you to continue the investigation with our support team.

Thanks

[Crusher]

Hi,

it's working for me too.

Value was corrected in my case automatically (Win Srv 2012). But not the NAME !!!

@Yuya: Navigate to registry key. Press F2 or choose "rename" from context menu. Make sure there is no trailing blank. Hard to recognize, because it's at the end of the string. I started server several times, but still run into error.

OLD: "VMwareOverrideApiVersion "
NEW "VMwareOverrideApiVersion"

I copied string from a private support board. Maybe this helps.

greetz Crusher

[bovie2k]

Any update on supporting 6.7U1 ETA? I'd really like to patch my hosts. Last I heard it was 9.5 Update 4.

[Yuya]

Thanks everyone!
After paying attention to the space, after reregistering the registry key, the backup succeeded.

Thanks,
Yuya

[wishr]

Any update on supporting 6.7U1 ETA? I'd really like to patch my hosts. Last I heard it was 9.5 Update 4.

Hello everyone,

@Bovie, no updates yet on the Update 4 availability, but please stay tuned - we'll keep you updated.

@Yuya, thank you for the information, glad to see you've managed to resolve it.

BR,
Fedor

[KaramuHS]

Is there a compatibility matrix for the latest Veeam version vs vSphere/hosts somewhere?

The product specification is misleading:
"Veeam FULLY supports VMware vSphere 6.7, providing you with the confidence to upgrade to the latest version of VMware and take full advantage of the most modern technology and functionality to maintain Intelligent Data Management for the Hyper-Available Enterprise™."

Is only 6.7GA fully supported, or can we upgrade to EP-04 (prior to U1)?

I intend to build a new vCSA.