[V13] Question regarding Veeam B&R 13.x

[Didi7]

Ok, but 13.0.1 is not publicly available or do I miss here anything?

And, is it possible to add this change from AppSec via standard updates in the VBR appliance?

[Gostev]

You didn't miss anything, RTM goes to partners only, so they could prepare for GA.

It should be possible, I see no reasons why not.

[Didi7]

Excellent news Gostev.

Appreciated.

[Didi7]

Next question ...

Is Tags combination considered to be available in the VBR appliance web GUI? I know it's available in the Fat Client GUI.

Regards,
Didi7

[Gostev]

Everything will be available in web UI because fat client will be discontinued eventually.

[Didi7]

Good to know and imo also the right way to go!

[Didi7]

Veeam 13.0.1.180 has made its way into our infrastructure, 29 systems are up-to-date, allthough not every machine has been rebooted.

This needs to be done manually? Is there a way to reboot VIA- & VHR-machines via the GUI (not the console) or is this something that will be incorporated later?

Furthermore, it would be nice, if the current version would not only be displayed in the console screen of a virtual or physical machine but also in the Veeam Host Management UI. To my knowledge, the current version is only visible in the main VBR web and fat client console for the VBR server itself but not for VIA- or VHR-based machines.

Nevertheless, awesome progress btw! The update worked like a charm.

[Gostev]

Great to hear, especially given the scale of your infrastructure!

Actually the systems will be rebooted automatically, but only if the particular update requires reboot.

[Didi7]

Actually the systems will be rebooted automatically, but only if the particular update requires reboot.

Allright, in this case it might not have been necessary, the respective VIA-machines showed the old version, so I decided to reboot them manually and 13.0.1.180 finally showed up in the console screen.

So, in this case (when a new release is available), I better reboot them manually, as long as it is not available from the GUI.

Cheers.

[Gostev]

You can use Ctrl-C to refresh the login screen to display the new version.

[Didi7]

Good to know, will give it a try, when I will integrate the HPE Alletra 4120 server next week. This one is still on 13.0.0.4967 and I will do the update, as soon as this one is part of the whole infrastructure.

28 systems on 13.0.1.180 now.

Continuing with 13.0.1.180 on Windows based infrastructures as well and every proxy will change to a VIA-based one there as well. Awesome, I love that.

[Gostev]

LOL, how many Veeam infrastructures do you manage???

[Didi7]

Well, in this case we are talking about a small 2-node VMware cluster and a couple of smaller infrastructures for small environments including Hyper-V, Nutanix & VMware.

I have a small restore infrastructure, which has still Socket-based licenses. It's the cluster I started with Veeam B&R back in 2014. It was 5 years in production beside other locations with Veeam software. Since 2019 it served 6 years for restores after someone decided to switch to a competitor, but now we are back with Veeam in production environments with full force.

I am doing the whole hardware, virtualization and backup stuff here *lol*.

The really big infrastructure is the one with the new VBR appliance, which will end up with approximately 70 systems, most of them virtual machines and of course a couple of HPE based Hardened repository server and soon VDCV hopefully.

[Didi7]

Guys, currently I am pushing the number of nodes to more than 40 machines. With Veeam B&R v13.0.1.180 the amount of time to add a new VIA node has significantly increased.

It will take more time to add those new machines

*************************************************************************************

What I further noticed is the non alphabetical order, if you add a WAN accelerator from the server list within the FAT client. Maybe this is already on the todo-list to be fixed?

*************************************************************************************

I am a little bit unsure about adding the amount of WAN accelerator cache to the machine. The standard size of VIA-machines is 2 disks with each 120GB in size, so I decided to add a third disk with 250GB, so in total I have 3 disks (120+120+250GB). If I choose this VIA-machine to be a WAN accelerator machine, the amount of disk space available for caching is 369.8GB and so it looks like he is adding the amount of 250GB of disk 3 to the amount of 120GB of disk 2.

Question is => Does this make sense or would it make more sense to change the size of disk 2 to 450 or 500GB instead, if Veeam is adding the amount of disk space of disk 3 to disk 2 anyway, when choosing the WAN accelerator cache (/var/lib/veeam/veeam-wan).

Enjoy your weekends guys,
Didi7

[Didi7]

You didn't miss anything, RTM goes to partners only, so they could prepare for GA.

It should be possible, I see no reasons why not.

Ok, the new year has started! Our new VSA-based environment has grown to 42 machines, the next couple of machines will be added soon.

Is there any news regarding 'Password expiry settings' for VSA- and VIA-based accounts? I think the 60 days will expire soon again and it will take another half day or more to change passwords for the 2 or 3 accounts on more than 40 machines again!

I really hope to avoid this.

Thanks for any reply.

[Gostev]

No news, we're still planning to deliver an option to disable DISA STIG requirement of mandatory passwords rotation in the first minor release. Which means you will still need to do a few rotations manually.

[Didi7]

I see

[Didi7]

Is this supposed to be a minor release?

Quote: 13.0.1 Patch 1 (build 13.0.1.1071) on January 6, 2026 > KB4738

[Gostev]

Minor releases have their 2nd octet of the build number changed (for example 13.1 which is the one you're waiting for).
The above is just a security/quality patch, nothing but a new build of 13.0.1 with a couple of hundred bugs fixed.

[Didi7]

Allright, thanks for the clarification.

[Didi7]

Ok, I upgraded the 42 machines to Veeam B&R 13.0.1.1071 and everything looks normal so far.

Downloading the Windows based backup console from the VSA still offers 13.0.1.180 even after pressing CTRL-C or a reboot.

Maybe that's intended or that has been missed?

Update:
Ok, as soon as I launch the Windows based backup console, the system offers an update to 13.0.1.1071

[Dima P.]

Hello Didi7,

This is expected - remote console contains autoupdate engine so it will 'update itself' whenever it's required after Veeam B&R has been patched. There might be little inconsistencies with the version number of the remote console (i.e. the old version will be displayed in add /remove programs) but we plan to address those in the next releases. Thank you!

[Didi7]

No real problem, I found the work-around. It just takes a little bit longer, as you first need to install the old version! And you are right, in add/remove programs the old version is shown