NVR / camera recording: hardware requirements guide
Always-on recording from IP cameras with retention policies.
Hardware requirements by tier
Three tiers for every workload: the minimum that works, the recommended sweet spot, and the comfortable headroom level. These are the same tiers the WisePC decision engine uses when it plans a build around your goal.
| Tier | CPU cores | RAM | Storage | GPU | VRAM | Network |
|---|---|---|---|---|---|---|
| Minimum | 4 cores | 8 GB | 4 TB (hdd) | None | — | 1 GbE |
| Recommended | 8 cores | 16 GB | 16 TB (hdd) | None | — | 2.5 GbE |
| Comfortable | 12 cores | 32 GB | 32 TB (mixed) | dedicated | 4 GB VRAM | 2.5 GbE |
| Overkill | 20 cores | 52 GB | 64 TB (mixed) | dedicated | 4 GB VRAM | 2.5 GbE |
Beyond Comfortable — 20 cores, 52 GB RAM, 64 TB (HDD): headroom you will never use for this workload alone. Put the difference into storage, backup or silence.
Recommended system shape
Derived by the decision engine from the recommended tier — the same logic that plans full builds.
- Form factor
- tower · 2× 3.5″ bays
- Build style
- diy
- Drive plan
- 2× 16TB HDD
Requirements (8 threads, 16GB RAM, 32TB storage) need a custom tower build.
One box or a separate machine?
Whether this workload deserves its own system or should live on the main server.
Consider a separate machine
Can grow past 32TB of storage — a dedicated NAS keeps the disk array and its redundancy separate from the compute that must stay up.
Storage arrays, priced
Five physical strategies for the recommended capacity — the same planner, drive model and reference prices as the storage planner tool.
| Strategy | Drives | Usable | Cost | Idle |
|---|---|---|---|---|
| CheapestRecommended | 2× 16TB hdd | 16 TB · parity1 | ≈ €480 | 12 W |
| Redundant | 4× 8TB hdd | 16 TB · parity2 | ≈ €600 | 20 W |
| Expansion-friendly | 2× 20TB hdd | 20 TB · parity1 | ≈ €600 | 14 W |
| Performance | 5× 4TB nvme | 16 TB · parity1 | ≈ €1200 | 5 W |
The balanced strategy gives you parity protection for a modest cost per TB — the right default for a family archive.
Backup is not storage
The extra copy that survives drive failure, deletion and ransomware — the same engine as the backup planner.
Protect 16TB with at least two copies on separate hardware, ideally one offsite. The recommended start is a dedicated NAS.
Recommended: Separate NAS — A dedicated box that only stores backups · ≈ €691
- No offsite copy (high): Add a second copy outside the building — cloud or a drive at a friend's house.
- No versioning (medium): Use a versioning-aware tool (restic, borg, Backblaze) that keeps history.
- Unscheduled backups (medium): Schedule backups automatically and monitor them.
- Backup on the same machine (medium): Keep the backup on separate hardware or offsite.
What will it cost?
Market-neutral EUR bands from the reference drive model (≈ = estimated street price). Live component prices resolve on the build page for your region.
- Storage array
- ≈ €480 – €1200
- Array energy / year
- ≈ €103/yr (∼47 W idle)
Compute (CPU, board, RAM, GPU) is not included — see the recommended build for live prices.
Growth outlook
What happens when the data keeps growing — the same engine as the growth simulator.
Storage stays within 32TB across the 3-year horizon — the architecture fits your expected growth. Add ~240€ and 1 bay(s) to reach 31TB within 32TB.
Add 1× 16TB hdd (~240€) — Cheapest strategy, 3 bays total for 31TB.
Also covered in this guide
Camera recording
Continuous camera streams written to disk with motion events.
Which tier do you need?
- Pick Minimum (4 cores, 8 GB RAM) only for a single-purpose machine on a tight budget — expect little headroom.
- Recommended (8 cores, 16 GB RAM) is the sweet spot: enough for the workload plus the usual side-services, without overspending.
- Pick Comfortable (12 cores, 32 GB RAM) when this workload shares the machine with others or will grow — you pay for headroom, not for anxiety.
- GPU rule for this workload: None.GPU rule for this workload: None (no discrete VRAM needed).
Frequently asked questions
How much RAM does nvr / camera recording need?
8 GB is the sensible minimum, 16 GB covers most real setups, and 32 GB gives comfortable headroom for growth and extra services.
How many CPU cores does nvr / camera recording need?
A 4-core CPU is the minimum, 8 cores is the recommended sweet spot, and 12 cores is comfortable when it shares the machine with other workloads.
Does nvr / camera recording need a dedicated GPU?
No — integrated graphics or a headless setup is enough.
What storage and network does nvr / camera recording expect?
Storage: 16 TB of HDD is the recommended baseline (4 TB minimum, 32 TB comfortable). Network: 2.5 GbE is the recommended baseline.
What runs well alongside nvr / camera recording?
It pairs naturally with: Camera recording, Object detection, Backup.
How much power does nvr / camera recording use?
The storage array idles around 47 W (≈ 103 €/year at 0.25 €/kWh). The full system adds CPU, board and fans on top — see the cost section for the honest bands.