Aller au contenu principal

Error 354 - Failed to enable CBT - Version VMX-08

Thread needs solution

--------------------
Error code: 354
Module: 149
LineInfo: d1ab7fa1e56ec968
Fields:
Message: Failed to enable Changed Blocks Tracking for virtual machine 'vm://E5CCC0EA-2169-46F8-A498-17C100809291/5025db68-d5b3-e1c4-40cf-55059a850a9b?host=host-9&type=vmwesx'.
--------------------

That is the error message I receive in the post-backup e-mail; it only occurs one one VM, which is the web server running Server 2003 R2 x64 -- the same OS and VM configuration as all of the other machines; VM ver is vmx08.

According to Acronis web interface, ALL backups completed without errors -- looking through the logs relative to the backup operation discussed in the e-mail there are no errors, however there is a mention of the failure (listed as a information though, not warning or error)... times are a bit off from the e-mail (2hrs -- see attachment).

Fichier attaché Taille
acronis-log-error.png 261.24 Ko
0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi Travis,

This message means that vmProtect could not update the VM configuration file automatically in order to enable CBT (ctkEnabled=true parameter in .vmx). Note that the parameter spelling is case sensitive so it might be the case here, i.e. on some VMs there is ctkEnabled parameter, while on the affected one it is spelled as "ctkenabled" or similar. Can you please check the .vmx configuration of the affected VM with some other VM which is backed up fine?

It would be really worthy to compare these 2 .vmx files (if possible please send me them in a private message).

See also the details on how to enable CBT manually here: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cm… - this should be a workaround for your case, but still it would be good to get to the bottom of the issue.

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Vasily,

Thanks for the reply! That's the odd thing -- the VMX for all of the VM's actually does show ctkEnabled; it's a bit different than the parameter casing and format you posted though -- see below.

All VM's (one reported as failure by Acronis, and others) have the same ctkEnabled status and format within the config; the only difference is that the line location is different; but overall, parameter and values are the same.

VM showing Acronis failure to enable CBT:
scsi0:0.ctkEnabled = "TRUE"
ctkEnabled = "TRUE"

VM not showing any Acronis failure on CBT:
scsi0:0.ctkEnabled = "TRUE"
ctkEnabled = "TRUE"

Log files sent to you via PM.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi Travis,

The order of the parameters doesn't matter. The thing that concerns here is the uper case spelling of TRUE word. In the .vmx files that you've sent all the other parameters which have "true" value are spelled in lower case, except for ctEnabled and scsi0:0.ctkEnabled. This might be the case here too (i.e. changing "TRUE" into "true" in vm configuration may do the trick), if this doesn't help then please check the detailed instructions which I've sent you via PM so that we can check which properties are returned for the affected VMs by the vSphere Object Browser. Please check it and let me know if there are any problems following the steps.

Thanks in advance!
--
Best regards,
Vasily
Acronis vmProtect Program Manager

Hi Travis, I was just checking up on this. So how did this work out for you if I may ask?