Skip to main content

VBR and VEM using PostgreSQL, however VeeamONE still using MSSQL, I am looking forward to see VeeamONE using PostgreSQL, it will be great to unify the DBs for Veeam infrastructure.

I totally understand and would like to have that too. I think the challenge is that a lot of the functionalities in Veeam ONE are based on SQL Reporting Services. So I wouldn't expect a too quick solution....


Let's have hope for that in v13!


It'll get there...soon we hope 🙂


Let's have hope for that in v13!

🤞


We are migrating to Postgres now with 12.1 so will be nice when VONE and VSPC move to that DB option.  Looking forward to it but not a big deal at the moment.


We are migrating to Postgres now with 12.1 so will be nice when VONE and VSPC move to that DB option.  Looking forward to it but not a big deal at the moment.

I’ll be curious to read your feedback after few weeks, large VBR? Tapes? pgsql for backup db on vbr? Dedicated VM? Linux or windows?


We are migrating to Postgres now with 12.1 so will be nice when VONE and VSPC move to that DB option.  Looking forward to it but not a big deal at the moment.

I’ll be curious to read your feedback after few weeks, large VBR? Tapes? pgsql for backup db on vbr? Dedicated VM? Linux or windows?

I am setting up Ubuntu 22.04 servers with Postgres 16.  I did a test in my lab and migrated both VEM, VBR and VCC over to the server.  Everything works well and removes the need for SQL which is going to save us money.


Je viens de voir une nouvelle interface pour Veeam ONE au VeeamON 2024, si quelqu’un à des infos.


We are migrating to Postgres now with 12.1 so will be nice when VONE and VSPC move to that DB option.  Looking forward to it but not a big deal at the moment.

I’ll be curious to read your feedback after few weeks, large VBR? Tapes? pgsql for backup db on vbr? Dedicated VM? Linux or windows?

I am setting up Ubuntu 22.04 servers with Postgres 16.  I did a test in my lab and migrated both VEM, VBR and VCC over to the server.  Everything works well and removes the need for SQL which is going to save us money.

I have BEM/VBR using PG16 on a dedicated Rocky server, but I seem to recall Veeam saying that the only officialy-supported configuration for the config database on Postgres is when Postgres is installed on the VBR server itself.  That said, I haven’t had any issues with this config.


We are migrating to Postgres now with 12.1 so will be nice when VONE and VSPC move to that DB option.  Looking forward to it but not a big deal at the moment.

I’ll be curious to read your feedback after few weeks, large VBR? Tapes? pgsql for backup db on vbr? Dedicated VM? Linux or windows?

I am setting up Ubuntu 22.04 servers with Postgres 16.  I did a test in my lab and migrated both VEM, VBR and VCC over to the server.  Everything works well and removes the need for SQL which is going to save us money.

I have BEM/VBR using PG16 on a dedicated Rocky server, but I seem to recall Veeam saying that the only officialy-supported configuration for the config database on Postgres is when Postgres is installed on the VBR server itself.  That said, I haven’t had any issues with this config.

Yeah you should not have issues for supported configuration like this.  Just ensure that the Rocky version is in the support matrix.  We are using Ubuntu 24.04 as that is supported for sure.


I have BEM/VBR using PG16 on a dedicated Rocky server, but I seem to recall Veeam saying that the only officialy-supported configuration for the config database on Postgres is when Postgres is installed on the VBR server itself.  That said, I haven’t had any issues with this config.

Yeah you should not have issues for supported configuration like this.  Just ensure that the Rocky version is in the support matrix.  We are using Ubuntu 24.04 as that is supported for sure.

 

So Veeam does officially support PG on a standalone machine?  The implication here is that only MS SQL can be used as a remote instance.


I have BEM/VBR using PG16 on a dedicated Rocky server, but I seem to recall Veeam saying that the only officialy-supported configuration for the config database on Postgres is when Postgres is installed on the VBR server itself.  That said, I haven’t had any issues with this config.

Yeah you should not have issues for supported configuration like this.  Just ensure that the Rocky version is in the support matrix.  We are using Ubuntu 24.04 as that is supported for sure.

 

So Veeam does officially support PG on a standalone machine?  The implication here is that only MS SQL can be used as a remote instance.

To me as long as it follows their best practices it should be supported.  Maybe this wording will change once v13 comes out?


Comment