How to obtain a backup file from an Omada Hardware/Software/Cloud-Based Controller (V5.8 and above)
OC200 , OC300 , Omada Software Controller( V5 ) , Omada Cloud-Based Controller( V5 )
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device and check either the Datasheet or the firmware section for the latest improvements added to your product.
An Omada Controller backup contains the configuration settings of all devices, as well as the controller. You can restore the configuration, migrate the Controller, or troubleshoot with our support team etc., using the Controller Backup file.
Here are some methods to obtain the Omada Controller Backup file.
Auto Backup
- For Hardware Controller (OC200/OC300)
You can store backups on a USB Drive or File Server with Auto Backup. The Auto Backup function can be accessed under Global Viewer → Settings → Maintenance → Auto backup)
- For Software Controller
You can set where to store backups using the Local File or File Server options when configuring Auto Backup. These settings can be located under Global Viewer → Settings → Maintenance → Auto backup.
- For Cloud-Based Controller (CBC)
Cloud-Based Controller backups can only be stored on a File Server with Auto Backup. Settings for this option can be found under Global Viewer → Settings → Maintenance → Auto backup
Manual Backup
- For Hardware and Software Controller
When accessing the controller locally using the main administrator account, you can download backups via local file or FTP Server. Settings for this option can be found under Global Viewer → Settings → Maintenance → Backup
If accessing the controller via the cloud with the administrator account, you can only store backups on a File server in your network. These settings can be found under Global Viewer → Settings → Maintenance → Backup.
- For Cloud-Based Controller
You can export backups via the local file or File server options under 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 under Global Viewer → Settings → Maintenance → Export for Support
Please note that the Configuration Data exported from the “Export for Support” option can only be used by TP-Link technical support team for diagnostics and troubleshooting; it cannot be used to restore your own Controller.
Site Backup
If you want to create a backup of a single site, this is currently only possible via Site Migration, under Global Viewer → Settings → Migration → Site Migration
One way to duplicate the site configuration is to use the Copy option via the Export Site function under Global View → Dashboard → Site List. This feature can be useful for a Managed Service Provider to create an entry for basic configuration settings and copy/export it to new sites, vastly streamlining deployment.
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
We'd love to get your feedback, please let us know how we can improve this content.
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Livechat
__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au
Meta Pixel
_fbp
Crazy Egg
cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs
Hotjar
OptanonConsent, _sctr, _cs_s, _hjFirstSeen, _hjAbsoluteSessionInProgress, _hjSessionUser_14, _fbp, ajs_anonymous_id, _hjSessionUser_<hotjar-id>, _uetsid, _schn, _uetvid, NEXT_LOCALE, _hjSession_14, _hjid, _cs_c, _scid, _hjAbsoluteSessionInProgress, _cs_id, _gcl_au, _ga, _gid, _hjIncludedInPageviewSample, _hjSession_<hotjar-id>, _hjIncludedInSessionSample_<hotjar-id>
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or