How "convince" DBA team to use Veeam for SQL backups

[BostjanUNIJA]

Hi.
I have a specific scenario where DBA team has integrated SQL native backup on 1 hour.

SQL instance is 2019 STD, databases are in FULL recovery mode and they've created a task (on native SQL level - I believe over SQL agent jobs or maintenance task...) to backup those databases on every 1 hour.
I'm trying to explain to them as we already backup those virtual machines daily (with guest processing enabled) that maybe VBR would be a better choice. What argument should be used to explain to them why making hourly SQL backups with Veeam would be better then SQL native solution?

Also would like to add additional info on this specific scenario:

About 2-3 years ago we had a support ticket opened with Veeam (I need to find the exact ticket number..). For this specific SQL server we weren't able to complete application awareness, because SQL instances had to many databases (I think the number was somewhere between 2000 to 3000 SQL databases).
As far as I can remember application awareness triggered VSS event and VSS timeouted because of the number of databases that needed to be proccessed.
We even had increased some VSS timeouts in registry and that didn't help, so we had to turn off application awareness as that was the only way to have a SQL VM backed up.
I don't know if this issue has been resolved over the year with Veeam newer versions, and newer OS versions....

I think that's the reason maybe that DBA decided to have this native SQL backups, because we were able to achieve it with application awareness.

We also never tried to backup SQL instances with SQL plugin.

[BostjanUNIJA]

Found a case number: Case # 05916007

[PetrM]

Hi Bostjan,

Based on what you wrote, the SQL plug-in will be the perfect choice. Designed especially for managing a large number of databases, it does not use VSS. It is integrated with Microsoft SQL Management Studio and can be launched directly from it. Moreover, it is possible to create SQL Server Agent jobs directly from the plug-in UI. Storing backups in the Veeam infrastructure also enables various options for enhanced data protection, such as Immutability on a Linux-hardened repository. Additionally, if SOBR is present, you can offload and copy backups to the Capacity Tier. Furthermore, there is a dedicated backup copy job that allows you to comply with the 3-2-1 rule.

In version 13, it will be possible to store primary backups in the object storage repository, create encrypted backups, and perform quick rollbacks by replaying transaction logs instead of restoring the entire database.

For more information, please see this FAQ.

Thanks!

[BostjanUNIJA]

PeterM thank you for your reply