Comprehensive data protection for all workloads
Post Reply
bokinns
Novice
Posts: 7
Liked: never
Joined: Dec 14, 2009 5:26 pm
Full Name: Carlos Caberol
Contact:

Changed Block Traking error

Post by bokinns » Jan 04, 2010 11:08 am

Hi all,

I have changed the datastore of the VMs and when backup runs shows me this message:

Verifying changed block tracking... Disk "Hard disk 1" has incorrect changed block tracking configuration. One or more VM disks have incorrect changed block tracking configuration. To resolve this, open VMware vSphere Client, right-click the VM, choose Edit Settings, Options tab, select General, click Configuration Parameters, and set all entries with ‘ctkEnabled’ substring to false. Veeam Backup will then automatically re-enable changed block tracking with the correct settings during the next job run.

I've done the procedure in a testing VM and I want to know if this procedure may break or unconfigure the VM.

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

Re: Changed Block Traking error

Post by Gostev » Jan 04, 2010 12:25 pm

No, this only affects changed block tracking functionality.

bokinns
Novice
Posts: 7
Liked: never
Joined: Dec 14, 2009 5:26 pm
Full Name: Carlos Caberol
Contact:

Re: Changed Block Traking error

Post by bokinns » Jan 04, 2010 12:51 pm

OK, thanks^^

kallex
Lurker
Posts: 2
Liked: never
Joined: Jan 03, 2010 9:46 am
Full Name: Kalle Launiala
Contact:

Re: Changed Block Traking error

Post by kallex » Jan 04, 2010 11:38 pm

Hi!

The how-to worked for all but one of our Win 2008 R2 servers. The Exchange 2010 server that is running on Win 2008 R2 with 4 GB RAM assigned and 2 vCPUs repeatedly reports the same issue, even though both (and all) the lines about cbt are set to FALSE.


Br,

Kalle

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

Re: Changed Block Traking error

Post by Gostev » Jan 05, 2010 12:58 am

Kalle, OS or application versions do not matter here, as these settings related to VM configuration, and are present even when VM has no OS installed. Either you have missed some values in configuration, or you are using special disk types with this VM which are not supported by ESX changed block tracking. Feel free to contact our support if you want to nail this issue down.

Post Reply

Who is online

Users browsing this forum: foggy and 63 guests