Why it matters
The geo-redundant default is often left as is, even for databases that would never be restored in another region, and backup storage grows with retention.How nOps finds it
nOps reads your pay-as-you-go Azure SQL billing for RA-GRS backup storage, including long-term retention backups. A database, elastic pool or managed instance is flagged when it was billed for RA-GRS backups on at least 25 of the last 30 complete days. The saving is its backup cost over the last 7 days, scaled to a month, times 37.5%. That is the smallest difference between ZRS and RA-GRS list prices across the regions in Azure’s price list, so the real saving is usually higher. It must be at least $5 a month.Before you start
Confirm that restoring in another region (geo-restore) is not part of your recovery plan. Permission to change the database (for example SQL DB Contributor).How to implement
- Check your recovery plan. If you rely on geo-restore, use active geo-replication or a failover group instead, or keep RA-GRS.
- In the Azure portal, open the database, go to Compute + storage and set Backup storage redundancy to Zone-redundant, or run
az sql db update --resource-group MY_RG --server MY_SERVER --name MY_DB --backup-storage-redundancy Zone. - For a managed instance, change the same setting on the instance.
- Update Terraform, Bicep or ARM templates to match.
Risks and considerations
- After the change you can no longer geo-restore the database in another region from its backups.
- Existing backups keep their old redundancy until they age out of retention, so the full saving arrives gradually.
- ZRS is not available in every region. Where it is not, locally redundant storage (LRS) is the alternative.
FAQs
Why 37.5%?
Why 37.5%?
It is the smallest price difference between ZRS and RA-GRS backup storage in any region, so nOps never overstates the saving.