My database size it 827.15 MB, i use autobackup to keep track of the snapshots.
Your screenshot of snapshot seems like how it should work instead of mine,
which the backup folder another backup folder which loop for a ridiculous amount of time ( as shown below) and eat up a large amount of storage
Thatâs pretty broken, not sure how you got all those subdirectories, but there should only be *.tar files in the root /backup directory.
I donât see any issue with your configuration.
I think itâs quite weird that every subdirectory is the same and that it appears to go on forever, so my guess is actually that somehow a directory junction (or hard link) has been used to create a loop. That is that /backup/backup actually links to /backup but the OS doesnât perceive it that way and so it appears as infinite subdirectories.
To check this open the windows command prompt in the /backup directory and run the command dir, you looking for something saying <JUNCTION>.
You can try deleting anything that is not a *.tar file in the root /backup directory, and see if the problem persists (i.e. itâs still creating subfolders). Itâs also worth checking the home assistant logs and supervisor logs around the time you take a snapshot. Are you running any other backup utilities that may be conflicting?
Great! so it was a circular link on the linux side, itâs weird that was even created, it couldnât have been home assistant or any of its components, as they donât have access to the /backup folder, so maybe the supervisor or an addon caused it.
Now I have another issue, after deleting the backup folders,
Supervisor > Snapshot still show there are 3 snapshots but in backup directory thereâs only 1
Auto Backup shows a snapshot as monitored until it expires even if itâs deleted externally, you could manually edit/delete the file under /config/.storage/auto_backup.snapshot_expiry and restart.
As for the supervisor it creates the list of snapshots by reading from the /backup directory. There should be a reload button in the top right corner, otherwise a restart should fix it.
@kavierkoo I had a similar problem recently but it was with my config folder. I only discovered it after the Visual Studio Code plugin started pegging my i5 NUC CPU useage at 100%. Turned out that it was disappearing down the infinite plughole of the config folder enumerating files as it went! I couldnât get rm -rf to remove the link, so I exported a backup and used 7-zip to delete it. Once I did a wipe & restore, it was fine.
However, on checking today I find that my backup folder has the same problem as you, but this time the rm -rf worked, but it is a strange problem!
@sota yea lol⌠When I run hassio directly on Ubuntu, I never have this issue,
It only happen after I dockerize itâŚ
Are you running on linux? or Docker?
Letâs see if we have any similarity here.
Iâm running it on Docker, and Addons are:
AdGuard Home
SSH & Web Terminal
Samba Share
HACS
Auto Backup
and few of frontend cards.
I use automation to snapshot daily 5 AM and keep for 7 days, and uses auto backup more insight info.
Iâm running HA Supervised under Ubuntu Server 18.04 along with about 10 or 12 other containers under docker compose.
I noticed the problem because the NUCs fan was running flat-out after installing VS Code. Other than that, I have:
Appdaemon 4
ESPHome
Google Drive Backup which runs every night
Letâs Encrypt
MariaDB
Mosquitto Broker
Node-Red
SSH & Web Terminal
Samba
Zigbee2mqtt
I suspect that file corruption may be at the root of the problem. However, itâs almost impossible to prove so I guess Iâll just keep an eye on it for now. I am planning to move to Proxmox, so this may force me to get on with it.
Hmm, the common thing I guess was we both running HA Supervised with Docker on the same OS and version too.
and yea, we can only monitor it for now. Good info about Proxmox⌠but I think the dashboard not as elegant compare to HA (just my opinion)⌠I do use Netdata and customize my own small dashboard to monitor my webserver tho.
This all started when I moved from Synology HA native to HassIO VM image. I simply created an OLD dir in each directory and moved the symbolic link into the newly created OLD dir and rebooted. Seeing how this works.
I also had this issue with the config folder (i think i after migration from hassio package on Docker to synology VM) I am no expert at all, so forgive me if i am saying that doesnât make sense. (or has been said already) But maybe these simple steps can help someone with the same issue:
open The Web UI of the âTerminal & SSHâ add-on-
navigate to folder by typing âcd configâ
then type âunlink configâ
Done
it seemed solved after navigating to the folder in