Hello,
We ar we are planning to upgrade our Vcenter to 8.0.2 but commvaul support only 8.0.1. Anyone know when Vcenter 8.0.2 wil be supported?
Our Commserver running on SP 11.32.28.
Best answer by wgrande
View original
- Vaulter
- 23 replies
-
12 December 2023
Hi
vCenter 8.0 update 2 will be validated with FR34 release time, but it should work from FR28 onward as we are not expecting any issues till now.
You can expect the release of FR34 on 15th Dec 2023 as per cadence.
Thanks,
Keshika Bisht
Hello,
The following versions are supported for vSphere, vCenter, vCenter Server Appliance, and ESX/ESXi:
4.1 or later, 5.0.x, 5.1.x, 5.5, 5.5.1, 5.5.2, 5.5.3, 5.5.6, 6.0, 6.0.1, 6.0.2, 6.0.3, 6.5, 6.7, 6.7.1, 6.7.2, 6.7.3, 7.0, 7.0.1, 7.0.2, 7.0.3, 8.0, 8.0.1
The validation was not successful, or the documentation is not updated?
BR,
Tamás
- Vaulter
- 737 replies
-
18 December 2023
Dear all,
You can check the other discussion:
Best Regards,
Sebastien
Userlevel 4
+9
- Vaulter
- 98 replies
-
19 December 2023
The Documentation page was meant to be updated to include stated certification for VMware 8.0.2. However, it was missed and is going to be actioned for change with priority.
The 2024 (11.34) documentation is already updated, and now include the vCenter 8.0.2 version.
But
vCenter 8.0 update 2 will be validated with FR34 release time, but it should work from FR28 onward as we are not expecting any issues till now.
The following versions are supported for vSphere, vCenter, vCenter Server Appliance, and ESX/ESXi:
4.1 or later, 5.0.x, 5.1.x, 5.5, 5.5.1, 5.5.2, 5.5.3, 5.5.6, 6.0, 6.0.1, 6.0.2, 6.0.3, 6.5, 6.7, 6.7.1, 6.7.2, 6.7.3, 7.0, 7.0.1, 7.0.2, 7.0.3, 8.0, 8.0.1
BR
Userlevel 4
+9
- Vaulter
- 98 replies
-
9 January 2024
- Answer
Regarding VMware 8.0.2, please note that VMware announced a CBT issue on their side to be aware of under this kb article, https://kb.vmware.com/s/article/95940. This issue could result in VMware's CBT feature losing track of data changed on the VMDK when the disk is hot-extended. They will be addressing it within ESXi 8.0p03 and 8.0u3.
Commvault has an existing CBT validation check in place within the product to reset CBT in specific situations. However, it is currently being reviewed to determine if it addressed the uniqueness of this VMware bug.
It's currently suggested to transition to a Full Backup schedule compared to leveraging Synthetic Fulls until the advanced detection feature can be confirmed to cover the CBT reset for specific VMDKs only. If you're otherwise unable to modify the scheduling, it's recommended to investigate within VMware reports for VMs that have had VMDK sizes extended while on 8.0.2. If you locate a specific VM, you should perform a Full of just that VM. This process should continue until we complete the validation of the CBT validation feature and report an update here (or in other locations.)
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.
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.”
Yestoday we have upgraded vCenter to 8.0.2 and with SP11.32.43 i dont have any issue with vmbackup.
Reply
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.