Maintain control of your Microsoft 365 data
Post Reply
GianlucaCroci
Veteran
Posts: 262
Liked: 29 times
Joined: Feb 26, 2019 12:08 pm
Full Name: Gianluca Croci
Contact:

Upgrade PostgreSQL

Post by GianlucaCroci »

I'd like to upgrade the PostgreSQL version on the "Veeam Backup for Microsoft 365" server.
It's a single server with the application and database. Veeam has been upgraded to 8.14, and the current PostgreSQL version is 15.8.
I'd like to upgrade PostgreSQL to 16.13, if possible. From what I've read, this is the most recent version available, although versions 17 and 18 exist.

I currently use "5432" as the database port, but I would use "5433" for the new version.
I don't remember what password I used when installing PostgreSQL the first time (assigned to the "postgres" user).


Here is the configuration line from the "config.xml" file.
<ControllerPostgres ControllerConnectionString="host=server_name;port=5432;database=VeeamBackup365;username=postgres;MaxPoolSize=100;ConnectionIdleLifetime=10" TlsEnabled="False" CertificateThumbprint="" />
I've already tried, but without success:
1. Installing PostgreSQL 16.13
2. Turning off the three Veeam services
3. Using "pg_dumpall" I created a backup of version 15 (pg_dumpall.exe -U postgres -f C:\backup\backup.sql)
4. I recovered the backup on version 16 ("C:\Program Files\PostgreSQL\16\bin\psql.exe" -U postgres -d postgres -f "C:\backup\backup.sql")
5. I edited the "config.xml" file, changing the port from "5432" to "5433"
6. I tried to start the three Veeam services, but none of them started.

I haven't found a specific KB for the in-place upgrade, and especially if there's a way to tell Veeam that the database has changed.
I saw that upgrading from Veeam version 7 to 8 asked for database information, but I haven't found a way to do it afterwards.

Thanks in advance for your help.
Polina
Veeam Software
Posts: 4026
Liked: 1031 times
Joined: Oct 21, 2011 11:22 am
Full Name: Polina Vasileva
Contact:

Re: Upgrade PostgreSQL

Post by Polina »

Hi Gianluca,

For PostgreSQL upgrades (between both major and minor versions), please follow the same steps described in KB4729.

The list of supported PGSQL versions is provided in our HelpCenter.

Thanks!
GianlucaCroci
Veteran
Posts: 262
Liked: 29 times
Joined: Feb 26, 2019 12:08 pm
Full Name: Gianluca Croci
Contact:

Re: Upgrade PostgreSQL

Post by GianlucaCroci »

Hello Polina,

thank's for your reply.

I'd read this KB4729 and others, but I still haven't been able to restart the Veeam services.
It's probably because I don't remember (or know) the password for the current Postgres user.
I'd have to re-enter the credentials.

For example, isn't there a way to move the database to another server? In my case, I wouldn't have to change the server name, just the credentials.

Thank's
Mildur
Product Manager
Posts: 11844
Liked: 3361 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Upgrade PostgreSQL

Post by Mildur »

Hi Gianluca,

Unfortunately, the KB article cannot be used for major upgrades. I will speak with our KB team to see to what extent we can provide a procedure, since most of the steps are performed on the PostgreSQL side and, in general, we do not write documentation for third-party applications. However, I hope we can document the steps required on the Veeam Backup for Microsoft 365 side to migrate from PostgreSQL 15 to PostgreSQL 16 and link to relevant PostgreSQL documentation where appropriate.

Keep in mind that PostgreSQL 15 is still fully supported by PostgreSQL until November 2027, so there is no need to upgrade today. I recommend staying on PostgreSQL 15 for now.

Best,
Fabian
Product Management Analyst @ Veeam Software
GianlucaCroci
Veteran
Posts: 262
Liked: 29 times
Joined: Feb 26, 2019 12:08 pm
Full Name: Gianluca Croci
Contact:

Re: Upgrade PostgreSQL

Post by GianlucaCroci »

Hello Fabian,

thank's a lot for your reply.

Yes, not urgent, but time is flying by, and there must be a migration solution.
Also because we're currently on Postgresql v18, so you're two releases behind on compatibility.


As you said, for the moment we continue to use the V15.

Thank's again
Best regards
Gianluca
Post Reply

Who is online

Users browsing this forum: Google [Bot] and 107 guests