I agree with per location backup retention settings.
Cloud is set at 1 - that’s OK
System set with a small number due to limited system storage
NAS set with a much higher number or longer period of time
Also the option for long term retention. These are standard features with many backup programs.
Another complain about forced encrypted backups! 
I hope to see in next release option to disable encryption for local backups. I don’t care about cloud backups.
I’m glad that you flagged this. I have several climate-related automations that would immediately break because of this change. This (and encrypted backups) gives me another reason to sit this upgrade out for now.
I understand some of the rationale for this type of thing, but ‘minor’ renaming / case changing of attributes / service calls is the number one reason I’m upgrade hesitant and the primary driver of reverting / restoring from backups.
I fully agree that this should have the proper public warning period first.
Reading all that I’m very much worried regarding all the upgrades, which will come…
I’m using HomeAssistant two years now - it’s an awesome project and there are awesome people making all that happen. But some time I’m at least surprised …
I learnt a lot within recent two years - very fast I learnt not to hurry with updates, but starting very carefully reading all the messages. Today it did save me from surprises regarding the move to Zigbee2MQTT 2.0 but luckely the suggested solution in case of problems was already possible to find in the release notes.
However the upgrade to HA Core 2025.1 seems to become a real challenge. Not only the heavily discussed backup strategy (well intended but not so well introduced), but all the other surprises with custom components are scaring. I know, that there is a risk especially with HACS, but on other side many things till today are only possible using such solutions.
As a sample: I made a dedicated weather-dashboard for a wall mounted tablet, heavily using custom packages (custom:canvas-gauge-card; custom:config-template-card; custom:button-card; card_mod …)
There wouldn’t be any replacement in case of upgrade-caused problems. But how long such loved solution can stay at life? (I’m not a programmer!)
My lessons learned from today:
You just need to create a 3 lines script/automation, backup action is still working, they’ve only added more functionality to automate backups using UI and providing the basics for future improvements.
On the other hand, and as a Nabu Casa subscriptor, I have to thank about the free space for cloud backup. They’re are adding benefits for the same price, you have to like them… 
Maybe what they have to do is to silently announce new versions, until it’s stable for a full month or something like that, many people complain about things they don’t even have (because I assume they didn’t install the latest version).
Or just leave it as is, forum gets animated…
MY HACS integration broke from this update. Not just integrations from HACS. After reloading the HACS integration that started working again (earlier reboots didn’t bring it back), but now HACS shows zero downloaded/installed integrations. I have a lot, and some of them still seem to exist within HA itself, but HACS doesn’t see them. One that was completely broken was mushroom cards, which I now reinstalled.
If I go to HACS it thinks HACS and Mushroom cards are the only integrations I’ve installed through there. That’s way off.
Well, I have to use a workaround now instead of perfectly working good old manual backups from the UI.
I just gonna wait for the next release, I still have my old backups from the last year around 
I think it was a big mistake to force encrypted backups.
OMG, I’ve planned to open an issue, but this is intentional???
Can’t beleive anybody on Earth thought this is a good idea. 
I’m glad to see I’m not the only one who thinks it is ridiculous to have encrypted backups without decryption tool. It really clashes with the open mindset of HA.
Don’t get me wrong, I’m all for encrypted backups. Even if it was for local. But a big (the biggest?) protection of the backup is from myself! It is when I make an edit to a dashboard or automation that I should not have done. And for that I want to restore that (or retrieve a part) and not a complete HA install including database en LTS.
So yeayyy encryption. But booooooooooo locking the files away… 
Is there a sensor for the new backups? I’d love to be able to use it on my dash to see the last time backed up, for example.
Correct.<>
Victron integration stopped working after the update
Setup failed for custom integration ‘victron’: Unable to import component: No module named ‘pymodbus.register_read_message’
Traceback (most recent call last):
File “/usr/src/homeassistant/homeassistant/setup.py”, line 334, in _async_setup_component
component = await integration.async_get_component()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/src/homeassistant/homeassistant/loader.py”, line 1035, in async_get_component
self._component_future.result()
File “/usr/src/homeassistant/homeassistant/loader.py”, line 1015, in async_get_component
comp = await self.hass.async_add_import_executor_job(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^That is a custom integration. Go to it’s GitHub page and post an issue (or contribute to an existing one of there is one)
Edit: there are at least 2 issues there with a solution, go read 
That looks awesome,its a really a needed feature to be added to the core and i 
it.
One missing thing from my perspective that i would personally need.
An option to keep some of backups indefinitely. I’m really reserved to migrate from the google backup addon to the new backup system due this missing feature.
I don’t want to wake up one day realizing that my 3backups (done daily) overwrote all “good” backups and now something is not working as it should because i’ve didn’t noticed in time.
For sure it can be handled offline by downloading the “good” backup for safe keeping, but that’s an extra job not willing to do.
Please consider this functionality as i see it mandatory
Is that lovely dashboard documented somewhere?
For whatever reason, the backup to samba share on NAS never finishes… keeps the message “Creating backup” spinning forever iven if the file is successfully uploaded to NAS? Anyone else experiencing the same issue?
Absolutely agree with per location retention settings. Also seems to be restricted to max of 50 days. Why impose this restriction? It seems arbitrary
It would be good to allow similar retention to ZFS auto snapshot. Keep daily backups for X days, keep a weekly backup for X weeks, etc.
Also not sure if there is a bug in the setup wizard. The retention settings I selected seem to be ignored (maybe because they were considered invalid?), and it instead defaulted to last 3 backups. Thankfully my backups weren’t cleaned (and they are already in snapshots and offsite anyway).
This is an awesome feature though, and throwing in cloud storage for Nabu Casa subscribers is amazing!
Edit: My first automatic backup to Nabu Casa failed. Doesn’t seem to be anything in the logs as to why. Backup to local and network share worked fine so not too much of an issue (I still have 3-2-1 by other means). Would be good to have a way to copy an existing backup to other locations though (i.e. retry upload to Nabu Casa). Seems that would require a new backup atm.
That is not a home assistant core integration, go to GitHub and create an issue,
Internal network: Different local IP addresses, example (not my real IPs, but as you can guess from my post above I wouldn’t care if you knew what it really was!) HA1:192.168.10.10, HA2:192.168.10.20 both on port 8123. I have a router/firewall that has ability to do NAT with PAT, so external ip is for example X.X.X.X:8123 for HA1 and X.X.X.X:8124 for HA2 and the firewall rule is to destination NAT 8123 to internal IP 192.168.10.10:8123 and NAT 8124 to internal IP 192.168.10.20:8123 (not a typo). On the internal network you can manage HA1 or HA2 based on different IP address (and same port), if trying to get in from the internet to manage it is the same IP address (of the router) but port 8123 for primary and port 8124 for backup. All sensors are on local network and most are command line “pulls” from the HA, so both servers sit there polling data happily all day long, and one (or the other) is responsible for automations. If for some reason you manually change a state (example manually turn on a light), then a command is sent by whichever server you were on and the state of the switch is then read back as command line sensor on both server indicating current (new) state on next poll interval. This works great day to day. The only pain is the upgrade/backup process which is more completely described as 1) HA1 backup pre-upgrade or changes, 2) upgrade HA1 (or run lets encrypt renewal, which also requires opening port 80 on the firewall usually to the primary HA), 3) run backup on HA1 again (post upgrade), 4) run restore of new HA1 backup onto HA2, 5) go into HA2 and turn off all automations. It can take a little time but I have once or twice had an HA1 hang or die and was really happy to just login, flip on automations for HA2 and then I could get to fixing HA1 at my leisure without any real downtime/gaps in the system.
I think you may have misunderstood the comment.
He was agreeing with you. He merely stated this thread was flooded with the back-up issues and your comment was as important but drowned.