NVR Storage and Retention Calculation Workshop

1. Retention is the design target

Define how many days/hours of recordings must be available and whether all cameras require the same retention.

2. Bitrate drives storage

Codec, resolution, frame rate, scene activity, noise, GOP and bitrate-control mode affect data rate. Axis documentation allows target bitrate and retention to be used to estimate storage.

3. Use the basic calculation

For a constant average bitrate estimate: storage bytes is approximately bitrate bits/second multiplied by recording seconds divided by eight. Then sum cameras and add project-defined headroom.

4. Do not use one bitrate for every camera

A quiet indoor corridor and a noisy outdoor tree line can compress very differently. Use camera-specific estimates or groups with similar scenes.

5. Continuous vs event recording

Event recording can reduce storage but retention becomes less deterministic because activity varies. Define what happens if activity is much higher than expected.

6. RAID changes usable capacity

NVR/NAS raw disk total is not the usable recording capacity. Account for RAID/protection and filesystem/platform overhead.

7. Check write performance

The storage must sustain aggregate camera writes while supporting playback, exports, analytics and rebuild conditions.

8. Validate after commissioning

After several representative days, compare actual average bitrate and retention against the design. Adjust quality or capacity deliberately, not reactively.

9. Record the sizing sheet

Keep camera count, bitrate assumptions, schedule, retention, usable capacity and measured post-install values with the system documentation.

Worked field scenario

A recorder has 32 TB raw disk and the requirement is 30 days retention. RAID reduces usable capacity and outdoor scenes may use more bitrate than quiet indoor scenes. Calculate from usable storage and per-camera bitrate, then verify actual retention after several representative days.

Procurement questions before ordering

The ordering stage is where many field problems are created. Capture the following before selecting the exact product:

• Purpose of every camera view
• Lens/FOV and target distance
• PoE requirement and switch budget
• Expected bitrate and retention
• NVR/storage, VLAN and UPS design

Where a manufacturer compatibility list, rail matrix, supported-optics table or battery cartridge reference exists, record the exact source used for the decision. That gives the later installer evidence rather than a verbal assumption.

Fault-finding decision path

Separate image, network, power and recording faults. A black or poor image can be optics/lighting while a missing recording can be NVR/storage. Check PoE state, link, IP reachability, time, stream bitrate and recording status in that order rather than factory-resetting cameras first.

Keep a simple change log while troubleshooting: observation, action, result. If a change does not alter the symptom, put the system back unless there is a documented reason to retain it. This prevents troubleshooting from becoming an uncontrolled configuration drift.

Common mistakes that create repeat faults

Do not choose cameras from megapixels alone. Do not aim one very wide camera at an area where identification detail is required. Do not size storage from raw disk capacity or a single guessed bitrate, and do not UPS only the recorder while leaving the PoE switch unprotected.

A technically successful installation can still be a poor operational result if the next technician cannot identify what was installed, why it was selected, or how it was tested. Serviceability is part of infrastructure quality.

Acceptance and handover evidence

Save camera names, locations, switch ports, cable IDs, IPs, time source, recording profile, retention target and representative day/night images. Confirm playback and export, not just live view.

Use filenames, labels and port/bay identifiers that match the physical installation. Handover evidence should let someone who was not present at the installation verify the final state and repeat the important tests later.