CCTV/NVR Storage Server Sizing Guide for Large Camera Networks in India
Quick answer: storage need comes down to one formula — bitrate per camera × number of cameras × retention days, converted to gigabytes. A 64-camera network recording continuously in H.265 at 1080p for 30 days typically needs somewhere in the 15-25TB range, but the exact number swings a lot with codec, resolution, frame rate and whether you're recording continuously or only on motion. For a retail chain, factory floor or campus running dozens to hundreds of cameras, that math — plus the right RAID setup — is what actually determines whether your NVR server holds up.
Why a Standalone NVR Appliance Stops Working at This Scale
A consumer or small-business NVR box — the kind with 4, 8 or 16 built-in channels and a couple of drive bays — is fine for a single shop or small office. Once a deployment grows past that, the constraints show up fast: limited drive bays cap total storage, the onboard CPU can't keep up with dozens of simultaneous streams plus any video analytics, and there's no real path to RAID redundancy beyond basic mirroring. Retail chains, manufacturing plants and campuses running a large, growing camera network are usually better served by a proper server running VMS (video management system) software — Milestone, Genetec, Hikvision's iVMS/Blazer, Dahua's DSS or similar — backed by dedicated, expandable storage. It's the same shift a business makes moving from a desktop-class NAS to a rack-mounted SAN storage array once data volumes outgrow a single box.
The Real Storage Math
The formula used by every major VMS vendor's own storage calculator is straightforward:
Storage (GB) = (bitrate in Kbps × 3600 × 24 × retention days × number of cameras) ÷ (8 × 1024 × 1024)
The variable that moves the number most is bitrate, which itself depends on:
- Codec: H.265 (HEVC) typically needs roughly 40-50% less bitrate than H.264 for comparable image quality — the single biggest storage-saving decision you can make when specifying new cameras.
- Resolution: a 2MP (1080p) stream commonly runs 2-4 Mbps in H.264 or roughly 1-2 Mbps in H.265; an 8MP (4K) stream can run 4-8x that.
- Frame rate and scene complexity: a busy loading dock or factory floor with constant motion pushes bitrate meaningfully higher than a quiet corridor at the same resolution.
- Continuous vs motion-triggered recording: motion-only recording can cut storage need dramatically, but many compliance-driven deployments (banking, high-security sites) specifically require continuous recording, so check your requirement before assuming you can rely on motion detection to save space.
These are approximate, industry-standard estimation figures used for planning, not a guarantee for your exact scene and settings — always size with headroom, and re-check actual per-camera bitrate against your specific camera model's datasheet before finalizing an order.
Approximate Storage by Camera Count and Retention (2MP, H.265, continuous recording)
| Cameras | 30-Day Retention | 60-Day Retention | 90-Day Retention |
|---|---|---|---|
| 16 | ~4-6 TB | ~8-12 TB | ~12-18 TB |
| 32 | ~8-12 TB | ~16-24 TB | ~24-36 TB |
| 64 | ~15-25 TB | ~30-48 TB | ~48-72 TB |
| 128 | ~30-48 TB | ~60-96 TB | ~96-144 TB |
These ranges assume ~1-2 Mbps per camera at 1080p in H.265. Switch to H.264, higher resolution, or busier scenes and the real number moves toward or past the upper end — always size storage for your actual bitrate, not just camera count.
RAID for Surveillance Storage — Different Rules From General-Purpose Servers
CCTV/NVR storage is a continuous, high-volume sequential-write workload running 24/7 — meaningfully different from typical file-server or database I/O patterns, and it changes a few decisions:
- Use surveillance-rated or nearline-SAS/enterprise drives, not desktop drives. Standard desktop hard drives aren't built for round-the-clock write cycles and fail faster under this load; surveillance-rated and enterprise/nearline-SAS drives are specifically rated for continuous read-write duty.
- RAID 5 or RAID 6 is the common choice for large NVR arrays — RAID 6's extra parity drive matters more here than in general server storage, because a failed drive during a long rebuild window is a real risk with large-capacity drives, and losing footage during a rebuild defeats the point of having redundancy.
- RAID 10 is worth considering where write performance for many simultaneous high-bitrate streams matters more than maximizing usable capacity, at the cost of needing more raw drives for the same usable space.
- Plan for hot-swap drive bays so a failed drive can be replaced without taking the whole recording system offline — for a security system, downtime during a replacement is exactly when you don't want a coverage gap.
Retention Requirements — Check Your Sector, Don't Assume
How long you're required (or choose) to keep footage varies by sector and isn't something to guess at. Banking and other RBI-regulated environments are commonly cited as needing a 90-day minimum for ATM and branch CCTV footage as a baseline compliance figure, and many retail and manufacturing operations independently choose a 30- to 90-day window based on their own insurance, loss-prevention or internal audit needs. Treat any number here as a starting point for your own compliance/legal check, not a fixed rule — requirements differ by state, sector and your specific insurer or regulator, so confirm the actual figure that applies to your business before finalizing retention and, in turn, storage capacity.
New vs Refurbished for CCTV Storage — Where Refurbished Genuinely Fits
An NVR storage server's job is mostly about storage capacity, RAID throughput and uptime — not raw CPU horsepower — which makes it a genuinely good fit for tested, warranty-backed refurbished hardware in most deployments. What matters more than "new vs refurbished" here is drive health: insist on SMART-verified, tested drives and a real burn-in process, since these disks will run continuously for years. Where a large camera network also runs heavy video analytics (facial recognition, license-plate recognition, real-time AI detection across many streams) alongside recording, that additional compute load is worth sizing carefully — and pairing dependable refurbished servers with proper server AMC support matters more here than on a typical office server, since a storage or RAID controller failure on a live security system is a compliance and safety issue, not just an inconvenience. Check current refurbished server pricing for a realistic budget range before sizing your final configuration. If you already have a server and just need to add drive capacity as the camera network grows, our guide on upgrading storage on a refurbished server covers what's realistically possible on an existing platform.
Frequently Asked Questions
How much storage do I need for 100 CCTV cameras?
Using the standard bitrate × cameras × retention formula, 100 cameras at 2MP/H.265 continuous recording for 30 days works out to roughly 25-40TB, and closer to 75-120TB for a 90-day retention window. The exact figure depends heavily on your actual per-camera bitrate, resolution and whether recording is continuous or motion-triggered, so always confirm against your specific camera models before finalizing storage.
Does H.265 really save that much storage over H.264?
Yes — H.265 (HEVC) typically needs roughly 40-50% less bitrate than H.264 for comparable image quality, which translates directly into a similar reduction in storage need for the same camera count and retention period. If your cameras and VMS software support H.265, it's usually the single biggest storage-saving decision available before you even touch drive count or RAID level.
Can I use regular desktop hard drives in an NVR server?
It's not recommended. Desktop drives aren't rated for the continuous, round-the-clock sequential-write workload a CCTV recording system generates and tend to fail earlier under that duty cycle. Surveillance-rated drives or enterprise/nearline-SAS drives are built specifically for this kind of continuous read-write load and are the safer choice for a server that needs to run reliably for years.
RAID 5, RAID 6 or RAID 10 for a CCTV storage server?
RAID 6 is the common default for large NVR arrays because its extra parity drive protects against a second drive failure during the long rebuild window that large-capacity drives require — a real risk given how much data sits on each disk. RAID 10 is worth considering when write performance for many simultaneous high-bitrate streams is the priority, at the cost of more raw drives for the same usable capacity. Plain RAID 5 is more common on smaller arrays where budget matters more than the extra rebuild-window protection.
Is a refurbished server reliable enough for 24/7 CCTV recording?
Yes, as long as it's properly tested and warranty-backed — an NVR server's job is mostly storage capacity, RAID throughput and uptime rather than raw compute, which suits refurbished enterprise hardware well. What matters most is SMART-verified drive health and a genuine burn-in test before deployment, plus AMC support with a fast response time, since a storage failure on a live security system needs to be fixed quickly.
How long am I required to keep CCTV footage in India?
There's no single nationwide figure that applies to every business — it varies by sector, state and your specific regulator or insurer. Banking and other RBI-regulated environments commonly cite a 90-day minimum for ATM and branch footage as a baseline, while many retail and manufacturing businesses independently choose 30-90 days based on their own policy. Confirm the actual requirement for your sector before finalizing your retention window and storage capacity.
Get Your CCTV/NVR Storage Server Sized Right
If you're planning a large camera rollout and want the storage, RAID and server configuration sized correctly the first time, call or WhatsApp +91-87968-22044. We'll help you work through your actual camera count, resolution and retention requirement, and match it to the right SAN storage or refurbished server configuration with proper AMC support behind it.