Skip to main content

Retention

Four retention tracks. One image at the intersection.

Daily, weekly, monthly, yearly tracks. Each backup image qualifies for one or more tracks based on its timestamp. Pin specific images so they never expire. Refcount-based dedup keeps storage minimal.

GFS retention tracks in BigMind — daily, weekly, monthly, yearly slotsClick to enlarge
0
Daily slots
recent days
0
Weekly slots
a year of weeks
0
Monthly slots
a year of months
0
Yearly slots
multi-year history

The four tracks

Daily, weekly, monthly, yearly — each on its own clock.

GFS-style retention runs four independent tracks. Each backup image qualifies for one or more tracks based on its timestamp, and each track keeps its own slot count.

Daily track

Up to 30 recent daily recovery points on paid tiers — the fine-grained "yesterday afternoon" rollback you reach for most often.

Weekly track

Up to 52 weekly points on DR Pro and Resilience Pro — a full year of week-end images for medium-horizon recovery.

Monthly track

Up to 12 monthly points — a month-end image kept for each of the past 12 months for longer compliance windows.

Yearly track

Up to 7 yearly points on Resilience Pro — a year-end image preserved for multi-year retention and audit history.

How GFS retention works

4 independent tracks. Intersection counts.

An image at the intersection of several tracks counts toward all of them at once, and overflow is handled per track — so one image is never double-stored and never lost while any track still needs it.

  • 4 independent tracks: daily / weekly / monthly / yearly
  • Each track has a slot count, configurable per tier
  • An image at the intersection (Saturday 6pm + month-end + year-end) counts toward all 3 tracks
  • When tracks overflow, the oldest in-track image expires from that track only — the image survives if any other track still references it
GFS retention track intersection and overflow in BigMindClick to enlarge

Pin & dedup

Mark images permanent. Store shared chunks once.

Mark images permanent

Mark a specific recovery point as "permanent" — it survives all retention pruning. Useful for compliance evidence preservation, post-incident snapshots, and baseline references.

Refcount-based dedup

A single chunk shared across 5 retained images is stored once. Real-world storage growth on a typical org runs 1.5–2× the initial backup size for full 4-track retention.

Per-tier slots

How many slots in each track.

TierDailyWeeklyMonthlyYearly
DR Free7
DR Plus3012
DR Pro305212
Resilience DR-Only3012
Resilience Standard301212
Resilience Pro3052127
Resilience Enterprisecustomcustomcustomcustom

GFS retention. Refcount dedup. Pinned images.

Four independent tracks, one image at the intersection, and storage that grows by 1.5–2× — not by the number of recovery points.