An Azure backup service that provides built-in management at scale.
You need to evaluate two distinct pricing components: a Protected Instance Fee, which is a flat fee charged per database instance based on size, and Storage Consumption Costs, which are based on the amount of data stored in the backup vault.
Before calculating the cost, collect several metrics from your existing SQL Server instance. These include the size of the databases before compression and the number of database instances you run, the percentage of data that changes daily, and the size of daily transaction logs as a percentage of the database size. You also need to determine whether the backups will use Locally Redundant Storage or Geo-Redundant Storage. The price of LRS is lower, but GRS provides replication across regions.
The easiest way to obtain a concrete dollar estimate is through the Azure Pricing Calculator page at https://azure.microsoft.com/en-us/pricing/calculator/. Navigate to the Azure Pricing Calculator, search for Azure Backup, and add it to the estimate. In the configuration panel, locate the Workload Type dropdown and select SQL Server in Azure VM.
Enter your environment details into the calculator, including the Azure region, SQL Server size, and number of workloads. If you use native SQL compression, you can keep Expected Compression at the default 80%, which reduces the billable backup storage footprint.
Set the desired retention policy, including the number of days for daily backups and the number of weeks or months for longer-term weekly or monthly backups. The calculator will then generate an estimated Average Monthly Backup Data size and provide a Total Monthly Cost breakdown.
If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.
hth
Marcin