Ubiquiti · UniFi

UniFi Backup vs Support File: What to Save Before a Change

A backup and a support file solve different problems. A backup preserves configuration for recovery or migration. A support file records diagnostic information needed to investigate behavior. Save both when preparing a significant change or documenting an intermittent fault; one is not a substitute for the other.

Scope: UniFi OS consoles/Cloud Gateways and self-hosted UniFi Network. Current documentation reviewed 2026-10-08; backup scope and UI labels differ by host. Not a universal cross-version restore compatibility promise.

For a UniFi OS console or Cloud Gateway, use its system configuration backup workflow. A self-hosted Network deployment also has Network application backups, commonly using the .unf extension. Check which applications and settings your selected export covers before calling it a complete site backup.

Choose the artifact by purpose #

ArtifactWhat you use it forWhat it does not establish
System configuration backupRecover the supported console configuration scopeThat a restore has been tested
Network application backupPreserve or migrate Network settingsThat every console application is included
Console support fileInvestigate console/application behaviorA replacement for a recovery backup
AP, switch or gateway support fileInvestigate one deviceComplete evidence from every other device
Incident notesRelate observed symptoms to test timesProof of the root cause by themselves

Find backup actions in the console's Control Plane/Backups area. For a device support file, select the device in Network, open its settings and locate Generate Support File, then download the completed result. Console support files are available through the console's management workflow. If the interface has changed, use the linked manufacturer instructions for the installed release rather than an old screenshot.

Collect evidence before the symptom disappears #

Write down the affected model, firmware, Network application version, incident time with timezone, client address and the exact action that failed. Capture the relevant device file as well as the console file when the fault spans both. Compare a working client with the failing client instead of collecting every device indiscriminately.

For an AP intermittently going offline, include uptime and the upstream port's events. For an adoption problem, include the device's management IP and the intended Network host. A bundle labeled only “network broken” forces the recipient to reconstruct details that were known during the incident.

Store exports outside the device being changed and verify that the download completed. Record backup scope and creation time in the change ticket. Exporting a file is not a restore test: recovery also depends on compatible software, working access and a known procedure. Do not attach unreviewed support files to a public forum. Even when software removes some sensitive fields, diagnostic archives can still disclose network structure, names and operational details.

Sources

Documentation reviewed: 8 October 2026