[ERRORS] Cannot use CBT: Soap fault.

[logos]

hello all,
I open this topic for ask you a question about this error:

We have a PDC with Exchange on board that has had this error in the previous backup schedules:
Cannot use CBT: Soap fault. Error caused by file /vmfs/volumes/4fe89ee8-7266c5c6-f20c-5cf3fcb8dd0a/MORO PDC/MORO PDC.vmdkDetail: '', endpoint: ''

I saw in some other posts 2 solutions:
- Remove all the machine's shapshots
- Try to reboot the machine.

We tryed to do these 2 tips but has worked nothing.

Some other machine details:
- This machine has the Fileserver Role and it has a disk of 1.5TB for Data
- In this machine there is installed Exchange server 2010.

does anyone know about this error?

Thanks in Advance

[veremin]

Hi, Logos . Have you also tried to create a new VM snapshot and, then, delete it? According to this user's experience, it might do the trick. Thanks.

[foggy]

Also please provide the support case ID for this issue, as requested when you click New Topic, so that we can facilitate and track resolution. Thanks.

[logos]

Also please provide the support case ID for this issue, as requested when you click New Topic, so that we can facilitate and track resolution. Thanks.

i'm sorry i'll do it. Could you tell me how can i open a support case?

[logos]

Hi, Logos . Have you also tried to create a new VM snapshot and, then, delete it? According to this user's experience, it might do the trick. Thanks.

Hi Eremin,
I did it but nothing has worked.

[logos]

I opened a support Case: 00441908

[foggy]

Thanks. Let's see what they can suggest after reviewing the logs.

[logos]

They asked me to follow this link:
http://www.veeam.com/kb1113

On Wednesday I'm going to modify this parameter.

I'll keep you updated.

have a nice day

[CaptainFred]

I've just had this problem on lots of VMs that I can't have an outage with easily. So we have put together the following script which *seems* to fix it without all the power off/power on/power off steps

NOTE: Test it on a VM/datastore that you don't care about just in case! The delete ctk files part is rem'ed out because this wasn't always necessary. Also change DATACENTER to your datacenter name.

It does the following:

1. Disables CBT
2. Deletes the *-ctk.vmdk files IF UN-REM'ED
3. Creates a snapshot called CBTFIX
4. Waits
5. Removes the snapshot called CBTFIX
6. Waits
7. Consolidates the disks
8. Waits
9. Enables CBT

Save as CBTFIX.ps1 file and run it:- .\CBTFIX.ps1 VMNAME

Code: Select all

$VM = $args[0]
$VMView = Get-VM $VM | Get-VIew
$VMConfigSpec = New-Object VMware.Vim.VirtualMachineConfigSpec
$vmConfigSpec.changeTrackingEnabled = $false
$vmView.ReconfigVM($vmConfigSpec)

#$Datastore = get-datastore -vm ($VM)
#Rm "vmstore:\DATACENTER\$Datastore.name\$VM\*-ctk.vmdk"

New-Snapshot -VM $VM -name CBTFIX

Start-Sleep -S 2

Remove-Snapshot -snapshot (get-snapshot -VM $VM -name CBTFIX) -confirm:$false

Start-Sleep -S 2

$VMCon = Get-VM $VM
$VMCon.ExtensionData.ConsolidateVMDisks()

Start-Sleep -S 1

$vmConfigSpec.changeTrackingEnabled = $true
$vmView.ReconfigVM($vmConfigSpec)

Let me know if it works for you!

[eric]

Hello All,

Running VBR 7.0.0.839, VMware 5.5 with vCenter

Two configured backup and replication jobs were running fine, now I am seeing this error for a few machines:
4/18/2014 9:09:28 AM :: Cannot use CBT: Soap fault. Error caused by file /vmfs/volumes/51350900-33885551-58ed-6cae8b63b452/blahlblah.vmdkDetail: '', endpoint: ''

This particular replication job is running but will take forever without CBT.

What can I look for?

~eric

[eric]

Update: I stopped a replication job that was running, disabled the job, rebooted server, restarted VBR and ran the job again.

The replication job has two virtual machines in it, one completed successfully using CBT and the other one is still failing with the Soap fault error...

~eric

[veremin]

You can try to reset CBT using procedure described above. If the issue persists, feel free to open a ticket with the support team. Thanks.

[eric]

You can try to reset CBT using procedure described above. If the issue persists, feel free to open a ticket with the support team. Thanks.

Okay, I was able to resolve the issue with the KB Article noted above.

The root cause of the problem is that the VMware host had a PSOD.

~eric