postgresql update

[karsten123]

Hi,
is it supported to update postgresql to like 15.12-1, with the procedure for VBR?
I didnt find any kb for this topic, tbh.
Thanks!

[Gostev]

Hi, our QA did not specifically test it yet as it's just been released, but normally yes - you can upgrade to minor releases as they become available. This has never caused any issues so far. Veeam is not using any super advanced Postgre capabilities, so it's unlikely for bug fix updates to break anything. When they do, the issue will likely be affecting many vendors and will be known quick. Thanks

[karsten123]

Thank you Anton. You are totally right.
So the procedure is to backup the VB365 server, shutdown all Veeam related services and run the setup?
Are there any special tricks to save the running configuration?
Is it necessary to shutdown nats as well?

[DaStivi]

@Gostev so there is another Post about PostgreSQL update already: post537720.html but my questions isn't answered there either... and its not mentioned anywhere else i guess..

the vb365 docs states "15.8 or later" ...
https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=80

in comparison VBR docs states explicitly "14.x or 15.x"
https://helpcenter.veeam.com/rn/veeam_b ... n-database

in the vb365 Case the 15.8 or later includes all the way to PostgreSQL 17 (17.4-1) now with no exception? or even newer version that might get released like a psql v18 ?

[DaStivi]

as i've just noticed, the text in the supported versions for psql looks like has been changed now to "exclude" v17, dropped the 15.8 and later... ! it only states now v16.4 as highest supported version?!
what if i've vb365 on psql v17 ? (or whatif, if you still are on 15.8, thats "not supported" anymore now?)

Case #07698684

[track1044]

We had a similar request, @DaStivi and Veeam support came back with the following response: (Case # 07694132)

"The short answer would yes, the later versions of PostgreSQL will work with Veeam Backup for Microsoft Office 365 without issue

Regarding the availability of the versions mentioned in the system requirements, Veeam Backup for Microsoft Office 365 comes with PostgreSQL included in the installer so unless you would like to use a newer version of PostgreSQL there is no need to install it separately"

[Polina]

Hi Stephan, hi David,

We made this change after thorough consideration and extensive internal discussion. Including the phrase "and later" in our documentation unintentionally suggested compatibility with future PostgreSQL versions that have not yet been tested—or in some cases, even released. To ensure the stability and reliability of v8, we’ve updated the system requirements to reflect only the versions we can confidently support.

Hope it explains...

[t7MevELx0]

Hi @Polina ,

I understand the need to revise the documentation. However, PostgreSQL 17.4 was already a stable, production‑ready release when the earlier guide was published. At that point, anyone following your instructions would have chosen 17.4 with confidence. The updated guide no longer lists version 17.x as supported.

If the goal was simply to exclude untested 18.x releases, it would be more consistent to keep support for the three most recent production versions, including 17.x.

Thank you for the clarification.

[Polina]

The whole thing is 17x has not yet been tested with vb365, and even if it's 'a stable and production‑ready release' we need to ensure there're no issues when vb365 works with it.

[t7MevELx0]

Hi @Polina ,

Thank you for confirming that PostgreSQL 17.x has not yet completed Veeam QA. I would like to clarify why this change is causing confusion:

Until the recent update, the system‑requirements page stated “15.8 or later.” That wording covered 17.x. Many partners, including us, built production deployments on 17.4 in good faith.

The revised guide now lists only 16.4 as the highest supported version, which makes our existing installations appear unsupported overnight.

Could you please advise on the following?

Is 17.x known to cause issues, or is it simply awaiting formal certification?

If issues are not expected, may we continue running 17.x with the understanding that support is “best effort” until QA is complete?

What is the tentative timeline for validating 17.x?

Would Veeam consider restoring the previous wording with an explicit note such as “17.x is provisionally supported, pending final QA,” so that partners are not forced to downgrade unnecessarily?

Clear guidance will help us set expectations with customers and avoid unplanned downtime.

Thank you for your help.

[DaStivi]

support currently advises to downgrade psql to a supported version, what i doesn't like todo because it causes another downtime and potential issues while the downgrade...