Question about Database Updates in V13.0.1 on Windows

[d.artzen]

Hello together,

I have a question concerning future database updates for V13 on Windows. According to the documentation the new installer brings PostgreSQL 17.6. I am currently on 15.4 with B&R 12.3.2. I plan to upgrade the PostgreSQL to the latest 17 after upgrading the B&R to V13, since I don't think the installer will do that automatically during the Upgrade from 12 to 13.
The question is future PostgreSQL updates. In the "What's new" document it is written that you will take care of those updates automatically on the new VSA, but will you also do this on a Windows Installation or is this impossible and will still be needed to be done manually? I ask because while still on MS-SQL Windows Update took care of the SQL-Updates, but PostgreSQL does not have any kind of auto-updater or even update notifications, so it is a manual task to check if there are any updates available.

Thanks in Advance.
Best regards
Daniel

[DaStivi]

I would even raise the question if normal PSQL Update from 15 to 17 upgrades and moves the DB Files?? as the setup, manually started just creates a new directory... not sure if the setup recognizes the old install and upgrade it?

[d.artzen]

In that case what would the recommended way to upgrade be? Or should I stay on the latest 15?

[DaStivi]

There’s currently no official Veeam KB for PostgreSQL upgrade procedures (for VBR or VB365), as far as I’m aware. The same question just came up in VB365 forum.

PostgreSQL does not support in-place upgrades for major versions. You need to install the new version in parallel with the existing one.
After installation, use the official PostgreSQL tool pg_upgrade (or alternatively pg_dump/pg_restore) to migrate the database to the higher Version and move to the new data directory.

probably also needed Update/move configuration files (postgresql.conf, pg_hba.conf) to redo veeam specific configs.

[d.artzen]

OK, then I will just stay on 15 until there is official guidance how to do this. I don't have knowledge of PostgreSQL, the instance was originally installed by the Veeam installer during an Upgrade of the VBR to the version that introduced Entra-ID Backup. I then just performed the official steps to migrate the database from the previous MS-SQL to PostgreSQL to get rid of the old MS-SQL Express. For "In-Version" Updates I used the steps of KB4386. And I don't want to destroy anything and make additional work for me.

[Gostev]

The question is future PostgreSQL updates. In the "What's new" document it is written that you will take care of those updates automatically on the new VSA, but will you also do this on a Windows Installation or is this impossible and will still be needed to be done manually?

Only software appliance will provide fully managed experience with updates for the entire software stack. The same is very hard to do when we don't control the stack and every VBR installation is different with 3rd party software like antiviruses constantly getting in the way, different Windows OS versions and settings, etc.

[d.artzen]

Thanks for the info Gostev. Concerning the question of PostgreSQL Major Version Update (on Windows), will there be a KB similar to 4286 to give guidance for those without PostgreSQL knowledge like me?

[Gostev]

Our Support always creates KB articles for every common question they get so this shouldn't be an exception.

[SKratzTS]

Only software appliance will provide fully managed experience with updates for the entire software stack. The same is very hard to do when we don't control the stack and every VBR installation is different with 3rd party software like antiviruses constantly getting in the way, different Windows OS versions and settings, etc.

Is it possible to use a config backup from v12 to restore to a new v13 with Postgres 17? (I've always gone for a config restore to the exact same version that was live.) Doable?

[Gostev]

Depends if there's replatforming involved:
VBR V12 to VBR V13 > supported
VBR V12 to VSA V13 > not supported

[ilyes.delaunay26]

Thank you all for the detailed discussion regarding PostgreSQL major version updates in Veeam Backup & Replication v13.0.1 on Windows. It’s very helpful to know that in-place upgrades are not supported and that parallel installation with migration tools like pg_upgrade is recommended. Hopefully, official KB articles will soon provide step-by-step guidance to simplify this process for users without deep PostgreSQL knowledge.

[spiritie]

Is anyone from Veeam able to answer if you've seen any performance gains from Postgres 15 --> 17 with VBR?

I'm asking because I want to evaluate if it's worth our time upgrading many of our managed VBR servers (We are an MSP), or if we should just ignore it for now and wait until we can get them moved to VSA

[Gostev]

They are significant and are definitely worth upgrading for in large environments. But since you're an MSP, I assume most of your clients are relatively small anyway?