Veeam 12 to 13 Upgrade and MS SQL Express to PostgreSQL Migration

[sarnold]

We're currently running Veeam 12.3 with Microsoft SQL Server Express 2016 (Veeam bundled) on Windows Server 2019 and it's rock solid, however, I'm considering switching to the Veeam Software Appliance in the future to take advantage of the all-in-one upgrades and security hardening. At the moment, we're running Veeam Backup Enterprise Manager and Veeam Backup & Replication on the same server (I believe I'll need *two* of the new Veeam Software Appliances, one for each of those products, if I switch from a Windows server to the appliance, is that right?).

In preparation for that future, and to get us up to date in the mean time, I'm looking to upgrade to Veeam 13.1 and migrate to PostgreSQL. After reading many, many separate articles, this is what looks like the best game plan:

Database Migration from Microsoft SQL Express to PostgreSQL

•Upgrade PostgreSQL from 15.10 (installed by a Veeam 12 update awhile back) to 15.18.2
•Configure PostgreSQL for Veeam with Set-VBRPSQLDatabaseServerLimits
•Disable all backup jobs
•Backup Veeam Backup & Replication Microsoft SQL Express Database and restore to PostgreSQL
•Backup Veeam Backup Enterprise Manager Microsoft SQL Express Database and restore to PostgreSQL
•Update Credentials for Veeam Backup & Replication Server in Veeam Backup Enterprise Manager (Part 3 here, not talked about in the article above)
•Reactivate Enterprise Manager Keyset (may not be needed)
•Enable all backup jobs
•Wait until all backup jobs run on their scheduled times and verify they're successful after the database migration

Veeam Upgrade from 12.3.x to 13.1.x

•Disable all backup jobs
•Upgrade Veeam Backup Enterprise Manager from 12.3.x to 13.1.x
•Upgrade Veeam Backup and Replication from 12.3.x to 13.1.x
•Enable all backup jobs
•Wait until all backup jobs run on their scheduled times and verify they're successful after the Veeam upgrade

PostgreSQL Upgrade from 15.x to 17.x

•Upgrade PostgreSQL from 15.x to 17.x
•Wait until all backup jobs run on their scheduled times and verify they're successful after the PostgreSQL upgrade

Some Questions:

[1] Does Veeam Backup Enterprise Manager really not need to be stopped when backing up and restoring the database? The documentation just makes it look like I can back it up, restore, and then use the Configuration Database Connection Utility to point Veeam Backup Enterprise Manager at the new database, but it never mentions stopping or starting any services. Can I safely assume the VBEM REST API and everything else will just accept the database being changed underneath it no problem while it's running?

[2] I've seen reference to staying on PostgreSQL 15 instead of upgrading to 17, even once upgraded to Veeam 13. But, Veeam 13.x now includes PostgreSQL 17, so wouldn't I want to upgrade to that to stay aligned?

[3] I wasn't able to find any official Veeam documentation that outlines upgrading PostgreSQL from 15 to 17, which seems odd given Veeam installs it in the first place and provides PostgreSQL updates on their own Veeam Software Appliance. It seems like there should be dome documentation somewhere that outlines the similar process for performing that same upgrade when you aren't using the appliance.

[DaStivi]

Hi,


I cannot say much about Enterprise Manager, but one thing to consider is whether you actually need it. I assume you do not have multiple VBR servers. In that case, the only other major use case would be the Web Restore Portal for user self-service restores. If you do not need that functionality, you can simply remove Enterprise Manager completely.


Regarding the upgrade: as you already discovered, upgrading PostgreSQL is not entirely straightforward. A major version upgrade can be performed by backing up and restoring the databases, and there is also a PostgreSQL migration cmdlet available.


If you are not currently using PostgreSQL 15 for Entra ID backup, another option would be to install a fresh PostgreSQL 17 instance and use that directly. Make sure to copy the pg_hba.conf and pg_ident.conf files from the PostgreSQL 15 installation directory.


PostgreSQL differs considerably from Microsoft SQL Server. If you are not familiar with PostgreSQL, you may encounter some challenges when reconnecting VBR to the new database instance.


At the moment, Veeam does not provide a detailed KB article covering PostgreSQL major version upgrades. The easiest approach would likely be a VBR configuration database backup and restore. Alternatively, you can manually back up and restore the PostgreSQL databases using pgAdmin. This can be done from a single pgAdmin instance connected to both PostgreSQL versions.


If you install multiple PostgreSQL versions on the same server, they use different ports! which are configured in postgresql.conf. VBR will connect to the database instance specified during the database configuration wizard (or via the relevant registry settings).


Overall, I would recommend upgrading PostgreSQL to version 17 before performing the Microsoft SQL Server to PostgreSQL migration. This avoids the additional complexity of a PostgreSQL major version upgrade after the migration has already been completed.

[sarnold]

I cannot say much about Enterprise Manager, but one thing to consider is whether you actually need it.

We use it for the web restore, and allowing users with lower permissions to restore files.

another option would be to install a fresh PostgreSQL 17 instance and use that directly. [...] Overall, I would recommend upgrading PostgreSQL to version 17 before performing the Microsoft SQL Server to PostgreSQL migration.

I thought about this, but the path I have outlined above is based specifically on all of the support articles I could find and documentation about the supported versions.

Veeam Backup and Replication 12 documentation says it requires PostgreSQL 14 or 15.
Veeam Backup and Replication 13 documentation says it requires PostgreSQL 14, 15, or 17.
Veeam Backup Enterprise Manager 12 documentation says it requires PostgreSQL 14 or 15.
Veeam Backup Enterprise Manager 13 documentation says it requires PostgreSQL 14, 15, or 17.

So, either the documentation isn't up to date, or I'm going to stick with my original plan and do the PostgreSQL upgrade last, after Veeam components are at 13.1. Granted, I can still do what you suggest and just do the Veeam upgrade under SQL Server Express, and then the config migration last once I'm on 13.1. Is that what you're suggesting?

[Mildur]

Hi sarnold,

Maybe an easier approach with fewer steps, if your goal is to move to VSA:

1.) Update VBR and EM to V13.0.2 and keep the MSSQL database for now.
2.) Migrate EM to PostgreSQL: https://helpcenter.veeam.com/docs/vbr/e ... tml?ver=13
3.) Migrate EM to VSA: https://helpcenter.veeam.com/docs/vbr/e ... tml?ver=13
4.) Migrate the backup server from Windows to VSA: https://www.veeam.com/kb4800
5.) Update VSA and EM to V13.1.

