let me try to clarify my problem with 'virtual full backup' again ...
First of all, we have a B2D-job (forever forward incremental) with 15 VMs, one of the VMs is a Windows Domain Controller, so every week day (MO-FR) incremental data is written to the B2D-repository, usually a few GB's of data in the range of 50-100GB per day, so in fact, there is changed data every week day (MO-FR).
The B2T-job runs after the B2D-job (MO-FR), selected is the B2D-repository used for the 15 VMs from the B2D-job, virtual full backup is selected, incremental backup is not selected, process latest full backup chain is selected in Advanced Settings under Options in the B2T-job.
Last night, the following log entries can be seen in the History of the B2T-job:
5/17/2018 12:52:38 AM :: Building source backup files list started at 5/17/2018 12:52:38 AM
5/17/2018 12:52:39 AM :: No restore point for 5/17/2018 is available for virtual full backup, using previous restore point for 5/16/2018
5/17/2018 12:52:40 AM :: 15 synthetic full backups will be placed into the media set
5/17/2018 12:52:41 AM :: Source backup files detected. VBK: 0, VBK map: 15, VIB: 0
Everything went fine and around 3,4TB of data was written to the LTO7 tape media!
A day before, the following log entries can be seen in the History of the B2T-job:
5/16/2018 12:54:53 AM :: Building source backup files list started at 5/16/2018 12:54:53 AM
5/16/2018 12:54:53 AM :: Synthesized full backup was not created for 5/16/2018: there are no new restore points between 5/16/2018 and 5/16/2018
5/16/2018 12:54:54 AM :: Source backup files detected. VBK: 0, VBK map: 0, VIB: 0
This happens randomly (MO-FR). Sometimes it works, sometimes not.
Something is fishy here.
Is this faulty behaviour already known? Is a fix available?
Veeam B&R 9.5 U3 is used in this environment.
Using the most recent Veeam B&R in 9 different environments now and counting!