Free disk space requirement for Upgrade are ridiculous!

[UnknownRectangle]

Hi Veeam,

Is there any chance that when performing an upgrade that the free disk space requirements detected during the upgrade wizard can be more realistic?

I tried upgrading to the latest version 12.3.1.1139, directly from the previous version but, the upgrade wouldn't let me continue due to the compatibility issues Selected location does no meet minimal disk space requirements. I have 18GB free. I managed to free up 800MB and the issue changed to a warning and I was able to continue. After the upgrade the amount of additional storage consumed was about 1GB so, I didn't need over 18GB free!

On another server, I received a disk space warning for the same upgrade scenario when I had 28GB free.

Does your wizard only calculate based on the free space required for a full install, as opposed to an upgrade?

This issue has been present for quite a while, and crops up almost every time but, still persists. Any chance you can modify your algorithm for upgrades?

[david.domask]

Hi Steven,

While I understand the concerns here, the space requirements aren't just for the actual changed files, but also temporary workspace during the upgrade to better facilitate roll-backs should there be a challenge during the upgrade. Much of the free space requirement is for this protection and safety, so it's not just about what added/changed files there are, but ensuring that an issue during upgrade can be rolled back.

[Gostev]

What version were you upgrading from, 12.3.0 or earlier? I believe additional disk space is only needed for upgrades that involve database schema changes, as we make a copy of the database before updating its schema. And for example, 12.3.0 > 12.3.1 upgrade does not require this.

[b.vanhaastrecht]

With v13 the upgrade requirement has become a massive 27GB free space. We have monitorred the upgrade on various boxes but we never see it use more then just a few extra GB's during all the setup stages. We are now running into problems where we just cant create anymore free space on pfysical servers.

Please explain this massive requirement while we dont see proof it is actuelle needed.

Is there are bootstrap switch to disable this requirement at our own risk.

[b.vanhaastrecht]

Or, remove unused components during upgrade. VBR has become a multi platform backup solution but in most cases only a fraction of it is actually used.

[Dima P.]

Hello Bastiaan,

When you are upgrading B&R on without the content of the iso must be stored locally in the cache as files are being extracted and decompressed. I believe setup team and @Egor Yakovlev planned some improvements in this area. Thank you!

[b.vanhaastrecht]

We are using VSPC to upgrade VBR. The ISO itself is 16GB, by default downloaded to C:\. Then the upgrade itself requires 27GB so a stunning 16 + 27 GB of free space is required. This is insane.

So workaround nr1 is to download to an aditional drive, but then again the setup needs 27GB which also is problematic.

Planned and not yet implemented??

Looks like this really needs some attention.