Changed block tracking errors

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Posts: 3
Comments: 4

I am getting the following error. I am running a Windows 2008 R2 Hyper-V cluster with iSCSI SAN backend for the CSV. Does anybody know a fix for this? Is it even necessary?

--------------------
Log Entry Details
--------------------
Type: Warning
Date and time: 9/19/2012 8:50:27 PM
Backup plan: FILESERVER-DC
Task: Simple backup (Full)
Managed entity type: Virtual machine
Managed entity: FILESERVER-DC
Machine: HYPERV.LOCAL.NET
Code: 9,764,948(0x950054)
Module: 149
Owner:
Message:
Failed to enable Changed Block Tracking for virtual machine 'FILESERVER-DC' because this machine does not support it.
Additional info:
--------------------
Error code: 84
Module: 149
LineInfo: d1ab7fa1e56ec79b
Fields: $module : disk_bundle_vs_32256
Message: Failed to enable Changed Block Tracking for virtual machine 'FILESERVER-DC' because this machine does not support it.
--------------------
--------------------

Thu, 09/20/2012 - 02:32
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Posts: 27
Comments: 1940

There is an option regarding CBT in backup options (on 'changed block tracking' page). Try to set it to 'no dot use' as it's apparently vmware-specific.

Thu, 09/20/2012 - 03:43
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Member
Posts: 1
Comments: 70

Jason fyi, i experienced this issue after upgrading from ABR11 to ABR11.5.
Disabling CBT was not possible, because the setting was not saved.
Cloning the backup plan did not help either, but instead of recreating it i found a workaround:
- export the backup plan
- import the backup plan
- delete the original backup plan

Mon, 11/19/2012 - 16:52