Feature Request: Select Components to Install/Upgrade

[TonyAtlaz]

++++ Plus 1 here as well.

It's crazy that it takes a 28 core dual Xeon 256gb ram all ssd array 30mins after a restart to sit and baby the primary veeam services to ensure the start in the right order before the other 20 services in order to get the VBR and VPSC working again.

I don't need Proxmox, Kubernetes amount many others....

[gtelnet]

+1 - it would be great to be able to omit modules from the installation via the answer file for automated installs

[weisker]

A start would also be if the services are installed as disabled or manual and B&R automatically takes care of setting them to automatic and starting them if a job which requires the service is used.

[m.novelli]

Super Like for the idea to disable / set to manual unused Services!

[b.vanhaastrecht]

Again, a major headache deploying the upgrade to our customers via VSPC. The new ISO is 21.2 GB, while the installer requires approximately 32 GB of free disk space. This means we need around 53.2 GB of free space in total to deploy the upgrade.

I just executed the upgrade, and only 35% of all managed VBR servers have enough free space. For all the others, we now have to go through the time-consuming process of freeing up or adding disk space.

What makes this even more frustrating is that around 80% of the required space is apparently not actually needed by the installer/customer environment.

This is honestly becoming ridiculous and extremely frustrating. The upgrade process should not require customers to have more than 50 GB of additional free disk space just to deploy an upgrade.

[s.eichner@vega.com]

+1

[ftravinsky]

Worth some perspective on this: vCenter has had URL-based online patching since VCSA 6.0 U1, September 2015. Point VAMI at a repo (Broadcom's depot or a local mirror with manifest/ + package-pool/), check, stage, install. No ISO, no CD-ROM mount. Essentially unchanged from 6.0 U1 through 9.0.

Veeam only got there on Windows with 13.1, in July 2026. The Linux Software Appliance had it from 13.0 in late 2025. Eleven years later.
And if you're on 12.x, or 13.0 on Windows, you're still downloading a ~3 GB ISO to shift a build number.

Great, that we're past ISO downloads now.

[pat_ren]

I think things are improving, but the installer size is becomming a problem. Lately it has also started to install postgres and make a new database for just for Entra ID backup on every server still using mssql, it is a bit ridiculous. We should be able to opt out of installing entra ID if we don't want it. Same with a lot of the plugins 99% of people will never use.

[matteu]

+1

[PerA]

+1

[PerHavn]

+1

[JMM_SM]

+1

[Mildur]

Thanks for the +1. We haven't forgotten about the request.

Lately it has also started to install postgres and make a new database for just for Entra ID backup on every server still using mssql, it is a bit ridiculous. We should be able to opt out of installing entra ID if we don't want it. Same with a lot of the plugins 99% of people will never use.

Hi Pat

Especially for Service Providers, we updated our ISO in the past to allow installations without PostgreSQL for Entra ID. It is not a UI option, but you can specify the parameter when deploying/updating Veeam Backup & Replication in silent mode.

I understand this is probably not what you would prefer, but I recommend giving it a try. If you use VSPC to upgrade your customers, then it should be easy to use the parameter for every customer during the upgrade with the XML file you have to provide (VSPC - upgrade backup server).

- VBR_ENTRAID_DATABASE_INSTALL = 0/1 (0 will not deploy PostgreSQL)

Best,
Fabian

[david.matthewson]

+1

[Victor van Hoek SLTN]

+1

[andrea@manzi.pro]

Really guys...it's getting very hard to maintain Veeam B&R up to date.
It takes too space and an imppressive ammount of time.
It used to be so easy....

[cgracie@sygnet.ca]

+1

[Gustav]

+1

[shooker]

I would agree the installer is getting huge! I only use the Proxmox plugins and I have a few Windows computers I have setup. I would think having the base components in the actual upgrade and add-ons be updated manually or as a subroutine after the main updates are completed. Maybe select the items needed then download and install them.

I used to just remove all the stuff I don't use until the updates would fail to run without all the components installed.

[jwhitford]

The ISO size is beyond ridiculous at this point. Thank goodness for flash speed, can't imagine doing these upgrades on spinning disk again. We're a service provider and aren't doing crazy things. Cloud Connect for Windows backups, Replicas of Windows systems, and Backup for Office 365. I installed an update in early August, it fixed an issue and introduced a new one. Saw there was a hot fix, installed it. Within a few days, a new issue popped up, installed another update. Fixed one issue, caused a new one. Whack-a-mole. I'm spending way too much time just keeping the system semi-happy instead of onboarding new customers. At some point I'll have to start looking around for something else...