A UniFi network runs on its configuration: WLANs, VLANs, firewall rules, port profiles, adopted devices and user profiles all live in the controller, not on the access points or switches themselves. Lose the controller and the hardware is still there, but the “brain” of your network is gone. That is why a current, tested backup is not an optional extra but the foundation of any serious network operation. This guide explains what a UniFi Controller backup contains, how automatic and manual backups differ, how to restore a backup, and which mistakes to avoid.
Why a UniFi Controller backup is so critical
UniFi devices (access points, switches, gateways) only store part of their operating data locally. The central configuration, meaning everything you set up in the controller, lives in the database of the UniFi Network application. If that database fails, your settings disappear with it.
Typical scenarios where a backup counts:
- A failed update or a corrupted database leaves the controller unusable.
- The server running the controller goes down (hardware failure, deleted VM, lost Cloud Key).
- A misconfiguration needs to be rolled back.
- The controller is being migrated to a new environment.
Without a backup, every one of these scenarios means rebuilding the entire network by hand and re-adopting every device.
What is inside a UniFi backup?
A UniFi Network backup captures your network configuration, essentially everything you have created in the controller. According to Ubiquiti, a backup includes your settings, devices and clients, but not UniFi Protect video data and not local logs.
| What gets backed up? | Included in the backup |
|---|---|
| Network settings (WLANs, VLANs, networks) | Yes |
| Firewall and routing rules | Yes |
| Adopted devices and their configuration | Yes |
| Client/user data and groups | Yes |
| Statistics and historical data | Depends on the backup type |
| UniFi Protect video recordings | No |
| Local system logs | No |
Important: a backup does not replace the protection of other systems. If you also run UniFi Protect (cameras), you need a separate backup strategy for it.
Automatic vs. manual backups (.unf file)
UniFi offers two basic ways to create backups. Both produce a backup file with the .unf extension.
Automatic backups
In the UniFi Network application you can enable automatic backups. You will find the option under Settings → Control Plane → Backups (menu paths vary by version and device; older interfaces used “Settings → Backup” or “System → Maintenance”). When enabled, the system creates a backup automatically on a regular schedule – according to Ubiquiti, once a week as well as before each major update.
The upside: you never have to remember. The downside: by default the backups sit in the same place the controller runs. If that fails completely, the local backup folder can be affected too in the worst case. With remote management enabled, cloud backups are stored in your UI account instead.
Manual backups
A manual backup is one you download deliberately as a.unf file from the same interface and store in a safe, separate location. Manual backups matter most before planned changes:
- before a controller or firmware update,
- before larger configuration changes,
- before migrating to a new host.
A good rule of thumb: automatic backups for day-to-day operation, manual backups before every risky action.
How to restore a UniFi backup
Restoring in the UniFi Network application generally takes just a few steps (the exact menu flow can vary by version):
- On the target controller, open Settings → Control Plane → Backups.
- Choose Restore and upload your.unf file, or select an existing automatic (cloud) backup.
- Confirm the restore and wait until the process is complete.
- Wait until all UniFi devices come back online and show a “connected” status.
When you migrate to a new controller, the order matters: first download the backup file (.unf) from the old controller, then connect the new host, restore the backup there, and only then point the devices to the new controller.
A note on compatibility: backups are most reliable when restored into the same controller version they were created on. Restoring across versions – especially a newer backup into an older version – can fail, and Ubiquiti recommends matching the controller version to the backup.
Common UniFi backup mistakes
Most data loss does not happen because there was no backup at all, but because the backup was no good when it was needed. These are the mistakes we see most often:
- Backup stored only locally: the backup sits on the same device as the controller. If that fails, both are gone. Backups belong in a separate, independent location.
- Never-tested backup: a backup that has never been restored is a promise, not proof. Only a successful test restore shows the file actually works.
- Outdated backup: enabling automatic backups but never checking that they actually run. Regularly verify the date and completeness of the last backup.
- No backup before updates: updates in particular are a common trigger for problems. Take a fresh manual backup before every update.
- Missing documentation: if nobody knows where the backups are and how to restore them, even the best backup will not help when it counts.
Failure scenarios – and how clevendo keeps you covered
Data loss is rarely “just” a technical problem: for as long as the network is not running cleanly, an entire team or site may be working with limitations. That is exactly why we at clevendo rely on prevention rather than improvisation.
When you host your UniFi Controller in the cloud with clevendo, automatic backups run in the background – on infrastructure separate from the controller, in a data center in Germany and GDPR-compliant. That sidesteps the most common mistake, “backup stored only locally,” from the start.
If a problem does occur – after a failed update, a corrupted database or an accidental misconfiguration – our team restores a clean backup and brings your network back to a working state. For smaller adjustments or questions, live support is available too, and you will find further guides in our help center. Want the full picture of managed cloud hosting? Start on our home page.
Conclusion
A UniFi Controller backup is only worth something if it is current, stored separately from the controller, and can actually be restored when it matters. Automatic backups take the routine off your plate, manual backups add extra protection around risky changes – and a tested restore path turns a backup into real protection.
Are you in the middle of an outage right now, or do you want to be on the safe side going forward? Get in touch with clevendo and we will help you protect and restore your network.
Frequently asked questions
What is a.unf file in UniFi?
The.unf file is the backup format of the UniFi Network application. It contains your network configuration – for example settings, adopted devices and clients. You can download it and restore it to recover or migrate your controller.
How often does UniFi back up automatically?
When automatic backups are enabled, UniFi creates a backup on a regular schedule – according to Ubiquiti, typically once a week as well as before each major update. The exact frequency depends on your settings and controller version. With clevendo, automatic backups run on separate infrastructure.
Does a UniFi backup include camera recordings (UniFi Protect)?
No. A UniFi Network backup captures the network configuration, not the video recordings from UniFi Protect. Protect needs its own, separate backup strategy.
Can I restore a backup to an older controller version?
Restoring is most reliable into the same controller version the backup was created on. Restoring a newer backup into an older version can fail, and Ubiquiti recommends matching the controller version to the backup. If in doubt, our team can help you choose the right approach.
Where are automatic UniFi backups stored?
By default, automatic backups are stored on the same system that runs the controller. With remote management enabled, cloud backups are kept in your UI account. Because a local-only copy is risky, clevendo stores automatic backups on infrastructure separate from your controller.
