CBT bug in 5.5/6 mixed environment questions

[rreed]

Afternoon all. Very grateful for the Community Forums Digest! We disabled CBT in our backup jobs per the workaround and went about our business. However, our VMware environment is mixed; one vCenter 6 (appliance), some hosts are 6u1a, some are 5.5u3something (just before the u3 fix patch but we're patching as we speak). Anyways, I disabled CBT in all our jobs, though some jobs are only 5.5 hosts, while some jobs were in our cluster w/ mixed 5.5/6 hosts (we were smack dab in the middle of upgrading when the alert went out and stopped upgrade work immediately).

Did I need to disable CBT in my backup jobs for VM's on our 5.5 hosts? If not, do I simply re-enable it in my jobs and go about my day? Do I need to run the CBT reset script for our 5.5 hosts? We have the 6u1b (or whatever) patch added to our Update Mangler in VMware and applying it to our affected hosts, and as we continue to upgrade 5.5 hosts to 6, they're getting the patch before being released back to production. Anything special we need to do w/ those "directly-patched" hosts' VM's once the VM's are migrated back over?

It kind of made a mess discovering this right in the middle of our upgrade process, I'm just trying to make sure I haven't added unnecessary work, or end up w/ at-risk VM's getting their CBT missed after a patched 6 upgraded host.

[Gostev]

Did I need to disable CBT in my backup jobs for VM's on our 5.5 hosts? If not, do I simply re-enable it in my jobs and go about my day?

You did not need to do that, so yes: simply go ahead re-enable it, nothing else needs to be done here. Thanks!

[rreed]

Many thanks, Gostev. I just finished re-running the script against all our VM's on our v6 cluster just for good measure and re-enabled CBT in ALL our jobs. I'm hoping that should be good, but will likely do some test restores next week to verify.