Discussions specific to the VMware vSphere hypervisor
Post Reply
timmi2704
Enthusiast
Posts: 92
Liked: 3 times
Joined: Jan 14, 2014 10:41 am
Full Name: Timo Brandt
Contact:

CBT reset still required?

Post by timmi2704 »

Hi forum!

I was just wondering, whether the CBT reset after a disk size change is still required (vSphere environment).
As far as I know, this behaviour was implemented as a workaround to a nasty VMware bug.
According to our technical contact at VMware this is not neccessary any more with the latest vSphere 6.5 release.
Is there any further information on this?

Thanks for that :D

Gostev
SVP, Product Management
Posts: 27411
Liked: 4541 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: CBT reset still required?

Post by Gostev »

Correct, not required.

JoshuaPostSAMC
Expert
Posts: 124
Liked: 21 times
Joined: Jul 30, 2015 7:32 pm
Contact:

Re: CBT reset still required?

Post by JoshuaPostSAMC »

Gostev, that should apply to even 5.5 as long as it has the update to correct the problem, right?

In that case, we can change the registry setting so Veeam stops resetting CBT
https://www.veeam.com/kb1940

──────────────────────────────────────────────────────────
Veeam Backup & Replication v8 and Later
──────────────────────────────────────────────────────────

Veeam Backup and Replication 8 has a built-in solution for this issue. Veeam Backup & Replication resets CBT for any resized VMware disk to prevent corruption. If ESXi hosts are patched against this issue, this behavior may no longer be desirable. To disable automatic CBT reset upon virtual disk size change, create the following registry value on the Veeam Backup Server (requires v8 Update 2 or later):

Key: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication
Type: REG_DWORD
Value name: ResetCBTOnDiskResize

Set this DWORD value to 0. To apply the registry change, make sure no jobs or restores are running, then restart the Veeam Backup Service.

timmi2704
Enthusiast
Posts: 92
Liked: 3 times
Joined: Jan 14, 2014 10:41 am
Full Name: Timo Brandt
Contact:

Re: CBT reset still required?

Post by timmi2704 »

Efficiency at its best!
Thanks Anton, thanks Joshua. RegKey is set.

Maybe B&R will detect current patch level and reset CBT only if really neccessary some day ;)

Frosty
Expert
Posts: 187
Liked: 42 times
Joined: Dec 22, 2009 9:00 pm
Full Name: Stephen Frost
Contact:

Re: CBT reset still required?

Post by Frosty »

Am just completing the build of our new Veeam-based backups environment, and I found this note from when we updated our old setup to VBR 8.0:

As part of the upgrade to VBR v8.0 the following Registry Key was created:
HKLM\Software\Veeam\Veeam Backup and Replication
ResetCBTOnDiskResize (REG_DWORD) = 0

Having read up on this and having found this thread, I've concluded:
(a) that if we do set this registry key, backups will be more efficient in cases where we resize a disk; but
(b) we might NOT want to set this key, so that in the event that some oddball CBT issue reappears in vSphere, we'll be better protected

I'm thinking to not bother adding this key. I prefer safety and reliability over performance.

Gostev
SVP, Product Management
Posts: 27411
Liked: 4541 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: CBT reset still required?

Post by Gostev »

Not a bad choice. I mean, how often do we resize those disks anyway :D

Post Reply

Who is online

Users browsing this forum: ncapponi and 8 guests