Start with detection delay
Think about an error discovered today that began before the latest backup. If every retained copy already contains the error, a technically working schedule will not solve that incident. Identify the oldest useful recovery point you need and the evidence that would tell you which copy to choose.
Copies and time differ
SimpleBackups documents retention by copy count for each schedule. Translate that count into the time horizon expected at your chosen frequency, then consider missed runs and schedule changes. Do not call seven copies a guaranteed seven-day history without checking how they were produced.
Coordinate deletion policies
A bucket lifecycle rule can remove files independently of a backup dashboard. Record which system governs deletion and whether retention settings conflict. Never experiment by purging real recovery copies. Changing a schedule can also leave files whose rotation needs separate attention; inspect the documented behavior before a change.
A review question
Fictional team: financial adjustments are reconciled monthly, but only a week of copies is retained. The team should examine its actual detection window and policy before declaring protection adequate. This is an operational planning example, not a legal retention recommendation.
Translate copies into approximate age
Fictional schedule: one completed copy every twelve hours with fourteen copies retained. At a steady cadence, the oldest of those fourteen copies is approximately thirteen intervals behind the newest: about six and a half days, not automatically seven full days behind the present moment. Actual completion times and gaps matter. Use the timestamps of real retained artifacts when making a recovery decision. Extra manual runs, changes in cadence or a separate storage lifecycle can alter the available history, so copy count alone is not a contractual time guarantee.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- SimpleBackups retention behavior — Merchant documentation · simplebackups.com · Merchant-controlled · checked 2026-10-01