Home / AWS Backup errors

VMware — Change Block Tracking invalid or unavailable

Information COMPLETED AWS Backup
What AWS reports
cbt was not availablechange block trackingcbt data was invalid

Matched case-insensitively — AWS wraps these phrases in longer messages that vary by resource type.

What is actually happening

The backup still completed — AWS fell back to its own change-detection mechanism. But without CBT, incremental backups are slower and heavier than they should be, so this is worth fixing even though nothing failed.

How to fix it

  1. In vSphere, select the powered-off VM → Edit Settings → Options → Advanced/General → Configuration Parameters.
  2. Confirm ctkEnabled is set to True.
  3. Check the host is ESXi 4.0 or later and the VM is hardware version 7 or later.
  4. If CBT is on and versions are current, power the VM off and on again, verify CBT is still enabled, then re-run the backup.
  5. If the message persists, reset CBT following VMware's documented procedure.

What AWS documents

AWS notes the incremental backup completed using its proprietary change detection, and gives the vSphere steps to verify ctkEnabled.

Source: AWS Backup Developer Guide — Troubleshoot VM issues

Stop finding this one failure at a time

BackupLens watches every AWS Backup job across every region, matches each failure against this catalogue automatically, and sends you the cause and the fix — instead of a job list you have to read line by line at 3am.

Start free trial