The 'official' way

I get your point on this. I have always used SSH—>WinSCP—> Copy backup to folder… to get my backups in.

There is a Download snapshot function, the solution is to make an upload snapshot button. Problem solved.

1 Like

@anon43302295.
See. I told you to carry on. I knew someone else would get it sooner or later :sunglasses:

1 Like

I think a simple “browse” would suffice. Click browse, select folder, loaded snapshots update to show currently browsed folders. Also, this could be a good avenue to start allowing backups to happen ANYWHERE on your network.

1 Like

Yes, that is what I was inferring. It would make things very easy.

Something in this area

4 Likes

GO +1

3 Likes

yes tht seems a good logical aera to add it but i would add the same option at setup time

as i said earlier when the setup ask to create the first username:

4 Likes

Totally agree with you there, it seems so obvious that I don’t understand why it’s not there already. Snapshots have been around for a really long time now.

To play devil’s advocate maybe it’s not that easy so it can’t be added for another six months, that’s fine, but then don’t deprecate the ability to have complete control of the system so that people can scp it across during the setup process until after the six months :slightly_smiling_face:

having experienced the restore process over the weekend I now realise that the whole concept is somewhat half-baked. It appears that a lot of effort has gone into the development of a process to create the backup, but restoring it is a completely different story.

I was able to get over the issue of uploading the backup using the SAMBA addon (although I did discover that I had to allow my IP range), once you start a restore its like sending Major Tom to the dark side of the moon, you get no feedback as to where the restore is up to.

It was a completely unnerving experience that ultimately for me ended in failure, it also makes me question the value of the backups when I can achieve a much faster and reliable re-setup using my own config backup and a little bit of time setting up the addons I need, not to mention that because HassOS can’t currently mount external resources (like my NAS) I now need to revisit my backup situation to make sure the backups are actually relocated off the device

1 Like

Yeah I totally agree. You only know something has happened when it restarts home assistant after completing the restore. It takes a lot longer than you expect it to as well and I think sometimes people think it’s not doing anything and restart. I have restored snapshots a heap of times without failures. I also use the Dropbox addon and there is a gdrive one as well.

Once you learn that the files are literally just zip files, it becomes really clear how to restore without home assistant doing it for you. Unzip, find the config direction inside the zip, drag and replace all files.

I’d hope that my failure is not a reflection of the product, rather an issue related to my setup

Yeah - i’ll need to look into the options - it would be nice to be able to get it into my existing local backup ecosystem as well

I done the same today. Out of the box Samba didn’t work however I changed the work group and pressed save, and it appeared to work. Allowed me to upload my snapshot to the backup folder

1 Like

Did the same thing yesterday (installing vanilla HassOS onto a pi4), and the Samba addon worked out of the box after setting up credentials in the config. I was immediately able to copy over files, snapshots, etc.

The fact that this thread is 54 posts long proves @anon43302295’s point.

2 Likes

Sounds like a good ole feature request. Although I don’t really agree with it being at the login screen.

image

Promotion?
Nice one!

Indeed. By a surprising aspect too.

Is joining the dark side a promotion? :stuck_out_tongue_closed_eyes:

2 Likes

I guess so? Depends on how you look at it :rofl:

Join me luke

1 Like