immutable backup delete failed: retention lock still active

TL;DR

A delete blocked by active retention is object lock doing its job, not a fault. First confirm the object retention date and mode. In governance mode, an account with bypass rights can delete under your change process if business need is real. In compliance mode, nobody can delete early; schedule the deletion for expiry and stop retry loops that just generate errors.

immutable backup delete failed: retention lock still active

Use this when

• Delete or retention cleanup jobs fail with retention lock still active.
• Storage costs grow because expired-looking backups will not delete.
• An operator expected the retention to have ended already.

Not for this skill when

• Backups fail to write because job and bucket retention disagree. That is a mismatch problem.
• Objects without any lock fail to delete for permission reasons. Different cause.

Steps

1. List the objects failing deletion with their retention mode and retain-until dates. Verify: each object lock state is known
2. Compare those dates with the retention the business intended and find any setting that extended them by mistake. Verify: intended versus actual retention is reconciled
3. If governance mode and policy allows, perform the deletion with bypass governance retention rights under change control. Verify: deletion succeeds and is audit logged
4. If compliance mode, record the earliest deletable dates and schedule cleanup for then. Verify: future deletions are scheduled, not retried nightly
5. Adjust job retention for new backups so future locks match the intended period. Verify: new objects carry the corrected retention

Variant phrasings

cannot delete immutable backup retention active

The blocked phrasing.

s3 object lock delete failed governance bypass

The governance variant.

immutable storage cleanup retention not expired

The cleanup wording.

Compatibility: AWS S3 Object Lock compliance and governance modes and equivalent immutable stores with retention enforcement.

Why it happens

Retention locks exist to make early deletion impossible, including by administrators and ransomware. Backup cleanup jobs that were written before immutability do not know that, so they report designed behaviour as failure. The operational skill is distinguishing mode and dates, then working with the lock through governance process or calendar, never around it.

Edge cases / pitfalls

• Document retain-until dates in the backup catalog view so operators stop rediscovering them during incidents.
• Storage forecasts must include the locked tail. Finance surprises come from ignoring it.
• Accidentally long retentions, such as years typed instead of days, are only fixable in governance mode. Double-check units at setup.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstxt7VS3W8-fLUROs_mMI2g