By Cloudledger · Updated
Protection charges and storage charges are separate
Azure Backup typically bills a protected-instance component alongside the storage consumed by recovery points. Retention settings drive the storage part: longer retention keeps more restore points, and daily, weekly, monthly and yearly rules compound. A backup bill can rise for months after a policy change as older points accumulate.
Retention policy is the main cost lever
Review each policy against an actual recovery requirement. Many estates run default long-term retention on non-critical workloads. Shortening retention reduces cost but reduces how far back you can restore, so agree the change with the data owner and record the decision.
- List vaults, policies and the workloads attached to each.
- Compare retention against documented recovery requirements.
- Check redundancy settings on the vault.
- Identify protected items that no longer exist or are no longer needed.
Watch for protection that outlives the workload
When a VM is deleted, its recovery points can remain and continue to incur storage charges. That may be intentional. If it is not, removing protection requires care: deleting recovery points removes the ability to restore. Confirm ownership and compliance requirements before cleaning up.
Site Recovery has its own model
Azure Site Recovery is charged per protected instance in addition to the storage and any compute used during test failovers or actual failovers. A disaster-recovery test can therefore create a temporary cost increase that is expected rather than anomalous. Record test windows so later cost reviews can explain the spike.
Check the figure against the workload
Compare backup cost with the value and recovery requirement of the protected data. A small database with seven years of retention can cost more than the workload it protects. Cloudledger’s Cost Explorer can show backup and recovery meters alongside the rest of the estate for that comparison.