-
- Service Provider
- Posts: 9
- Liked: 2 times
- Joined: Feb 11, 2020 11:13 am
- Full Name: Sami Erjomaa
- Contact:
[Feature Request] MySQL and MariaDB support for VBR configuration database
This must have been asked before but I couldn't find it.
Plain and simple: add support to use MySQL and MariaDB as VBR configuration database.
Plain and simple: add support to use MySQL and MariaDB as VBR configuration database.
-
- Product Manager
- Posts: 14840
- Liked: 3086 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: [Feature Request] MySQL and MariaDB support for VBR configuration database
Hello,
actually you are really the first one for MySQL for the config database. The common request is Postgres SQL
Quick question: why do you want MySQL / MariaDB?
Best regards,
Hannes
actually you are really the first one for MySQL for the config database. The common request is Postgres SQL
Quick question: why do you want MySQL / MariaDB?
Best regards,
Hannes
-
- Chief Product Officer
- Posts: 31814
- Liked: 7302 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: [Feature Request] MySQL and MariaDB support for VBR configuration database
I'm afraid these won't scale to our needs these days anyway... backup server became too smart over years and from what I heard, we had to start using pretty advanced SQL Server capabilities for performance reasons. From open-source databases, I believe only the recent versions of PostgreSQL can more or less match them.
-
- Service Provider
- Posts: 9
- Liked: 2 times
- Joined: Feb 11, 2020 11:13 am
- Full Name: Sami Erjomaa
- Contact:
Re: [Feature Request] MySQL and MariaDB support for VBR configuration database
Hi,
Postgres would be ok too.
The main reasons for "open source" alternative is the 1 CPU limitation in the MS SQL Express and the license costs when upgrading to Standard.
Also supporting other than MS SQL would hopefully mean that the VBR could run on Linux in the future.
Postgres would be ok too.
The main reasons for "open source" alternative is the 1 CPU limitation in the MS SQL Express and the license costs when upgrading to Standard.
Also supporting other than MS SQL would hopefully mean that the VBR could run on Linux in the future.
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: [Feature Request] MySQL and MariaDB support for VBR configuration database
Someone who can afford a veeam solution for 300-500 vms and above should be able to pay for a prober sql standard license.
Below that number, sql express should be enough for small customers without a big budget.
I don‘t see the need of a open source solution here.
Below that number, sql express should be enough for small customers without a big budget.
I don‘t see the need of a open source solution here.
Product Management Analyst @ Veeam Software
-
- Veteran
- Posts: 643
- Liked: 312 times
- Joined: Aug 04, 2019 2:57 pm
- Full Name: Harvey
- Contact:
Re: [Feature Request] MySQL and MariaDB support for VBR configuration database
>I don‘t see the need of a open source solution here.
I do Why pay for something I don't need to?
I get what you're saying and I do agree, "If it's important, pay to protect it", and Postgres wouldn't necessarily solve the cost issues as you simply would shift the cost to maintaining a Postgres DB instead of an MSSQL server. But for quite a few persons, I could see this being beneficial; no built-in performance limitation, no size limitations, license considerations are __VERY__ convenient (for now though...)
So you're not wrong, but the benefits are pretty clear.
The costs of transitioning though I imagine must be pretty steep, as Veeam has 11 versions now of MSSQL under their belts and I suppose probably they know the strengths/weaknesses pretty well.
I do Why pay for something I don't need to?
I get what you're saying and I do agree, "If it's important, pay to protect it", and Postgres wouldn't necessarily solve the cost issues as you simply would shift the cost to maintaining a Postgres DB instead of an MSSQL server. But for quite a few persons, I could see this being beneficial; no built-in performance limitation, no size limitations, license considerations are __VERY__ convenient (for now though...)
So you're not wrong, but the benefits are pretty clear.
The costs of transitioning though I imagine must be pretty steep, as Veeam has 11 versions now of MSSQL under their belts and I suppose probably they know the strengths/weaknesses pretty well.
-
- Product Manager
- Posts: 9848
- Liked: 2607 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: [Feature Request] MySQL and MariaDB support for VBR configuration database
Hi Harvey
You are absolutely right.
From a financial view, it makes sense to prefer something free before paying for something. Most of the time
You are absolutely right.
From a financial view, it makes sense to prefer something free before paying for something. Most of the time
Product Management Analyst @ Veeam Software
-
- Veteran
- Posts: 643
- Liked: 312 times
- Joined: Aug 04, 2019 2:57 pm
- Full Name: Harvey
- Contact:
Re: [Feature Request] MySQL and MariaDB support for VBR configuration database
For sure ) But to reiterate, I get that there's no such thing as "free" in tech, so this is not just a matter of "migrate to Postgres". But if it's a slow, intentional, and planned move, I do think it'd end up being a net positive.
Who is online
Users browsing this forum: Google [Bot], Semrush [Bot] and 63 guests