Postgres & SQL Express to SQL server

[COGRobman]

We have a small environment of 20-25 servers (17-22 VMs, 3 physical servers).

Currently we have:
1 Veeam Backup & Replication VM (local M$SQL Express)
1 Veeam Office 365 VM (local PostgreSQL)
M$SQL server VM

I would like to install Veeam ONE and Veeam Backup Enterprise Manager on our VeeamBR VM. It appears Veeam Backup Enterprise Manager installs a local PostgreSQL instance while Veeam ONE uses standalone M$SQL. Since our environment is small, I don't see a reason to install a 3rd Veeam VM for Veeam ONE and Veeam Backup Enterprise Manager. However, having local M$SQL Express and local PostgreSQL on the same server/VM is not something that I'm very excited about.

Has anyone migrated their PostgreSQL VeeamBR & VeeamO365 databases to a standalone M$SQL server? I had opened a ticket with Veeam and was told installing all the things (VBEM & ONE) on one server is not recommended but is supported.

We don't have a DBA on staff, but some of us have more experience with M$SQL than PostgreSQL. So naturally getting everything to one database is win-win in our view.

Thoughts? Suggestions?

Thanks in advance.

[david.domask]

Hi Rob, welcome to the forums.

Veeam Backup for Microsoft 365 can only use Postgres as the configuration database, so while it's possible to use a dedicated MSSQL server for VeeamOne, Veeam Backup and Replication (VBR), and Veeam Enterprise Manager, Veeam Backup for Microsoft 365 will need to be on Postgres. I think there is logic in just using the instance that is installed with the software.

As for the consolidation the installations, it works just it's important to ensure sufficient cumulative resources for each of the installations (Enterprise Manager, VBR, and Veeam One). I think Support's statement may have been related to ease of management of the systems and ensuring proper resources. (i.e., if some maintenance operations requires a reboot for one of the services it will interrupt the other services)

I do recommend consider Postgres however, as it will be the focus moving forward, and we have quite a bit of tooling and documentation to assist with the configurations:

KB4638: How to Use Existing Veeam Backup & Replication PostgreSQL instance for Veeam Backup for Microsoft 365 Deployment
https://www.veeam.com/kb4638

KB4542: "SSPI authentication failed for user" (For VBR Postgres connection troubleshooting)
https://www.veeam.com/kb4542

Auto-configure PGSQL server resources
Set-VBRPSQLDatabaseServerLimits

So I would advise consider Postgres moving forward, there will be many resources available to assist with the common configuration challenges and maintenance.

[COGRobman]

Thank you David for your response. I guess my plan is not inline with Veeam's. When will Veeam ONE be supported using PostgreSQL?

After reading several posts, etc, Veeam ONE needed to stay with M$SQL due to reports, so that was part of my reasoning for trying to consolidate to a database server that we already pay for.

Case #07474943

[david.domask]

Happy to advise, Rob.

Regarding Postgres for Veeam One, it's planned, but no ETA at the current moment. I think everyone agrees not having multiple DB requirements is ideal, just will take some time.