jmealo
January 31, 2024, 5:27pm
1
If Network Storage is unavailable when a backup is created, the backups will be written to the local mount point and prevent network storage from ever being mounted again. There are other related issues and bugs that stem from the first-pass/rough implementation of Network Storage.
A change in behavior to write locally and copy/sync backups rather than write directly to network storage would address all reported issues.
A good first step would be adding the fallback behavior. Follow-up enhancement would be the copy/sync to remote storage (cloud or network).
Meta issue tracking many reported GitHub issues related to this:
opened 01:10AM - 27 Dec 23 UTC
### The problem
**There are a number of related issues with network storage b… ackups that can cause data loss and inflict great pain on users. This issue will require multiple fixes and improvements to fully address.**
# Technical issues:
- Not reconnecting after a power loss, where home assistant boots prior to network server.
- No backups being shown when the network mount fails to re-establish.
- No easy way to rectify the failure condition from inside of HA, especially if running inside of a VM.
# UX issues:
- Backups aren’t occurring as configured.
- The errors and notices that appear are not helpful.
- Past backups “disappear” when the network mount cannot reconnect.
- Not enough contextual information in the backups page when there is a network issue.
- No backup/fallback (local) backups when the network mount fails.
# Data loss issues
- A previously "correctly" configured backup setup stops working without any configuration changes being made, a power cycle is enough.
# Opportunities for improvement
- Offer Cloud-based backup options
- Offer retries/async uploading of backups to remote storage
- Offer a fallback/offline storage location in the event that the main/remote storage location fails
# GitHub issues:
- https://github.com/home-assistant/core/issues/103907
- https://github.com/home-assistant/core/issues/103796
- https://github.com/home-assistant/core/issues/103652
- https://github.com/home-assistant/core/issues/102009
- https://github.com/home-assistant/core/issues/100560
- https://github.com/home-assistant/core/issues/99551
- https://github.com/home-assistant/supervisor/issues/4662
- https://github.com/home-assistant/supervisor/issues/4643
- https://github.com/home-assistant/supervisor/issues/4577
- https://github.com/home-assistant/supervisor/issues/4473
- https://github.com/home-assistant/supervisor/issues/4357
- https://github.com/home-assistant/supervisor/issues/4358
- https://github.com/home-assistant/supervisor/issues/4789
### What version of Home Assistant Core has the issue?
All
### What was the last working version of Home Assistant Core?
Never
### What type of installation are you running?
Home Assistant OS
### Integration causing the issue
_No response_
### Link to integration documentation on our website
_No response_
### Diagnostics information
_No response_
### Example YAML snippet
_No response_
### Anything in the logs that might be useful for us?
_No response_
### Additional information
_No response_
Related architecture discussion: