REF: Case # 07998875 (Incorrect Veeam Build no is displayed on daily backup job reports and not align to the actual newer VBR product versioning build no installed)
1. Veeam (VBR) upgraded from 12.3.x to Veeam 13.01 (build no: 13.0.1.1071).
2. From: Veeam Backup & Replication console = Main Menu > Help > About ==> product versioning build no 13.0.1.1071 is displayed.
3. From: Daily Veeam Backup Job reports via smtp notification (bottom left of report) email / pdf versioning build no of 13.0.1.180 is displayed.
note: it's only cosmetic but raised a concern whether product is patched to address a known vendor versioning vulnerability.
-
jnaude
- Novice
- Posts: 7
- Liked: never
- Joined: Mar 26, 2019 8:39 am
- Full Name: Jaco Naude
- Contact:
-
Mildur
- Product Manager
- Posts: 11546
- Liked: 3239 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Veeam 13 (13.0.1.1071)
Hi Jaco,
Thank you for the case number.
1.) Yes—this is a confirmed bug and should already be fixed in the upcoming patch.
2.) I can’t confirm this one; it works in my lab and 13.0.1.1071 is shown correctly.
3.) Could you share a screenshot? Which report in Veeam Backup & Replication exactly do you mean?
Best,
Fabian
Thank you for the case number.
1.) Yes—this is a confirmed bug and should already be fixed in the upcoming patch.
2.) I can’t confirm this one; it works in my lab and 13.0.1.1071 is shown correctly.
3.) Could you share a screenshot? Which report in Veeam Backup & Replication exactly do you mean?
Best,
Fabian
Product Management Analyst @ Veeam Software
-
jnaude
- Novice
- Posts: 7
- Liked: never
- Joined: Mar 26, 2019 8:39 am
- Full Name: Jaco Naude
- Contact:
Re: Veeam 13 (13.0.1.1071)
Hello, it is a backup session job report that displays a incorrect build no.
-
Mildur
- Product Manager
- Posts: 11546
- Liked: 3239 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Veeam 13 (13.0.1.1071)
Ah, I apologise.
I misunderstood your first post yesterday, my fault.
Yes, the build number in the backup session report is scheduled to be fixed in Patch 2.
Best,
Fabian
I misunderstood your first post yesterday, my fault.
Yes, the build number in the backup session report is scheduled to be fixed in Patch 2.
Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: Google [Bot], Semrush [Bot] and 60 guests