Upgrade from 7a to 8.1

[Montross]

I have recently been through a 7a to 8.1 upgrade that failed. The issue was tied to the amount of disk space required for the upgrade. I looked at the documentation given and the requirements for disk space were minimal. I increase the drive which housed the software by 40GB. When the install was done there was only 1.86GB of space left. In the end I had to revert the system to its previous version. My question from all of this is what is the space increase needed for the upgrade? How can I calculate this based on the properties of the current environment? The "System Configuration Check" window during the upgrade tells you to be sure you have sufficient space but no number is given. How can I calculate this?

Thanks
Case 07632752

[DaStivi]

have you checked what took the space with something like treesize or windirstat ??

genereally speaking, at least in the v7 versions, the upgrades made a backup of the "configuration" database thats in programdata...

[Montross]

Thanks for the reply. Unfortunately I could not install winstatdir due to the size limitation of the drive and I couldn't increase the drive size because of the VM snapshot taken before the upgrade.

Thanks.

[sumeet]

Hi Montross,

Please read this KB article related to drive size and the issue I have had in the past -- veeam-backup-for-microsoft-365-f47/upgr ... 84519.html

With 7a to 8.1 upgrade, we did one last week and this is what I observed -- Under ProgramData\Veeam\Backup365 - The ConfigDB folder size is 16 GB, and so I make sure there is atleast 3 times more space available. But since this is the first time we are doing the upgrade, we made sure 5 times of 16 GB is free.

Our upgrade was successful and post upgrade this is what I observe - There are two BackupConfigDB_<UUID> folders exists in the above path - which is 32 GB.
There is no ConfigDB folder anymore (as I think all the data is now migrated to PostgreSQL)
The PostgreSQL 15 folder is 20+ GB

So the primary extra usage post upgrade is 16 GB (for an extra ConfigDB backup folder) + 20 GB for PostgreSQL = 36 GB
There will be few more extra space used for the setup files and logs. But primarily it is the backup folders and the new PostgreSQL
The ProxyDB is 0.3 GB and a backup for this exists too.

Maybe you can use this calculation to figure how much free space you require.

As informed in the above R&D thread - I fail to understand that when such complex piece of software can be written, then why cannot such simple calculations be added as part of the upgrade?
I see a warning is listed to ensure sufficient space on the disk be available - but isn't this such a vague thing to say? What can this sufficient space value be?

-Sumeet.