Matching Console Version for Veeam Software Appliance

[hgoetze]

Hi.

I wanted to try the Software Appliance. It version 13.0.1.2067.

Since some features (support for proxmox) are not availabe in the WebGUI at the moment, I installed the console. The downloadable version is 13.0.1.180. So after starting the console, it wants to update to 13.0.1.2067. But nothing happens, probably because it can't find .2067.
The I tried do install the console from the full B&R iso, which is .2067. But when I start the console it still wants to do an "maintenance update" (259.3 MB).

Any idea how to fix this other then downgrade the software appliance to .180 or wait for Veeam to publish a now download for the console?

[Mildur]

Hi Helko,

The web UI currently provides only the console installer for the base version without patches. The patches are retrieved from the backup server during the first connection.

Since we currently have a known issue with the automatic console update, I recommend following the procedure shared by my colleague @HannesK. We plan to fix this in an upcoming patch.

Hello,
I don't have a chance to test quickly with a fresh machine, but this is what I did / the setup looks like.

1. I have a separate Windows Server 2025 that runs the console (there was the suspicion that only Windows 2025 is affected, but I heard of older versions, too)
2. I only had the issue with the Veeam Software Appliance / separate console. Not in the Windows-based lab where I use the local console.
3. I downloaded the VeeamBackup&Replication_13.0.1.2067_20260310.iso full ISO (the 20GB, not the patch)
4. I installed the console: "X:\Tools\VeeamBackup&ReplicationConsole_13.0.1.180.exe"
5. I updated the console: "X:\Updates\VeeamBackup&Replication_13.0.1.2067_patch_20260310.exe"
6. after the patch, the connection worked and the last update package was installed automatically during first login
7. The Proxmox plugin on the Windows server where the console runs is shown as version 13.3.1.7 in control panel, yes.

Best,
Fabian

[hgoetze]

Hi.

Thanks for the tip. I tried the steps on my Win11-Workstation. Still no luck. But the size of the required maintenance changed. Now it's 285.2 MB.
Seems I have to wait till the next patch