Quick answer: Live video without the expected playback can have several causes. Preserve relevant evidence first, then verify the actual channel, search/filter/time, recording status and schedule, supported event path, storage state and capacity. Change one approved setting at a time and verify a representative recording, playback and export. Do not format a drive, enable deletion or reset the system as a first diagnostic step.
On this page
Is the schedule set to continuous, motion or alarm, and for which hours?
A connected/live channel is not proof the expected recording is being made. Read the exact model/firmware’s schedule and recording configuration for that channel, supported stream and storage destination. Labels, combinations and behavior vary; do not assume every CASE NVR offers the same recording types or logic.
| Mode to verify where supported | What to check | Common diagnostic question |
|---|---|---|
| Continuous / timed | Actual enabled channel, interval, stream and destination | Does the device report recording and can the interval be played? |
| Motion / analytics event | Supported detection source, event delivery, arming and recording action | Does the actual event reach the recorder and trigger the required clip? |
| Physical alarm input | Approved input/wiring, state, schedule and action mapping | Does a safe authorized test produce the expected input and clip? |
| Combined mode | Exact AND/OR or other supported logic | Do not infer either-source behavior from a menu label |
Review every required day/interval, copied-channel selection, holiday override and any record-enable or storage assignment. Pre/post recording depends on support, limits and buffering; confirm and test it rather than promise it recovers every missed lead-in. Do not present a specific midnight gap as the most common cause without evidence. Before testing intervals, verify the recorder clock with the NVR time/date guide.
Is the NVR clock right? Wrong time looks like missing footage
First note the displayed time, zone/offset, DST rule and search filters without changing them. Wrong timing can misplace a search, but missing footage is not guaranteed to exist. Preserve relevant clips and document the offset before an approved time correction, which can affect chronology and schedules. Confirm the correct current local rule and supported reachable time source; the NVR time/date guide covers jurisdiction changes and safe verification.
Are motion sensitivity and detection zones actually set on the camera?
Detection may happen in the camera, the recorder or another supported analytics path. Determine the actual source and required event/recording integration for the exact camera, NVR, firmware and client. A working live stream does not establish compatible events. Check supported enablement, zones, arming and action mapping, then test the required target safely.
- Identify the actual event source and supported integration, including which device owns each setting.
- Check enabled rule, target/zone, sensitivity or classification and any schedule/filter relevant to the task.
- Confirm receipt and recording action on the correct channel; a camera-side event alone is not a saved clip.
- Test representative targets and required pre/post coverage, playback and export. Do not weaken privacy masks or agreed coverage to make a test pass.
CS-N220 P16H-AI lists NVR analytics, but the exact supported channel count, source, configuration and event behavior still need confirmation. Do not diagnose a missing animal clip as intentional filtering without checking the active rule. Verify any ONVIF conformance against full model/firmware in its official database and test the required events. If a temporary continuous-recording workaround is proposed, obtain approval and reassess privacy, storage and retention; it is not an automatic fix.
Disk status, overwrite and retention: is the drive allowed to record?
Read and preserve the actual disk status, capacity, assignments, alarms and logs before changes. A recorder may show live video while storage or recording has failed. Status wording and a SMART Good result do not prove health, while an abnormal status does not uniquely identify a failed drive. For a Seagate drive that reports a SMART error, use Seagate’s drive-specific diagnostic guidance.
| Observation | Check before changing | Approved next step |
|---|---|---|
| Full / overwrite disabled | Retention policy, incident holds and evidence preservation | Enable cycling only with authorization and verified preservation; it replaces older data |
| Uninitialized / unformatted | Correct drive identity, existing evidence, compatibility and prior use | Do not initialize until authorized data-loss implications and exact instructions are addressed |
| Abnormal / missing / intermittent | Logs, supported drive, power/cabling and safe model-specific diagnosis | Use approved service/drive tests; do not assume formatting repairs it |
| One channel missing | Search/time, schedule, stream, storage group/quota and actual supported mapping | Correct the confirmed cause and verify a test clip |
| Old footage gone | Actual writes, capacity, expiry/deletion, schedule and holds | Resolve against approved retention; do not change expiry blindly |
The smaller CS-N105 P4H-AI, CS-N110 P8H-AI and CS-N220 P16H-AI catalog rows state up to 10 TB per HDD, not bay count or compatibility with every drive. CS-N440 M-AI lists 4×10 TB and CS-N880 H-AI8×24 TB. Obtain exact supported drive/revision/storage-mode instructions. General category policies are a starting point, not a warranty for every SKU. Confirm the term, exclusions and claim process for the exact model and revision in writing. Project Series items, intercoms, powered accessories and model-specific exceptions need their own confirmation; hard-drive claims follow the applicable drive-manufacturer terms.
Shorter retention can come from storage sizing, actual bitrate/duty cycle, additional recordings, reserved space, expiry or another fault. Use the NVR storage calculator with actual usable capacity and requirements, then measure retained footage; do not treat a healthy-status label as proof the only issue is drive size.
Per-channel recording check: the eight-step sequence
Work the channel in question in order and write down each result; the list doubles as the fault report for the customer and for Anabon technical support. Use Anabon’s exact-model documents and manuals for the supported controls; menu names and options vary.
- Preserve relevant evidence, record symptoms/time and identify the exact channel, camera/NVR and versions. If offline, use the DHCP checklist or PoE power checklist first.
- Check search location, time/zone, permissions, filters and whether the expected recording type is selected.
- Read actual recording state and schedule, intervals, overrides, stream and destination for that channel.
- For event recording, verify the actual supported source, arming, filters, delivery and record action.
- Read storage state, alarms, assignments, capacity, overwrite/expiry policy and any holds before changes.
- Check actual input/output/decoding/AI and network limits. CS-N220 P16H-AI lists 160/120 Mbps input with AI off/on; a bandwidth boundary is not a unique diagnosis of gaps.
- Apply one authorized correction and perform safe representative continuous/event tests with required pre/post coverage.
- Play back and export the correct channel/time through an approved secure route. Verify it independently, record the change and any unresolved retention/evidence issue; a two-minute clip alone does not validate all schedules.
CASE Cloud is a separate remote NVR configuration product, not a claim of cloud recording or guaranteed access to every schedule/HDD screen. Confirm exact supported device/version, account permissions and approved secure access. Do not expose ports or disable security to fix a ticket. The NVR hardening checklist covers the access plan; keep credentials out of reports and screenshots.
What to tell your customer
We will explain the confirmed cause and the exact change made, then show the tested recording, playback and export. We will state any unverified period or retention limit rather than claim missing footage exists or a drive is healthy from one status label. End users should contact the installer/company that supplied the system for service and warranty.
FAQ
Why does the camera show live video but nothing on playback?
Live view and recording are separate paths. Check channel/search/time, permissions, schedule and actual record state, supported event mapping, storage and resource limits. Do not assume a live image proves the whole network/storage path or that the cause must be one of three settings. Preserve evidence before destructive changes.
Should I set the schedule to continuous or motion?
Choose from the actual evidence task, policy, privacy and storage requirements. Event-only recording depends on detection and can miss untriggered intervals; continuous recording has its own storage demands. Obtain approval for a change, test the required coverage and verify real retention rather than prescribe one mode to every location. Use the NVR storage calculator to compare the proposed recording pattern against usable capacity, then verify actual retention.
What does overwrite do, and should it be on?
Supported cycling can replace older recordings to allow new writes. It does not guarantee recording never stops and may conflict with preservation requirements. Verify exact behavior, retention and authorized holds before enabling it. Preserve required evidence first and document the approved policy.
Can the wrong NVR time make it look like nothing was recorded?
Incorrect time or search settings can make footage hard to locate, but do not prove it was recorded. Document the existing offset, preserve relevant evidence and obtain approval before correction. Confirm current local zone/DST and the actual supported time source, then verify recording and chronology without rewriting the history silently. Use the IETF time-service operational guidance when agreeing the time source with IT; local zone and DST rules still need their own check.
Which hard drive size can I put in a CASE NVR?
Use exact supported drive models, revision, capacity, bay count and storage-mode instructions. Smaller catalog rows list a 10 TB per-HDD maximum; CS-N440 M-AI4×10 TB and CS-N880 H-AI8×24 TB. A capacity ceiling alone does not approve every drive. Hard-drive manufacturer claim terms are separate from the NVR’s exact written warranty.
References
- Anabon: exact-model documents and manuals
- ONVIF: model/firmware-specific conformance
- Seagate: a reported SMART error needs drive-specific diagnosis
- IETF: time-service operational guidance
