I’m probably going to jinx it, but I want to add that I’ve been running HA on the same SD card since early 2019, and no failures…yet.
As Russel points out, it’s writing to the database which will really tax your SD card. In the past few releases, the HA development team has made some dramatic improvements in the database design, and I think there are more to come. That should help.
But there’s a lot you can do right now to mitigate the problem. In configuration.yaml, manage your
recorder: section closely. I have mine set to:
I also ruthless
exclude entities from ever being recorded in the database. Others have gone farther and used the
include to only allow the few they want recorded, automatically excluding the rest.
Finally, I do no automatic backups. When I change something, I’ll copy the file I changed to another system. I regularly copy the entire
config folder to my NAS. I only use the HA backup function just before I do a version update, which I do about once a month. Even that is probably unnecessary, but it would make the restore a bit easier.
The reason for this is that the HA backup writes everything to the local drive, in my case the SD card. As you found out, the SD card probably won’t be available when restoring, so you need to copy it somewhere else anyway. I do have a Feature Request recommending the ability to back up directly to external storage, but I haven’t heard that it’s been considered yet. Feel free to up-vote if you think it’ll help you.