Skip to content
TechnoGuru — Think Technology, Think TechnoGuru

— CCTV Storage · 2MP

Axis AXIS P3245-LV (2MP) — storage & retention

Problem. A fleet of Axis AXIS P3245-LV (2MP) dome cameras recording continuously for 30 days needs a head-end sized before the NVR is ordered, not after. Getting the per-camera daily footprint wrong at the planning stage means a disk array that either runs out of retention early or sits over-provisioned.

Answer. 16 Axis AXIS P3245-LV (2MP) cameras at continuous 24/7 recording with 30-day retention land at roughly 10 TB of usable storage, around 22 GB per camera per day. At this camera count the recording head-end sits in the Entry NVR class. That figure is the recorded data volume; the calculator on this page reports about 12.9 TB, because this preset carries 24% headroom on top.

02 / In depth

How this preset reads — the engineering view.

The 2MP sensor at a typical 2 Mbps (30 fps) with Zipstream is the storage driver for this model — worked through continuous recording that comes to roughly 22 GB per camera per day. Zipstream is Axis's smart codec: it holds detail where a scene is active and lets static regions compress harder, so the recorded bitrate tracks real scene activity rather than staying pinned at a worst-case constant rate the way plain H.264 often does.

Scaling is linear from that per-camera figure: 16 cameras × 30 days of continuous recording is the roughly 10 TB result shown here. Add cameras or extend the retention window and the total moves in direct proportion — 32 cameras or 60 days each roughly double it. At 16 cameras and this bitrate, the recording head-end falls in the Entry NVR class rather than a multi-bay enterprise array.

Use the calculator by adjusting camera count, retention days and recording schedule to see the storage total recompute live. Switching the schedule from continuous ("always-on") to motion-only applies a duty-cycle factor that reduces recorded hours per day, which cuts the storage figure well below the continuous-recording baseline shown in this preset.

The calculator does not decide real-world scene-activity variance (Zipstream's actual bitrate moves with motion, lighting and clutter, so the 2 Mbps figure is a planning average, not a guarantee), RAID or storage-redundancy overhead, a failover or long-term archive tier, network write throughput at the switch, or the exact drive make-up and count for the physical build.

What this preset deliberately does not solve

  • The 2 Mbps bitrate is a typical scene-average for Zipstream, not a fixed or worst-case rate — busier scenes will record higher.
  • This preset assumes continuous 24/7 recording; switching to a motion-only schedule lowers the storage total by the duty-cycle factor.
  • The figure shown is raw usable storage before RAID or redundancy overhead, which a real build adds on top.

How this preset differs from its siblings

This camera's 2MP sensor and Zipstream codec put its typical bitrate at around 2 Mbps, notably lower than higher-resolution or plain-H.264 models covered in other presets on this tool. That lower per-camera bitrate is why the same 16-camera, 30-day scenario lands near 10 TB here rather than the larger totals a 4MP or 8MP fleet would produce, which is the reason this model gets its own preset rather than sharing a generic one.

02 / What that means, drawn

Cameras to rack · Zipstream · 30-day retention. Cameras: 16 cameras (2MP · 30 fps) — your figure. Per-camera stream: 2 Mbps, reached by profile default (Indicative) — published figure. Recorded to disk: 32.0 Mbps, reached by × 16 × 100% duty (24/7 continuous) — computed here. Storage: 12.9 TB, reached by × 30 days + 24% (0.8 TB per camera) — computed here. PoE load: no figure (the PoE tool sizes this) — not sized here. Switching: no figure (ports are sized elsewhere) — not sized here. Rack: no figure (rack units come from the kit) — not sized here.

32.0 Mbps live before the duty factor · linear in cameras, bitrate and days

This preset’s storage chain uses the same profile, duty factor and headroom as the calculator. Published profile figures retain their source status. Scene coverage, PoE, switching and rack design are not sized by this calculation.

03 / Hydrated calculator

Try the configuration — live.

The calculator below is preloaded with this preset’s state. Adjust any input — your URL stays shareable.

Loading the calculator…

· Next

Brief us on the project — with this configuration.

Presets are a typology starting point. The brief wizard captures the room geometry, programme and constraints we need to translate this configuration into a real design.