I’ve been trying to restore latest HA backup to new fresh install w/o success.
First problem was timeout during BU upload, timeout hit after 3minutes and couldn’t upload backup tar in that time (13GB)
After creating credentials and made first backup, it was able to upload backup file to folder and then system recognize BU properly.
When starting recovery process system requires key and after proper key system restart HA session and recovery message popup appear.
After 6+ hours nothing has happen yet, popup still appear, no changes to any files.
Backup is created in Hassio installation and recovery is going to container installation.
Any help is appreciated. All help to perform recovery using cli would be great
#Restore from backup doesn’t work
fickle spear
fickle spear
Update to issue. Restore does work if history data is excluded from backup
Backup tar file size without history is 612MB and with history 13GB
home-assistant db2 file size is 51GB and that seems to be an issue
zealous ether
You can try to follow the restore progress with ha supervisor logs -vf and ha core logs -vf via SSH or keyboard and monitor but that's an extremely large database. Maybe it runs out of memory or something. Did you modify purge_keep_days?
fickle spear
Yeah, I have 90d purge time, but made also lot of filters what reduce growing more
Anyways, I were able to restore system in 2 step. First create backup without history and recover that, second scp home-assistant_v2.db from old system to new
I still think there’s couple of bugs in backup-restore process
- timeout to upload backup tar is too short
- can’t restore backup with large db, popup message restoring system just keep rolling
Need to report them
zealous ether
You might want to think about changing that. I recommend the default of 10d unless you have a very good reason not to https://www.home-assistant.io/blog/2023/12/06/release-202312/#history-dashboard-showing-long-term-statistics
The backup system does indeed have a lot of flaws in my opinion.
fickle spear
Long term statistics was unuseable with raspberry pi4, but works well with this i5-7600T based mini PC.
I’m going to migrate it to external db
zealous ether
What do you mean unusable? I don't think it can be disabled. Maybe we're talking about different things.
fickle spear
It’s unuseable in that context that if you tap history or logbook tab, entire rpi freezes for several minutes when purge time is smth like 90d what I do have
zealous ether
LTS does not depend on the purge time as they are never removed and I recommended 10d 🙂
fickle spear
I’ll close this thread, thank you for support 👌🏼