Azure MySQL Flexible Server Excessive Backup Retention
Backup storage beyond the included allowance is billed per gigabyte per month, and retention nobody chose is paid for every month it goes unreviewed.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, fixed.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Shorten backup retention on the MySQL flexible server. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
After a guided review, where you confirm the change, ZopNight applies a lifecycle policy, then checks the change took.
- Applies to
- MySQL Flexible on Azure
- The fix, by hand
- Confirm the resource is a non-production MySQL/PostgreSQL Flexible Server where shorter retention is acceptable.
- Flexible Server → Settings → Compute + storage → Backup.
- Reduce Backup retention period toward the supported minimum (7 days).
- Save; older backups outside the new window are pruned on the next backup cycle.
- Update DR documentation to reflect the new RPO/retention.
ZopNight does this for you after a guided review.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-246- Full reference
Related checks
See the oversized resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.