Where Does the Omada Controller Store Data and Backups?
The Omada Software Controller keeps its database in data\db under the install folder (Windows) or /opt/tplink/EAPController/data/db (Linux), with auto backups in data/autobackup.
Last updated
Omada stores everything in a local database, not in the cloud. Manual and scheduled backups produce .cfg files through the Backup and Restore pages. Underneath, the live data sits in a db folder whose path depends on the host OS.
Auto backup drops files into data/autobackup inside the install location, capped by the maximum files setting. For upgrades, stop the controller and copy the db folder itself in addition to exporting a .cfg. The two methods fail differently, which is why the docs recommend both.
Where Omada Controller stores this, by platform
C:\Users\[Username]\Omada Controller\data\db
Live database plus autobackup folder beneath data/. Stop the controller before copying db by hand. Export .cfg files from Settings, Maintenance for migrations.
/opt/tplink/EAPController/data/db
Same layout as Windows under the EAPController tree. Back up here before upgrades. Auto backups land in the sibling autobackup folder up to the configured file limit.
Frequently asked questions
How do I back up Omada before upgrading?
Stop the controller normally first, then copy the whole data/db folder aside before upgrading. TP-Link documents this exact precaution for version jumps. The .cfg backup files from Backup and Restore cover migration, the raw db copy is your belt and suspenders.
Can I migrate Omada to a new server?
Use the same major and minor version on both ends, since controller backups only restore into matching releases. Exporters also note the file is encrypted and compressed, so it restores settings but cannot be read or edited by hand.
Notice an outdated path? Let us know.