Azure SQL Backup License

[agrob]

Good Day

As i have seen, there is a VUL needed for every Azure SQL DB we want to protect with VBA. As Veeam was not able to do those kinds of Backups, we used another product in the past. This solution is doing more or less the same, backup the DB with BACPAC. The SW supports also Backup for PostGre DB on Azure and is way cheeper. In my opinion, you should overthink the License price for Azure DB Backup. It would be fine to use a VUL per SQL Server, and not per SQL DB. We have a Azure SQL Server with about 15 small DBs. To use 15 VUL is to expensive and for now, we will use the other product for DB backups.

Just my opinion...

Best Regards

[Gostev]

Hi Andre

Unfortunately this decision flew under my radar. I agree this licensing makes no sense and moreover does not match how we license all other workloads in all other products.

Let us take a closer look. I think it should be 1 VUL per 1 Azure SQL Managed Instance, just like we have it for on-prem SQL Server.

Thanks!

[agrob]

Hello Gostev

Thank you for your reply and that you will overthink the license for Azure DB. I just thought that the license as it is for Azure DB now is maybe for other Customers also to expensive. So I thought better post this question here than just not using the feature....

Looking forward if it will be changed

Best Regards
André

[nielsengelen]

Hi André,

We are indeed looking into this but no update yet on any potential changes. Once we know more, we will update this topic.

[nielsengelen]

Good news @agrob. We will be changing the licensing model to align with our other products in an upcoming update so it won't consume 1 VUL per DB but 1 VUL per SQL instance.

[agrob]

Hello Niels, Good News, Thanks!

[Vitaliy S.]

The licensing model has been adjusted in Veeam Backup for Microsoft Azure v3a which is now Live in the Marketplace. Thanks for your feedback!

[agrob]

Thanks!