-
-
Notifications
You must be signed in to change notification settings - Fork 198
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this Repo still actively supported? #1124
Comments
Check out HA 2025.1 which features new Backup functionality. I haven't tested this yet, but it seems this addon is no longer necessary. https://www.home-assistant.io/blog/2025/01/03/3-2-1-backup/ |
You might want to read the comments in the HA community forum first. There is a lot of unhappiness with the way it's executed... especially the encryption. Also the cloud backup offered by Nabu Casa only stores one version. |
Another concern I have with the way it's going is handing over backups to a cloud provider (nabu) not of my choice. Until they work the kinks out I don't think they should have pushed that new functionality in 2025.1 |
The new HA backup was designed to be extendable to other cloud systems and I saw that someone has already created an integration to Google Drive and is preparing the PR. |
I have forever used this add-on, and would like to take this opportunity of thanking @sabeechen for an absolutely excellent & robust add-on, in my opinion one of the best at least of those that I personally use. So a great thanks, & I sincerely hope his great work continues. I have also been contemplating how this add-on will continue to function after the 2025.1 update which incorporates its' own scheduling & encryption system. So far; I have not configured the new core backup features at all, & have still successfully managed to make a manual backup with the add-on, so I am guessing that the add-on's own scheduling will work as usual. My main concern is; if I do go ahead & setup the new core backup features (I don't really need/want the encryption but I would like the ability to have a synced copy on the Nabu Casa cloud), will this add-on still operate as usual on schedule? Also; will the backups still be pruned in the normal fashion? Will these backups now be encrypted? I'm not 100% sure this is the right place for raising these questions - so I will probably also post this on the HA core site. |
Encryption is mandatory at this point if you enable the new HA backup. |
So just to be clear, updating to 2025.01 will not effect our current backup workflow with this addon? |
I'm still wondering what will happen if I setup the backup with encryption (as is required AFAIK) what will happen to my regular scheduled GDBs; will they also start being encrypted? |
I have my doubts - but maybe you/someone can confirm after an actual test. I won't be configuring the core backup until I have firm evidence. |
I see your images, but have you already configured (encryption key etc.) in the new core backup in HA? |
of course as the new backup is a killer feature :) |
Soooo, as long as you don't enable it, you just continue on as normal? |
I've just checked my backup from overnight and it is not encrypted. I have not activated the new backup system - just Google Drive backup. What's not clear to me is that if I enable encryption in this back-up repo (ie set password), does it encrypt both local and Google Drive? |
no, you can enable it and use both in parallel without any problems. The Google Drive backups will continue to work as normal |
As soon as this lands in HA core this Addon is really not needed anymore (especially as it seems to be unmaintained anyhow): |
Thanks for this great info! I'm only hoping that they also allow in the new core backup system encryption/non-encryption by choice & also robust scheduling mechanism. This current add-on (GDB) allows an extremely versatile scheduling mechanism (which I use). I'm also hoping that the retention policy will also be configurable for the Google Drive - as this add-on is. |
@gfn256 read the announcements:
Encryption is now mandatory.
Yes, it does. In summary, there is likely no need for this add-on after home-assistant/core#134576 Even if sabeechen came back - what would this add-on do differently? I too enjoyed this add-on, but with the new core implementation, extending it with more capability would likely be a separate new add-on - not this one. |
My comments above were written AFTER reading the announcements (& updating).
Exactly why I requested the option be left to the user. (It could be defined as opt-out, but should definitely offer the option). You should read the various threads & posts from the past, of users trying to restore their systems with only encrypted backups. Also think of the scenario if one wants to just retrieve a small portion of a config file / automation etc. to copy to current setup.
So if I want to backup every three days at 2.00 am, I can do that? You can't - read the announcements. |
I'll continue to use Google Backup as long as it works or at least the following capabilities are implemented in HA backup:
Features I'd like to see in order of importance:
|
This is one thing I hope they will fix shortly. I have read the explanations, but the 4:45am time set is still odd to me. The fact that there is only one Nabu Casa backup is also a weakness that I hope they will fix. At the moment this repo is meeting all my backup needs and just works, so I see little incentive to use the HA version until it is more refined. I just don't know what they could add or how they can make it much better than this one.. |
I've just installed the latest HA patch. In the past I'm sure there was an option to do an HA OS back-up before installing these and the monthly update. There is nothing now. Am I dreaming that they have removed this backup feature before OS updates?? I'll just do a partial via this repo if that is the case. |
I wish you were! They have taken the decision to remove the backup before update option. I haven't yet discovered what the reasoning behind this decision is - but I'm pretty sure it is linked to the new encrypted-only policy. You can go to the HA blog to witness the steam being let off on this & the general new backup features. |
There is something worrying I've just thought of. It is possible that even if you continue to use this add-on (or a normal service call as outlined here) to carry on doing your backups un-encrypted, I'm not sure that the HA core is going to allow you to restore from them. This poster may be experiencing exactly this phenomenon. |
The main question of the thread has not been answered. And sadly it appears that the answer is "no". |
Have you tried restoring one of those unencrypted backups post |
I agree, the addon continues to work as intended, I didn't state otherwise. Yes I've tried restoring with an unencrypted backup and it works. In fact I reverted back to 2024.12 from 2025.1. |
But your 2024.12 backup was created prior 2025.1, therefore not a valid test. |
Have you tried it and it fails? I can't see a reason why. Anyway, I'm a little bit worried that the developer of this great add-on does not seem willing to maintain it any further. And for now this is my best option. |
Try this. Download a backup created on 2025.1 with Google Backup. |
I have already looked into that. All backups created by this add-on after 2025.1 are unencrypted and fully accessible. Unless the user opts to set a password in the settings and encrypt them. Otherwise they are unencrypted as before. |
@Tryfos give it up, those guys are really resistant to believe that the Google Addon still works 😂 |
What main maintenance does it require? What is the issue you think needs fixing? |
To answer the original question in this thread:
The short might be yes, though not because its abandoned and it isn't going to be dead soon. Its more in an indefinite maintenance mode. I intend to keep it "maintained" for as long as people are using it and HA doesn't change the API enough to render it inoperable. What that means in place of the new backup features in HA ... I'm not entirely sure. I share the frustration with how they've implemented the new backup features but its also obvious this is just their first pass and more changes are to come. I'll continue to keep this addon working as well as I can, but I can only "react" to changes they make. I go for long periods of time not answering issues because, honestly, I'm kind of sick of answering the same questions over and over. 95% of what people ask in this repo is answered by just reading the log output from HA and the supervisor in the issue they post. The error is right there in plain text, its why I added that bug reporting mechanism. I'm gonna lose it if I have to explain to someone again that the addon isn't "leaking CPU", you just have big backups that take a long time! That could probably be considered harsh or negligent on my part, but I just don't have the same kind of time I used to. I started this project while taking a break from work a few years ago, now I've got a full time job and some babies to care for so thats always going to come first. AFAIK the addon has a few uncommon (and hard to track down) bugs but is broadly speaking still fully functional, even with HA 2025.1. What I really do need to do in the next few weeks it comb through the 150+ issues in this repo and see if there is anythign actionable.
Thankfully thats what I've seen too. HA 2025.1 adds a lot of stuff to the native backup panel that makes it seem like backups are "always" encrypted, and in the blog post they even say |
Thanks for the reply. I didn't intend to sound hostile or unappreciative of your effort. |
Thanks @sabeechen Your work has saved me a lot of time and given me some assurance that I can’t/won’t lose the backups. I did buy you a coffee via PayPal - not much - but you will need all you can get with the babies! |
Everything said before - thx @sabeechen for that highly valueable add-on! |
No worries and I've taken no offense, given my silence its very reasonable to assume I'd died or something, thats my bad. I'll try to keep on top of new issues better for the near future, I think I'm going to:
If anyone knows of any "real" problems buried among my hunderds of open bugs, @sabeechen on it to draw my eye. |
I'll just say it one more time sabeechen - simply awesome! |
interesting sabeechen, i think your situ really mirrors a very common issue around open source projects i don't feel hopeful about open source in the long term, anecdotally there seems to be less and less of the newer younger generation taking up the open source mantel which is a shame as i would recommend to any up and coming talented youngster to stop paying for all these courses, actively involve themselves in this type of project, take over some of the responsibilities, eventually even fork it if needed with everyone's blessing the things they would learn over the period (not just programming but maintaining/interacting) would allow them to walk into jobs over those who have studied purely theoretically. So beginning their career path before it became time for them to have babies and pass on the mantel to someone younger :) |
It appears that a partial restore may not work. See here. |
in HA core 2025.2.0 there is a lot changed in the direction of backups, so maybe @sabeechen can retire from developing this addon and use the time for family caretaking. ❤ apart from that: thank you for your great work over the last years, it was more than one time I would be screwed without having your backup solution in place! just a short wrap up:
there is only one feature I use from this plugin here which is not on the HA side yet:
details can be found here. if you want to test it out, you need to wait for final 2025.2.0 release or switch to beta and follow this guide. |
I will now switch to Backup that is now part of HA core as it has achieved functional parity with Google Backup @sabeechen Thank you for your very nice backup for HA. |
Thank you @sabeechen for a great addition to HA. You saw an obvious hole in HA's functionality and took steps to remedy the situation. You've set the standard for what a good backup system should achieve. I'm sorry that the core developers didn't offer you a path for integration and instead felt the need to reinvent the wheel. NIH syndrome I guess. |
I haven't seen a lot of action by the repo owner @sabeechen in quite a while
Is this repo dying?
The text was updated successfully, but these errors were encountered: