VBR 12.2 to VBR 12.3 - upgrade failing 1st time if you are on SQL

[BostjanUNIJA]

Hi.
Don't know if it was mentioned in any other post on this forum, but we are experiencing a pattern with upgrading VBR where database is on SQL and not on PostgreSQLL.
For example (had at least 3 customers with same behavior), a customer has VBR 12.2 and we trigger upgrade to VBR 12.3.
In the wizard we see that it's gonna upgrade the current SQL instance, and when we click proceed with upgrade, the first step that is shown in wizard is:
Step 1 of 7: Installing PostgreSQL server 15.10-1...
At the end of this step 1 the installation throws an error: VBR 12.3 installation failed. Click here to open logs folder.
This was resolved (on all three customers with same approach), rebooting the VBR server and triggering that upgrade again.

[Gostev]

@tpayton should this be a Support KB?

[Egor Yakovlev]

Hi Bostjan,
We will be glad to inspect installation logs for details. If you don't mind opening support case(s) and sharing the number here, of course.

[BostjanUNIJA]

I can open a support ticket and share logs. Problem is already resolved. Will do this on Monday since I am not in the office anymore. Thanks.

[tpayton]

We'd need to confirm details and understand the specific scope of the issue to document it clearly in a KB article.

In my lab, I deployed VBR 11a (the last version to self-deploy Microsoft SQL Server), upgraded it to 12.2, and then to 12.3 without any issues. This confirms that the upgrade process should function properly.

Therefore, it's essential to understand what occurred in the customer's environment(s), which is why the logs will be crucial. I'll monitor next week for the support case to be created with the logs from C:\ProgramData\Veeam\Setup\.

For those curious about why the installer was trying to deploy PostgreSQL for a VBR deployment already using a local Microsoft SQL Server: the installer detected that the existing VBR deployment was not using a local PostgreSQL instance and needed to deploy one for the new Backup for Entra ID functionality added in VBR 12.3. The new Backup for Entra ID feature stores its backup data in a PostgreSQL database, and the installer deploys a PostgreSQL 15 instance to ensure this functionality works as expected.

[mjs66]

I ran into a similar situation today upgrading from 12.2 to 12.3. The first thing I saw was that it was installing postgresql, but the vbr server uses MSSQL. The upgrade completed. When I checked the db config using database connection setting wizard, it seems that it's still pointed to MSSQL. So why did it install postgresql?

[mjs66]

Just saw tpayton's explanation for postgresql being installed.

[mikame]

I had 5 installations and all did the same, failed for installing Postgresql, reboot and all installed well after that. All systems were on latest 12.2. I bet soon there will be a fix / KB.

[BostjanUNIJA]

Opened a case:
Case #07533355

Uploaded logs:
C:\ProgramData\Veeam\Setup\

[Egor Yakovlev]

Thanks for the logs.
It states that setup has failed to install PostgreSQL(triggered installation, waited, received a negative reply), so better look into PG logs rather than Veeam's.
Check out %TEMP% for pgsql logs - they usually are quite explicit with the failure reason.

[BostjanUNIJA]

Does this mean you need me to upload also %TEMP% into support ticket?
Per posts on this thread looks like we are not the only one experiencing this upgrade issue.

[Marijn]

...

For those curious about why the installer was trying to deploy PostgreSQL for a VBR deployment already using a local Microsoft SQL Server: the installer detected that the existing VBR deployment was not using a local PostgreSQL instance and needed to deploy one for the new Backup for Entra ID functionality added in VBR 12.3. The new Backup for Entra ID feature stores its backup data in a PostgreSQL database, and the installer deploys a PostgreSQL 15 instance to ensure this functionality works as expected.

Hi TPayton,
Would it be possible to do a manual postgresql installation and make Veeam use that PSQL instance for the EntraID backup? I'd like to keep my compute and storage seperated. I heard something like a "hardened" postgresql install on redhat being an option?

[Gostev]

Sure, you can have VBR use any PostgreSQL instance you want.

[brian.mathis]

I can confirm......I ran into the same issue.
Got Veeam 12.2 installed with database on MSSQL. The update failed the first time trying to install PostGreSQL.

-> "C:\ProgramData\Veeam\Setup\Temp\VbrSuite_09_12_2024_10_40_32.log" -> [09.12.2024 10:48:48][ERROR] Failed to install PostgreSQL server 15.10-1.

After I rebooted the server the installation ran through without any issues and updated to 12.3.

[Egor Yakovlev]

Does this mean you need me to upload also %TEMP% into support ticket?
Per posts on this thread looks like we are not the only one experiencing this upgrade issue.

Yes, please upload pgsql installation log from temp. Interesting to look at it.

[BostjanUNIJA]

%TEMP% uploaded to the case.

[collierusf02]

Happening the same as well to us. Case #07534296

[Gostev]

Do you have Windows Script Host disabled? This might be the reason.

[DaStivi]

is it normal that the psql service is disabled upon installation with 12.3 update?

[Gostev]

Yes.

[BostjanUNIJA]

@gostev - thank you for your reply.
Regarding: "Do you have Windows Script Host disabled? This might be the reason."

Will check tomorrow & report back.

If this is a part of built-in security analyzer in VBR we have probably mitigate/disable it in veeam hardening phase.

[Steve-nIP]

I just experienced this issue too, Step 1 of 7, PostgreSQL install failed.
Windows script host was naturally disabled due to it being part of Veeam's hardening recommendations.
I enabled it and re-ran the installer, but this time it looked different - Step 1 of 6, updating Veeam Backup & Replication.
Second time round it didn't seem to attempt to install PostgreSQL, but it ended up being installed anyway..?

[Gostev]

PosgreSQL is the mandatory component going forward, so it's normal.

[tpayton]

This issue is now documented in KB4698: Upgrade to Veeam Backup & Replication 12.3 Fails During "Step 1 of 7: Installing PostgreSQL server 15.10-1..."

The most critical takeaway is: If the upgrade fails the first time, do not attempt to run the upgrade again without first following the instructions documented in the article to enable Windows Script Host and clean up the partial PostgreSQL installation.

Those customers who ran the upgrade twice and completed the upgrade are encouraged to review the More Information section of KB4698. In short, technically, yes, the upgrade succeeded, but you've likely got a partial PostgreSQL 15 deployment left on your Veeam Backup Server that you should consider removing. Also, if you want to use the new Backup for Microsoft Entra ID, you'll need to deploy a PostgreSQL instance manually and configure the Microsoft Entra ID backup repository

[BostjanUNIJA]

Hi @tpayton.
Thank you for your reply.
I have read the documentation you have provided.
Is it possible that regarding section More information ("If you plan to use Microsoft Entra ID backup, you'll need to create a PostgreSQL 15 instance and configure the Microsoft Entra ID backup repository yourself") - (those customers who "unfortunatelly alread did upgrade and now VBR is partly "inconsistent" regarding new functionality Backup Enetra-ID)

Can you guys publish an update 12.3.1 to resolve this issue automatically?
We have "an issue" on customer level where we had upgraded VBR servers and now they are unhappy with additional manual work, and expect this should be resolved with some "patch" that would automatically fix the issue.

[Gostev]

Yes, the current plan is to resolve this automatically in 12.3.1 which is our release vehicle for vSphere 9 support.

We will also try to patch 12.3 ISO to throw an error if WSH is disabled.