QNAP Multi-Site Surveillance: Recording, Central Viewing and Failover

When a business adds a warehouse, workshop or second office, camera buying is usually the easy part. The difficult questions arrive later: who notices a recording failure, what happens when the branch internet drops, and can an authorised operator export the right incident quickly?

What the Five-Factory Example Actually Shows

QNAP’s published automotive example describes five factories with 60 cameras per factory, managed through QVR Center. It reports a 30% reduction in video-channel and deployment costs for that project. Those are the vendor’s case figures, rather than a saving to apply to every quotation.

The transferable lesson is the division of work. Each factory has recording equipment, while headquarters needs selected live views, playback and a consistent operating process. A smaller business can apply the same thinking to a shop and stockroom without buying a factory-sized installation.

Recording, Viewing and Recovery Are Three Different Jobs

Match the exact recording package and versions to QVR Center and any QVR Guard design. Current package names, supported NAS models, channel licences and recovery features need checking together. A feature mentioned for one software family is not proof that another package has the same behaviour.

Calculate the Traffic That Actually Crosses the Link

Consider a branch with 12 cameras averaging 4 Mb/s each. The arithmetic recording load is 48 Mb/s before overhead. Sending all those main streams continuously to headquarters creates a different WAN requirement from requesting one view when an incident occurs. These are planning inputs, not measurements from a deployed system.

Substreams can make a multi-camera overview lighter while the recorder retains the main stream, subject to the camera and recording configuration. Check the resolution and frame rate used for live view, recognition, playback and export separately. A sharp desktop preview does not prove that the retained recording has the same detail.

Use the NVR storage calculator for a starting estimate, then compare it with actual recording growth. Include event frequency, audio, retention, free-space reserve and the chosen disk-protection arrangement. The 30-day NVR planning guide explains how to keep the assumptions visible.

Write Down What Each Failure Should Do

If the WAN is unavailable, should local recording continue and should an operator receive an alert? If a recorder fails, what takes over, which cameras are included and what happens after recovery? If a disk is replaced, how will you check recording while the storage rebuilds?

QVR Guard and a managed network or VPN solve different problems. Recorder failover concerns the recording service; a VPN concerns communication between locations. Neither is a substitute for protecting recordings against deletion, compromise or loss of the entire site.

Test an authorised outage in a controlled window. Record the last good frame, alert timing, takeover behaviour, gaps, recovery and final export. Keep the acceptance criteria tied to the required outcome instead of using an unqualified “uninterrupted” promise.

Choose a Recorder for the Workload

Camera support needs more than an ONVIF badge. Check the exact model, codec, audio, event and analytics requirements against the intended recorder. Keep the ONVIF compatibility guide beside the camera schedule. For a mixed-vendor project, this can prevent a camera that records video correctly from being assumed to deliver every smart event.

A Handover Operators Can Use

Deliver a site and camera register, naming convention, retention settings, authorised user roles, update responsibilities and tested export procedure. Show who receives alerts and who is responsible for the response. Keep time synchronisation consistent across sites so a timeline search has meaning.

The practical recommendation: begin with one representative site and prove the recording, viewing and recovery workflow before repeating it. A proof of concept is useful when software compatibility, WAN performance or failure behaviour remains uncertain.

Frequently Asked Questions