Why it matters
Long retention or forgotten long-term backups on a few databases can cost more than the databases’ own storage, and billing does not show the retention setting.How nOps finds it
nOps reads the last 7 complete days of Autonomous Database storage and backup storage billing. It works out each database’s backup-to-storage ratio and the median ratio across the tenancy, which needs at least 5 databases. A database is flagged when its ratio is at least 1.5 times the median and at least 3, and its backups were billed on at least 5 of the 7 days. The saving is what bringing it down to the median ratio would save on its backup cost, scaled to a month, and must be at least $5 a month. Tenancies with 90% or more of database spend covered by credits are left out.Before you start
Know the recovery and compliance requirements for the database, and permission to manage its backups.How to implement
- In the OCI Console, open the Autonomous Database and check its automatic backup retention period and any long-term backups.
- Confirm with the database owner how far back you need to be able to restore.
- Lower the automatic backup retention (it can be set between 1 and 60 days) to what you need.
- Delete long-term backups that are no longer required.
- Check backup storage over the following weeks.
Risks and considerations
- Deleted backups cannot be restored, and a shorter retention means you cannot restore to points before it.
- Some databases legitimately need longer retention; the comparison with other databases is only a signal.
- The change cannot be rolled back for backups that are already deleted.
FAQs
Why compare with other databases in my tenancy?
Why compare with other databases in my tenancy?
Billing does not show each database’s retention setting, so nOps uses the typical backup-to-storage ratio of your own databases as the reference.