NVR Selection Checklist for Multi-Site Security

Confirm Camera Compatibility and Codec Support

The first failure point in most multi-site installations is a mismatch between the cameras and the recorder. Before selecting an NVR, obtain the exact list of cameras, including make, model, resolution, and codec. A recorder that supports H.265 may not handle the specific H.265 profile used by your cameras. Some cameras default to H.264 for compatibility, while others require H.265 for higher frame rates at the same resolution.

Check the vendor’s compatibility list for each camera model. Do not assume that any H.265 capable NVR works with any H.265 camera. Codec support includes the specific profile and level. A camera outputting H.265 at a high level may exceed the recorder’s decode limit. This causes dropped frames, black screens, or unstable streams. For example, an H.265 Level 5.1 stream at 4K resolution demands significantly more processing power than a Level 4.1 stream. If the NVR’s decoder cannot handle the specific profile, the stream may drop out entirely or display corrupted images.

Red flag: The compatibility list is vague, such as “supports major codecs.” Ask for the exact model numbers of cameras tested with that specific NVR firmware version. Firmware updates can change supported features. Sometimes a new firmware update adds support for a specific camera model, while other updates may remove legacy support. Request the release notes for the latest firmware version and verify that your camera models are explicitly listed as tested.

Calculate Real Storage Capacity

Marketing capacity figures are often misleading. An NVR may advertise 16 TB of storage, but usable space depends on the file system, drive type, and overhead. More importantly, retention time depends on the actual data written, not the camera’s maximum resolution.

To calculate storage, multiply the number of cameras by the bitrate per camera, then by the number of seconds in the desired retention period. Use the actual bitrate, not the maximum. A 4 MP camera recording at 30 fps may use 8 Mbps, while the same camera at 15 fps may use 4 Mbps. If your cameras use variable bitrate, use the average or peak value to be safe. Variable bitrate encoding adjusts the data rate based on scene complexity. A static scene with few moving objects will generate a much lower bitrate than a busy intersection with heavy traffic and changing lighting conditions.

When estimating for multi-site projects, account for different scene contents at each location. A warehouse with static racks will generate less data than a retail store entrance with frequent pedestrian movement. Calculate the average bitrate for each site individually, then aggregate the total for the central NVR. If you are using a distributed storage model, calculate storage needs per site.

Red flag: The vendor provides only a single bitrate figure. Ask for the bitrate under your specific recording conditions, including motion detection and time-based settings. If the vendor cannot provide a detailed bitrate breakdown, assume the higher end of the range to ensure sufficient retention time.

Camera Resolution	Typical Bitrate Range	30 Day Retention per Camera	90 Day Retention per Camera
1080p (1080)	2 to 8 Mbps	10 to 40 GB	30 to 120 GB
4 MP (2K)	4 to 12 Mbps	20 to 80 GB	60 to 240 GB
8 MP (4K)	8 to 20 Mbps	40 to 160 GB	120 to 480 GB
16 MP (8K)	16 to 40 Mbps	80 to 320 GB	240 to 960 GB

These ranges are general estimates. Your actual numbers will vary based on scene content, codec, and recording mode. Always add at least 20 percent extra storage for file system overhead and future expansion. File system overhead includes metadata, journaling, and fragmentation. As the drive fills up over time, performance may degrade, and available space for new recordings will shrink.

Verify Network Throughput and Architecture

Multi-site deployments put significant load on the network. Each camera stream consumes bandwidth on the switch, the router, and the NVR’s network interface. A single NVR with 1 GbE ports may struggle with 40 or more 4 MP cameras if all streams are full quality.

Check the NVR’s network card specifications. Some NVRs have multiple network ports, or support teaming to create a higher bandwidth link. For multi-site projects, confirm how the NVR handles remote streams. If you are pulling footage from a remote site over the internet, the NVR must support efficient streaming protocols and enough concurrent user sessions.

Consider the physical layout of your network. In a multi-site setup, you may need a star topology where each site connects to a central hub, or a mesh topology for redundancy. Each site’s local switch must have sufficient bandwidth to handle all camera streams to the local NVR or uplink. A 1 GbE switch may be sufficient for up to 12 to 15 4 MP cameras, depending on the bitrate. If you have more cameras, you will need a 10 GbE switch or a higher capacity uplink.

Red flag: The NVR only has a single 1 GbE port and no mention of bandwidth management. In a multi-site setup, this creates a bottleneck. Consider a distribution NVR or a local storage approach at each site if bandwidth is limited. If the NVR cannot handle the total bandwidth of all streams, you may need to reduce the resolution or frame rate of some cameras to maintain stable streaming.

Review Site Security and Remote Access Features

Security cameras protect a site, but the NVR itself becomes a target if misconfigured. Check the remote access methods. Many NVRs support direct IP access, port forwarding, or cloud relay services. Each method has different security profiles.

