Veeam One Database

[Rumple]

So I have a trial of Veeam One 13 trail running and it sure didn't take long to hit the limit on the database size.
CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 10240 MB per database.

I'm not going to pay for a full SQL server license + cal's to run Veeam One, but from what I can tell they don't support postgres (even though a database should be a database, all you need is the Db connectors...hell it should run with mysql if you really felt like it.

Anyone know if there is a way to switch the database. I can see where to change sql database and how to set retention (which can't even be less than a month)

Short term for trial I am going to upgrade SQL express to 2025 as the new DB limit is 50gb...which should help.

[jorgedlcruz]

Hello Mark,
Did you use our calculator before deploying? https://www.veeam.com/calculators/simple

The new SQL Express 2025 should be of help on your case, but I would be curious on understanding the number of workloads, if you are planning to use it for Monitoring Virtual Infra as well, etc.

Full PostgreSQL support is being considered for future releases.

I wish it was that easy as say, let's use some connectors to MySQL or any other DB, but how Veeam ONE was developed, it has lots of dependencies of SQL Server like reporting services, stored procedures, etc.

Keep us posted

[Rumple]

I just installed the community originally for the VBR monitoring and then got a trial license when troubleshooting community errors with 9 workloads so installed it.
Its a bigger environment so for production it would have to be I guess full SQL (which means I'm not going to be implementing that as we are an oracle shop. I didn't really think about it NOT supporting postgres since VBR uses postgres now.

A database is a database really so I can't figure out how or why its not already an option to switch to postgres..especially since you just released V13...seems like a missed opportunity (at least for new deployments)

PS..database upgrade went fine...however it seems to have broken the VBR licensing (same problem I had when I first implemented community) so I opened another ticket...see if we can fix that again. License is valid, but I technically think it broke all the licensing as Under instances there is nothing showing at all so even though Virtual Infrastructure is working, I suspect its not really licensed either but only VBR is giving an unlicensed error...

[jorgedlcruz]

Thank you, I hope the ticket can be resolved and work with SQL Express 2025. For v13, we fixed most of the Customer concerns, like first one it was VBR Data Collection (so we created an agent-based data collection, for WMI, and for GRPC as VBR v13 transitioned to that), for Reports generation speed (we had reports taking hours to generate qhen historical on our larger enterprises, now take under 5 mins, if not seconds. We used PpstgreSQL for that), and finally Reporting experience (we transitioned from old static SSRS, to fully HTML5 experience so you can customise any Veeam report the way you like, and do atomic filtering to just a single VM if you need to).

We couldn't add to that load, the full migration to PostgreSQL, but as we removed the SSRS dependency from our reports, it was a great step further for v13. The feedback has been possitive on all of the aspects mentioned.

Thanks, keep us posted