How to Set Up a Network Video Recorder and Confirm Retention

Why this matters

A recorder that looks finished on install day can fail the customer in three quiet ways: the clock is an hour off, so the clip they hand the police has the wrong time on it; the drive holds nine days when they were told a month; or the admin password is still the one printed in the manual. None of those show on the live view. They show the day the customer needs a recording from three weeks ago, and by then the footage is gone. This card sets up a network video recorder (NVR) so that every one of those is checked and written down at handover.

The arithmetic that predicts storage from bitrate, camera count and days is in Recorder Storage Math: Bitrate, Days and Cameras. This card uses a different number: the one the recorder actually measures.

Before you start

The recorder, its drive or drives, the camera plan with each camera's name and job, the customer's router and an outlet nearby, and the customer present for the password and user steps. If this is a takeover of an existing recorder, ask before touching the drives: initializing a drive erases it, and the old footage may be the reason the customer called. The only physical hazards are a plug and a lifted box; mount the recorder where it breathes, not in a sealed cabinet over a water heater.

The procedure

1. Install and initialize the drives. Fit drives rated for continuous recording, then initialize them in the recorder's storage menu. Why: a drive from a desktop or a different recorder is not formatted the way this one expects and may not record at all. What breaks if you skip it: the recorder shows live video and records nothing, which nobody notices until they search.

2. Change the admin password at first boot, with the customer choosing it. Set a strong password the customer enters themselves, set the recovery method (security questions or an email) to the customer's own, and disable or rename any default accounts the recorder ships with. The shop's rules for who holds which credential are in The Installer Code and Customer Passcode Handling SOP. Why: default credentials on a recorder reachable from the internet are the single most common way camera systems get taken over. What breaks if you skip it: the customer's cameras end up viewable by strangers, and the shop installed it that way.

3. Set the time zone, daylight saving and network time. Choose the customer's time zone, turn daylight saving on where it applies, and point the recorder at a network time server so it corrects itself. Then compare the recorder's clock to a phone. Why: every clip is evidence of when something happened. A recorder set to the wrong zone puts a 2 pm event at 3 pm, and a recorder with no time sync drifts a little every week until searches stop landing. What breaks if you skip it: the customer searches the right hour and finds the wrong one.

4. Update firmware on the recorder and the cameras before adding users. Download from the maker's own site, check the version matches the model, and do not interrupt power during the update. Record the versions. Why before users: an update can reset app pairings, and doing it first means the customer's phone is linked to the version they will keep. Updates also close security holes found after the unit was boxed.

5. Add and name the cameras. On a PoE recorder the cameras usually appear on their own as they connect. Set each camera's own password (not left at default), and name it from the plan: "C1 Driveway", not "IPCamera 01". Why: when a police officer asks for the driveway at 2:14 am, nobody should be guessing which camera that is.

6. Set the recording mode and stream for each camera. Three common modes: continuous, motion or event only, and continuous on a lower-resolution second stream with full-resolution recording on events. Set the main stream's resolution, frame rate, compression and bitrate per the plan, turn on overwrite so the oldest footage rolls off rather than recording stopping when the drive fills, and set motion zones that ignore the street and the neighbor's tree. Why: the mode is the biggest lever on how many days the drive holds, and the motion zones decide whether motion-only cameras record events or record weather.

7. Set up remote access the safe way. Use the maker's app and its cloud or relay connection rather than opening ports on the customer's router, and turn off automatic port opening (UPnP) on the recorder. Why: a forwarded port puts the recorder's login page on the open internet.

8. Add the people who will use it. The customer as admin; other household members as viewers, with playback or live-only rights as the customer decides. Dealer remote access only if the customer agrees and it is written on the handover sheet. Why: a shared admin login means nobody can be removed later without changing it for everyone.

9. Measure retention after at least 24 hours of real recording. Read the drive's used space after a clean 24-hour window and divide total capacity by it. That is measured retention in days. Compare it to the customer's target. Why measured rather than calculated: the calculation assumes a bitrate, and variable-bitrate streams and motion recording make the real figure higher or lower depending on the scene. What breaks if you skip it: the customer is told 30 days off a spreadsheet and has 19.