Direct IP access requires opening ports on your router, which exposes the NVR to the internet. Port forwarding is common but risky if the NVR’s authentication is weak. Cloud relay services often handle the connectivity, but you must review the data handling and privacy policy. When using cloud relay, confirm where the data is stored and who has access to it. Some services store footage on the vendor’s servers, while others only store metadata and require a local NVR for full footage.

Check the authentication options. Does the NVR support multi-factor authentication for remote users? Can you create separate user accounts with different permissions? A single admin password for all remote access is a major risk. Implement role-based access control so that site managers can only view footage from their specific locations, while regional managers can access all sites. Disable unused accounts and change default passwords immediately after installation.

Red flag: No ability to restrict access by IP address or subnet. In a multi-site environment, you need to limit who can view footage from which site. If the NVR allows any IP address to connect with valid credentials, you are exposed to brute force attacks and unauthorized access.

Check Failover and Redundancy

A single NVR failure can leave a site blind. For critical multi-site security, redundancy is a must. Check if the NVR supports RAID configurations. RAID 1 or RAID 5 can protect against a single drive failure. RAID 6 can handle two drive failures.

For network failures, check if the NVR supports local recording when the network drops. Some NVRs store footage locally and sync when the connection returns. Others stop recording entirely. For multi-site projects, consider a hybrid approach where each site has local storage, and a central NVR aggregates metadata or specific streams. This ensures that if the central network link fails, each site continues to record locally and can sync later.

RAID configuration requires careful planning. RAID 1 mirrors two drives, doubling the cost but providing full redundancy. RAID 5 requires at least three drives and can tolerate one drive failure. RAID 6 requires at least four drives and can tolerate two drive failures. For multi-site projects, RAID 6 is often preferred because it allows for drive replacement without downtime. Confirm that the NVR supports hot-swappable drives so that failed drives can be replaced without shutting down the system.

Red flag: No RAID option or no local buffering. If the network goes down for an hour, you lose an hour of footage. In a critical environment, such as a data center or a high-risk facility, this is unacceptable. Ensure that the NVR can continue recording locally during a network outage.

Confirm Service, Warranty, and Support

Multi-site projects span a large area. If one NVR fails, you do not want to wait weeks for a replacement. Check the warranty terms. Does the warranty cover the entire system, or just the NVR unit? What is the turnaround time for service?

Ask about firmware updates. Security vulnerabilities are patched regularly. If the vendor does not provide regular updates, the NVR becomes a security risk over time. Confirm the update process and whether you can apply updates without losing stored footage. Some NVRs allow remote firmware updates, while others require a local connection to the device. Ensure that you have a documented process for applying updates across all sites.

Also, check if the vendor provides documentation for your specific configuration. A multi-site setup with multiple NVRs and sub-NVRs requires clear documentation for troubleshooting. Request a configuration guide that includes network diagrams, IP address assignments, and user permission settings. This document will be invaluable when troubleshooting issues or when new staff members are trained on the system.

Red flag: The warranty is only one year and does not include on-site service. For a multi-site deployment, this is not sufficient. Ask for a multi-year support contract. A good support contract should include 24/7 technical support, on-site service for critical failures, and regular firmware updates. Confirm the response time for service calls. For critical sites, you may need same-day or next-day service.

Final Pre-Purchase Verification

Before signing the purchase order, run through this final checklist.

1. Verify that every camera model is on the NVR’s compatibility list.
2. Confirm the codec support for your specific camera settings.
3. Recalculate storage using your actual bitrate and retention period.
4. Check the NVR’s network ports and bandwidth capacity.
5. Review remote access security and user management features.
6. Confirm RAID or redundancy options for drive failure.
7. Check the warranty terms and service coverage for all sites.
8. Request a written confirmation of the configuration from the vendor.

This final step prevents the most common installation errors. It also gives you a document to reference during commissioning and troubleshooting. Keep a copy of the written confirmation with your project documentation. If issues arise in the future, you can refer back to the agreed specifications and hold the vendor accountable for any discrepancies.

Red Flags Summary

Avoid the following signs when selecting an NVR for a multi-site security project.

• Vague compatibility lists: If the vendor cannot provide exact camera model support, do not proceed. Request specific model numbers and firmware versions.
• No storage calculation support: If the vendor does not provide tools to calculate retention, you are taking a risk. Perform the calculation yourself using the bitrate ranges in the table above.
• Single network port: For a large number of high-resolution cameras, a single port will bottleneck performance. Verify the total bandwidth capacity of the NVR’s network interfaces.
• Weak remote access security: If you cannot restrict access or use multi-factor authentication, the NVR is a liability. Ensure that you can implement strong authentication and role-based access control.
• No redundancy options: A single point of failure is unacceptable for critical site security. Confirm that the NVR supports RAID and local buffering during network outages.
• Short warranty: One-year coverage is insufficient for a multi-year security investment. Seek a multi-year support contract with 24/7 technical support and on-site service.