Report says failed but job indicates success

[ddayton]

I received an automatic e-mail from Veeam B&R that the subject reads "[Failed] Backup Job RIB Windows7 32bit (3 VMs)". The job is performing a Reversed Incremental Backup of three Windows 7 Enterprise VMs.

When I look at the job report it indicates a backup error not failure. As far as I can tell there was no failure just maybe a delayed start. Should I be concerned? The formatting will be lost but I am pasting the e-mail text below. The last line was in the details column.

VMware Backup job: Backup Job RIB Windows7 32bit
Created by RVDPA-WSUS\Administrator at 11/13/2012 1:57:04 PM. Error
3 of 3 VMs processed
Friday, December 07, 2012 7:00:15 PM
Success 3 Start time 7:00:15 PM Total size 240.0 GB Backup size 49.0 GB

Job has failed unexpectedly
Warning 0 End time 7:51:39 PM Data read 4.8 GB Dedupe 0.0x
Error 0 Duration 0:51:24 Transferred 2.6 GB Compression 2.1x
Details
Name Status Start time End time Size Read Transferred Duration Details
RVDPA-REPORTSA Success 7:10:54 PM 7:22:57 PM 80.0 GB 1.2 GB 746.3 MB 0:12:03
RVDPA-REPORTSB Success 7:23:21 PM 7:39:55 PM 80.0 GB 2.5 GB 1.2 GB 0:16:33
RVDPA-REPORTSC Success 7:39:58 PM 7:50:43 PM 80.0 GB 1.1 GB 672.0 MB 0:10:45
Job [Backup Job RIB Windows7 32bit] cannot be started. SessionId: [4dd0138a-2ff2-47eb-9449-93902ed89a3a], Timeout: [363.6815135 sec]

[Vitaliy S.]

Hi Don,

It seems like you had some kind of a race condition issue. If all three VMs have a successful backup status in the Veeam backup console, then there is nothing to worry about.

On top of that, if you observe this issue one more time, please contact our support team for further troubleshooting.

Thanks!

[ddayton]

Thanks. It appeared that maybe it was a delayed start or something, but was actually successful. By the way I am on B&R version 6.5, which I upgraded too about 2 weeks ago. I hadn't seen this in 6.1, but I have made several scheduling changes. I started with a seperate job per VM and then changed to a seperate job per OS type while in 6.1, but only schedule changes in 6.5 to stagger full backup days on the incrementals to avoid two fulls on the same day.