VMware vSphere • Re: vCenter 8.0 Update 3 is out. Does this need QA approval?

Right, but CBRC looks to be a host-wide feature which configuration parameters thus affect all VMs on the host, not just those few static ones. From the error it looks like the ESXi host is trying to enable caching for VMs that should not be using one, or something along these lines.

Plus QA does not see any issues with VSAN in their U3 labs (which do not have Horizon). So it does appear to be specific to environments with Horizon present, and the likely cause is a regression from the above-mentioned CBRC bug fix.

Hi, I just wanted to thank you for pointing me in the right direction.

The problem we were experiencing with 8.0U3 and VEEAM 12.1.2 was indeed due to the View Storage Accelerator option in VMware Horizon.

We have desktop pools that had the View Storage Accelerator turned on that were causing the issue.

The desktop pools in question weren't instant clone pools, they were full fat VM pools that had some individual users assigned, but we did back them up on the hourly backup.

You don't really need the VSA turned on for those pools and we certainly don't need it on with our storage speed anyway for those VMs, so we turned off the VSA on the pool and powered down the desktops. View would get rid of the digest disks on the VMs then automatically power them back on (due to power policy).

After this was done, the CBRC messages went away during VEEAM backup.

Statistics: Posted by vfwdit — Aug 15, 2024 1:24 pm

---