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?
-
- Veeam Vanguard
- Posts: 395
- Liked: 169 times
- Joined: Nov 17, 2010 11:42 am
- Full Name: Eric Machabert
- Location: France
- Contact:
CBT failure With patch3 and hotadd
Veeamizing your IT since 2009/ Veeam Vanguard 2015 - 2023
-
- Veeam Vanguard
- Posts: 395
- Liked: 169 times
- Joined: Nov 17, 2010 11:42 am
- Full Name: Eric Machabert
- Location: France
- Contact:
Re: CBT failure With patch3 and hotadd
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.
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/ Veeam Vanguard 2015 - 2023
-
- Veeam Vanguard
- Posts: 395
- Liked: 169 times
- Joined: Nov 17, 2010 11:42 am
- Full Name: Eric Machabert
- Location: France
- Contact:
Re: CBT failure With patch3 and hotadd
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
Still investigating, If you have any idea on what can cause the "Soap Fault: error caused by file ....".
Thanks
Veeamizing your IT since 2009/ Veeam Vanguard 2015 - 2023
-
- Veeam Vanguard
- Posts: 395
- Liked: 169 times
- Joined: Nov 17, 2010 11:42 am
- Full Name: Eric Machabert
- Location: France
- Contact:
Re: CBT failure With patch3 and hotadd
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.
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/ Veeam Vanguard 2015 - 2023
-
- Veeam Software
- Posts: 215
- 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
Don't be sorry. It's great information to have here.
Who is online
Users browsing this forum: No registered users and 66 guests