Postgres vs SQL

[mrodriguezCC]

Can anyone tell me if future versions (hopefully the next one), will be using Postgres instead of SQL, like the VBR's are switching to?

[Mildur]

Hi Michael

Welcome to the forum.
Veeam One V12 will continue to use MSSQL as the database. There are dependencies on MSSQL components which cannot be simply replaced by Postgres.

Thanks
Fabian

[RomanK]

Hello Michael,

Recently when I discussed this question with devs they told, me that in theory, it should not be hard just to switch the database for the UI data. But currently, Veeam ONE is using SSRS for the reports and that is the сase. They would need to rewrite and test each and every report as well as a few other things related to reporting services. It's a big task.

As Fabian mentioned, v12 would use MSSQL and we cannot comment anything about the future as things are subject to change.

Was it just a question of curiosity or do you have issues with MSSQL and Veeam ONE?

Thanks.

[mrodriguezCC]

Its not really an issue, but clients that have large infrastructures and do not want to pay for an SQL license, they will not have reporting enabled for the Virtual Infrastructure tab.

Thank you for your responses.

[kpolsana]

Hello,
Sorry for this is being out of scope in this thread but I'm looking to add PostgreSQL to Power BI desktop, when adding the connection I was getting error saying "we encountered an error while trying to connect. Details: "PostgreSQL: SSPI aurgebtucation but integrated security not enabled " I really appreciate if you can help fix this issue. Thanks

[Mildur]

Hi Koushik

That question seems out of Veeam's scope.
From reading the error message, you have to enable additional security mechanism inside the PostgreSQL database.
Have you tried to find an answer in PostgreSQL support forums? I found some blogs and guides with Google.
As an example this wiki link: https://wiki.postgresql.org/wiki/Config ... on_Windows

Thanks
Fabian

[ashleyw]

Hi,
I just wonder now that V12 has been released to service providers what the roadmap look like for VeeamOne to switch to PosgreSQL?
We upgraded out development infrastructure a few days ago, and all is well, but we'd really like to see PostgreSQL as a deployment/migration option for VeeamOne.

I fully understand the SSRS dependencies but I think it would be to everyone's benefits if these could be worked through and replaced with cross platform equivalents.
On some of our own development projects we are starting to use Birt etc where applicable.
The SQL Express instance size issue is the main issue specifically with VeeamOne, and this requires regular intervention to keep it within size limits.

Eventually we'd love to see all the Veeam products including the main Backup and replication product available to run on PostgreSQL and deployable on Linux platforms to avoid unnecessary Microsoft licensing and to be able to scale to our requirements.

thanks again.
Ashley

[RomanK]

Hello Ashley,

You are right, benefits are seen and the SQL Express limitations are annoying.
On the other side, nothing has changed since my last post in this thread. Each and every report must be rewritten then tested then, probably, rewritten again and probably optimized to the new database. There are also other complicated things and not only reporting would be affected.

I can't add anything to the above at least now.

Thank you for the feedback and stay tuned

[albertwt]

Can anyone tell me if future versions (hopefully the next one), will be using Postgres instead of SQL, like the VBR's are switching to?

Yes, I agree with @Mildur,

The Custom Reporting service is utilizing the Microsoft SQL Server features.

[mcz]

In a relatively small environment the veeam one database has hit 10 GB disk space and now there are some issues due to that. We did decrease the retention from 10 to 8 months, but nothing has happened so far allthough we removed the old data...

I guess it's time to switch to pgsql... Any news on that topic? Thanks!

[jorgedlcruz]

Hello Michael,
No news regarding fully migration to PostgreSQL, you can always change the data collection mode, which is without a doubt the most problematic use-case, like using Veeam Backup Data and VMware, without large-scale, will take a lot of database, some links:

• https://helpcenter.veeam.com/docs/one/d ... ml?ver=120
• https://www.veeam.com/calculators/simpl ... ing/backup

Perhaps you can change to large-scale VMware, or if not using VMware monitoring, even select the backup data only.

Give it a try and let us know.

[mcz]

Hi Jorge,

I have switched to large-scale 10 days ago, but still, nothing has changed. veeam one reports 100 % db usage and the db-file itself is also around 10 GB according to SSMS. Do I have to trigger a manual cleanup or something similar? Thanks!

[RomanK]

Hello Michael,

It is not recommended to manually change anything in the Veeam ONE database. You may try to open a support case. Our engineers should be able to determine if the growth is natural and expected. If not, they should be able to clean the database of unnecessary data and give advice on how to decrease the usage in your particular case.
If you do so, please share the case # in this thread for transparency.

Thanks

[mcz]

Well, by "manual cleanup" I mean starting a procedure or the cleanup task via the veeam one settings... I've created a case: #07313168

[RomanK]

Hello Michael,

Thanks for the case number. I can see that the T2 team was involved in the troubleshooting. Some tables related to the data collector mechanics are unusually huge.
Please continue to work with our support engineers. I'm confident they will find the cause of this issue.

Thanks

[RomanK]

Hello Michael,

It would be useful to know that VONE db retention "applies" to the session data immediately, while it applies to restore point data only when the restore point is deleted. It makes sense as the object is presented in the infrastructure. If I remember correctly, the VB365 repository has a retention of 3 years by default.

So if this is your case, the monitoring data about your restore points would be stored for a long time. Having thousands of processed objects per day in a relatively small environment could generate a lot of data.

Anyway, I believe support engineers will check the diagnostic information and let you know the outcome.

Thanks

[mcz]

Ok folks, the result is that the VBO-data is very huge compared to other objects. The problem is that there is only one retention for all objects - you can't distinct between vbo and the "rest". Now it makes sense that the db exploded a short time after I have added a vbo server.

The solution was to buy a SQL-license so that there won't be the 10 GB limitation anymore, but to be honest: That's quite a waste of money for a small environment. The best solution for me was to switch to PGSQL or to somehow split the database, but I guess that's not possible right now.

Any ideas?

[mcz]

guys? any updates please?

[Vitaliy S.]

Hi Michael,

Yes, splitting the database is not possible (if that's the question), and PostgreSQL is not supported by Veeam ONE yet.

Thanks!

[mcz]

Is my assumption right that there will be a change (whatever it might be) in future releases?

[RomanK]

Hello Michael,

This assumption is always right! Everything is always changing. New releases bring not only new features, new reports or alarms, but there are always changes and improvements in the architecture and the way we work with the data.
We can't talk about any details... until we can. Please follow this forum and other official Veeam channels. Until that, no promises or approximate ETA.

Thank you and stay tuned