Different ISOs from Veeam for 12.3.1.1139

[Spex]

There are 2 iso's you can download from Veeam for 12.3.1.1139 :
VeeamBackup&Replication_12.3.1.1139_20250315
VeeamBackup&Replication_12.3.1.1139_20250331
Maybe there are still more....

One contains a private fix veeam_backup_12.3.1.1139_PrivateFix_TF946183.exe and some updated plugins (AWS and Azure).
Why are the changes nowhere documented and what is the reason for TF946183.

But most important how can I get from 20250315 to 20250331?
Unfortunatelly the backup team wasn't aware of this and installed more then a dozent backupservers by random and now our powershell scripts can not connect to many of the servers because of different versions.

[Gostev]

ISO is constantly refreshed with latest components versions and it's well documented. The ISO release history is always available at the bottom of the main release article, which you can find in the sticky topic in this forum. For version 12.3 it is KB4696

You never want to use older versions of the ISO, only the most current. There are no use cases for using older versions, which is why they are not available.

You don't "get from 20250315 to 20250331" in principle, these are ISO versions not product versions (product build is the same in both). But you can always install documented delta e.g. new plug-in versions or hotfixes manually.

[Spex]

Whether your sticky topic nor the kb you linked mention the 3103 iso release for 12.3.1.1139
This release is not compatible with the older one(s).
So please answer my questions.

[Gostev]

You are just not looking carefully because it's there in the KB article, at the very top of the ISO release history, and has been there for over 2 weeks now. If you are not seeing it, please share a screenshot of the ISO release history section that you are seeing.

[Spex]

Ok, thanks for helping me in finding this information.

One thing remains:
How can I update from 1st to last iso version to be able to use vbr-connect to remote vbr servers again?
Is it sufficent to install the private fix?

P.S. IMHO i would expect a new version everytime incompatible changes are made

[Gostev]

Correct, you just apply the delta documented in the ISO release history, in this case the hotfix.

Personally I would love the "new version every time" approach however our larger customers push us to ship small changes in small, contained hotfixes. As having to upgrade to a new product build triggers a much more complex adoption workflow for them.

[TWuser]

You never want to use older versions of the ISO, only the most current. There are no use cases for using older versions, which is why they are not available.

I have been hit by this issue as well and wasn't real impressed. All my VBR servers were running the same version, meaning I can manage them similarly from the same jumpbox.
We spun up a new site, new VBR server, so I downloaded the ISO of the exact same version all other servers were running. Installed and configured via RDP, then disabled RDP as per hardening checklist.

A few days later, I go to manage it via my jumpbox, and I can't open the new server, running the exact same version of Veeam, because an incompatible change/fix of some sort was slipped into the ISO.
My choices:
- upgrade every other server, whether it needs the hotfix or not
- Uninstall/reinstall the new VBR server using the old ISO (which is no longer available via Veeam's website)
- Manage the new server in a completely different way than ever other server

The frustrating part for us is when updates/hotfixes are slipped into the ISO with no version change, and likely no mention that that new ISO is incompatible with the old version, even though the old version is no longer available for download.