Unable to restore configuration to new controller
Unable to restore configuration to new controller
I installed the v5.13.23 controller on a Raspberry Pi 4. Prior to this I have been using the software controller on my desktop PC. The plan was to put the Raspberry controller in my server room and use it instead of my desktop. (The desktop PC is also running v5.13.23).
I did a backup on the desktop instance and a restore on the Raspberry. At least I tried the restore. I get:
"Restore failed. Failed to restore because of unexpected errors. Please try again later."
So, what should I do next? Do I need to reconfigure all of my LANs and my fixed IP clients? Did I do the backup/restore wrong?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
HI Steve
When changing controller platforms, I have found that you must migrate the sites rather than try to restore the whole controller. Essentially set up your new controller as a new controller, and then follow the Wizard instructions on 'Site Migration'.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
HI Steve
When changing controller platforms, I have found that you must migrate the sites rather than try to restore the whole controller. Essentially set up your new controller as a new controller, and then follow the Wizard instructions on 'Site Migration'.
- Copy Link
- Report Inappropriate Content
Thanks for the tip.
So, basically, start over.
Is there any to get a list of the clients with fixed IP addresses?
- Copy Link
- Report Inappropriate Content
It's not that bad...the only thing that's 'new' is the controller umbrella environment itself (admin login, whether cloud connected or not, IP). Everything else, ie your router, switch and AP configs are stored at the site level. So your subnet definitions, static IP assignments, etc etc will all come across just fine.
- Copy Link
- Report Inappropriate Content
"Everything else, ie your router, switch and AP configs are stored at the site level. So your subnet definitions, static IP assignments, etc etc will all come across just fine."
How do I do this? The backup/restore is not working. I found another post on these forums that sid this:
You can save the whole 'data folder' at C:\Program Files (x86)\TP-LINK\EAP Controller\data ( the installation of Omada Controller) of old Controller, install a new Controller at your server and replace the 'data folder', then the configuration of Omada Controller will be same as the older one.
AI said to use the migration option in Settings, but I don't have the migration option in settings. Would copying the data folder from the old to the new controller work as well? Even going from Windows to Linux?
If this would work it could save me a couple of hours...
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Thanks. Migration worked.
But, I swear on every server here that "Migration" was not in my old controller software menu when I started this process.
So, everything looks to be in order now, and no calls of "the network is down", so I think we're all good.
Again, your assistance is greatly appreciated. If we ever meet I will buy lunch.
Really. "migration" was not on the settings men this morning.....
- Copy Link
- Report Inappropriate Content
Glad you are up and running :). Your 'lunch' offer was much appreciated, it's the 3rd of my forum career here :)
I've often found people get tripped up by trying to do controller level stuff (like migration), but when not at the Global view level. It's a flaw in the UI design that there's not a link from a site's sidebar back to the Controller Options sidebar content, and especially confusing when there is only a single site on the Controller that you have to switch views to do different things. @Hank21 some thoughts for the controller team.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 635
Replies: 11
Voters 0
No one has voted for it yet.