Backup is growing rapidly without a special reason - from 2 to 4.1GB in 12 days

Configuration
,
1

It seems like the generated tar archives (full backup) grow a lot recently without me having done to my HA setup. From what was “once upon a time” 700MB on average the files grew to 2GB 12 days ago and 4.1GB yesterday.

Somehow I lack a tool to analyze the backup properly, so I can tell only the obvious differences of the files. So far I found out by opening the generated tar file that the contained file core_mariadb.tar.gz is causing most of the growth. I found found out that data/databases/homeassistant/states.ibd is now 12410MB big compared to 4700MB 12 days ago.

I had an idea that the recorded camera streams are stored in HA. But I set up my Reoling to record to SD card. Nothing altered in HA. So no clue again…
Can anybody help tell me how to find out what is causing the growth?

My setup: I use a supervised HA setup with HA and ESPHome and everything else updated to the latest version. The HA Google Drive Backup addon is working fine. Recently though I was told by the addon that my Google drive cannot hold the 5th backup.

2

MariaDB is your recorder and the typical cause is a sensor that reports lots of different values or maybe even unique values, like timestamps.

Check and control your recorder settings.

1 Like
3

See also: How to keep your recorder database size under control

4

I changed no recorder setting. The kind of major change was that I deleted three or so ESPHome devices and got different entity names. As far as I was told this name change does not matter as the entity id is used in the database .

Is there any way to access and analyse the MariaDb database within the backup?

5

I think the entity name is the entity id.
Friendly name is not the entity id though.

6

Also there is two purge functions to delete data from the database