VBR 12.3 : OS Upgrade from Win2016 to 2025 + SQLServer->PostgreSQL ...

[ThierryF]

Hello,

Currently running VBR 12.3 on SQL Server 2016 on Win2016 Physical server,
I plan to upgrade my OS Version to Win2025 after migrating from SQLServer to PostgreSQL.
We kept Win2016 to not upgrade SQLServer as we wanted to ago away from due to lic cost.

As DB is 30GB, SQLXpress Edition was not possible.

From releases notes, I read VBR12 is supported on Win2025. OK.
As I am planning to migrate away from SQL Server, I plan first to migrate the DB to PostgreSQL
before OS Inplave Upgrade.

Now, from PostgreSQL release notes : https://www.postgresql.org/download/windows/
Postgres Version 64 Bit Windows Platforms
18 -> 2025, 2022
17 -> 2022, 2019
16 -> 2022, 2019
15 -> 2019, 2016

So, I need to target PostgreSQL 18 for Win2025.
And Version 15/16/17 are not supported on Win2025

But, in VBR12 RN, https://helpcenter.veeam.com/archive/ba ... ments.html :
Local or remote installation of the following versions of PostgreSQL1:
PostgreSQL 14.x
PostgreSQL 15.x (PostgreSQL 15.14-1 is included in the Veeam Backup & Replication 12.3 setup)

How to get out this situation without new physical server and without upgrade steps like
Win2016+SQLServer2016 -> Win2016+Postgre15 -> Win2019+Postgre15 -> Win2019+Postgre17-> Win2022+Postgre17 > Win2022+Postgre18 -> Win2025+Postgre18 ?

Thanks for input ...

TH

[Egor Yakovlev]

Hi Thierry,
Both PostgreSQL and Veeam are quite flexible when it comes to supported OS and database version lists. PostgreSQL's platform notes describe where the installer has been tested and verified - it doesn't mean the database won't work fine on platforms not listed there. Same story with Veeam - we commit to tested configurations, but never claim things will break on newer ones, and we have plenty of customer reports confirming success on unlisted combinations.

Your path forward in this case:
1. Make sure you are up to date with VBR 12.3 installation (latest patch 12.3.2.4465).
2. Install PostgreSQL15 (grab the latest build).
3. Migrate VBR configuration database from SQL Server to PostgreSQL and verify its healthy operation (read migration guide carefully, including manual Set-VBRPSQLDatabaseServerLimits).
4. Perform an in-place Windows upgrade to Server 2025.

[ThierryF]

Hello,

Thanks for your reply. I will proceed following your inputs.

Thanks again

Th

[FCU_JE]

My 0.02:

It's far easier to just do a fresh OS installation and do a BCO migration/restore. Make everything fresh. Besides, if you're doing regular backup/restore testing (of which the VBR server itself should be part of that....) you already know this works.

Even with a physical server, you likely have a RAID card and concepts of virtual disk (volume) on that card. Assuming whoever built/installed the server initially didn't commit 100% of the space (a practice I don't see many admins do.....), you should have some space you can use to make a new volume, install WS2025 there, and perform the change. If you have issues for whatever reason, simply reboot back to the other virtual disk with your WS2016 installation.