Support
Back Up and Restore an NVR Configuration
Configuration Recovery
Summary
Follow the four stages below to diagnose an NVR configuration must be protected before firmware, replacement or major changes without losing evidence, configuration or device ownership.
Applies to
- NVRs with configuration import/export
- Planned maintenance and recorder replacement
Difficulty and time
Difficulty: Advanced
Estimated time: 20 to 60 minutes
What you will need
- The exact model and current firmware or app version
- Administrator access where authorised
- A photo or screenshot of the current status
- One controlled test case and its exact time
What this guide covers
- Preserve and reproduce the fault
- Open the correct diagnostic screen
- Correct the proven cause
- Verify and document the result
Use this page when an NVR configuration must be protected before firmware, replacement or major changes. It includes the menu or screen to look for, the status that matters and a repeatable proof test.
Exact labels can differ between recorder, controller, app and firmware versions. If the named screen is not present, do not guess at destructive options; note the model and current version for support.
Before you start
Protect the current system and record a baseline before changing anything.
- Write down the exact symptom: the site has no current configuration backup or needs a known-good configuration restored.
- Photograph the current status, error text, wiring or timeline as applicable.
- Record the last known working time and anything changed immediately before the fault.
- Export a fresh backup before every firmware update, factory default or large settings change; do not overwrite the last known-good file.
A configuration restore can overwrite working network and user settings
Do not import an unknown, incompatible or untrusted configuration. Keep the pre-change backup and current network details available for recovery.
If the required option is missing or the result does not match this guide, stop and identify the exact model before continuing.
What usually causes this
- No handover backup exists
- Firmware maintenance is planned
- Recorder replacement is required
- Settings were changed accidentally
Step 1: Preserve the current state and reproduce the fault
Begin with a repeatable baseline so you know whether a later change genuinely helped.
- Reproduce the problem once and record: the site has no current configuration backup or needs a known-good configuration restored.
- Note whether every device or user is affected, or only one.
- Compare one working path with the failing path if a comparison exists.
- Export a fresh backup before every firmware update, factory default or large settings change; do not overwrite the last known-good file.
Step 2: Open the correct screen and inspect the evidence
The primary diagnostic location is Main Menu > Maintenance > Import/Export, Configuration > System > Maintenance or Configuration File. Do not change anything until the displayed state is recorded.
- Open Main Menu > Maintenance > Import/Export, Configuration > System > Maintenance or Configuration File. Menu wording can vary by model and firmware; use the nearest equivalent label.
- Record model, serial, firmware, IP address and cloud ownership.
- Check whether exported files are encrypted or tied to the same model/firmware family.
- List settings that may not be included, such as app ownership, certificates or licences.
Step 3: Correct only the cause you proved
Use the matching correction below. Make one change, save it, then repeat the same test.
- Insert a known-clean USB drive or choose a secure client download location.
- Export the configuration and set a strong backup password if offered.
- Store a dated copy outside the recorder with a short change note.
- Restore only to a compatible device/version, then review network and ownership before applying.
Step 4: Verify, monitor and document the handover
A saved setting is not proof. Test the real outcome locally first, then test any app, cloud or client path separately.
- Confirm the backup file exists, has non-zero size and can be identified later.
- After restore, verify camera channels, schedules, users, network and time.
- Test a new local recording and playback.
- Test remote/cloud access only after local operation is stable.
Controlled support test
Situation: The reported symptom was: the site has no current configuration backup or needs a known-good configuration restored.
Solution used: The current state was recorded in Main Menu > Maintenance > Import/Export, Configuration > System > Maintenance or Configuration File, one matching correction was made, and the same test was repeated.
Why this was chosen: This separated the proven cause from unrelated settings.
Installation notes: The final screenshot and test time were saved with the handover record.
Official reference used for this guide
Menu names differ between releases. Confirm model-specific behaviour in Hikvision NVR User Manual before firmware, reset, storage or security-sensitive work.
Common mistakes
- Changing several settings before repeating the original test.
- Using a factory reset, initialise or format option as an early troubleshooting step.
- Treating an app symptom as proof that the local hardware or recording has failed.
- Failing to record the model, version, exact error and test time before escalation.
- Assuming similar-looking models use identical menus or features.
Troubleshooting table
| Symptom | What to check | What to do next |
|---|---|---|
| the site has no current configuration backup or needs a known-good configuration restored | planned maintenance, recorder replacement, accidental changes or disaster-recovery preparation | Open the named diagnostic screen, record the displayed state and use the matching correction above. |
| The named menu is not visible | Different firmware, permissions or model capability | Do not substitute a destructive menu. Capture the model and version and use its official manual. |
| The change saves but the fault remains | The selected cause was not the root cause | Undo the change if appropriate, return to the baseline and compare the failing path with a working one. |
| Local test works but app or client test fails | Account, permission, cloud or remote-network path | Keep the proven local configuration and diagnose the remote path separately. |
| Problem returns later | Intermittent power, cable, storage, network or schedule condition | Record the new failure time and status; correlate it with logs, events and the last known working interval. |
When to contact support
Contact SecurityWholesalers support when the export fails, the backup password is unknown, the replacement model differs, or licences/cloud ownership may not transfer.
Send the order number if available, exact model, firmware or app version, screenshot of Main Menu > Maintenance > Import/Export, Configuration > System > Maintenance or Configuration File, the failure time, and the result of the local proof test.
Related support guides
- CCTV Networking Support - Browse every guide in this support area.
- All Technical Support Guides - Return to the complete support library.
Related buying guides
- CCTV Buying Guide - General CCTV planning guide.
Relevant product categories
- CCTV Products - General CCTV products.
Still stuck?
Need help choosing or setting up a system? Contact SecurityWholesalers support with your order number, product model and a clear description of the issue.
Frequently asked questions
-
Where should I click first for backup NVR configuration?
Start at Main Menu > Maintenance > Import/Export, Configuration > System > Maintenance or Configuration File. Record the existing state before changing it because labels and available options can vary by model and firmware.
-
What should I look for on that screen?
Look for Import/Export Configuration, encryption/password options and any warning describing model or firmware compatibility.
-
What must I avoid changing during the first check?
Do not import an unknown, incompatible or untrusted configuration. Keep the pre-change backup and current network details available for recovery.
-
How do I prove the correction worked?
Verify the exported file, then after any restore check channels, users, schedules, network, recording, playback and remote access.
-
Why might my menu names look different?
Recorder, controller, camera, app and firmware releases can use different labels. Use the closest equivalent only when its function is clear; otherwise record the model and version for support.
-
Should I factory-reset the device?
Not as an early step. A reset may erase users, network settings, recording configuration, licences or cloud ownership. Back up the configuration and confirm the recovery plan first.
-
What should I send technical support?
Send the exact model and version, screenshot of Main Menu > Maintenance > Import/Export, Configuration > System > Maintenance or Configuration File, exact error text, failure time, what changed before the fault and the result of the controlled local test.
-
Can configuration changes recover data or events that were never recorded?
No. A correction can restore future operation, but it cannot recreate footage, alarm events or access transactions that were never stored.