CCTV Storage Solutions — NVR, SAN, NAS & Cloud
How to calculate, plan, and implement the right storage architecture for your building's CCTV system — covering embedded NVRs, enterprise server-based recording, SAN and NAS storage, RAID configurations, surveillance-grade hard drives, cloud and hybrid models, and the two-tier storage strategy used in professional deployments.
Contents
ToggleStorage is the silent foundation of every CCTV system. When it works correctly, nobody notices it. When it fails — footage is lost, retention periods are not met, drives crash, or recordings are overwritten before incidents are discovered — the consequences range from regulatory non-compliance to a complete inability to investigate security events. Getting storage right requires understanding both the technology options and the mathematics behind capacity planning.
1. Why Storage Is the Most Critical Infrastructure Decision
Consider the numbers: a single 4MP IP camera recording continuously at 15 frames per second using H.265 compression generates approximately 43 gigabytes of data every day. A 64-camera installation produces nearly 2.8 terabytes daily. Over a 60-day retention period, that translates to over 165 terabytes of raw video data that must be reliably written, stored, protected against drive failures, and made instantly searchable for playback.
Storage is also the single largest recurring cost component in a CCTV system. Hard drives have a finite lifespan (typically 3–5 years under continuous surveillance workloads) and must be proactively replaced. Under-provisioning storage means footage is overwritten before the mandated retention period expires. Over-provisioning wastes capital on unnecessary drives. A calculation-based approach — not vendor guesswork — is essential.
2. Storage Architecture Types
There are four primary storage architectures used in CCTV systems today. The right choice depends on the size of the installation, the required retention period, the budget, and the level of redundancy needed.
Embedded NVR (Standalone Appliance)
A self-contained recording device with built-in hard drive bays (typically 1–8 bays), embedded processor, and basic VMS software. Cameras connect directly or via PoE switch. Best for small-to-medium installations up to 32–64 cameras. Simple to deploy but limited in scalability, redundancy, and integration. Maximum storage typically 8 × 20TB = 160TB per unit.
Server-Based Recording (DAS)
A rackmount server running enterprise VMS software (Milestone, Genetec, etc.) with Direct Attached Storage — hard drives installed directly inside the server chassis or in attached JBOD (Just a Bunch of Disks) enclosures. Suitable for medium installations (32–128 cameras). More flexible than embedded NVR, supports RAID, and can be managed centrally.
SAN (Storage Area Network)
A dedicated, high-performance storage network connecting recording servers to external storage arrays via Fibre Channel or iSCSI. SAN provides block-level storage with enterprise-grade redundancy, high throughput, and the ability to pool storage across multiple servers. Best for large enterprise installations (128+ cameras) requiring maximum reliability and centralised storage management.
NAS (Network Attached Storage)
A file-level storage device connected to the network. NAS provides shared storage accessible by multiple recording servers or VMS instances. Many NAS vendors offer built-in surveillance station software, making NAS a dual-purpose platform for both recording and archival. Good for medium-to-large installations requiring flexible, expandable storage with built-in RAID.
Storage Architecture Comparison
| Parameter | Embedded NVR | Server + DAS | SAN | NAS |
|---|---|---|---|---|
| Cameras supported | 4–64 | 32–128 per server | 128–1,000+ | 32–256 |
| Max storage capacity | Up to 160 TB | Up to 400 TB per server | Petabyte-scale | Up to 500+ TB |
| RAID support | Basic (RAID 0/1/5) | Full (RAID 5/6/10) | Full (RAID 5/6/10/50/60) | Full (RAID 5/6/10) |
| Redundancy | Limited | Moderate (RAID + hot spare) | High (dual controllers, hot spare) | Moderate to high |
| Performance | Moderate | Good | Excellent (Fibre Channel) | Good (10GbE iSCSI) |
| Scalability | Limited (add more NVRs) | Moderate (add JBODs) | Excellent (add shelves) | Good (add expansion units) |
| Cost per TB | Lowest | Low to moderate | Highest | Moderate |
| Best for | Small offices, housing societies | PSU offices, hospitals | Bank HQ, large PSU campus | Multi-purpose deployments |
3. Storage Architecture in an Enterprise CCTV System
The following diagram illustrates how storage integrates into the overall CCTV network architecture, showing the data flow from cameras through the recording layer to tiered storage.
4. Storage Capacity Calculation
Accurate storage calculation prevents both under-provisioning (footage lost before retention period expires) and over-provisioning (wasted budget). The calculation is straightforward once you understand the variables.
The Five Variables
- Number of cameras
- Average bitrate per camera — determined by resolution, frame rate, compression codec, and scene complexity
- Recording mode — continuous (24/7) recording uses the most storage; motion-triggered recording uses significantly less, but may miss critical events in the seconds before motion is detected
- Retention period — the number of days footage must be kept before overwriting (typically 30 days for commercial, 60 days for PSU, 90+ days for banks)
- RAID configuration — the redundancy scheme that protects against drive failures, but reduces usable capacity
Storage Calculation Formula
Simplified: Daily Storage (GB) = Bitrate (Mbps) × 10.8
Total Raw Storage (TB) = Daily Storage per Camera × Number of Cameras × Retention Days ÷ 1,000
Usable Capacity Needed (TB) = Raw Storage ÷ RAID Efficiency
RAID 5 ≈ 75% usable · RAID 6 ≈ 67% usable · RAID 10 ≈ 50% usable
Total Physical Disk Capacity = Usable Capacity × 1.10 (add 10% for file system overhead)
Bitrate Reference by Resolution and Codec
| Resolution | H.264 @ 15 fps | H.265 @ 15 fps | H.265+ / Smart Codec @ 15 fps |
|---|---|---|---|
| 2MP (1080p) | 3–4 Mbps | 1.5–2.5 Mbps | 0.5–1.5 Mbps |
| 4MP (2K) | 5–8 Mbps | 3–5 Mbps | 1–3 Mbps |
| 5MP | 6–10 Mbps | 4–6 Mbps | 1.5–3.5 Mbps |
| 4K / 8MP | 12–20 Mbps | 8–12 Mbps | 3–6 Mbps |
Worked Example — 64-Camera PSU Building
64 cameras, 4MP resolution, H.265 compression at 15 fps, continuous recording, 60-day retention, RAID 6:
- Average bitrate per camera: 4 Mbps (using the mid-range value for 4MP H.265)
- Daily storage per camera: 4 × 10.8 = 43.2 GB/day
- Total daily all cameras: 43.2 × 64 = 2,765 GB/day (2.77 TB/day)
- 60-day raw storage: 2.77 × 60 = 166.1 TB
- RAID 6 adjustment: 166.1 ÷ 0.67 = 247.9 TB
- File system overhead (+10%): 247.9 × 1.10 = ~273 TB total physical disk capacity
- In hard drives: approximately 17 × 16TB drives or 14 × 20TB drives (plus hot spares)
🧮 Interactive Storage Calculator
Storage Calculation Results
5. RAID Configurations for CCTV
RAID (Redundant Array of Independent Disks) combines multiple physical hard drives into a logical unit that provides either improved performance, data redundancy (protection against drive failure), or both. For CCTV, RAID is not optional — it is essential. Without RAID, a single drive failure means permanent loss of all recordings stored on that drive.
| RAID Level | How It Works | Usable Capacity | Drive Failures Tolerated | Best For |
|---|---|---|---|---|
| RAID 1 | Mirroring — data written to two identical drives | 50% | 1 drive | Small NVRs (2-bay), OS drives |
| RAID 5 | Striping with single parity — data and parity distributed across all drives | ~75% (N-1 drives) | 1 drive | Medium CCTV with good balance of capacity and safety |
| RAID 6 | Striping with double parity — tolerates two simultaneous drive failures | ~67% (N-2 drives) | 2 drives simultaneously | Enterprise CCTV — recommended for all installations above 32 cameras |
| RAID 10 | Mirrored stripes — combines speed of RAID 0 with redundancy of RAID 1 | 50% | 1 drive per mirror pair | Tier 1 live recording (highest write speed) |
6. Surveillance-Grade Hard Drives
CCTV storage demands a specialised type of hard drive. Standard desktop drives — designed for 8 hours/day operation with intermittent read/write — will fail prematurely under the 24/7 continuous sequential write workload of video surveillance. Surveillance-grade drives are engineered specifically for this purpose.
Key Differences from Desktop Drives
| Feature | Desktop HDD | Surveillance HDD |
|---|---|---|
| Designed workload | 8 hours/day, intermittent | 24/7 continuous streaming writes |
| Annual workload rating | ~55 TB/year | 180–300 TB/year |
| Simultaneous streams | Not optimised | Optimised for 32–64+ simultaneous camera streams |
| Error recovery | Aggressive retry (causes dropped frames) | Limited retry (TLER/ERC) — prevents recording interruptions |
| Vibration tolerance | Low | Enhanced — designed for multi-drive enclosures with vibration from adjacent drives |
| Temperature management | Basic | Advanced — operates reliably at sustained higher temperatures |
| Warranty | Typically 2 years | Typically 3 years |
| Available capacities | Up to 24 TB | Up to 24 TB (with 10TB, 14TB, 16TB, 18TB, 20TB being most common for CCTV) |
Drive Replacement Planning
Surveillance drives have a typical operational life of 3–5 years. For a system with 20 drives, you should expect to replace 4–7 drives per year as they age. Budget for proactive drive replacement as part of the Annual Maintenance Contract (AMC). Monitor drive health using S.M.A.R.T. data — replace drives showing early warning signs (reallocated sectors, pending sectors, uncorrectable errors) before they fail completely.
7. Edge Storage — On-Camera Recording
Most modern IP cameras include a micro-SD card slot that enables the camera to record video locally on the camera itself, independent of the NVR or recording server. This feature — called edge storage — provides a critical safety net.
Automatic Network Replenishment (ANR)
ANR is the most important use of edge storage. When the network connection between the camera and the recording server is interrupted — due to a switch failure, cable damage, network congestion, or server downtime — the camera automatically begins recording to its local micro-SD card. When the network connection is restored, the camera automatically transfers the locally recorded footage to the central recording server, filling in the gap seamlessly. The operator sees a continuous, uninterrupted recording timeline.
Edge Storage Best Practices
- Use high-endurance micro-SD cards rated for continuous write operations (not standard consumer cards, which will fail within weeks). Industrial-grade or surveillance-rated cards from reputable manufacturers are essential.
- Card sizes of 128 GB to 256 GB are typical — providing 1–3 days of buffer recording depending on bitrate settings.
- Configure the camera to record the sub-stream (lower resolution) to the SD card rather than the main stream — this extends the available recording time significantly.
- High-endurance micro-SD cards have a typical lifespan of 1–3 years under continuous write workloads. Include card replacement in the AMC schedule.
8. Cloud & Hybrid Storage Models
Cloud-based video storage — where footage is stored on remote servers operated by a third-party provider rather than on on-premises hardware — offers compelling advantages for certain deployment scenarios but comes with significant constraints for Indian enterprise and government installations.
Full Cloud Storage
In a full cloud model, cameras stream video directly to cloud servers via the internet. There is no on-premises NVR or storage hardware. This model is attractive for retail chains, distributed small offices, and organisations without on-site IT infrastructure. Advantages include zero hardware maintenance, automatic scaling, built-in redundancy, and access from anywhere. Disadvantages include ongoing subscription costs (which can exceed on-premises costs over 3–5 years), dependency on internet connectivity (footage is lost during outages), significant upload bandwidth requirements, and potential data sovereignty concerns.
Hybrid Storage (Recommended for Enterprise)
The hybrid model — local recording with selective cloud backup — is emerging as the optimal approach for Indian enterprise deployments. Video is recorded locally on-premises (NVR, server, or NAS) for full-quality retention, ensuring recording continues even during internet outages. Simultaneously, selected content is uploaded to the cloud: alert clips triggered by analytics events, low-resolution sub-streams for remote viewing, or periodic backup copies of critical cameras. This provides the reliability of local recording with the accessibility and disaster recovery of cloud.
Data Sovereignty for Indian Organisations
For PSU and government CCTV installations, any cloud storage component must comply with Indian data localisation requirements. The Digital Personal Data Protection Act, 2023 (DPDPA) has implications for cross-border transfer of personal data — and CCTV footage of identifiable individuals qualifies as personal data. Verify that the cloud provider stores data exclusively within Indian data centres and complies with applicable Indian regulations.
9. Storage Sizing Quick Reference by Building Type
| Building Type | Typical Cameras | Retention | Estimated Storage (RAID 6) | Recommended Architecture |
|---|---|---|---|---|
| Small office (single floor) | 8–16 | 30 days | 4–15 TB | Embedded NVR with internal drives |
| Housing society | 16–32 | 15–30 days | 8–25 TB | Embedded NVR (8-bay) |
| Corporate office | 32–64 | 30–60 days | 40–140 TB | Server + DAS or NAS |
| Hospital | 48–96 | 30–60 days | 60–210 TB | Server + NAS/SAN |
| PSU / Government building | 64–128 | 60–90 days | 140–420 TB | Server + SAN (two-tier) |
| Bank headquarters | 128–256 | 90–180 days | 420–1,600 TB | Multi-server + SAN (two-tier) + failover |
| Multi-branch bank | 16–32 per branch | 90 days | 25–70 TB per branch | Embedded NVR per branch + centralised VMS |
10. Storage Maintenance & Lifecycle Management
Ongoing Monitoring
- Daily: Verify all cameras are recording. Check storage utilisation dashboard — ensure retention targets are being met.
- Weekly: Review drive health reports (S.M.A.R.T. data). Check for any degraded RAID arrays.
- Monthly: Verify that the oldest recordings match the expected retention period. Test footage playback and export from the oldest available date.
- Quarterly: Review storage growth trends. Plan capacity expansion if camera additions are expected.
Proactive Drive Replacement
Do not wait for drives to fail before replacing them. Surveillance drives have a rated operational life of 3–5 years. After year 3, begin proactive replacement of the oldest drives in the array. This scheduled replacement — during planned maintenance windows — avoids the risk of emergency drive failures during critical recording periods. Always maintain at least one hot spare per RAID array, and keep two additional spare drives in inventory for immediate replacement.
Need Help Planning Your CCTV Storage?
Storage calculation errors are among the costliest mistakes in CCTV procurement. BuildingInfra provides independent storage sizing, architecture design, and tender specification services — ensuring your system delivers the right retention period at the right cost, with the right level of redundancy.
Request a Free Consultation