Feature Request: Centeral SQL Server

[sunil.nagmal]

Hi Team,

Installing Veeam Endpoint Backup installs SQL Local DB.
Option to utilize an exiting SQL Server instead of installing localdb for infrastructure where SQL is already available.

Regards,
Sunil Nagml

[Vitaliy S.]

Hi Sunil,

In this case if the SQL Server hosting all the metadata goes down, Endpoint backups will not be possible. Can you please elaborate a bit more on this request? Just trying to understand all use cases possible.

Thanks!

[Dima P.]

Hello Sunsil,

It might be related to the central management, like in other paid products where you deploy a central server with one SQL on board and the agents use it. Since each Endpoint uses one local db right now it is not possible.

[bhively]

Utilizing a local, compact DB on each endpoint machine and a centralized backup option are not mutually exclusive. The local instance can easily store all the schedules, backup history, etc. while a central server could collect and collate the data from multiple endpoint systems and could also push new backup settings down to one or multiple machines. The feature set as-is competes nicely with some paid endpoint backup software, centralized management would just be icing on the cake. I wouldn't expect centralized management in a free product, but if it was added it would definitely make for a killer product.

[jonaz]

Having this product fully integrated into Veeam B&R would solve this issue and many more. I would love to see a free version, a paid version (for those who want central management and such), and a fully integrated version with Veeam B&R.

[bhively]

They don't even need to make a paid version. They could just add modules to Veeam Backup and Replication's Enterprise Manager console to be able to push/pull information from Endpoint clients so you could centrally manage the jobs, see successes/failures and other reporting information while the client piece remains free for everyone with the limitation that you can't centrally manage the systems without having an Enterprise Manager in your environment.

If they wanted to add a paid option, perhaps a dedicated, stripped down version of Enterprise Manager with just the capability to manage/monitor the Endpoint clients and nothing else. That would be a small one time cost to get the management aspects while keeping the spirit of the free product, no per-endpoint fees, you just pay for the management console.

[hoFFy]

Hi Sunil,

In this case if the SQL Server hosting all the metadata goes down, Endpoint backups will not be possible. Can you please elaborate a bit more on this request? Just trying to understand all use cases possible.

Thanks!

I think it would just save the resources that are needed by the LocalDB. Settings for Veeam Endpoint could be saved in an local config file, but statistics, maybe an index of archived files (as requested in other threads), and so on could be saved on a central SQL-Server. Or you could let the user choose how to store data: local or local/remote. As written above the config could be saved local, but restore of single files by searching all archives maybe only possible if the central SQL-Server is available - if not (in case of desaster), the user has to crawl manually through his backups...

[Vitaliy S.]

Yes, I see your point and it does perfect sense, though LocalDB should not take much resources > Design related