Restore 2026.2 --> 2026.1.3 lost backup to local storage --> error

[afkdk]

The problem

After I lost 130+ automations in the upgrade from 2026.1.3 to 2026.2.1 - and I could not see what/how/where to get them back, I restored the Home Assistant automatic update backup (via HA GUI) in hope to get them back.

I lost (of course but sad loss of time) the 5+ hours of work on changing/improving the automations since the upgrade took place but I also observed that I lost some connections to cloud integrations but that was fixed by re-authenticating them...

BUT after a reboot, I seem also to have lost the "local storage option".
More precisely HA complained about a backup error - and that was the This system that was pinpointed.
I checked Storage - and the Backup categori was there (containing 45GB of backups) but I saw now immediate means to "restore it" - only the Garbage can to get rid of it.

So I did; pressed the can icon and the error went away. But now I wanted it back - both to get the old backup links restored but also to get the upcoming backup working again on This machine.

BUT I see no means/way to get this back. I tried to Create manual backup but only the other (three) remote locations are seen - and no way in Storage section to set it up.

Checked with AI - and yes, it don't know everything (far from it) but it states that it is a known bug but I cannot find it (besides som old bug in 2025.1 that has been closed). Neither in this stack of current issues is it found - or at least I cannot locate it...

HELP - bug or way to get it back...?

What version of Home Assistant Core has the issue?

System Information version | core-2026.1.3 -- | -- installation_type | Home Assistant OS dev | false hassio | true docker | true container_arch | amd64 user | root virtualenv | false python_version | 3.13.11 os_name | Linux os_version | 6.12.51-haos arch | x86_64 timezone | Europe/Copenhagen config_dir | /config

Home Assistant Community Store

GitHub API | ok -- | -- GitHub Content | ok GitHub Web | ok HACS Data | ok GitHub API Calls Remaining | 4978 Installed Version | 2.0.5 Stage | running Available Repositories | 2738 Downloaded Repositories | 52

Solcast Solar

can_reach_server | ok -- | --

Home Assistant Cloud

logged_in | true -- | -- subscription_expiration | August 23, 2026 at 02:00 relayer_connected | true relayer_region | eu-central-1 remote_enabled | true remote_connected | true alexa_enabled | false google_enabled | false cloud_ice_servers_enabled | true remote_server | eu-central-1-7.ui.nabu.casa certificate_status | ready instance_id | bbd45b0733294d3e85c3a69d0ce141ef can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok

Home Assistant Supervisor

host_os | Home Assistant OS 16.3 -- | -- update_channel | stable supervisor_version | supervisor-2026.02.1 agent_version | 1.7.2 docker_version | 28.3.3 disk_total | 295.3 GB disk_used | 85.1 GB nameservers | 10.10.10.1 healthy | true supported | true host_connectivity | true supervisor_connectivity | true ntp_synchronized | true virtualization | kvm board | ova supervisor_api | ok version_api | ok installed_addons | Studio Code Server (6.0.1), Samba share (12.5.4), Home Assistant Google Drive Backup (0.112.1), MariaDB (2.7.2), Advanced SSH & Web Terminal (23.0.2), Mosquitto broker (6.5.2), UniFi Network Application (5.0.0), Zigbee2MQTT (2.8.0-1), Ring-MQTT with Video Streaming (5.9.2), ecowitt2mqtt (2024.10.0), File editor (5.8.0), TubesZB Zigpy-CLI Tools (0.5.1.2), Matter Server (8.2.2), Network UPS Tools (0.17.0), ESPHome Device Builder (2026.1.4), DbStats (0.5.12), Get HACS (1.3.1), Log Viewer (0.17.1), Automation Inspector (0.4.3), Music Assistant (2.7.6), Home Assistant Time Machine (2.2.0), MQTT Explorer (browser-1.0.3)

Dashboards

dashboards | 35 -- | -- resources | 54 views | 33 mode | storage

Network Configuration

