What happens when our backups still contain records that are under a legal hold we tried to lift?

When you lift a legal hold, the obligation to preserve specific records ends. But lifting a hold does not automatically purge those records from your backup systems. Backups are point-in-time copies, and the records they captured while the hold was active will remain there until the backup itself ages out or is overwritten. Understanding this gap is essential to defensible information governance.

Why the records linger

Most backups are not designed for selective deletion. They are created on rolling cycles to support disaster recovery, and a single backup set may contain thousands of unrelated items in a compressed or imaged format. Surgically extracting one record from a backup is usually impractical and sometimes technically impossible. As a result, held records often persist in backups long after the primary copies are eligible for disposition.

This is generally acceptable, provided your organization treats backups consistently and in good faith.

The key distinction: active vs. disaster-recovery copies

Information governance practice draws a line between:

• Active recordkeeping systems, where you manage retention and apply disposition deliberately.
• Disaster-recovery backups, which exist to restore systems after a failure, not to serve as an archive.

Courts and governance frameworks have long recognized that organizations are not expected to mine disaster-recovery backups for routine disposition. What matters is that you follow a documented, consistently applied policy rather than making ad hoc decisions about individual records.

What to do

• Let backups expire on their normal cycle. Do not single out specific held records for special deletion or special retention once the hold is lifted; that can look like spoliation or favoritism.
• Document the disposition. Record that the hold was lifted, that primary copies were dispositioned per schedule, and that backup copies will age out under the standard rotation.
• Confirm no other hold applies. Before allowing anything to expire, verify the records are not subject to a separate hold, audit, or regulatory retention requirement.
• Suppress restoration if needed. If a backup is restored for unrelated reasons, ensure the once-held records are not reintroduced into active systems contrary to their retention schedule.

Consistency and documentation are your strongest defense. For broader context on retention, holds, and defensible disposition, see the information governance topic hub.