Camera Periodic Maintenance Checklist

Camera periodic maintenance checklist: image and lens, mounting, cabling and PoE, NVR disks and RAID, recording gaps, NTP, firmware, users and function tests.
Technical summary
Technology
IP cameras, NVR, PoE, UPS
Topic
Maintenance
Level
Start
In this article9 sections

Camera systems don’t break overnight; they slowly decay. The lens gets dirty, the bracket loosens, IR LEDs weaken, a disk quietly accumulates reallocated sectors, the NVR clock drifts a few minutes, and a departed employee’s account stays open. None of this raises an alarm. The moment it’s noticed is usually after an incident, when someone says “there was no recording” or “the plate isn’t readable”. The list below is designed so you can carry out maintenance in a measurable, recorded way.

Set the maintenance frequency

Applying the same schedule to every site means either too much work or too little maintenance. Physical maintenance (on site, with a ladder, handling the camera) and logical checks (remote checks of recording, disks, clocks and users) should be planned separately.

Medium Physical maintenance Logical checks
Offices and indoor common areas 1–2 times a year Monthly (remote)
Outdoor and perimeter 2–4 times a year Monthly
Dusty/oily production, warehouses Every three months or more often Weekly–monthly
Critical sites According to risk assessment Continuous monitoring

The frequencies are examples; they’re adjusted using past fault data and criticality. It helps to time outdoor maintenance with the change of seasons: seals and heaters before winter, vegetation and spider webs after spring. The team setting up the plan should rewrite the schedule after looking at the first year’s fault records. The schedule isn’t a fixed document.

1. Image and camera

The only reliable method for checking the image is comparison. At installation or the first maintenance, take a day and night reference screenshot of each camera and store it with the camera name. On the next visit, put the same frame side by side. Angle drift, loss of focus and new obstructions show up within seconds this way.

  • Daytime image: sharpness, focus, color, white balance
  • Night image: is IR working, are there reflections or spider webs, noise level
  • Angle drift: comparison with the reference screenshot
  • View obstruction: vegetation, racks, new structures, signs
  • Are privacy masks and analytics zones still in the right place?

A common situation is a camera that looks sharp by day being useless at night. A thin film on the dome isn’t noticeable by day; at night it reflects IR light back and the image turns into a milky fog. That’s why the night check should be done separately, even if remotely. IR LED ageing progresses similarly: the center of the image stays bright while the edges start to go dark. Varifocal lenses can drift out of focus with temperature changes; on motorized lenses, re-run the autofocus command and compare the result with the reference.

2. Physical condition

  • Lens and dome cleaning
  • Housing sealing, gaskets and cable entries
  • Bracket, pole and screw tightness; corrosion
  • Heater/fan operation (outdoor)
  • Vandal damage and cable protection

If you see condensation or water droplets inside the housing, the problem is usually not the gasket but the cable entry. The gland wasn’t tightened, the cable runs straight down from above, and water follows the cable inside. Giving the cable a drip loop reduces this risk. On pole mounts, wind-induced vibration loosens screws over time; a slight shake in the image is the first sign. In coastal and chemical environments, also note corrosion of fasteners. Corrosion isn’t fixed in place; the part is replaced.

3. Network, PoE and power

  • Switch port errors (CRC, drops) and link speed
  • PoE consumption and switch budget usage (PoE budget)
  • Cabinet layout, labels, ventilation
  • UPS status, battery test date, alarm notifications
  • Condition of surge protectors

Port counters tell you the condition of the cable. Increasing CRC errors, a link that has dropped to 100 Mbps instead of 1 Gbps, or link down/up entries repeating during the day are usually caused by the connector, a splice or a damaged cable. If a camera comes in with the complaint “it drops out now and then”, the first place to look is the switch port’s error counter and log.

On the PoE side, the classic fault shows up at night. When IR and the heaters of outdoor cameras kick in, consumption rises; a switch running at the edge of its budget restarts certain cameras or stops powering them at night. Measuring the budget by day and calling it “enough” is misleading. Repeat the measurement at night and in cold weather. For the UPS, record the battery’s last test date and how many minutes it actually lasts under real load; the test result counts, not the estimate on the panel.

