1. Confirm Live Channels
Identify whether one, several or every camera has a current picture.
NYC Security Camera Recording Troubleshooting
A live camera picture does not prove that usable footage is being recorded. Unlimited Applications Security Company troubleshoots the complete recording path—camera feed, power, cabling, DVR or NVR, surveillance hard drive, recording schedule, system time, network connection and remote-viewing settings—throughout Brooklyn, Queens, Manhattan, the Bronx and Staten Island.
Customer Troubleshooting Selector
Choose the symptom that best matches the problem. Each explanation identifies the system path that should be tested before equipment is replaced.
When other channels work, the fault may be local to that camera: power, connector, cable, PoE port, recorder input or camera hardware. Test the channel before replacing the recorder.
Call (347) 433-6873 for camera-channel troubleshooting.A shared power supply, PoE switch, network path, recorder setting or damaged cable route may affect multiple cameras. Note whether the failed cameras share a floor, power source or switch.
Call (347) 433-6873 and describe which channels failed.The cameras may still send video while the recorder fails to save it. Check the recording schedule, hard-drive status, storage, overwrite setting, channel assignment and recorder time.
Call (347) 433-6873 for recording troubleshooting.Record the exact message before restarting. Disk, network, fan, power, channel and configuration errors point to different components.
Call (347) 433-6873 with the recorder brand, model and error.The warning may indicate an uninitialized disk, write failure, bad sectors, incompatible storage, loose connection or failed surveillance hard drive.
Call (347) 433-6873 for hard-drive and recorder testing.If the local monitor still works, inspect internet service, router changes, recorder network status, cloud/P2P status, account access, application settings and system time. Test local recording separately.
Call (347) 433-6873 for remote-viewing troubleshooting.Check recorder power, surge protection, monitor input and network equipment. A dark monitor alone does not prove the recorder is off.
Call (347) 433-6873 for complete-system troubleshooting.Recording and Playback
Live view and recording are separate functions. A camera can deliver a current picture while the recorder fails to save usable video. Common causes include a failed or uninitialized surveillance hard drive, disabled recording schedule, full storage with overwrite turned off, incorrect channel settings, recorder clock error or DVR/NVR hardware fault.
Identify whether one, several or every camera has a current picture.
Look for missing, abnormal, uninitialized, read-only or failed HDD messages.
Verify the correct channels and hours for continuous or motion recording.
Select a known recent time and confirm video opens, advances and exports when required.
A failed hard drive and a failed recorder can produce similar symptoms. The distinction matters because replacing a compatible surveillance drive may restore recording without replacing working cameras or the DVR/NVR.
| Finding | Possible cause | What to verify |
|---|---|---|
| Live video works; HDD is missing or abnormal | Drive, connection, power or storage failure | Disk detection, health, compatibility and write test |
| Known-good compatible drive is not detected | Recorder storage interface or recorder fault | Connections, power and recorder hardware |
| Drive is healthy but no events record | Schedule, channel, motion or overwrite configuration | Recording plan and playback by channel and time |
| Recorder freezes, reboots or loses settings | Power, cooling, firmware or recorder failure | Stable operation under recording load |
Verified Brooklyn Repair
At a Park Slope apartment building, all 16 analog cameras still displayed live video, but the Hikvision DVR was not recording and playback produced no usable footage. The recorder showed a storage or hard-drive error. Testing confirmed a storage-related failure.
The failed DVR hard drive was replaced with a 2TB drive and the recorder was reconfigured with the existing cameras.
Recording, playback and remote viewing were each tested and restored after the repair.
View the full Park Slope repair evidence on our Brooklyn camera-repair page →
Important: the 2TB replacement is not presented as proof of a specific retention period because the system’s bitrate, frame rate, codec and recording schedule were not documented.
Useful Storage Guidance
Storage is not determined by camera count alone. Retention changes with each camera’s average bitrate, resolution, frame rate, codec, scene activity, continuous-versus-motion schedule and usable drive capacity. Higher resolution and frame rate generally increase storage. H.265 can reduce bitrate compared with H.264 when supported and properly configured.
Approximate decimal TB = cameras × average Mbps per camera × 86,400 seconds × retention days ÷ 8 ÷ 1,000,000
| Planning example | Approximate raw storage | Limitation |
|---|---|---|
| 4 cameras × 2 Mbps × 30 days, continuous | 2.59 TB | Before operating margin |
| 8 cameras × 2 Mbps × 30 days, continuous | 5.18 TB | Actual bitrate varies by scene and settings |
| 16 cameras × 2 Mbps × 30 days, continuous | 10.37 TB | Not a claim about the Park Slope system |
| 16 cameras averaging 0.5 Mbps × 30 days | 2.59 TB | Motion activity and bitrate must be measured |
Continuous recording provides a consistent timeline but uses storage around the clock. Motion recording can extend retention only when zones, sensitivity, pre-record and post-record settings are configured and tested. Busy sidewalks, trees, headlights and delivery traffic can increase actual recording time.
With overwrite enabled, the recorder normally replaces the oldest footage when usable storage becomes full. With overwrite disabled, recording may stop at capacity. Confirm the property’s retention and evidence-preservation requirements before changing this setting.
Responsible Pricing Guidance
Camera and recorder work should be priced after the symptom, equipment and scope are identified. Unlike qualifying common intercom repairs, DVR/NVR work varies substantially by recorder capacity, surveillance-drive size, camera count, wiring, compatibility, network access and whether the failure is limited to storage or involves the recorder.
DVR/NVR brand, model, age, channel capacity, drive size, number of bays and compatibility.
Camera count and whether the system uses analog, HD-over-coax or IP cameras.
Resolution, bitrate, frame rate, codec, recording schedule and required history.
Playback, footage export, remote viewing, accounts, switches, routers and cabling.
Recording, storage, playback and remote-viewing questions live here rather than being duplicated on the general camera page.
Live video proves that at least part of the camera-to-recorder path is working, but it does not prove footage is being stored. Check the DVR/NVR recording schedule or mode, recorder time, hard-drive status, storage initialization, overwrite settings and playback. A real Park Slope repair documented by Unlimited Applications Security Company involved a 16-camera Hikvision DVR where live views worked but recording and playback had failed because of a storage/HDD fault.
Possible causes include a failed surveillance hard drive, disabled recording schedule, storage that is not initialized, recorder errors, incorrect date/time settings or a failing DVR/NVR. Recording and playback should both be verified after the repair rather than relying only on the live screen.
Warning signs include HDD or storage errors, missing playback, recording that stops while live view continues, abnormal drive status, repeated disk warnings or footage that cannot be retrieved. The hard drive and recorder should be tested separately so a failed drive is not mistaken for a failed DVR/NVR.
Remote viewing can stop after internet or router changes, recorder network-setting changes, app/account problems, IP or Domain Name System changes, an offline recorder or lost port/cloud connectivity. First confirm whether cameras still record locally; that separates a remote-access problem from a wider camera-system failure.
Repair can make sense when the problem is limited to the hard drive, power, settings, network or another replaceable component. Replacement becomes more practical when the recorder itself is obsolete, unsupported, incompatible with needed cameras or repeatedly failing. The decision should follow testing, not the symptom alone.
If yes, the camera path may be intact even though storage or recording has failed.
Test a known past time. A blank timeline or missing footage is more useful than simply saying the recorder is on.
Record the exact message and the recorder brand/model if visible. That helps separate a failed drive from a failed recorder.
Call Unlimited Applications Security Company and describe the camera count, recorder brand and model, exact error message and whether the problem affects live view, playback or remote access.
Call (347) 433-6873