I have filters on history and logbook in an attempt to keep DB size smaller, however it would be really useful if there was some sort of tooling which could be used to show what is consuming DB size.
I use the MariaDB and myphpadmin addons for this reason. It allows me to do deeper analysis into my db.
It would be goos to have some basic diagnostics for the built in db though.
Good point!
Another good tool would be breaking down the size of the snapshot.
I think most of my add-ons are pretty stable in that time, so I put the snapshot growth down to DB growth.
Also HA takes longer and longer to restart which I also attribute (equally without evidence) to DB growth.
Use the tar command to view the content of a given backup file.
tar -tvf somefile.tar
Below a screen capture of such a sequence. I was surprised to discover how large the backup of the AdGuard add-on was in particular. I removed that one from my backups as I have no need for those logs.
No idea why these are consuming so much space though.
Will uninstall the dev and beta, and do a reinstall of esphome, and see if tomorrows snapshot is smaller.
Thanks
Oh I know. Been there done that. The problem is the large number of small files each occupying a muinimum disk allocation unit. e.g.
I also worked out the automated partial snapshot: Automated snapshot optimisation but don;t use it any more. I use the [Smaba Backup Addon](http://Smaba Backup Addon) instead.
I’m a little confused. Do I run this as a call service from the python script documentation? What exactly will it output? I tried running it through SSH without luck.