Full Snapshots missing loads of files

This is still happening. I’m fairly new to HA and I screwed up my automations.yaml that caused my HA instance to not start up… Long story short, I have the google drive auto-backup add-on and all of those backups were incomplete. Luckily I had one I’d done manually (albeit days earlier) that I was able to recover most of my work.

@seanomat, @jdbrookes, @Arjen_W have you guys had any issues since you moved the db to shared? Also, is recorder the only integration responsible for writing to the db? On its info page, it says:

The recorder integration is responsible for storing details in a database, which then are handled by the history integration.

Does this mean we also need to let history know about the db file’s new location? It doesn’t seem to me that this is necessary, but since I’ve really only been playing around with Home Assistant for a month, I’m scare to just move the db, plus I’ve been collecting utility_meter data and would hate to lose that history.

I don’t have any issues after moving the DB location. Also upgrading to version0.112 went fluidly.
I only changed the settings as described above, no other setting changes were needed.
I must say that I hardly use the history tab at all, so I have no idea if that is working as it should be, but I do believe that it works as expected

Yes the backups are now working correctly, I’ve inspected a few and found all of the yaml intact. The database file also seems to be intact in it’s own folder but I don’t know for sure that this is backed up correctly as I haven’t needed to restore a snapshot.

Yes, moving the database is a working workaround.
All other integrations use recorder so no need to change the database location anywhere else.

@Arjen_W, I agree with your suggestion to comment on the Github issue as a way to get the attention of the devs, but I’m having trouble finding the issue! Could you possibly post a link please?
TIA.

Did this get fixed in the new release of the supervisor?

I don’t know. As my config still contains the workaround, I haven’t tried to check it again without the workaround in place.
@AndrewJ: sorry for not reacting earlier, was kinda busy. There were some issues logged, but I think those were all closed by a remark that it was due to Supervisor. I thing the issue that @CaliKev linked is the most important one, but the issue might already been solved.

Hello everyone! Is anyone else having problems with snapshots? All of mine, both complete and partial, are corrupted. Does anyone have any solution!. Thank you. snapshot|690x487

did you find any solution for this. I am having this problem not just in automation but also in normal UI

No, as a workaround I backup the config folder complete not just the snapshot.

As I use a Synology NAS it was just another backup task.