Veeam says Success - vSphere says Failed?

[mcwill]

I'm hoping this is just a little glitch in 4.1.1 but I've noticed that in the vSphere event log I get the following at the end of a backup...

User logged event:
Source: Veeam Backup
Action: Job "Router"
Operation: Stopped
Status: Failed
ID: b1d40143-0228-4fbf-9327-da6539b2d2ab
Description: user 28/02/2010 08:09:30 yyy\xxx

whereas in the Veeam console...

1 of 1 VMs processed (0 failed, 0 warnings)

Total size of VMs to backup: 12.00 GB
Processed size: 12.00 GB
Processing rate: 50 MB/s
Start time: 28/02/2010 08:05:22
End time: 28/02/2010 08:09:30
Duration: 0:04:08

I'm assuming the vSphere "failure" is incorrect but it would be good to get some reassurance to that effect.

Thanks,
Iain

[Gostev]

Hello Iain, yes - I've seen this issue referenced in the recent build's notes last week, meaning that the fix for this should already be available through our support. The bug is with Veeam Backup component that writes these events to vCenter.

[mcwill]

Gostev,

Thanks for the prompt response.

Iain

[n2it-dk]

is there a fix for this event errors?

[Gostev]

Yes, it is available.

[n2it-dk]

What would the ref number be for this hotfix.?

[Vitaliy S.]

You may just refer to this topic that describes the issue while writing to support team asking for the hotfix.

[jroot]

Guys,
Should we just wait for the next build release or get the hotfix? Based on my last restore the job was indeed successful despite the status in vCenter.
Jim

[n2it-dk]

k, tnx...

[Gostev]

Jim, if you are using vCenter events to track backup status then you should definitely get the hotfix from support now instead of waiting for next maintenance release, for your convenience. But, if you use email notifications (which is what most people seem to be doing), or SNMP traps, or Veeam Backup UI, or web UI to track backup activities - then don't worry about getting the fix... the issue does not affect anything except those custom vCenter events being always set as "failed".

[jroot]

Thanks Anton! We use email notifications and Veeam Backup UI. We noticed this issue during a cursory check of events and then checking the forum to see this recent post. I hate dirty logs but we'll wait on this one.

[Gostev]

Yes, apparently this is what most people are using to monitor their jobs... because we only had 2-3 requests for this fix so far