GCP Cloud SQL Excessive Backup Retention for Dev/Test
Backups are billed per gigabyte per month, and a dev/test instance keeping weeks of them is paying to preserve states nobody restores.
Free to start. No card. The playground just needs your work email.
Google Cloud
Found, explained, fixed.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Shorten backup retention on the Cloud SQL instance. 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
- Cloud SQL on Google Cloud
- The fix, by hand
- Open Cloud Console → SQL → Instances → the resource → Backups tab.
- Click EDIT BACKUP SETTINGS and adjust Number of backups to retain.
- Confirm with your compliance / governance owner before reducing 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-147- 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.