-
Notifications
You must be signed in to change notification settings - Fork 602
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
Backup page listing empty when network storage is configured #4357
Comments
Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) backup documentation |
Same problem. 2023.7 |
I'm getting these errors in the log Logger: homeassistant.components.hassio Failed to to call /resolution/info - and Timeout on /resolution/info request |
I have discovered that if I reduce the number of backup files then it works. It appears as if the request to list backup files times out |
Having the same issue: Logger: homeassistant.components.hassio.handler Timeout on /backups/reload request |
Same problem here. The list of backup files in Home Assistant on my Fritz NAS is empty. Before it took a while for the files to show up. Please fix that bug. 🙏 |
I believe this is a duplicate issue here. |
I have a similar issue : the list is empty when the NAS is powered OFF; but the list is correctly displayed when it is ON. Home assistant : 2023.08.3 |
Same issue here. I can't see any backups in the HA backups page, even though the backup files are there on the CIFS share and get created by schedule. Log show the timeout messages for me as well: 2023-10-06 12:02:21.474 ERROR (MainThread) [homeassistant.components.hassio.handler] Timeout on /backups/reload request Home assistant : 2023.10.0 on rPi4 PS: After deleting old backups manually on the share (with now 19 files left) I can now see my backups again in HA as well. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
This is still an issue with latest versions. |
still an issue for me too |
I've started today using SMB for Backups. I ran into the same issue, but found an easy workouround which works for me. On empty backups menu I select "Upload Backups" then the windows file explorer opens, then i close it again without selecting any thing, 5 sec later my 40 backups appear in the list. |
Thanks for the workaround. Unfortunately does not work for me. I still see it empty. Not sure how is it working for you anyway, since I don't see any calls whatsoever in the websockets when doing that flow. The only way I see any websocket call is by using the reload option (or the first time I access the section). Ofc it never gets the expected response... all the responses I get after a reload are just from sensors and other HA related calls, nothing related to the backups. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
This is still an issue. Not stale. |
Still can‘t see my backups. |
Please fix this. |
+1 |
This is still an issue with latest versions. |
Just placing some links to relevant source code in case I or someone else picks this up. I asked again on Discord and no contributors have shown any interest. Proposed fixPreventing the error conditionWhen writing a backup
Follow-up enhancement
Recovering from the error condition
Follow-up enhancement
UI Fixes
Links to relevant code bits
supervisor/supervisor/mounts/mount.py Line 250 in 375789b
async def async_pre_backup(self, hass: HomeAssistant) -> None:
"""Perform operations before a backup starts."""
# We can likely do a check here to see if the directory is a mount, and whether the mount is in good status https://github.com/home-assistant/supervisor/tree/main/supervisor/mounts |
Architecture discussion on a proposed fixed to the Network Storage issues: |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
still an issue when lots of backups are present in the remote directory |
Same issue here. Wasn't a problem in the past, but since a few days. guess @ToXinE idea might be valid. Update: I had 25 Backups files on my shared network drive. In HA the Backup-list was empty. |
Haven‘t tested this myself yet but maybe it is better to use the advanced AUTO BACKUP integration from HACS to solve the problem? |
Yes, i do automatic backups - but using a custom script instead of the above integration. But in case you want to restore your backup, or just get an overview of existing backups, the list is useful. |
That's what I use and, as said by Florian in the previous message, doees not help/affect to the issue. |
Listing the files should be a very fast operation, but problem occurs because the backend needs to open each and every tar file and read the details to be able to return a complete list to the GUI. |
don't now if it helps. I had similar kind of symptom as described above. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
The problem still persists. |
I have this same problem, it renders backups invisible to users and makes recovery far more difficult that necessary. Can we not at least cache backups we know we made, and then test if they're still present only when they're accessed? |
The problem
I've added an CIFS/SMB share as a backup destination.
Server: hostname.example.com
Remote Share: share\folder
After doing so, the backup page no longer lists any backups, local or on the share. Creating a backup works (it's created on the share), but isn't listed.
What version of Home Assistant Core has the issue?
core-2023.6.0
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Backup
Link to integration documentation on our website
https://www.home-assistant.io/integrations/backup/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
Additional information
No response
The text was updated successfully, but these errors were encountered: