veeam updates iso only

[galbitz]

is there a reason the smaller updates are no longer released? downloading 13gb per deployment is a bit much to keep things patched on all installs we support.

[FCU_JE]

This isn't an "official" answer, but I like the new ISO method. It sucks for low bandwidth sites, but what it *does* provide is that now if I have a catastrophic loss of the Veeam server I now need only a single ISO installation file/media to install Veeam from.

Install Veeam fresh. Restore latest configuration file. Do any other configurations required to suit the environment, and we're back in business. No need to "catch up" the brand new installation with patches/updates - it is already cumulative.

[DanielJ]

How about a tool which takes as input two isos and generates a patch executable with the difference? Doesn't seem like it would be very difficult to write, and it would save a lot of bandwidth both for Veeam and users.

[Gostev]

For maintenance releases like 12.3.2 there's no need for a tool, the difference is 100% as every module is rebuilt and has a new build number.

For "smaller updates" like emergency security patches we will soon be able to provide smaller updates with only a few affected modules rebuilt with a different build number.

[galbitz]

for years they offered the full iso and a patch file for most updates.

[Gostev]

Correct, but that scheme was discontinued because it didn't work well for our customers. You can find many existing discussions here about this issue but in essence it was too hard to track if certain security update was actually installed, because the affected modules were rebuilt with the same build number as the original release. Only in Help > About you could see the patch level based on PXXXXXX string added to a build number, but automated checks with purpose-built software inventory tools were too hard to implement.