Discussions specific to the VMware vSphere hypervisor
Post Reply
emachabert
Veeam Vanguard
Posts: 373
Liked: 165 times
Joined: Nov 17, 2010 11:42 am
Full Name: Eric Machabert
Location: France
Contact:

CBT failure With patch3 and hotadd

Post by 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?
Veeamizing your IT since 2009/ Vanguard 2015,2016,2017,2018,2019

emachabert
Veeam Vanguard
Posts: 373
Liked: 165 times
Joined: Nov 17, 2010 11:42 am
Full Name: Eric Machabert
Location: France
Contact:

Re: CBT failure With patch3 and hotadd

Post by 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.
Veeamizing your IT since 2009/ Vanguard 2015,2016,2017,2018,2019

emachabert
Veeam Vanguard
Posts: 373
Liked: 165 times
Joined: Nov 17, 2010 11:42 am
Full Name: Eric Machabert
Location: France
Contact:

Re: CBT failure With patch3 and hotadd

Post by 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
Veeamizing your IT since 2009/ Vanguard 2015,2016,2017,2018,2019

emachabert
Veeam Vanguard
Posts: 373
Liked: 165 times
Joined: Nov 17, 2010 11:42 am
Full Name: Eric Machabert
Location: France
Contact:

Re: CBT failure With patch3 and hotadd

Post by 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.
Veeamizing your IT since 2009/ Vanguard 2015,2016,2017,2018,2019

Jfmoots
Veeam Software
Posts: 214
Liked: 26 times
Joined: Oct 28, 2011 3:26 pm
Full Name: James Moots
Location: Ohio, United States
Contact:

Re: CBT failure With patch3 and hotadd

Post by Jfmoots »

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

Post Reply

Who is online

Users browsing this forum: No registered users and 16 guests