PostgreSQL disappears from 12.3.1 upgrade steps

[kevin.boddy]

Hi,

We have upgraded our VBR servers from 12.1.1 to 12.3.1.
During the upgrade process the installer start off installing PostgreSQL and shows steps 1 of 7.
Our EDR software detected the PostgreSQL installer as suspect and blocked the installation which then failed the upgrade.
We updated our EDR's exception list.
We then re-ran the upgrade and the number of steps shown is now 1 of 6.
PostgreSQL did not get installed and re-running the upgrade does not install it.

Why doesn't it try and re-install after re-running the upgrade?
How do I install PostgreSQL from the Veeam ISO using the same parameters the upgrade installer was using?

Thanks
Kevin

[Gostev]

Hi, the easiest would be to perform configuration backup, uninstall everything including PostgreSQL, and do a clean install of VBR. Since I suspect your EDR left the current installation in an inconsistent state. Thanks

[kevin.boddy]

Hi,

It's only the PostgreSQL that was affected, everything else was not affected.
Why did the upgrade process drop this when re-running the installation? Is this expected?
How to install it manually? Do I just run the installer for PostgreSQL or are there specific parameters required.

Should I log this with support and get them to help fix the upgrade installer and the PostgreSQL installation?

Thanks
Kevin

[Gostev]

It's of course impossible to guess how exactly your EDR has impacted setup logic and the resulting installation. But looks like the upgrade process is not prepared to see the end result.

Sure, you can work with our support if you'd like. I simply offered you the easiest and fastest way I would use to fix an inconsistent installation of any product, including VBR (for which it is super easy).

I personally like to keep all software in the designed "flight envelope" because adding manual fixes on top of erroneous install only accumulates inconsistencies and may result in even more upgrade issues later.

[kevin.boddy]

Hi,

Thanks for the reply.
We know the EDR stopped this file from running "POSTGRESQL-15.12-1-WINDOWS-X64.EXE"

What I don't understand is why when re-running the upgrade, the Veeam installer did not re-try the PostgreSQL installation.

Unfortunately, in my case it is not easy to reinstall a VBR server. Bearing in mind this also affected our VCC servers.
While the process itself is not too difficult, there are other considerations like change control, customer notifications and various ISO processes which have to be followed.
I also need to report on what the issue was and how to prevent this in future which I'll need Veeam support to assist with.

Thanks
Kevin

[kevin.boddy]

Hi,

There is an article https://www.veeam.com/kb4698 about a similar issue with the VeeamBackup&Replication_12.3.0.310_20241201.iso from which December 2024 which was fixed where the Veeam installer does the same thing and skips the PostgreSQL installation.

This is not the issue I experienced but the behaviour is similar.

I did log a case #07666244 and it appears the Veeam installer is creating a registry key for the PostgreSQL before PostgreSQL is even installed.
Not knowing the logic of the Veeam installer we assume it sees this registry key and skips the PostgreSQL installation.

The question then is why the Veeam installer is creating the registry key first and then running the PostgreSQL installation? Surely you run the installation and if it is successful then you create the required configuration in the registry, not beforehand.

Thanks
Kevin