Setting up rclone was super easy, and I just used it to ssh into the cloud key with root as user, and then the password I have set for the cloud key. The biggest task was actually to find where the backups were stored, so here they are
Making the initial connection to each device is probably better explained on the site itself. I just wanted to provide the paths for the backups generated, as that was actually the biggest task in this.
Download Unifi Backup From Cloud
DOWNLOAD 🔥 https://blltly.com/2yGApl 🔥
The UniFi Controller manages your UniFi network, including device settings, network configurations, and user profiles. A backup of the UniFi Controller ensures that you can quickly restore your network to a previous state or migrate your data between UniFi Controllers.
Sometimes you like to check what is inside the backup of your UniFi Controller. Maybe that one password that you need, or some other settings. For that, we created a Backup Explorer. The Backup Explorer works completely in your browser, we don't have access to any data inside your backup. Here is how it works:
Regularly backing up your UniFi Controller is an essential practice to make sure your network's configuration is safe. At UniHosted, we manage this for you. We are a cloud-hosted UniFi Controller hosting provider that takes your network to the next level.
I thought this might be useful for anyone that would like to copy their nightly backups off their Unifi OS system. I just upgraded to a new UDMP from a USG so I had to move to this. Anyways it works so if your interested keep reading.
Thanks. Previously I was using the Cloudkey with CRON job to copy and unmount to Synology. This was all done directly on the Cloudkey and the Synology just received the copy. I had to change this up though as UniFi OS does not allow apt-get. I did this using these instructions here and look for @kubotronix response using NFS.
I considerd that and Unifi OS does run docker locally but I have a docker server anyways so I just deployed it there and left the UDMP alone. If running wireguard in docker interests you check it out here it works really well and has not skipped a beat.
If you plan to use Wireguard both remotely and locally, say on your mobile phone, you will need to consider routing. Most firewalls will not route ports forwarded on your WAN interface correctly to the LAN out of the box. This means that when you return home, even though you can see the Wireguard server, the return packets will probably get lost.
I turn wireguard on or off based on presence. The home automation platform sends a silent pushover notification to my phone to turn on and off. I have tasker installed on my phone handling the phone side.
I bought a C8 but the C7 will not backup to the cloud. It is registered and passes the network tests. When I click settings > backup and restore > create and upload (Create a cloud backup for C-8 migration), all it does is display "Last cloud backup upload failed, please try again." any ideas? Thanks.
Was pinging cloud.hubitat.com one of these tests? If not, try that--or make sure you have valid DNS servers set (try setting them again even if they look right) or just try a network reset if DHCP is fine for you just to make sure.
Are you on a static ip or DHCP? This sounds like a DNS issue. If you have a static ip, even if it looks like the c7 has dns settings, set the dns to 8.8.8.8, 1.1.1.1 and click save. Then try the update.
Thanks for the reply. Are you asking if the C7 is static, or if my WAN's IP is static? Both are DHCP, but the C7 has a 'fixed' DHCP assignment, set by my UniFi Dream Machine Pro. I did disable the setting to fix the DHCP assignment, making it truly DCHP (but it didn't change, of course) and tried again but got the same result.
I have another C7 at work, with a similar network setup; UniFi equipment, but a USG instead of the Dream Machine. The WAN has a static IP and the C7's IP is DHCP and fixed. I was able to create and upload the cloud backup on that one, so at least I have a success to compare and contrast.
Press the network reset button on the bottom of the hub that is not connecting to the internet using a toothpick or a paperclip for 7 seconds. (This will be the only round hole out of all the square ones). Make sure you have a DHCP reservation. Then see if it's getting on the internet properly. If not check your dream machines isn't blocking DNS for some reason to the hub ip.
I did the network reset with the paper clip just to make sure, but no change. I combed though the UDMP and disabled anything that could possible have an effect, but no change. It was a pretty vanilla config to begin with.
When I attempt the cloud backup, the progress circle moves for 2 seconds at most, the screen flashes, the circle disappears and that's it. "Last cloud backup upload failed, please try again" has been displayed since the first attempt. Regarding that flash, I created a 60 fps recording hoping to find an error message, but there is none, it's just a flash.
Next, I took my UniFi router off the network and used the ISP supplied cable modem to provide DHCP service. I did the network reset on the C7, forcing it to pick up a new IP (a 192... address; I use 172... in my UniFi config). I confirmed the new IP, signed into it, went to the network test and successfully pinged host cloud.hubitat.com. I tried the backup again but got the exact same result.
Something just occurred to me. Since I've ruled out my network config, I looked at what is different between my home C7 and my office C7 (which did backup to the cloud) and found something that may be significant. My office C7 has only ZigBee devices; no Zwave. My home C7 has Zwave devices only; no ZigBee. The home C7 perpetually lists one alert: ZigBee radio is offline. I always assumed that was due to having no ZigBee devices and ignored it. However, the office C7 does not have an alert saying the Zwave radio is offline. I suspect the alert is what is causing the back to fail (probably aborted at the server end). So either my ZigBee radio is really faulty, or else that alert will go away when I connect a ZigBee device. We'll see.
There are backups in multiple places - for the CloudKey, and for the controller - and my notes say that I got the backup I needed from /usr/lib/unifi/data. However, that feels a bit suspect - I think it was probably in /data (and some subdirectories under that) for the controller.
The second option is via the UniFi Site Export Wizard, which provides a guided site-per-site migration from one Cloud Key to another. It is a simpler process and will allow users to select which sites and which devices they wish to migrate.
2. To avoid having duplicate Controllers shut down the old Cloud Key once the backup download is complete. Scroll down in the Settings > Maintenance > Cloud Key Operations and click the Shut Down Cloud Key button.
3. Upload the backup onto the new Cloud Key by following initial setup instructions. Launch the Setup Wizard by discovering the new Cloud Key and then clicking Adopt in the Cloud Access Portal. If you have already configured the Cloud Key with the wizard or via the UniFi app/bluetooth, open the controller and go to Settings > Maintenance > Restore and click Choose File. Select your recently downloaded .unf file. After the system has restored all configurations it might appear duplicated and with the same host IP address, in the Cloud Access Portal with your old controller name (online) and with the controller name you just substituted (offline). You can launch it using the one that is online.
4. Once the Setup Wizard launches, the first page will offer the option to restore from a previous backup. Click that link and select your recently downloaded .unf file. Note that this will also restore the Controller credentials from your original Cloud Key.
5. Wait until the backup is restored. Once UniFi finishes working, you will be presented with the login screen for the new Controller. Remember to use the username and password from the old Controller.
6. Once you have confirmed that all devices and settings have migrated successfully to the new Cloud Key, it is strongly recommended to reset the old Cloud Key to factory defaults to avoid duplicate Controllers which could cause issues. While still connected to the power source:
7. Close the browser page with the Cloud Access Portal from where you launched the Controller Wizard. To open the Cloud Access Portal again, go to Settings > Cloud Access and click the Dashboard link from there.
If you have a CloudKey or onsite UBNT Controller, or even a hosted controller, UniFI Dream Machine or UDM Pro, your backups are saved locally. BackiFi allows you to connect to your own 3rd party cloud storage and run your own schedules to backup to Dropbox, Google Drive, AWS S3, MS One Drive, Backblaze or a FTP/SFTP location.
Log into your UniFi Controller -> Settings (lower left corner) -> Backup -> Enable Auto Backup -> On. That was easy. It also gives you warm a warm fuzzy feeling knowing that your controller configuration is backed up in case something goes wrong, right? What if your hard drive crashes? What if the server burns down? Oh my...
After all, it is the responsible thing to do. You already have 1/2 of your life saved to the cloud somewhere and, if you followed along with Chris Sherwood at Crosstalk Solutions, you have your UniFi controller in the cloud. Lets put one more piece of your valuable data in one more place where you don't have control of it and rely on the "black box" to keep it safe, secure, and backed up...
Dropbox seems to be a reasonable place to start. It looks like everyone from individuals to large corporations are trusting their data to them, why shouldn't we? Go set up an account, or try to remember what your password is to your current account, I will wait. 152ee80cbc
google pinyin download windows 7