GUI : Incomplete Tape backup copy listed ...

[ThierryF]

Hello,

Running VBR 10.0.1, I run my backup jobs to a scale-out repository during night.
The morning, I run a Tape-job to copy daily backups to tape.

I just discovered that (some but not all) Vmware Vm backup jobs that succeed from BackupJob
to NOT be "listed" from Backup -> Tape GUI part, even looking for VM machine job contains using
search does not allow backuped VM to be retrieved, meaning I can restore VM from Console.
Looking at File on tape inventory, I retrieve backup files from tape inventory.

Or for some other backup jobs, backup job name is listed in Backup->Tape but exploring it
gives no details ...

What am I missing / doing wrong ?

Thanks

TH

[PetrM]

Hello,

It's hard to make a conclusion without seeing the screenshots but it sounds like a technical issue with GUI.

Therefore, the best way to address it is to reach out our support engineers and to ask them to look at the issue via remote session. Please don't forget to paste a support case ID over here.

Thanks!

[Dima P.]

TH,

File node represents data on tapes, but that might be the imported tapes (i.e. tapes which are not used in any jobs, likely previously written). Backups > Tape represents the backups files written by actual tape jobs, if something is missing here - you need to open the desired tape job and check the list of source disk jobs. Cheers!

[ThierryF]

Case #04517357 was created.

[ThierryF]

Case update & resolution ...

Engineer working on the opened case at Veeam support provided us a SQL Script
to patch a procedure from SQL Database side.

Stopping VBR Services, backuping db, patching sql procedure, restarting VBR Services
and all is back on track ! Super fast and efficient support team.
Big Thanks to Vitaly Zadorozhny !

[Egor Yakovlev]

Thanks for update.

It is a confirmed minor UI issue - when triggering restore from [Ribbon > Restore] all backups will be visible, however triggering from [Backups >] might filter some out.
It is fixed in v11, until then, if anyone meets this again, feel free to reach Veeam Support team for a solution!

/Cheers!