Veeam update and PostgreSQL

[Koldov]

I've been avoiding the PostgreSQL that's bundled with Veeam as I didn't want another thing to check on and update (actually not sure how I'd even do that) also due to already having Microsoft SQL installed and it getting automatic regular MS updates in the usual manner.

 

However, the latest Veeam update helpfully installed it for me (along with all the 'missing' components that I'd uninstalled previously)...

 

So, the questions are:

 

1. How do I actually know that Veeam is now using PostgreSQL?

 

and

 

2. If it is, how do I get rid of this lot, or at least work out if ANY of it is still being used (nothing else that I know of is using MS SQL on this server)?

 

[jtotheb]

On 24/03/2025 at 13:43, Koldov said:

1. How do I actually know that Veeam is now using PostgreSQL?

When I performed this it installs the PostgreSQL, but if you reconnect to your SQL config database during the upgrade it will still be using that.

 

Look in the History node -> System.  Look at your most recent Backup Configuration Job and open it.  Up near the top you'll see a line:

Active database type: ***** which should show you what the active database is.

 

Check the Veeam support/the manual for the full steps, but the high level steps for migration are:

1. Have no running jobs.

2. Disable your jobs so that one doesn't start during the migration.

3. Take a config backup.

4. Restore the config backup from the Veeam menu, but to the PostgreSQL database that was created by the installer.

5. Wait for it to finish.  It's clear from the onscreen messages that it's converting it to PostgreSQL.

6. Restart.

7. Stop MS SQL service and disable MS SQL Server from loading at startup.

8. Restart again.

9. Check Veeam is all happy.

10. Enable your jobs.

11.  When you're happy everything is running as planned after a soak test you can uninstall MS SQL Server if it was only used by Veeam.

Edited March 27, 2025 by jtotheb

[PotNoodleTech]

The big security hotfix installed posgresql here automatically, I just let, it as I assumed that was something to do witht the security improvements?

[jtotheb]

3 minutes ago, PotNoodleTech said:

The big security hotfix installed posgresql here automatically, I just let, it as I assumed that was something to do witht the security improvements?

 

It installs it, but it doesn't automatically move your configuration database onto it if it is already running on MS SQL.

[PotNoodleTech]

Hm dunno everything seems to be working fine?

 

I'll check.

[jtotheb]

Just now, PotNoodleTech said:

Hm dunno everything seems to be working fine?

It should.  You don't need to migrate the config database over, it's entirely optional.  Everything should still work as it was if you're running your config DB on MS SQL and PostgreSQL is also installed but not in use.

[Koldov]

My issue was that I just like to keep my installs as clean as I can. Previously there were options when you installed VEEAM from scratch and anything I couldn't deselect, I uninstalled straight after. I try to keep my servers with the minimal amount of fluff, if it's not using it, I'll try to find a way to get rid...

However, there were no options on this update as I believe VEEAM are pushing heavily for PostgreSQL and away from MSSQL, which is great AS AN OPTION, so let me choose if I want it installed or not... 

 

I guess there may be downsides to MSSQL...? But I like having it updated/security patched along with the OS and all the other MS software on the server, via the official MS updates.