Hello
Veeam announced compatibility-level support for vSphere 8.0 U2 with the latest VBR release v12 P20230718.
https://www.veeam.com/kb2443?ck=1676356277100
This is great and before 12.1 too.
If upgraded, be aware of a nasty CBT bug in 8.0.2: https://kb.vmware.com/s/article/95965?lang=en_US
I did not found any Veeam KB regarding this:
“vSphere 8.0 Update 2 changed the way disks are extended. The changes were specifically intended to make certain disk hot-grow operations more efficient.
This has unintentionally resulted in incorrect tracking of changes, leading to backups not capturing the right data and, consequently, corrupt restores.
This issue will only be seen if backups are taken after the VM disk is hot extended. Simply resizing a VM with the VM powered off will not cause this.
This problem can happen with disks of all datastore types (VVOL, VMFS, NFS, vSAN). “
I better read this. Getting ready to upgrade to 12.1 and 8.2
I better read this. Getting ready to upgrade to 12.1 and 8.2
It is a bad bug but not as bad as you would think if you followed the KB to work around it. Veeam is working on fixing this from what I understand.
Right, Running an active full after each hot expand might be a bit of a pain though. Especially with the size of my file servers.
I think I may wait a while.
Right, Running an active full after each hot expand might be a bit of a pain though. Especially with the size of my file servers.
I think I may wait a while.
While that would be a pain yes, I was referring to the cold expansion where the VM is powered off then you expand the disk. 
Right, Running an active full after each hot expand might be a bit of a pain though. Especially with the size of my file servers.
I think I may wait a while.
While that would be a pain yes, I was referring to the cold expansion where the VM is powered off then you expand the disk.
That’s actually WORSE for me lol. 24/7 shop of critical systems. I get small patching windows, but when a disk fills up nobody wants to power down a server. Especially as others are reading for it, or an another drive etc.
Knowing about this is half the battle though. For some it won’t be an issue at all
I better read this. Getting ready to upgrade to 12.1 and 8.2
It is a bad bug but not as bad as you would think if you followed the KB to work around it. Veeam is working on fixing this from what I understand.
you mean VMware? There is no info from Veaam about this bug.
VMware plan to correct this issue in 8.0.3, with no available ETA today.
An I think this is a really bad bug, because you will only face it, when you need restore something, Surbackup will detect is, but lot of customers don’t use that.
And I thin there should be more info and communication about this...
I better read this. Getting ready to upgrade to 12.1 and 8.2
It is a bad bug but not as bad as you would think if you followed the KB to work around it. Veeam is working on fixing this from what I understand.
you mean VMware? There is no info from Veaam about this bug.
VMware plan to correct this issue in 8.0.3, with no available ETA today.
An I think this is a really bad bug, because you will only face it, when you need restore something, Surbackup will detect is, but lot of customers don’t use that.
And I thin there should be more info and communication about this...
Yes, VMware is going to address it, but Veeam is also aware of it and looking in to it as well from what I have heard.
I agree about more communication about it and am not dismissing it being a bad bug as we are at least aware from the KB VMware published.
@molnar.tamas Actually this bug has been discovered by Veeam. All details can be found in this post and the following replies:
https://forums.veeam.com/post505571.html#p505571
The patch from VMware was planned for last week so we should see it very soon.
@Chris.Childerhose It's a VMware bug which cannot be fixed by Veeam. The only workaround from Veeam's side was to reset CBT for full backups.
@molnar.tamas Actually this bug has been discovered by Veeam. All details can be found in this post and the following replies:
https://forums.veeam.com/post505571.html#p505571
The patch from VMware was planned for last week so we should see it very soon.
@Chris.Childerhose It's a VMware bug which cannot be fixed by Veeam. The only workaround from Veeam's side was to reset CBT for full backups.
Yes, I get that and understand. I am just saying that if anyone is eager to test U2 they can, and it works minus the CBT issue. I don’t hot extend my VMs in my lab so I don’t have the bug and can use this release.
I guess that patch hasn’t arrived yet…… Was ready to upgrade but I’ll continue to hold tight.
I guess that patch hasn’t arrived yet…… Was ready to upgrade but I’ll continue to hold tight.
Yeah, they pulled back and now it is going to be in P3 and U3 according to the KB article.
I guess that patch hasn’t arrived yet…… Was ready to upgrade but I’ll continue to hold tight.
Yeah, they pulled back and now it is going to be in P3 and U3 according to the KB article.
I didn’t see that, thanks for the post. I’ll consider going to U1 or staying on 7.3 a little while longer. It’s running good and I like my CBT not broken!
I guess that patch hasn’t arrived yet…… Was ready to upgrade but I’ll continue to hold tight.
Yeah, they pulled back and now it is going to be in P3 and U3 according to the KB article.
I didn’t see that, thanks for the post. I’ll consider going to U1 or staying on 7.3 a little while longer. It’s running good and I like my CBT not broken!
Yeah, U2 on vCenter is ok but go just to U1 on hosts. You are safe with that configuration.
I guess that patch hasn’t arrived yet…… Was ready to upgrade but I’ll continue to hold tight.
Yeah, they pulled back and now it is going to be in P3 and U3 according to the KB article.
I didn’t see that, thanks for the post. I’ll consider going to U1 or staying on 7.3 a little while longer. It’s running good and I like my CBT not broken!
Yeah, U2 on vCenter is ok but go just to U1 on hosts. You are safe with that configuration.
My brain will suffer. haha. I like things the same. but you are right, that’s an option forsure.
I guess that patch hasn’t arrived yet…… Was ready to upgrade but I’ll continue to hold tight.
Yeah, they pulled back and now it is going to be in P3 and U3 according to the KB article.
I didn’t see that, thanks for the post. I’ll consider going to U1 or staying on 7.3 a little while longer. It’s running good and I like my CBT not broken!
Yeah, U2 on vCenter is ok but go just to U1 on hosts. You are safe with that configuration.
I think this combination may be an option if you are not running PROD, because in case of any problem, the VMware support will ask you to upgrade the latest version on the given main version, so you will be forced to use ESXi 8.0u2
If you are running PROD, then you need to use vCenter 8.0u2, and ESXi 7.0u3 for a supported and maintainable config.
Also be informed, I got info from VMware support:
This issue affecting ESXi only.
80U3 version ETA on this Summer.
So you can move forward with the vCenter upgrades, and ESXi upgrades need to be planned for the summer.
Please be informed, I got info from VMware support:
This issue affecting ESXi only.
80U3 version ETA on this Summer.
So you can move forward with the vCenter upgrades, and ESXi upgrades need to be planned for the summer.
Great news. I’d advise to wait until the fall to see if there are any other issues added with this release
Please be informed, I got info from VMware support:
This issue affecting ESXi only.
80U3 version ETA on this Summer.
So you can move forward with the vCenter upgrades, and ESXi upgrades need to be planned for the summer.
Great news. I’d advise to wait until the fall to see if there are any other issues added with this release
Yes, that is always a good idea due to updates tending to break something else. We will see how well Broadcom’s QA is. 
8.0u2 B was released on 1th of March, and the VMwares KBs were also updated, that this version is the corrected, we don’t need to wait for the 8.0u3:
https://kb.vmware.com/s/article/95965
“In order to resolve this issue, update to ESXi 8.0 Update 2b or newer.”
8.0u2 B was released on 1th of March, and the VMwares KBs were also updated, that this version is the corrected, we don’t need to wait for the 8.0u3:
https://kb.vmware.com/s/article/95965
“In order to resolve this issue, update to ESXi 8.0 Update 2b or newer.”
Yes, this release fixes that bug with CBT.
Very interesting. I’ll wait a bit and add to the test environment.
