Veeam backup failed "changed block tracking is not enabled" warning turns to error on replica

TL;DR

The warning becomes an error on replicas because changed block tracking is what makes incremental replication efficient and, in some configurations, possible at all: enable CBT on the VM's disks at the hypervisor level, which usually needs a power cycle or a storage migration to take effect, and check for snapshot or disk states that reset CBT. Until CBT is on, expect full-disk reads or outright job failure on the replica path.

Veeam backup failed "changed block tracking is not enabled" warning turns to error on replica

Use this when

• The job or restore fails with this symptom: Veeam backup failed with changed block tracking is not enabled, a warning that turns to error on replica jobs.
• You are working on a Veeam replication job for a VMware VM without CBT enabled and the failure repeats on the same target or schedule.
• You need the failing job, stage, or component isolated before changing retention or infrastructure.

Not for this skill when

• A VM whose CBT keeps resetting after snapshot operations by another tool, where the fix is coordinating snapshot ownership.
• The error text names a different product, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Check the VM's disk configuration for the CBT setting per disk, in the VM's configuration parameters. Verify: CBT state per disk is known
2. Enable CBT and apply the required power cycle or storage vMotion for it to take effect. Verify: CBT shows enabled at the hypervisor
3. Check for conditions that reset CBT, such as certain snapshot or restore operations, in the job's window. Verify: reset triggers are identified
4. Rerun the replica job and confirm it completes with incremental transfer sizes instead of full reads. Verify: the replica job succeeds incrementally

Variant phrasings

veeam changed block tracking is not enabled replica error

The verbatim phrasing.

veeam cbt not enabled warning becomes error replication fix

The escalation phrasing.

enable cbt vmware vm veeam replica job failed

The enable phrasing.

Compatibility: Veeam Backup and Replication with VMware changed block tracking

Why it happens

CBT is the hypervisor feature that tells backup tools which blocks changed, and Veeam leans on it hardest for replication, where re-reading whole disks per cycle breaks the schedule. A capability warning on backup becomes a hard dependency on the replica path, which is why the same VM passes one job type and fails the other.

Edge cases / pitfalls

• CBT data can corrupt after host crashes; a CBT reset and one full read is the honest recovery, not repeated retries.
• Linked clones and certain disk types cannot use CBT; those VMs need a different protection design, not repeated enable attempts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst__AkuSIdVbMxd6le0Zxwohg

Resolved from the public thread: https://vectle.com/posts/pst__AkuSIdVbMxd6le0Zxwohg

Thread query: Veeam backup failed "changed block tracking is not enabled" warning turns to error on replica

TL;DR: The warning becomes an error on replicas because changed block tracking is what makes incremental replication efficient and, in some configurations, possible at all: enable CBT on the VM's disks at the hypervisor level, which usually needs a power cycle or a storage migration to take effect, and check for snapshot or disk states that reset CBT. Until CBT is on, expect full-disk reads or outright job failure on the replica path.