Imported backups missing most recent in GUI

[HouseAtreides]

Hi

I have two VBR 9.5U4 servers:

- 1 x on-prem
- 1 x in Azure

My on-prem VBR backs up VMs into a SOBR, the capacity tier is Azure BLOB storage
My Azure based VBR has a SOBR using the same Azure BLOB storage account for it's capacity tier

This was working fine but I have found that when I rescan the SOBR on the Azure based VBR, it is not showing the most recent backups in the GUI any more. For example, I have a VM that is backed up every night on-prem. After re-scanning the SOBR I can see the backup files on the Azure based VBR on the performance tier (local disk) but the restore wizard GUI says the most recent point was 33 days ago. It should say about 6 days.

The on-prem SOBR has the "age out" window set to 0.
The backup jobs are encrypted if that makes a difference?

In the screenshot see the blank entry dated 27/09/2019 23:01. I can see that file on the disk.


Basically I can see the backup files on the disk but not in the GUI. Any idea why?

Thanks
HA

[HannesK]

Hello,

not showing [...]any more.

asking the other way round: when did it work fine and what did you change since then? If "nothing" is the answer, then please contact support and post the case number here for reference.

I can see the backup files on the Azure based VBR on the performance tier (local disk)

also sounds strange to me. Please contact support.

Best regards,
Hannes

[HouseAtreides]

Hi Hannes

I believe the problem started when I enabled encryption on the backup jobs on-premises. Both servers are federated by Veeam Enterprise Manager so the encryption passwords are available to both servers

I have opened a case #03796484. Support have said to deploy a new Azure based VBR server and import the config

Thanks
HA

[veremin]

Both servers are federated by Veeam Enterprise Manager so the encryption passwords are available to both servers.

This makes Enteprise Manager aware of encryption keys added on both backup servers. However, this doesn't make one backup server aware of the encryption keys added on the other one. So, the reason must have been enabling encryption on on-premises backup server.

Thanks!