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.
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.
Statistics: Posted by david.domask — Oct 23, 2024 9:58 am