4. Recording and storage

  • Recording gaps per camera over the last 30 days
  • Actual retention: does the oldest recording date match the target? (capacity guide)
  • Disk S.M.A.R.T. values, RAID status, hot spare
  • Recording server/NVR temperature and fans
  • Taking a configuration backup

Recording gap checks should be done per camera. While the NVR appears to be “recording” overall, it’s quite common for a single camera to skip a few hours of recording a day; the cause is usually a network drop, a changed stream setting or the camera restarting. Scanning 30 days in the timeline view and noting gaps takes a few minutes.

A common mistake with retention is defining the target only in the settings. When the disk is full, the system overwrites the oldest recording; even if the setting says 30 days, if capacity covers 18 days you have 18 days. Look at the date of the oldest recording. On the disk side, an increase in reallocated and pending sector counts shows that a replacement should be planned while the disk is still working. If RAID is “degraded”, a second disk failure during the rebuild can lose the whole array. Without a hot spare, this window gets longer. Keep the configuration backup somewhere separate, not on the NVR’s own disk.

5. System and security

  • Clock sync: the NTP offset is measured and recorded
  • Firmware and software versions; checking security bulletins (firmware management)
  • User list: departed staff and service accounts
  • Checking for default passwords and open services
  • Checking for internet-exposed ports (cybersecurity checklist)

Clock offset looks like a small detail. It isn’t. When you put footage from several cameras side by side for an incident, clocks that are minutes apart break the sequence of events and make the recording’s evidential value debatable. Cameras should sync to the NVR and the NVR to the organization’s NTP source; during maintenance, the real offset should be measured and written in the report.

Don’t apply a firmware update to the whole site at once. Try it on one or two cameras first, verify that recording and analytics functions haven’t changed, then roll it out. The most common picture in the user list is a single shared admin account; who did what can’t be tracked. Move to personal accounts and keep service company accounts time-limited. UPnP left on and port forwards forgotten on the modem are also items to check at every maintenance.

6. Function tests

  • Playback and a sample export
  • Notification test: briefly disconnecting a camera and verifying the notification arrives
  • Accuracy of PTZ presets and tours
  • Sample alarm test from analytics rules
  • Remote access and mobile app access

A checklist lets you see; a function test proves it works. Try opening the exported sample clip on another computer where the system isn’t installed; the person who receives this file on the day of an incident will most likely be in the same situation. If no notification arrives for a camera connection loss, there’s no health monitoring. This is one of the most important maintenance findings. PTZ presets often drift over time on PTZ cameras; verify every point of the tour visually.

7. Reporting

Every maintenance visit should close with a report containing a per-camera results table, before–after image samples, measured values, fixed issues and prioritized recommendations. In the annual report, recurring issues and renewal needs (disk age, unsupported devices) are gathered in a single table.

A good report is the input to the next maintenance. If the same camera shows a focus problem three visits in a row, the problem isn’t cleaning but mounting or the device. Splitting recommendations at the end of the report into “urgent”, “planned” and “renewal budget” makes the decision maker’s job easier. An item that isn’t measured doesn’t go into the report.

Frequently asked questions

Can our own team do the maintenance?

Physical cleaning and visual checks can be done by a trained internal team. Firmware, RAID, network and security checks need technical expertise; keeping records with a checklist matters in every case.

What should be used for lens cleaning?

Non-abrasive cleaning materials in line with the manufacturer’s recommendation; dry wiping can cause scratches from sand or dust. On dome cameras, care is taken not to damage the coating.

What records should be kept during maintenance?

Per camera: date, work done, measured values (clock offset, PoE consumption, port errors), problems found and before–after image samples.

To turn this checklist into a contracted, reported service, see our periodic maintenance or, for multi-site setups, managed support services.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Video Surveillance

IP cameras, recording and central management infrastructure. We plan blind spots, retention periods and the camera network around the risks of each site.

Knowledge Center

Other articles