NVR Storage and Retention: Camera Count, Bitrate, Recording Mode, RAID and Capacity

1. Bitrate drives storage

Recorded data volume depends heavily on bitrate. Resolution influences bitrate, but codec, frame rate, scene complexity, quality settings and motion also matter. Use the camera/NVR planning data for the actual configuration.

2. Continuous versus event recording

Continuous recording produces a predictable stream of data. Motion or event recording can reduce storage use but depends on scene activity and detection behaviour. Critical evidence requirements may favour continuous recording for selected cameras.

3. Retention requirement

Define how many days of footage must remain available under normal conditions. Add operational margin and understand what happens when the recorder reaches capacity.

4. Simple capacity model

Approximate bytes = total average bitrate in bits/s x seconds retained / 8.

This is a planning calculation, not a product guarantee. Real systems add filesystem, database, RAID and platform overhead.

5. RAID and drive failure

Multi-drive NVRs may support RAID or other protection. Protection consumes raw capacity but can reduce the risk of losing all recording from a single drive failure. Verify supported RAID modes and drive requirements on the recorder.

6. Recorder camera limits

NVRs can have limits based on camera count, total bitrate, resolution, analytics or playback capability. Storage capacity alone does not prove the recorder can ingest the intended cameras.

7. Backup and export

Retention on the NVR is not the same as evidence archiving. Define how important clips are exported and protected from overwrite or recorder failure.

8. Sizing worksheet

• Record the exact model and firmware/software level.
• Verify physical interfaces and supported media.
• Confirm power, cooling and environmental requirements.
• Test the intended workload, not only basic connectivity.
• Record baseline measurements and configuration.
• Label and document the installation for future fault finding.

Field application and acceptance

This section turns the technical concepts above into a repeatable procurement, installation and handover process.

Field design workflow

Survey the site and define what each camera must achieve. Mark camera positions, target scenes, lighting, cable routes, switch locations and recorder location. Estimate camera bitrate and PoE demand, then design storage retention, VLANs, uplinks and UPS coverage. Only then select the camera and NVR models.

Questions to answer before ordering

• What must each camera observe, recognise or identify?
• What lens/field of view and low-light behaviour are required?
• Indoor, outdoor or vandal-resistant construction?
• What PoE class or other power source is required?
• What recording platform and compatibility are required?
• How many days of footage must be retained?
• What switch ports, uplink bandwidth and UPS runtime are required?
• Who may view, export and administer footage?

Fault-finding method

Separate camera, power, network and recorder faults. Confirm camera power and link, switch PoE state, negotiated speed, VLAN/IP path and recorder reachability. For image problems, inspect lens cleanliness, focus, exposure, IR reflection and scene lighting. For missing recordings, check recorder health, storage capacity, retention policy and camera stream status.

Operational documentation

Record camera ID, model, serial, physical location, viewing direction, IP address, switch port, cable ID, PoE requirement, NVR assignment, recording mode and retention policy. Maintain an authorised-user list and an evidence-export procedure.

What correct looks like

Each camera produces usable images for its stated objective in day and night conditions, the network and PoE path are stable, recording retention meets the requirement, time is synchronised, alerts are meaningful, UPS protects the critical path and the system can be maintained from accurate documentation rather than trial and error.