Azure SQL VMs backup cost estimates

Question

Azure SQL VMs backup cost estimates

TwickyBrain 45

I need to know the backup cost estimation for the Azure SQL VMs in our environment. Could you please guide how to find the backup estimated cost these VMs?

If needed I can help with the details.

Thanks!

0 comments

2 answers

Your answer

Answer 1

To estimate backup cost for SQL Server workloads running in Azure VMs with Azure Backup, gather these inputs and use the Azure Backup pricing estimator:

SQL workload size
- Total size of the SQL Server workloads to protect.
- Number of SQL workloads of that size.
Expected backup compression
- With SQL compression enabled, many Azure Backup customers see about 80% compression compared to SQL Server size.
- If the environment differs, enter a custom compression value.
Log backup size
- Estimate daily log backup size as a percentage of SQL Server size.
Daily data churn
- For databases, churn is typically High.
- If the actual churn percentage is known, use a custom value.
Backup policy
- Recommended policy: Daily differentials with weekly/monthly/yearly full backups. This is described as the most effective policy and supports restore from differentials through single-click restore.
- Another option is daily/weekly/monthly/yearly full backups, which uses slightly more storage.
- Define retention for:
  - Log backups: 7–35 days
  - Daily backups
  - Weekly backups
  - Monthly backups
  - Yearly backups
Backup storage redundancy
- GRS is recommended for highest availability and compliance needs.
- LRS is suitable for development or test environments that do not need enterprise-level backup.
Region or discounted rates
- The estimator also allows trying a different region or applying discounted rates.

For estimation tools:

Use the Azure Backup pricing estimator workbook to get detailed estimates.
Azure Backup pricing guidance for SQL in Azure VMs is covered in the Azure Backup pricing documentation.

If the environment details are available, the estimate can be built from:

SQL database/workload size
Number of protected SQL workloads
Compression expectation
Daily log growth
Churn rate
Retention policy
Redundancy choice
Target Azure region

References:

Estimate Azure Backup costs and understand pricing

Answer 2

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