Quick answer: Choose central or local recording from the required outage behavior, tested links, site power and complete recording workload. Fiber can support a central design; local recorders can reduce reliance on an interbuilding link. Neither link ownership nor camera count alone decides it. Write down which recordings, searches and client functions remain available during each failure, then test that design with the actual equipment.
On this page
What link do you actually have between the buildings?
Map the actual route, ownership, approved network boundaries, power and maintenance responsibility. Standard structured copper designs commonly use a 90 m permanent link within a 100 m channel, subject to the actual link type, components and test specification. Interbuilding metallic paths need a qualified review of applicable grounding, bonding and surge requirements; distance compliance alone does not approve that route.
| Link candidate | Design checks | Recording decision |
|---|---|---|
| Optical fiber | Actual transceiver/host support, fiber type, connectors, optical budget, route and test results; remote equipment needs power | Assess central or distributed recording against the agreed failure behavior |
| Existing LAN | IT-approved routing/access, shared workload, maintenance and measured capacity | Specify what happens when that network or its power is unavailable |
| Wireless bridge | Approved path, interference, weather/fade margins, measured traffic and continuity requirements | Local recording may improve resilience; a tested central design is not automatically prohibited |
| Cellular | Supported architecture, variable usable uplink, data terms, access method and outage tolerance | Often useful for remote viewing; camera backhaul needs explicit engineering rather than a universal never rule |
An all-dielectric optical path avoids an electrical connection through that fiber. Metallic armor, other cables, remote power and connected equipment still need their own protection review; fiber does not make a site immune to lightning. Reach is specific to the modules, fiber and loss budget. Cat6 cable length planning covers the copper route. CS-POE33024PF and CS-POE33108PF list gigabit SFP interfaces, but the catalog does not establish which modules are supported; obtain the exact host/module confirmation.
How much bandwidth crosses the link in each design?
For central recording, budget the remote streams required by the actual recorder configuration, plus other traffic sharing the link. Distributed recording can keep those recording streams local, but remote viewing, playback/export, monitoring, replication or other configured services may still cross the link. Do not assume interbuilding traffic exists only while a person watches.
Illustrative payload: twelve remote streams at 4 Mbps each total 48 Mbps. That is not a measured site result or proof that a gigabit link has ample usable headroom. Add protocol overhead, peaks, concurrent viewing/export and shared demand; compare with representative measured usable capacity and the agreed margin. A bridge whose available capacity falls below the workload will not meet that recording requirement.
Check channels, formats, decoding, AI concurrency, input/output limits and storage separately. CS-N440 M-AI lists 400/400 Mbps I/O, 200/200 with AI on; CS-N220 P16H-AI lists 160 Mbps input, 120 with AI on, and 80 output. Confirm the exact supplied revision and how the manufacturer defines these budgets. The bandwidth calculator supports arithmetic, not automatic design approval.
What happens in building B when the link drops?
Document each failure separately: interbuilding link, recorder, switch, local power, shared network and remote client. A central recorder cannot receive a remote camera stream across a failed path; supported camera edge recording may behave differently. Local recorders can continue if their cameras, power, storage and local paths remain healthy. Never promise continuity from the recorder count alone.
- Link continuity: record expected maintenance and representative failure cases for fiber, LAN, wireless or cellular without claiming any one medium is outage-free.
- Local resilience: verify local cameras, recorder, switch, storage and power during an approved controlled link interruption.
- Edge storage: check exact camera media support, health, recording settings and retention. Automatic recorder gap recovery requires confirmed camera/NVR/firmware support and an actual test.
- Operator access: establish what the customer can still view, search and export through the remaining paths, with results and unresolved cases recorded.
Central or distributed recording: the decision table
| Decision | Central recorder | Recorder in each building |
|---|---|---|
| Required outage behavior | Remote recording depends on a working path unless a separately verified fallback exists | Local recording can survive interbuilding loss if local dependencies remain healthy |
| Data/storage | Budget all required streams and complete central resources | Budget each local workload and all traffic still crossing the link |
| Operator workflow | Test required search/export and permissions on the actual client | Test multi-recorder access/search/export; no assumed unified timeline |
| Power/security | Protect recorder and both buildings’ cameras/switches/link equipment | Protect each local system and any shared viewing infrastructure |
| Commercial comparison | Price all routes, power, equipment, support and failure impacts | Compare the full installed and service scope, not recorder price alone |
A small remote building may suit a central recorder, while two busy buildings may suit local recording. Treat those as options to compare, not camera-count rules. Existing routes, access costs, recording resilience, operator tasks and lifecycle service can change the result; price the actual alternatives and state their assumptions.
CASE examples: two CS-N220 P16H-AI or one CS-N440 M-AI?
Illustrative arithmetic only: sixteen 4 Mbps streams in building A and fourteen in B total 64 and 56 Mbps respectively, or 120 Mbps combined. Assume one required recording stream/channel per camera only for this example. Verify the real modes, channel use, peaks and all other demands before selecting either design. Select each network video recorder against that documented workload and the approved growth requirement.
Distributed: one CS-N220 P16H-AI in each building
CS-N220 P16H-AI lists twenty channels, sixteen PoE ports, 160 Mbps input/120 Mbps AI-on and 80 Mbps output, with up to 10 TB per HDD. The 64 and 56 Mbps example fits that input arithmetic before other demands, but does not prove decoding, AI, compatible streams, peak PoE or retention. Confirm addressing/channel behavior and test both complete local systems. Interbuilding management/viewing and other configured traffic still needs its own budget.
Central: one CS-N440 M-AI in building A with switches in both buildings
CS-N440 M-AI lists forty channels, no integrated PoE, 400/400 Mbps I/O or 200/200 AI-on, four 10 TB drives and two gigabit Ethernet interfaces. The 120 Mbps example is below its AI-on input row before other demands; spare channels do not prove spare processing or retention. CS-POE33024PF lists twenty-four PoE ports and two gigabit SFP interfaces; CS-POE33108PF lists eight PoE ports, so one cannot directly serve fourteen separate wired cameras. Confirm the supplied switch budget variant, supported optics, peak power and complete design. Both buildings still need protected local camera/switch power.
Size usable retention independently for each design, actual recording profiles and approved drive configuration. The NVR storage calculator is an estimate; document assumptions and later measured use. Confirm the term, exclusions and claim process for the exact model and revision in writing. Include secure enclosures, environment and continuity for all required equipment, not just the central rack.
How does the customer see both buildings as one system?
Describe CASE Connect only by the functions confirmed for the actual device and software version. Android is available; iOS is forthcoming. A web version exists, but do not publish an unverified access URL or assume feature parity. CASE Station desktop and CASE Cloud remote NVR configuration are separate products; neither name establishes cloud recording. Confirm actual multi-device access, account roles, viewing/playback and supported remote path before promising an operator workflow. P2P vs VPN discusses access design; do not infer a unified search or timeline from a device-list feature.
For a desk operator, confirm the actual CASE Station version, device support, layouts, permissions and search/export workflow. Transfer owner control securely and retain only agreed revocable service roles; keeping all administrator credentials exclusively with the installer is not the default handover design.
What to tell your customer
We will compare central and local recording against your required footage and operator tasks. The proposal will show what each design records during a link or power failure, the complete equipment and route costs, and which client functions have been verified. Any untested fallback remains an open item.
FAQ
Can one NVR record cameras in two buildings?
Yes, where supported streams can reach it and the complete channel, processing, network, power and storage design meets the requirement. Confirm failure behavior and any edge fallback. A printed incoming-bandwidth row or fiber connection alone does not validate recording continuity or the operator workflow.
Fiber or a second NVR: which is the smaller job?
Compare the actual approved routes, civil work, optics/switches, power, storage, security and service scope. Existing ducts can help, but may need inspection, permission or repairs. A local recorder can improve independence from the interbuilding path without removing the need for a network/power design. Read the module-specific fiber and reach data as an example of the documentation needed; it does not confirm module compatibility with CASE.
Do two NVRs mean two apps for the customer?
Not necessarily, but do not promise one login or a unified view from the recorder count. Confirm the supported CASE Connect/client versions, device/account workflow, roles and required remote functions for both recorders. Verify search/export behavior separately; feature names are not proof of cross-recorder synchronization.
Can I run Cat6 between the two buildings instead of fiber?
A compliant copper distance does not by itself approve an interbuilding route. Have a qualified designer review the actual metallic paths, environment and applicable protection requirements. An all-dielectric fiber leg avoids conduction through that leg; it does not remove risks from other services, armor or power. Specify reach from the exact supported optics/fiber budget, not one universal multimode or single-mode number.
What should the proposal say about link outages?
Name each dependency, failure case and recorded result. State which cameras continue recording, where the footage is stored and which viewing/search/export paths remain available. Confirm fallback and gap recovery for the exact equipment/firmware before commitment. Mark any untested condition pending with an owner and acceptance step. Use the commissioning checklist to keep the tested results and pending conditions with the handover record.
References
- Anabon: current model/revision manuals and documents
- Cisco: optical modules have specific fiber and reach requirements
- Anabon: surge and interbuilding protection planning



