Configured retention is not actual retention
Retention in a recorder is not a setting that holds; it is an equilibrium that drifts. The configuration says 'keep 30 days or overwrite when full' - and 'when full' wins every time. Actual retention is whatever your storage can hold at your current write rate, and that number changes every time anything about the system changes.
The write rate only ever goes up: cameras get added, resolutions and frame rates get raised, motion-only channels get switched to continuous after an incident, H.264 scenes get noisier in winter rain. Storage, meanwhile, only ever goes down - disks fail and get removed from arrays, volumes are shared with new systems. The result is a retention window that shrinks silently, month after month, while the configuration screen still says 30.
What a shrunken window costs
Investigations that die at the archive
Incidents are often reported late - a theft noticed at stocktake, a complaint filed a month after the event. If actual retention is 11 days, everything older is permanently unanswerable.
Contract and policy breaches
Where retention is promised to customers, insurers or regulators, the requirement is the number - not 'usually about that much'. A measured shortfall found by an auditor is a finding; found by you, it is a maintenance ticket.
False confidence
Teams plan investigations, exports and legal holds around the configured number. Every decision made on a wrong retention assumption inherits the error.
How retention monitoring works
The measurement itself is simple to state: for each recording system, find the oldest retrievable footage per channel, compute its age, and compare against the required window. The oldest-footage query runs through the recorder's archive search - the same interface used for playback - so the number reflects what is actually recoverable, not what an index claims.
Doing this well means doing it continuously and per system. Retention differs recorder by recorder (different disks, different channel loads), and the trend matters as much as the number: a window that shrank from 34 to 31 days over two months is on a trajectory that crosses your 30-day requirement soon. Continuous measurement turns that into an early warning instead of a surprise.
IOSentra runs retention tracking as part of its storage monitoring: measured retention per system, compared against the window you define, with an incident opened when the real number approaches or breaches the requirement - routed to whoever owns that site's hardware.
Retention health checklist for any estate
- A written required-retention number per site or system - the comparison baseline
- Measured oldest-footage age per recorder, refreshed at least daily
- Alerting on approach, not just breach - trend crossing the requirement within weeks
- Storage health watched alongside - failing disks are tomorrow's retention loss
- A documented history of measured retention for audits and disputes