ESXi 6.0 CBT issue

[saintdle]

Just got off the phone with VMware.

They have a patch and its scheduled to be released on Thursday May 14th!

Sit's here, patiently waiting for tomorrow

[benbour]

We had our exchange server dismount a store with corruption too. I'm wondering if this is related or a separate issue. The store is way too big and it did this before it was virtualized.

It does backup, but the job has CBT disabled. Even though CBT is disabled, because it is enabled on the VM itself, would this cause issue?

[LorettoCNY]

Patch was released today!

[benbour]

I'm downloading and going to apply asap. I'll post back.

[rmcmillan]

I've downloaded and applied to 2 of my 4 hosts so far.

Who wants to go first with running a full exchange/oracle/sql/active directory backup and report back?

[Trelor]

I am testing the AD / SQL backups now. I do not want to test exchange in the middle of the day the AD is the secondary server and SQL is my personal test server. Will report back..

AD Server 1 before ESXi Patch: OK, legacy mode invalid CBT data.
AD Server 2 before ESXi Patch: Error, legacy mode invalid CBT data (when I don't get the following error). Unable to release guest. Error: Unfreeze error: [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [NTDS]. Class ID: [{b2014c9e-8711-4c5c-a5a9-3cf384484757}]. Instance ID: [{9d60d02c-299f-401e-af1a-0f8a479faa01}]. Writer's state: [VSS_WS_FAILED_AT_POST_SNAPSHOT]. Error code: [0x800423f4].]
Error: Unfreeze error: [Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [NTDS]. Class ID: [{b2014c9e-8711-4c5c-a5a9-3cf384484757}]. Instance ID: [{9d60d02c-299f-401e-af1a-0f8a479faa01}]. Writer's state: [VSS_WS_FAILED_AT_POST_SNAPSHOT]. Error code: [0x800423f4].]


AD Server 1 after ESXi Patch: Success, legacy mode invalid CBT data. Should reset now when I redo the backups.
AD Server 2 after ESXi Patch: Success, legacy mode invalid CBT data. Should reset now when I redo the backups.


AD Server 1 after ESXi Patch After CBT Reset: Success, VALID CBT data.
AD Server 2 after ESXi Patch After CBT Reset: Success, VALID CBT data.

[benbour]

good to know, Thanks!

[rmcmillan]

AD Server 1 after ESXi Patch After CBT Reset: Success, VALID CBT data.
AD Server 2 after ESXi Patch After CBT Reset: Success, VALID CBT data.

Just to clarify did you have to manually reset CBT data, or did you simply run the backup again and it was reset automatically?

[Trelor]

Just to clarify did you have to manually reset CBT data, or did you simply run the backup again and it was reset automatically?

the CBT data reset was automatic. Went to edit my post but it would not longer let me. I have also successfully backed up Exchange without and error messages in the windows event log like there has previously been.

[rmcmillan]

Thanks!

[eahernand249]

I just updated one of my VMware ESXi 5.5 hosts to ESXi 6.0 with the CBT fix and my VMs are backing up perfectly.
Upgrade from 5.5 was done via Update Manager, first Deployed the v6.0 ESXi image and then applied the CBT patch.
Seems that backup times are a little faster.

[benbour]

I have also had successful backups after applying patch to 6.0 hosts via update manager.