HeatWave Introduces Soft Delete for Backups – June 3, 2025 Release


In the June 2025 update, Oracle’s HeatWave for MySQL introduced a powerful enhancement to its backup management: Soft Delete for Backups. Enabled by default for both automatic and manual backups, this feature adds a new layer of protection and control. Let’s dive into what it does and why it matters—backed by practical use cases.

What Is Soft Delete?

When a backup reaches its designated retention period, it typically transitions from ACTIVE to DELETE_SCHEDULED. Previously, this meant it was queued for immediate deletion—irreversible and sudden.

Now, with Soft Delete, backups in the DELETE_SCHEDULED state:

  • Remain accessible for an extra 7 days

  • Can be restored to ACTIVE if needed

  • During this period, they cannot be moved, copied, or restored until you cancel the deletion.

Why This Matters

1. Safety Buffer Against Accidental Deletion

Admins and automated scripts often manage retention settings. With soft delete, even accidental or overly aggressive deletion policies now have built-in undo protection.

2. Compliance & Audit Readiness

Need to retain data for an audit—even once it’s “expired”? The soft delete window allows backups to linger long enough to satisfy sudden compliance requests.

3. Operational Flexibility

Restoring a mistakenly deleted dataset? Soft delete lets you reverse the deletion without going through costly recovery procedures.

Real-World Examples

Example 1: Retail Analytics Recovery

A large retailer retains daily backups for 14 days. On day 15, the backup moves to DELETE_SCHEDULED. Midway through the soft-delete window, an analytics lead realizes they need historical sales data for a trending report:

  1. They navigate to HeatWave MySQL Console → Backups

  2. Identify the DELETE_SCHEDULED backup

  3. Click “Cancel Deletion”, returning it to ACTIVE

➡ They perform queries and export needed data—all without having incurred additional backup costs.

Example 2: Compliance Check Surprise

A financial services firm enforces a 30-day retention policy. A backup from day 30 enters DELETE_SCHEDULED. On day 32, compliance officers request evidence for a transaction from day 29. Thanks to soft delete, the backup is still available for inspection—ensuring audit compliance without emergency restores.

Example 3: Scripting with Confidence

A DevOps team deploys an automated cleanup script that retroactively deletes backups older than 7 days. With soft delete, the script no longer risks irreversible deletion; backups removed by scripts still remain recoverable for seven extra days, reducing stress around automation.

How to Enable / Use Soft Delete

You’ll find the feature enabled by default, but here’s how to adjust or disable it:

Via Console:

  1. Go to HeatWave MySQL → Backups → Edit backup

  2. Toggle Soft delete (defaults to Enabled)

  3. Save changes

Via CLI:

oci mysql backup update \
  --backup-id <backup_ocid> \
  --soft-delete DISABLED  # or ENABLED

This command updates backup metadata instantly.

Lifecycle Flow with Soft Delete

  1. Retention period ends → Backup enters DELETE_SCHEDULED

  2. 7-day grace window → Still recoverable

  3. If not restored → Permanently deleted after grace period

This ensures they’re safely retained just long enough to prevent data loss from oversight or delays.

Final Thoughts

By enabling Soft Delete, HeatWave delivers thoughtful backup retention enhancements that balance data safety, compliance readiness, and operational efficiency. It’s a small change with a big impact—especially for teams relying on mission-critical data and robust governance.

Comments

Post a Comment