How to backup unifi controller install#

How to backup unifi controller install#

Perform an update followed by an install to proceed as per usual. Sudo echo '#deb stable ubiquiti deb unifi-5.6 ubiquiti' | sudo tee /etc/apt//100-ubnt.list Remove device footprints from the old controller ('Forget' the APs) 1. A popup will be shown when the download is complete. Select registry and download the latest version of the Unifi Controler image.

Log on to your Synology NAS and open Docker. Check they have correctly provisioned on the new controller. Log on to the unify controller -> press the Cog Wheel -> Controller Settings -> Backup and press Download. Initiate the migration from the old controller. No point spending double the money (if you buy the devices) and wear them both down. Plus if you run your key on a vm environment youвЂ™ll likely have a local backup method. Next up, the repo will have to be pointed back down to 5.6, if not, the install will simply reinstall 5.7 for you, link The basic steps are: Export a backup file from the controller (UNF file) Import that file onto the new controller. Everything works fine when theyвЂ™ve been provisioned and the controller is down, unifi has a backup system. To perform the rollback youвЂ™ll need a 5.6 backup of the controller, as well as SSH access to the box.ДЇirst off youвЂ™ll need to remove the 5.7 version using the following command sudo apt-get purge unifi -y. If you were to attempt to install 5.6 over 5.7 and in a sense downgrade that way, youвЂ™ll be faced with 'We do not support upgrading from 5.7.20', to solve this, go ahead with rollback. The device will still function, but no new updates will be installed, settings updated, or statistics reported back. the autobackup which you download from the setting is for the time period which you set for e.g if you had set time today so it will take a backup of that day. After installing the new shiny 5.7.20 version of the UniFi Controller software you might be faced with an 'Connected (Incompatible Model)' error on your older devices, this is simply due to the EOL being reached.