Fix corrupted / malformed SQLite database (home-assistant_v2.db)

[e-raser]

Great news

As confirmed in

WTH: Finally reliable, restorable backups by not corrupting the default recorder database (SQLite) during backup creation anymore

They were both merged 10 months ago… I guess if you’re not aware, if something is merged then it is included in next major release. So in this case that was 2022.2.0 (and obviously every release after that). Sometimes commits are cherry picked into a patch release of the previous major version. One of those has the cherry picked tag so it actually came out even before 2022.2, was in one of the patches of 2021.12

the two fixes taking care SQLite database is not being corrupted during the backup process (Allow to lock SQLite database during backup by agners · Pull Request #60874 · home-assistant/core · GitHub and Refactor recorder queue handling by emontnemery · Pull Request #61161 · home-assistant/core · GitHub) have been merged already a long time ago, roughly around February 2022.

…which is the final confirmation of my experience of restoring a backup without having a corrupted database back in July this year (Fix corrupted / malformed SQLite database (home-assistant_v2.db) - #23 by e-raser).

Really wondering if I missed that in the release notes or if they just shipped it silently (why not promoting this fix as it is really really REALLY great news?!?).

• I’m gonna mark this post as “solution” (as it prevents databases getting corrupted during backup creation) even this topic is about fixing a corrupt database, no matter how that happened.
• Those options can be found in the original post @ Fix corrupted / malformed SQLite database (home-assistant_v2.db).