CBT failure With patch3 and hotadd

[emachabert]

Hi again,

I thought patch 3 had solved this problem (hotadd backup), issue 18.
Second incremental run gave many warnings tonight for half of the client VMs:

The warnings are:
Cannot use CBT: Soap fault. Erreur provoqu?e par le fichier /vmfs/volumes/4e37f841-e901ea07-39c9-0017a4770002/srv1/srv1.vmdkDetail: '', endpoint: ''
Cannot use CBT: Soap fault. Erreur provoqu?e par le fichier /vmfs/volumes/4e37f841-e901ea07-39c9-0017a4770002/srv1/srv1_1.vmdkDetail: '', endpoint: ''

Yesterday there was no warnings.

Do I have to open a support case?

[emachabert]

Ok I think i found What is the problem.
http://www.vmware.com/support/developer ... ckup12.pdf
Page 23.

The virtual machine must have had no (zero) snapshots when Changed Block Tracking was enabled.

This client is using netapp snapmanager and both jobs ran at the same time yesterday when it was first activated.

[emachabert]

Doesn't seems to be caused by the Netapp backup.

Still investigating, If you have any idea on what can cause the "Soap Fault: error caused by file ....".

Thanks

[emachabert]

Found it.

The client has had a server crash the night before. Like it is explained on VMWare KB, ESX crash can cause CBT to fail.
He will reset CBT.

End of story.

Sorry for the post.

[Jfmoots]

Don't be sorry. It's great information to have here.