2025.1: Backing Up into 2025!

Tried that but no luck

There is. Join the beta team.
Settings ā†’ System ā†’ Updates ā†’ 3-dot menu ā†’ Join beta channel

Meh. I gave the exact same feedback related to encrypted backups during the Beta,
I was downvoted and ignored.

16 Likes

Ah 3rd time worked :slight_smile: Thnx!

Just to reiterate, if you are using any custom solution for backups (blueprints, automations, or add-ons that do not use encryption), they will continue to work today. Even with everything new, weā€™ve made sure to keep everything backward compatible.

As always, weā€™ll keep improving the functionality of automatic backups over the coming releases. As mentioned in our recent livestream, weā€™re looking at ways to decrypt your local automatic backups from the UI. This would be helpful if you needed to access the files in them. Hopefully, weā€™ll have more on that soon.

36 Likes

you are allowed to pay for more.
Isnā€™t it the main goal of this whole story?

Not sure where you got that idea. Thereā€™s only one price plan. Everyone is capped at 5gb.

1 Like
  1. At least weekly

  • I check backup file sizes at least weekly to ensure my database is behaving - especially when Iā€™m adding new integrations, devices, helpers, etc.
  • 2x per year I review the configurations of the automated backup scripts I use to ensure the daily partial backups I make (database and a few others) are properly excluding/including items and the weekly backups are indeed capturing the full system backup.
  • About 2x per year I extract the individual database to repair long-term stats that have gotten screwed up due to a device resetting and totalizers getting reset
  • About 1-2x per year to complete a full restore usually because of rollbacks on HA versions (1x/yr) OR because my database has become corrupted (<1x/yr). Sometimes entities break that I canā€™t fix manually, so itā€™s easier to rollback and wait for fixes.
  • About 2-6x per year to restore individual integrations.

Calling action ā€œbackup.createā€ from an automation does not work anymore, calling ā€œhassio.backup_fullā€ is a workaround on HAOS, but for obvious reasons not with a core installation in a python venv.

True and unfortunately. Usage of Discord is forbidden in the company I work for and their (used) CDNs are blocked as well on top.

On my system it is still working.

1 Like

I may have misunderstood and, since I havenā€™t updated to 2025.1, I canā€™t test but, when we update the core system or an add-on, does a backup still get made?

3 Likes

Do you think this capacity is enough for serious use?

You will see.

I mean, I use HASS seriously and my backups are less than a gigabyteā€¦

Itā€™s a very large amount. Iā€™m barely above 1gb with 4+ years of data and 40 days of retention.

Hmm, maybe I should look into cleaning it up a bit then but the size of mine has never ever been an issue until now.

Mine (5+ GB) is about 6 years old and has been ever-growing with automations, scripts, dashboards etc etc. Sure, I also have some long-term data stored in InfluxDB which probably increases the space a bit as time goes on but stillā€¦ I donā€™t view 5GB as that much considering all the information stored in HA. But considering everyone else seems to hover around a GB I should probably analyze what exactly takes up what amount of space and clean it.

As far as Iā€™m aware it does, but itā€™s encrypted.

1 Like

2nd day in a row failed upload to Nabu Casa cloud. My rclone to proton drive works without issue so no internet connection issues. Anyone else experiencing the same? Is the cloud simply overloaded? A manual backup works without issues, unfortunately nothing in the logs. How can we debug?

Thanks for the input. Glad to see youā€™re listening.

But why encrypt local backups at all?
Please inform us of the reasoning behind all of this. As has been requested multiple times here. That would help us all to understand and possibly stop the chatter regarding everybodyā€™s concerns.

There should be no need to have to decrypt a local backup. Itā€™s local.

And advocating custom solutions seems a strange thing when there is no official support.

15 Likes

Ironically, this latest release discourages people from participating in the beta.
Who in their right mind would want to be on the bleeding edge now thereā€™s an extra barrier to restore your backup should anything go wrong?

19 Likes

Tom, I refuse to believe you really think backups are the right solution for that one specific use case, one where a version control system would excel at. Can it be used that way? yes or course but in an extremely inefficient and limiting way, like driving an 18-wheeler to the corner store to get a pack of cigarettesā€¦

Like most people here, I donā€™t agree with this change. I donā€™t think forcing backup encryption is a good idea and I totally understand how the lack of a better solution in core pushed people to rely on backups for this.

That said, it is still confusing to see so many people using backups that way specially when its apparent most of these users are advanced users that should know better and implement a proper solution or at least be equally vocal in raising a WTH requesting a better solution to be included in core, long time agoā€¦

Should this change have been pushed without first providing such proper solution to these use cases? I donā€™t think so, but, my unencrypted Samba Backups are still being created every night just fineā€¦

2 Likes