Strange email about scale-out backup repo

[GabesVirtualWorld]

TESTLAB Setup!!!

In my lab I was playing with directly backing up to S3 storage. All seems fine and I got a daily email about the repository space usage, strangely enough 2 emails daily. But never really looked at them. As soon as 12.2 was available this week I upgraded and today, just before clicking 'delete' on that repository email, my eye caught: "Veeam Backup & Replication 12.1.2.172" in the footer of the email. Huh, I upgraded, didn't I ?

So for the first time really I started to examine these emails and I noticed the following:

date: Thu, 29 Aug 2024 22:00:44 +0200
subject: [Success] Scale-out Backup Repository: VeeamOnS3
In the html header: donderdag 29 augustus 2024 22:00:42. <=== date notation !!!!
Performance tier: used space 789,8 GB
Space limit: 1024GB (22% free)
Performance tier: Extent: Veeambackup-idrive-S3
Space limit: 1024GB (22% free)
Used space: 789,8 GB <==== used space
Capacity and archive are empty.
Veeam Backup & Replication 12.2.0.334 <==== new version


date: Thu, 29 Aug 2024 22:00:58 +0200
subject: [Success] Scale-out Backup Repository: VeeamOnS3
HTML Header: Thursday, August 29, 2024 10:00:56 PM <==== date notation!!!
Performance tier: used space 379 GB
Space limit: 1024GB (22% free)
Performance tier: Extent: Veeambackup-idrive-S3
Space limit: 1024GB (22% free)
Used space: 379 GB <==== used space
Capacity and archive are empty.
Veeam Backup & Replication 12.1.2.172 <==== old version

When I check the Veeam Console I see two backup repositories. One is the windows f-drive of 10GB. The other is the S3 repository "Veeambackup-idrive-S3" 798GB used space, which is the same in the scale-out repositories.

So, now I'm really confused about why there are 2 emails daily and have different views on the space of the s3 storage and version of Veeam

[marina.skobeleva]

Hi Gabrie,

We will check with QA team, stay tuned.

Thanks!

[marina.skobeleva]

Hi,

At first glance, there are two assumptions:
1) One of the email was sent before Veeam B&R was upgraded to the newest version.
2) It looks like two different Veeam B&R installations, with different versions, but with the same repo name.

Did it happen just once or you could provide some extra examples of such odd behavior?

Thanks!

[GabesVirtualWorld]

I
am
so
ashamed !!!

A few weeks ago I needed to move the VEEAM B&R VM to a new host but storage VMotion was impossible because somehow the vmdk was corrupt. So I installed a new VEEAM B&R server, disabled all jobs, restored the config to the new server and guess what.... I forgot to turn off the old server.

Really sorry take up your time. I will now go and stand in the corner