VMware backup with (Retry) ==> (0 VMs)

[stevenfoo]

All,

We are using Veeam backup & replication 6.1.0.204 (32 bit) to backup our Vsphere 5.0 vms.

Often we get alter email header ==> [Success] SERVERNAME (0 VMs)
and content as below.

VMware Backup job: SERVER (Retry)
Created by ABCdomain\backupadmin at 8/15/2012 3:15:27 PM. Success
0 of 0 VMs processed
Thursday, November 01, 2012 1:12:42 AM
Success 0 Start time 1:12:42 AM Total size 0.0 KB Backup size 43.2 GB
Warning 0 End time 1:14:01 AM Data read 0.0 KB Dedupe 1.1x
Error 0 Duration 0:01:19 Transferred 0.0 KB Compression 3.2x
Details
Name Status Start time End time Size Read Transferred Duration Details

We don't see that Veeam actually retry the backup after that. Going into the console, we see the line item with Stopped Success.

If there is a job failed, Veeam will continue 3 attempt. For the above case it will not continue to retry. Any ideas ?

[Gostev]

How do you have the job setup? Looks like Veeam cannot find any VMs in the specified container.

[stevenfoo]

Gostev,

All of our jobs are setup accordingly. The jobs are run daily without issue. Only sometime the issue came out where by it did not backup the VM and return an email with green header in the content. On the subject there is (0 VMs). We see inconsistency here. It defer from one VM to another. Sometime every VMs is backup properly (1 VMs). There are times with (0 VMs). This happen randomly. Is there a bug in the product?

[Gostev]

What do you mean by "accordingly"? Are using containers, or specifying VMs explicitly.

There is a known bug in vCenter/ESXi that may be causing this. They sometime would not return the list of VMs in container correctly. It is quite rare (I only know about it from support, it was never reported on forums). Usually happens when infrastructure is overloaded or has some other major problems (vCenter database performance etc.)

[dellock6]

Anton,
I've seen in the past this exact behaviour, receiving Veeam job report with 0 VMs backed up in it. This happens especially on retry, for some reasons a job with several VMs in it fails at some point, but in reality all the VMs are correctly backed up. The job goes into the execution queue as a retry, but since it retries only failed VMs and there are none to be retried, the retry jobs completes with 0 VMs.

Luca.

[Gostev]

Oh, I see. Thanks Luca.

[stevenfoo]

Any solution on this issue ? Thanks.

[Gostev]

I need to know the support case ID for debug logs access before I can talk to R&D regarding the issue.

[stevenfoo]

Hi Gostev,

I have raise the case # 00152882.

Thank you.

[dfowler]

Hi,

I experienced the exact same thing this past weekend. However, I didn't consider it a problem i.e. the first attempt to run the backup job generated the following error:

"CompileFIB failed Client error: There is not enough space on the disk. Failed to write data to the file [D:\VeeamBackups\Hyperion Dev\Hyperion Dev2012-11-03T205001.vbk]." However, the status of each individual VM within the job was success.

The repository had 0 space available, after cleaning up old data and freeing up space the first retry completed successfully: "VMware Backup Job: Hyperion Dev (Retry) - Success 0 of 0 VMs processed" (the job was the weekly synthetic full, the retry ran for ~ 1.5 hrs and subsequent incrementals have been fine).

I am not sure this helps but reading on the forum that previous a poster had seen this behaviour helped me sleep easier, so thank you Luca.

Dave