Quick answer: Update through the approved procedure for the exact model and release, inside an agreed window, with a verified recovery plan. Test the required recording and access functions afterwards. A saved configuration or old firmware file does not guarantee that downgrade or restoration is supported.
On this page
Make a reasoned change decision
Review supported firmware and relevant advisories as part of maintenance. Do not wait for a visible fault before assessing a security fix. Consider exposure, vendor/support advice, compatibility and the consequence of downtime with the customer’s IT contact.
Routine reviews and urgent advisories need different response paths. If an update is deferred, record why, who owns the decision, any temporary controls and the next review date. The firmware maintenance calendar organizes that ongoing work; this guide covers the actual change window.
Identify the device and the approved file
Record the complete SKU, hardware revision where applicable, serial number and exact installed version. Obtain the approved package from the Anabon Download Center or support. Match the release’s eligible hardware and supported starting versions before uploading anything.
Read prerequisites, intermediate versions and dependencies across cameras, recorder and software. Verify the file using supplied integrity information where available. If the file or instructions are unclear, resolve that before the window. A similar chassis or shortened model name is not evidence of compatibility.
Prepare for interruption and recovery
Agree which recording/viewing functions may stop and for how long. Protect relevant incident footage through the approved export process before making changes. Keep configuration exports and useful records in the protected project folder; credentials and sensitive screenshots need controlled handling.
Confirm whether configuration import and downgrade are supported between the versions involved. Some changes need a special recovery procedure or cannot be reversed in the assumed way. Arrange authorized on-site assistance where physical intervention may be required.
| Before the window | After the change |
|---|---|
| Exact SKU/revision, installed version, approved target and release instructions | Actual installed version and required device status. |
| Protected configuration/log exports and confirmed recovery instructions | Required channels, storage, recording and playback before/after the change. |
| Agreed downtime, access, stable power and on-site assistance where needed | Time, accounts, approved remote access and integrations. |
| Required analytics/alarm functions and their safe test plan | Observed tests passed/failed, open action owner and customer notification. |
Follow the release’s sequence
- Confirm approval, stable power, required backups and the current maintenance window.
- Test a representative device/combination where feasible and supported.
- Apply updates in the documented order. There is no universal camera-first or NVR-first rule.
- Use controlled batches where the procedure permits and stop when a required check fails.
- Follow the instructions during progress and restart. Do not interrupt power, repeatedly reboot or improvise recovery when the device appears unresponsive.
Remote configuration access is not proof that remote updating or recovery is supported. Confirm that scope separately. A remote connection cannot restore lost power or reconnect a failed cable.
Verify the functions the customer bought
Check the installed version, relevant logs and storage state. Verify required channels, recording schedules and playback recorded after the change; retain awareness of earlier footage the customer needs. Check time, users, network settings and supported integrations.
Test the actual analytics, alarm actions and approved remote functions used on this project. Do not mark a generic feature list passed when the installation never used those features. Record any change in settings or behavior and obtain acceptance for unresolved limits.
If a check fails, pause and use the agreed plan
Preserve the current symptom and logs. Compare settings against the recorded baseline, but only change or restore them through the supported procedure. Do not import an incompatible configuration or load old firmware because an internet post suggests it.
Contact support with the exact versions, file, hardware and observed failure. A spare recorder is only a recovery option if its compatibility, credentials, power, channels and required configuration were planned and tested; an export alone does not make any spare interchangeable.
Close the work order with an exact record
Record before/after versions, reason, approval, start/end time and zone, technician, files used, checks and open actions. Notify the customer when the system is returned to service and identify any function still unavailable.
Update the handover record and hardening baseline. Keep earlier version history instead of replacing it with “latest.”
FAQ
Can I always roll back?
No. Confirm the actual supported downgrade/recovery path before the change.
Will recordings always survive an update?
Do not guarantee that. Protect required footage beforehand and verify the relevant storage/playback afterwards.
Should I update every device at once?
Follow the documented dependencies and controlled rollout plan, with checks before expanding the change.
Send the complete SKU/revision, installed/target versions and required functions to Anabon technical support when the approved update or recovery path is uncertain.
