Problem with backup à VM 2003

[Greg_Bieber]

Hello,

I am a new Veeam admin on a new infra. with vmware 5.5 on HP Proliant DL385 and 3par 7200 optical 8GB etc...

I have a problem on one 2003 VM who backs op but veeam put messages like :

Code: Select all

Cannot use CBT: Soap fault. Error caused by file /vmfs/volumes/54739536-a923a36a-57b7-40a8f02d1fc4/fgfrtra01as01/fgfrtra01as01.vmdkDetail: '', endpoint: ''
Cannot use CBT: Soap fault. Error caused by file /vmfs/volumes/54739536-a923a36a-57b7-40a8f02d1fc4/fgfrtra01as01/fgfrtra01as01_3.vmdkDetail: '', endpoint: ''
Cannot use CBT: Soap fault. Error caused by file /vmfs/volumes/54739536-a923a36a-57b7-40a8f02d1fc4/fgfrtra01as01/fgfrtra01as01_4.vmdkDetail: '', endpoint: ''
Cannot use CBT: Soap fault. Error caused by file /vmfs/volumes/54739536-a923a36a-57b7-40a8f02d1fc4/fgfrtra01as01/fgfrtra01as01_1.vmdkDetail: '', endpoint: ''
Unable to truncate transaction logs. Details: Cannot keep snapshot. No job found.

and : 

Unable to truncate transaction logs. Details: Cannot keep snapshot. No job found.

 :( 

We have done the procedure for reset CBT witch we recieved in the case : Veeam Support - Case # 00688669. The KB : http://www.veeam.com/kb1113

Thank for helping me.

Best Regards,
Greg.

[Vitaliy S.]

What did your engineer suggest to do after reviewing your debug log files? I see two error messages that are unrelated to each other, so full debug logs review is required.

[Greg_Bieber]

The case was not opened by me and not for the same problem. It was for slowness in restore and save. We have 2Mb/s for a restore and about 48Mb/s for save. We think its slow because with DataProtector (D2T) with the same VMs on the old infrastructure the times are better. What do you think about that ?

For this problem I will open a new case I think. If you have ne idea about that...
I generated the job logs with http://www.veeam.com/kb1832

Thank you for your answer anyway.

[Vitaliy S.]

The case was not opened by me and not for the same problem. It was for slowness in restore and save. We have 2Mb/s for a restore and about 48Mb/s for save. We think its slow because with DataProtector (D2T) with the same VMs on the old infrastructure the times are better. What do you think about that ?

What kind of restore are you doing? Full VM restore? Files?

For this problem I will open a new case I think. If you have ne idea about that...

Yes, all technical problems should be resolved by our support team. For unable truncate logs problem, check Windows Event log of the VM you're backing up with this job to see what could be the reason for this behavior.