This is what I’m getting when i try to install. I have installed on previous devices with Hass.io installed without issues - Has there been a change??
I think you’re trying to install it through HACS or … something else. This is a Home Assistant Addon, so you’ll need to add the repository through the Supervisor’s addon store.
Installation Instructions
I was being dumb - Should have gone to bed and not tried to function @ 2am!!
Many thanks!!
Hello.
I’m prepping to migrate from SD to SSD so I’m gathering possible information.
- Can this backup/restore method be used to move config from one Pi to another? Are those any details I need to remember about when moving to another device?
- Does this method backs up/restores network settings? My HA has fixed IP set in HA. I want to avoid to create conflicts in network
thank you.
The addon actually just asks the supervisor to create its snapshots, but its hard to answer these questions broadly because documentation on what it does exactly is pretty scant.
Can this backup/restore method be used to move config from one Pi to another? Are those any details I need to remember about when moving to another device?
Generally yes. I’ve even restored a snapshot taken on a raspberry pi onto a full x86 when I upgraded my hardware. There are caveats to this, for example some addons and integrations have a hardware dependency that can’t be met when you switch devices.
Does this method backs up/restores network settings? My HA has fixed IP set in HA. I want to avoid to create conflicts in network
I’m not sure but I’d guess no. I’ve only ever restored a backup that used DHCP and usually setting the network configuration is something you have to do before restoring a snapshot anyway.
Thank you for the answer.
I asked the same question somewhere in Supervisor/backup thread but got no answer (only only me)./
Anyway, yesterday I risked it.
When restoring, HA gives option to opt-in to restore single components/integrations. Which is very useful, cause you can backup all, while select requested parts during restore.
On the top, HA itself is listed. Because I had HA already in recent version I unchecked it.
At this point I can confirm that network settings hasn’t been changed by restore process.
One may hope that including HA component doesn’t change this fact 
Why would I see this:
upon indicating to upload a snapshot from my drive during the initial onboarding of a fresh HA install? Isnt this in the same format as the core HA snapshots maybe?
since restoring wouldn’t go, I decided to install the add-on in the fresh HA install, hoping I could then connect to my Google drive and re-install from there. I have 3 folders for my instances and the newly installed add-on found 1, unfortunately not the correct one, and what ever I tried, it would not connect or show me the interface to change to the other folder. Kept asking me to authorize, but it simply wouldn’t work. I got the code to copy somewhere in a folder choser, but never saw that anywhere?
after that I installed the SMB add-on, manually copied a snapshot from my GD local folder to the backup folder of the HA instance, and could then reload that from within the core snapshot interface (so not the add-on interface)…
seems a very longwinded way, and something must have gone wrong, because I would have thought this all to be possible from within the add-on?
anyways, we’re backup and running after a desasterous update to OS 4.18. beware for that. (think it is pulled from the Beta’s for now)
thanks for having a look
What would be the optimal config to keep sd card wear to a minimum?
Currently, I’ve set the backup to once a week, 1 full snapshot locally, and 2 in Google Drive.
Yup, the snapshots this addon makes exactly the same format as the ones the supervisor makes. I’m glad the feature is there, but perosnally I’ve had a lot of trouble with the “initial onboarding” snapshot upload. I’ve never been abel to get it to work with snapshots over a few hundred Mb in size.
You can upload a snapshot if you install the addon and connect it to Drive right after a fresh installation, but using samba is a perfectly fine way to do the same thing too.
1 Like
Since the snapshot is just one big file, I think its unlikely to contribute much toward disk thrashing when compared to something like HA’s log file. That being said, general advice would be:
- Keep the snapshot small. you can use partial snapshots to only backup the folders/addons you really need.
- Snapshot as infrequently as possible.
Minimizing the number of snapshots you keep in HA wouldn’t do much, since the its the same number of writes no matter how many backups you keep locally.
1 Like
thanks, the last option is what I used in the end, as Google kept referring me to 1 folder, and wouldn’t switch to another, the one for this instance…
mysterious ways sometimes.
hi, i have the same error… Any solution??
thanks in advance 
Not yet, I am still struggling.
I’ve read some posts that maybe the disk space could be too low, so I tried to clean up my docker (remove obsolete images and containers as well as log files), but still no luck.
Interestingly, this is the only addon I am not able to install (besides Duck DNS, ESPHome, MariaDB, Mosquitto, NGINX, Node-RED, Samba, Terminal & SSH, Zigbee2mqtt which all worked)
1 Like
Hi! It seems that I need to be signed in to Google for the plugin to work at all even though I’ve turned of the upload-feature. Is there a setting I’m not seeing or could you please implement an ”offline” feature?
Rgds Fredrik
Not essential, addon runs well and safely.
After moving to x86_64 Debian HA supervised, it no longer shows an OS in the name. Did I do something wrong or miss it?
Full-Snapshot - 2020.12.1 - OS-None - SV-2020.12.7
If you’re using the {version_hassos} key for that in your snapshot name, thats the HASSOS version number. If you’re running on supervised debian, then you aren’t running on top of HassOS so there is no version number for it.
You might want to use {version_super} or {version_ha} depending on what you’re trying to keep track of.
A new year, a new version. I’ve just release v0.103.0. In addition to some minor bug fixes (see the changelog for details) this version adds the ability to use the addon without connecting it to Google Drive. I’m not 100% sure why its become so popular for my addon to be used in that way, but the deal is that you guys buy me coffees and I deliver features.
Speaking of which thank you to everyone who has provided support on 
. I have my phone set up to make a “ka-ching” sound every time someone donates, and it is my greatest source of motivation. I read every comment with furious attention. You guys have secured funding for the infrastructure to keep the addon running for many months into the future. It is greatly appreciated.
9 Likes
Hi all
I’m having issues with Authentication
So I installed this onto HA via RPI4.
Clicked Authenticate
Clicked Allow Grant habackup.io permission for my Google Account
Then nothing happens??? Just sits there asking me to select an account again.
The logs don’t show any errors.
Help please
Hello @sabeechen,
I think I’ve spotted an inconsistency. In your message you mention 4 different folders, however this is what I see in the current Docuentation
exclude_folders: "homeassistant,ssl,share,addons/local,media"
I’m trying to find a way for motioneye recorded videos to not get in the way of my backups. I just can’t exclude the /share folder because there I have very valuable information, but if I could create a folder named media and store there all my recordings, I could simply exclude that folder.
I would appreciate it if you could shed some light on this. Any chance of at least excluding some filetypes like jpg and/or mp4?
thanks!
I’m running zigbee2mqtt addon. It is a key add-on for me. It uses /share folder to store relevant data. I just can’t exclude the whole folder. Any idea?