# Unnecessary use of RA-GRS for Azure SQL backup storage Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/unnecessary-use-of-ra-grs-for-azure-sql-backup-storage Azure SQL databases often use the default backup configuration, which stores backups in RA-GRS storage to ensure geo-redundancy. By: Balazs Engedi Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Unnecessary Use of RA-GRS for Azure SQL Backup Storage The short version Azure SQL databases often use the default backup configuration, which stores backups in RA-GRS storage to ensure geo-redundancy. [Balazs Engedi](https://www.linkedin.com/in/engedib/) FinOps Specialist @ KPN Azure service [Azure SQL](https://www.pointfive.co/efficiency-hub/cloud-services/azure-sql) Category [Databases](https://www.pointfive.co/efficiency-hub/service-category/databases) Reference CER-0031 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. While suitable for high-availability production systems, this level of resilience may be unnecessary for development, testing, or lower-impact workloads. Using RA-GRS without a business requirement results in avoidable costs. Downgrading to LRS or ZRS - where appropriate - can significantly reduce monthly backup storage spend. Backup frequency and retention stay the same, but switching to LRS or ZRS disables geo-restore as soon as the change is made. The change applies only to new backups (existing backups stay in the old storage until their retention expires) and can take up to 48 hours to apply. Hyperscale backup redundancy can only be set at creation, so changing it requires a database copy or geo-replication. ## Billing model The pricing dimensions that drive this cost. - Backup storage is charged per GB-month, but vCore databases are billed only for backup storage above the maximum data size (in the DTU model, PITR backup storage is included in the database price), so savings apply to that excess and to LTR backup storage - RA-GRS (geo-redundant) storage is the default; geo-zone-redundant storage (GZRS) is also offered, and LRS is the least expensive option - LRS (Locally Redundant Storage) and ZRS (Zone Redundant Storage) are lower-cost alternatives - Changing backup storage redundancy lowers the per-GB rate for billable backup storage without affecting primary database performance ## How to detect 4 checks to find it in your estate. - Review backup redundancy settings for Azure SQL databases - Identify databases with RA-GRS enabled by default - Determine whether geo-redundant backup storage is a business or compliance requirement - Validate whether LRS or ZRS would be sufficient based on workload criticality and risk tolerance ## How to fix 4 ways to remove the waste. - For non-critical or non-regulated workloads, change the backup redundancy setting to LRS (or ZRS where supported) - Document any exceptions where RA-GRS must be retained for compliance - Incorporate backup configuration reviews into provisioning and governance processes - Monitor backup storage cost trends following changes to confirm savings ## Documentation Vendor references for pricing and configuration. - [Automatic, geo-redundant backups - Azure SQL Database learn.microsoft.com](https://learn.microsoft.com/en-us/azure/azure-sql/database/automated-backups-overview) - [Change automated backup settings - Azure SQL Database learn.microsoft.com](https://learn.microsoft.com/en-us/azure/azure-sql/database/automated-backups-change-settings#configure-backup-storage-redundancy) - [Azure Storage Redundancy Options learn.microsoft.com](https://learn.microsoft.com/en-us/azure/storage/common/storage-redundancy) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure SQL CER-0053 ### [Business Critical Tier on Non-Production SQL Instance](https://www.pointfive.co/efficiency-hub/inefficiencies/business-critical-tier-on-non-production-sql-instance) Non-production environments such as development, testing, or staging often do not require the high availability, failover capabilities, and premium storage performance offered by the Business Critical tier. Running these workloads on... Databases - Azure SQL CER-0264 ### [Suboptimal Use of Serverless Compute for Azure SQL Database](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-use-of-serverless-compute-for-azure-sql-database-4fe48) Serverless is attractive for variable or idle workloads, but it can become more expensive than Provisioned compute when database activity is high for long portions of the day. As active time increases, per-second compute accumulation... Databases - Azure SQL CER-0263 ### [Suboptimal Use of Provisioned Compute for Azure SQL Database](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-use-of-provisioned-compute-for-azure-sql-database-9bb83) Databases deployed on Provisioned compute incur continuous hourly charges even when workload demand is low. For databases that are active only briefly within an hour, or for limited hours per month, Serverless can provide significantly... Databases --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.