10. Prove playback twice. Play back the oldest recording on the drive at the recorder, then on the customer's phone with Wi-Fi turned off so it runs over cellular. Why both: playback at the recorder proves the drive records; playback over cellular proves the remote path works from outside the house, which is where the customer will be when they need it.

The handover sheet, filled in

A four-camera house. Installed on 10/13 with all four cameras recording continuously, because that is what the customer first asked for. The customer's stated target is 30 days.

The first measurement failed the target. Over the first 24 hours the drive used 150 GB. A 4 TB drive is 4 trillion bytes, which the recorder displays as about 3,725 GB because it counts in binary units; use the figure the recorder shows. 3,725 divided by 150 is 24.8, so 24 days, under the 30-day target. The tech showed the customer the three choices: a second drive, a lower bitrate on all four, or motion-only recording on the two cameras whose job is "see if anyone came through". The customer chose the third, keeping full-time recording on the driveway and the front door.

The second measurement passed. With C3 and C4 on motion only, the next clean 24 hours used 96 GB. 3,725 divided by 96 is 38.8, so 38 days against a 30-day target.

RECORDER HANDOVER SHEET          10/15
Recorder 8-port PoE NVR, fw updated 10/13
Cameras fw updated 10/13, versions on ticket
Admin password set by customer, not written
  here; recovery email is the customer's
Defaults disabled, UPnP off, app via cloud
Time zone US Central, DST on, NTP on;
  matched phone clock to the second
Drive 1 x 4 TB, shows 3,725 GB, overwrite ON
CAMERA        MODE          MAIN STREAM
C1 Driveway   continuous    4 Mbps cap VBR
C2 Front door continuous    4 Mbps cap VBR
C3 Side gate  motion only   4 Mbps cap VBR
C4 Backyard   motion only   4 Mbps cap VBR
24 h used, all continuous   150 GB = 24 days
24 h used, C3 C4 motion      96 GB = 38 days
Target 30 days: met with 8 days of margin
Users: owner admin; spouse playback;
  teen live only. Dealer access: none
Oldest playback 10/13 at recorder: OK
Oldest playback 10/13 on phone, LTE: OK
Retention check day 40, 11/22: oldest clip
  must date no later than 10/23

Two lines on that sheet deserve a note. The phone playback was done with Wi-Fi off, so it went out over cellular and back through the maker's relay. And the check date sits after the drive has filled: at 150 GB on the first day and 96 GB a day after, the drive reaches full in about 38 days (3,725 minus 150 is 3,575, divided by 96 is 37.2, plus the first day). Before it fills, the oldest clip is simply the install day and proves nothing about retention. On 11/22, 30 days back is 10/23, so an oldest clip dated on or before 10/23 means the target is met in practice, not only on paper.

What changes the answer

Motion recording is measured on the day you measure. A calm October day records less on C3 and C4 than a windy day with the maple dropping leaves through the zone, or a week the kids have friends over. That is why the sheet carries margin: 38 days against 30 leaves room for busy days, while 31 against 30 would not. If the measured figure lands within a few days of the target, add the second drive or lower the bitrate rather than handing over a number that depends on the weather.

A customer with a required retention. A small business whose insurer or lease names a retention period, or a property manager with a written policy, should be handed that number with margin and the measurement attached. The shop does not decide what the requirement is; it proves what the system does.

More cameras later. Adding a fifth camera changes the measurement. The sheet should say so, and the shop's change order for an added camera should include a new 24-hour measurement.

Finish test

The job is not handed over until: the oldest recording on the drive plays back at the recorder and on the customer's phone over cellular, the measured retention in days is written on the sheet against the target, and the retention check date is on the shop's schedule. At that check, the customer (or the shop, if granted access) reads the oldest clip's date, and it is written onto the ticket beside the target. If it falls short, the fix is the same three levers, and the sheet gets a new line.

References

• See related: Recorder Storage Math: Bitrate, Days and Cameras
• See related: The Installer Code and Customer Passcode Handling SOP
• See related: The Camera System Handover and Privacy SOP
• Recorder and camera maker setup and firmware documentation