Backup and retention
Version history, the recycle bin, and retention policies all protect data in specific, limited ways. Knowing exactly where that protection stops is the first decision, not an afterthought.
Book a scoping callFour things worth understanding
File-level undo for accidental edits and overwrites—not protection against a deleted site or a compromised account.
Deleted items are recoverable for a bounded window, not indefinitely, and that window can be shortened by other actions.
A hold preserves specific content for a legal reason and should be released deliberately, not left running by default.
Whether a separate backup tool is warranted depends on the data's value and how the organisation would need to recover it.
A plain distinction
Different tools, different promises.
Retention policies, version history, and the recycle bin all operate on the same live data set. They are genuinely useful and cover most day-to-day accidents, but they were designed as compliance and continuity tools first, not as a disaster-recovery product—recovery windows are bounded, and some deletion paths bypass them faster than people expect.
A true backup keeps an independent copy, recoverable even if the source data, the retention configuration, or an account is compromised. Deciding whether that extra layer is worth the cost is a business decision about risk tolerance, not a default either way.
Three moments this decision matters
Someone notices a missing file or mailbox weeks later, after the native recovery period has already closed.
Content needs to remain accessible to the business well beyond the point the account itself is disabled.
Specific content needs to be preserved exactly as it stood, separate from ordinary retention settings.
What belongs in the monthly view
Connect this to the rest of care