There is no need to migrate the VBR database to PostgreSQL first if your goal is to move to VSA.
Also, migration to VSA is currently only possible with version 13.0.2. V13.1 will NOT allow any migration.

We use it for the web restore, and allowing users with lower permissions to restore files.

If you only use it for restore, then you may be pleased to hear that V13.1 provides Advanced RBAC support for its new modern Web UI. You can create custom roles and decide which user can restore from which server. Enterprise Manager is no longer required for that.

So maybe the best option for you is to migrate only the backup server directly to VSA and remove EM:
0.) Remove Enterprise Manager.
1.) Update VBR to V13.0.2 and keep the MSSQL database for now.
2.) Migrate the backup server from Windows to VSA: https://www.veeam.com/kb4800
3.) Update VSA to V13.1
4.) Configure custom roles and let your users restore through the new backup server Web UI

Best,
Fabian

[sarnold]

Thanks Fabian, that's super helpful!

I actually just remembered another reason we require Backup Enterprise Manager; PRTG monitoring. At the moment, PRTG Network Monitor's Veeam sensors are only written to check against Backup Enterprise Manager, not Backup and Replication. But hopefully as many people as possible can vote here so that native Backup and Replication sensors get created soon! Then we can eliminate Enterprise Manager altogether and use the native functionality you're talking about.

Does that Advanced RBAC support require the Veeam Software Appliance, or does that work on Windows servers as well with 13.1? As for the Windows server to Veeam Software Appliance migration, is that coming back in a future version of Veeam 13.x? Or is the only chance one will have to migrate to the Veeam Software Appliance while on 13.0.2, and if we upgrade past that, we've lost our chance?

[Mildur]

Advanced RBAC support and Backup Server UI works with both, Windows and VSA based backup server.
Future versions will allow migration again, potentially with v13.2.

Best,
Fabian

[DaStivi]

very important thing with migration to VSA is not to update to windows vbr 13.1, only update with 13.0.1 ISOs! its in the KBs but can be overlooked easily!

VSA Migration Version Limitation
The Windows-to-Linux conversion path has been tested and is supported on Veeam Backup & Replication 13.0.x only. It has not been validated against future releases, including 13.1, and will not be supported on that release.

If you plan to convert, do not upgrade to 13.1 until your conversion to the Veeam Software Appliance is complete, or you will remain on Windows.