[SOLVED] Veeam: Failed change tracking (CBT)

Failed to flush change tracking data, using full scan to determine changes.

Failed to create change tracking time stamp for virtual disk file

I've encountered the above, after i added some new CSV to a cluster. The backup jobs have been running fine for ages before this.
As per say, this is not really a critical issue, since the backups just takes longer. Needless to say, i wanted it to function.


I tried:

• Reboot Nodes, Hosts, VMs
• Fully update
• Stop VeeamFCT service and Start it again
• Update hyper-v integration service
• Delete previous backups
• Run full backups
• Read Veeam forums
• Running Reset-HvVmChangeTracking

Din't work.


However!




The solution for me in this case, was fairly simple. I suspect the issue was an old store or data entry for the CSV, and therefor the CBT was not able to find the data needed. All of the above issues, is one and the same, and may only apply to some of your virtual machines or may apply to all of them.

All i had to do, was to reset CBT. You can do this, by stopping the veeamfct service and deleting the CTDB from regedit.

Heres how to:

1. Go into "Backup Infrastructure".
2. Rightclick on hyper-v node and select "Manage volumes"
3. Tick "Disable changed block tracking for this host"
4. Apply and do the same with the other nodes in your cluster.
5. Stop VeeamFCT Service, open cmd and run: sc stop veeamfct
6. Do 5. on all nodes.
7. Open regedit and find: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VeeamFCT\Parameters\CTDB
8. Export it, just in case.
9. Delete the entry
10. Go back into manage volumes in veeam and enable changed block tracking. (This should enable the service again, if not, enable them again)
11. Try run the job again. In some cases, you need to allow a couple of jobs to run before the changes take effect.

This time it should be successful.


Feel free to comment, if this helped you.