postgresql 15 -> 17

[karsten123]

hi,
is there a from Veeam supported and documented way for a upgrade for postgresql 15.x to 17.x?

is it worth the effort or is it just fine to stay on latest 15 version?

Veeam server is a Windows based v13.

Tia
Karsten

[david.domask]

Hi Karsten,

I would advise schedule a maintenance window and then do a Configuration Migration using the native Configuration Restore utility.

Updating to more recent versions of PGSQL are generally recommended, at least for security fixes; staying on PGSQL 15.x latest security patches should be enough until you're prepared to migrate to PGSQL 17.

[chrislove]

Yeah we had the same question and had to do this as well (config backup > restore). Does 15.x go EOL before VBR v13? so those we upgraded from v12 using postgresql may need the same doing.

[karsten123]

ok. got it.
but is there a step by step how to for going from 15 to 17? i am not a postgresql guy and do not know how to do it. and maybe there are Veeam specific things to consider?

[RandomTrooper]

I don't know if this will help you, but I upgraded another app using this:

Dump the database

Code: Select all

pg_dump -U <username> <database-name> > db_backup.sql

Upgrade the PostgreSQL version, then:

Import the database

Code: Select all

cat db_backup.sql | psql -U <username> <database-name>

That was it. Be sure you have a backup before proceeding.

Reference: https://www.postgresql.org/docs/current/app-pgdump.html

[david.domask]

Thanks for sharing RandomTrooper; I would still advise to any readers looking to migrate to a newer postgres instance to use our Configuration Restore as noted before. Our KB here explains the potential pitfalls of trying to backup the configuration database using native SQL backup / restore and the User Guide outlines some of the challenges on migrating using native SQL tools; the pitfalls _can_ be avoided, but you can be assured they're avoided by using Configuration Backup / Restore.

Hint: After migrating, it is recommended to run Set-VBRPSQLDatabaseServerLimits for your PGSQL instance once more to ensure that the PGSQL optimizations are set correctly.

[david.domask]

ok. got it.
but is there a step by step how to for going from 15 to 17? i am not a postgresql guy and do not know how to do it. and maybe there are Veeam specific things to consider?

With Configuration Restore, nothing too special. Install Postgres, you may need to adjust some settings as per this KB to allow the backup server to properly access the postgres instance.

Outside of that, as noted in previous post, you will probably want to run Set-VBRPSQLDatabaseServerLimits to ensure that the postgres 17 instance is configured optimally.

[karsten123]

thank you David. i am still not confident, tbh.
but i will try it in a isolated demo environment in the next few weeks.
a dedicated Veeam kb article would be greatly appreciated.

[jackal2001]

Just upgraded VBR from 12.3 to 13.1. Saw that PostgreSQL was still running 15.18 on our server. Just checking to see if there was any Veeam documentation on how to perform the upgrade to 17.x as that is supported on VBR 13.1

[david.domask]

Hi Jason,

Please see our KB here.

This KB outlines an in-place upgrade, but you can also install side-by-side and use the Configuration Restore to migrate as well. Configuration Restore is required as opposed to manually moving database files / using native SQL backup & restore tools.

[d.artzen]

I successfully used this guide, which is not from Veeam: https://mytechnugget.com/2026/upgrading ... n-windows/
The first part is using the Veeam supported method of a configuration restore to the new instance.
Important to note is, that I copied the whole pg_hba.conf and pg_ident.conf from the 15 folder to the 17 folder instead of editing the new files and I did not change the port back (Step 3 of the Guide), I just pointed Veeam to the new port during configuration restore. Worked fine in our environment.