I come in this morning to see if my GFS tape job set to run on the first Monday of the month is running happily and I find that it has decided to bypass 4 weeks of full VBK files on one of the VMs to create a virtual full from a VIB over a month old. This source job runs an active full every Friday night and yet Veeam has decided to ignore it.
Code: Select all
11/7/2016 12:00:28 AM :: Full backup from FILE012016-10-03T220122.vib (10/3/2016 12:00:00 AM) restore point will be placed to monthly media set 11/7/2016 12:00:28 AM :: No GFS candidate for Monthly media set was found for today, waiting 11/7/2016 12:00:28 AM :: Backup file J:\Backups\FILE01\FILE012016-10-03T220122.vib will be excluded from the list of files to backup, because it is unavailable. Virtual full backup creation will be skipped 11/7/2016 12:00:28 AM :: Source backup files detected. VBK: 0, VBK map: 0, VIB: 0 11/7/2016 6:05:24 AM :: Source backup files detected. VBK: 0, VBK map: 1, VIB: 0 11/7/2016 6:05:25 AM :: Creating full backup map for J:\Backups\FFILE01\FILE012016-10-03T220122.vib 11/7/2016 6:06:36 AM :: Queued for processing at 11/7/2016 6:06:44 AM 11/7/2016 6:06:36 AM :: Required backup infrastructure resources have been assigned 11/7/2016 6:06:36 AM :: Backup to media set monthly started at 11/07/2016 00:00:10 11/7/2016 6:06:39 AM :: Drive 1 (Server: VR01, Library: IBM 3573-TL C.50, Drive ID: Tape1) locked successfully 11/7/2016 6:07:16 AM :: New tape backup session started, encryption: hardware 11/7/2016 6:07:26 AM :: Processing FILE012016-10-03T220122.vbk
I have not opened a ticket about this yet, since the job is still running "pending" its wait on source backup copy jobs to have a restore point it will deign to use.