adapters | lo (disabled), enp6s18 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth3ca1c86 (disabled), veth145b5e9 (disabled), veth30cda0c (disabled), veth7369b16 (disabled), veth2908117 (disabled), veth69fbdb8 (disabled), veth6c747c2 (disabled), veth9e6f64b (disabled), vetha5adf90 (disabled), veth196a82e (disabled), vethaa935b9 (disabled), veth2cf0bbc (disabled), veth580efff (disabled), veth701e7bc (disabled), veth3b6d2f1 (disabled), veth27977f8 (disabled), vethfedbdba (disabled) -- | -- ipv4_addresses | lo (127.0.0.1/8), enp6s18 (10.10.10.206/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth3ca1c86 (), veth145b5e9 (), veth30cda0c (), veth7369b16 (), veth2908117 (), veth69fbdb8 (), veth6c747c2 (), veth9e6f64b (), vetha5adf90 (), veth196a82e (), vethaa935b9 (), veth2cf0bbc (), veth580efff (), veth701e7bc (), veth3b6d2f1 (), veth27977f8 (), vethfedbdba () ipv6_addresses | lo (::1/128), enp6s18 (fd1c:c65f:b90c:a678:ddb7:1b76:4b9:b283/64, fe80::3982:91dc:8971:a73b/64), docker0 (fe80::8c0b:e3ff:fe08:d073/64), hassio (fe80::88d:54ff:fe55:80d5/64), veth3ca1c86 (fe80::1087:8cff:fe8b:e8e1/64), veth145b5e9 (fe80::c27:56ff:fec5:b023/64), veth30cda0c (fe80::b8dc:73ff:fe86:ef9e/64), veth7369b16 (fe80::ecf6:fdff:fe85:2d0d/64), veth2908117 (fe80::3ced:74ff:fef1:f792/64), veth69fbdb8 (fe80::54f2:38ff:fe5e:3f16/64), veth6c747c2 (fe80::7c93:69ff:fe2b:8547/64), veth9e6f64b (fe80::98ce:efff:fec6:eb2/64), vetha5adf90 (fe80::c41b:a9ff:fe06:7ff9/64), veth196a82e (fe80::58b3:7dff:fe95:576e/64), vethaa935b9 (fe80::a8a1:f1ff:fe4b:7a57/64), veth2cf0bbc (fe80::5c67:a1ff:fe20:7c43/64), veth580efff (fe80::4022:c3ff:fe82:f822/64), veth701e7bc (fe80::10f0:bdff:fecd:5328/64), veth3b6d2f1 (fe80::3cf6:d3ff:fe94:3d2a/64), veth27977f8 (fe80::f44c:a1ff:fe5c:16b1/64), vethfedbdba (fe80::84d3:1eff:fe31:9e4/64) announce_addresses | 10.10.10.206, fd1c:c65f:b90c:a678:ddb7:1b76:4b9:b283, fe80::3982:91dc:8971:a73b

Recorder

oldest_recorder_run | January 24, 2026 at 23:09 -- | -- current_recorder_run | February 9, 2026 at 22:40 estimated_db_size | 10590.73 MiB database_engine | mysql database_version | 10.11.6

Sonoff

version | 3.9.3 (7c75c46) -- | -- cloud_online | 0 / 1 local_online | 0 / 0

What was the last working version of Home Assistant Core?

2026.1.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Backup (core feature, I believe)

Link to integration documentation on our website

No response

Diagnostics information

Not sure where/how to find it for the core

Example YAML snippet

Anything in the logs that might be useful for us?

Searched for backup in the core log:

2026-02-09 22:40:32.660 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved (task: None)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/backup/manager.py", line 458, in _async_reload_backup_agents
    agents = await platform.async_get_backup_agents(self.hass)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/hassio/backup.py", line 78, in async_get_backup_agents
    mounts = await client.mounts.info()
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohasupervisor/mounts.py", line 12, in info
    result = await self._client.get("mounts")
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.13/site-packages/aiohasupervisor/client.py", line 170, in get
    return await self._request(
           ^^^^^^^^^^^^^^^^^^^^
    ...<5 lines>...
    )
    ^
  File "/usr/local/lib/python3.13/site-packages/aiohasupervisor/client.py", line 136, in _request
    await self._raise_on_status(response)
  File "/usr/local/lib/python3.13/site-packages/aiohasupervisor/client.py", line 79, in _raise_on_status
    raise exc_type(
    ...<3 lines>...
    )
aiohasupervisor.exceptions.SupervisorBadRequestError: System is not ready with state: setup

-------

Additional information

As stated, I restored 2026.1.3 backup after failed upgrade to 2026.2.1 so this issue may be one of many...
But right now, this is worrying me the most!

[home-assistant]

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (backup) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of backup can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign backup Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@afkdk Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20backup%22%20
_{^{(message by IssueContext)}}

---

backup documentation
backup source
_{^{(message by IssueLinks)}}

[afkdk]

The problem breanches into actual backup issues as ESPHome cannot back up before updating - it seems still to have a link to this local backup that I CANNOT create again - or at least not find out how to do it (via UI...)

[MartinHjelmare]

Your system doesn't seem to be in a good state, if the local file system can't be used for backups.

Check the Supervisor logs for errors.

[afkdk]

This (closed) issue has some resemblance: #140511
I will add the suggested increased log level and see if it brings better light into the issue...

[afkdk]

I have now checked the log - no warnings related to Backup besides som tar-files that seem to have been cut off...

BUT much to my surprise, the 3+ days after (after this Restart derived from the logger addition to Configution), I checked Backup Locations again - and MUCH to my surprise (despite that I have restarted several times after discovering the issue but not in the last couple of day): The local location has appeared again so I enabled it!

The location "This system" has risen from the dead and seems to be active :-)

Still a "wonder why" issue spotted: I got this config for This system:

BUT I got this observation when I listed the manual backups (that somehow has continued to work 🤯)

That may originate from another issue so I will lay it to rest for now...

MOST IMPORTANTLY: It seems now to be back on track including the local backup:

[afkdk]

...and just checked the newly run backup and THAT seems fully encrypted so it make be confident in the backup is back on track!

GREAT!

[MartinHjelmare]

Great that it's back on track. Can we close here?

[afkdk]

There is/was an error but I have moved on so I am closing it upon your request to reduce the clutter, maybe if I am/wad the only one that was trapped by this ...