The Omada Controller backup contains the configurations of all devices and the whole controller. You can restore the configuration, migrate the Controller, troubleshot with the support team etc., using the Controller Backup file.
Here are some methods to get the Omada Controller Backup file.
Auto Backup
-
For Hardware Controller (OC200/OC300)
You can store backups on a USB stick or File Server with Auto Backup. (Global Viewer > Settings > Maintenance > Auto backup)
-
For Software Controller
You can store backups on the local host or File Server with Auto Backup. (Global Viewer > Settings > Maintenance > Auto backup)
-
For Cloud-Based Controller (CBC)
You can only store backups on a File Server with Auto Backup. (Global Viewer > Settings > Maintenance > Auto backup)
Manual Backup
-
For Hardware and Software Controller
If you access the controller locally with the main administrator account, you can download backups on your local host or FTP Server. (Global Viewer > Settings > Maintenance > Backup)
If you cloud access the controller with the main cloud administrator, you can only store backups on a File server in your network. (Global Viewer > Settings > Maintenance > Backup)
-
For Cloud-Based Controller
You can export backups to the local host or File server. (Global Viewer > Settings > Maintenance > Backup)
Export for Support
As a Main Admin, you can export the support files, Running Log+Configuration Data, via both local and cloud access. (Global Viewer > Settings > Maintenance > Export for Support)
Please note that the support configuration data only can be used by TP-Link technical support team, it is invalid if you restore it in your own Controller.
Site Backup
If you want to create a backup of a single site, this is currently only possible via Site Migration. (Global Viewer > Settings > Migration > Site Migration)
A way to duplicate the configuration is to be able to copy sites on Global View > Dashboard > Site list. For example, it would be useful for an MSP to create a page only for the basic configuration and copy it to new sites again and again to keep the workload as low as possible.
