CCTV storage and retention: how to plan it without overspending
Storage is usually the second-largest line in a CCTV BOQ — and the most over-specified. Plan from three numbers: stream bitrate (Mbps per camera), retention days required by policy or regulator, and RAID overhead. Pair smart codecs (H.265, H.265+) with motion-based recording on low-activity zones to cut storage by 40–60% without losing forensic value.
How to picture it.
Worksheet: cameras × bitrate × hours × retention days ÷ codec efficiency, then RAID overhead and growth headroom — sized as NVR-attached, SAN or hybrid cloud cold storage.
From the field.
A 240-camera campus was quoted 1.2 PB for 30-day retention. Re-engineering with H.265+ smart codec, motion-based recording on parking and corridors, and a tiered hot/warm/cold storage plan brought the requirement to 410 TB — at the same forensic quality.
What to take away.
- 1Bitrate, not megapixels, drives storage. Tune VBR per zone.
- 2H.265+ and smart codecs cut storage 40–60% versus H.264.
- 3Tier storage: hot NVR, warm SAN, cold archive for incident retention.
- 4Plan RAID overhead and 20% growth headroom into the spec, not after.
- 5Match retention days to policy or regulator — over-retention is wasted money and a privacy risk.
Where this thinking shipped.
Corporate campus, Bengaluru
See projectsLogistics yard, North India
See projectsQuick follow-ups.
How many days of retention do we really need?+
Most enterprises plan 30 days hot, 90 days warm; regulated industries (banking, critical infrastructure) extend to 180–365 days on tiered storage.
NVR, SAN or cloud?+
Hot recording stays on NVRs near cameras. Warm/cold tiers go to SAN or object storage. Cloud is right for cold archive and disaster-recovery copies, not primary recording.
Talk to Arif directly.
From a single private theatre to a multi-site security programme — get an honest, experienced read.
Request a Project Review