Open rj45jack opened 10 months ago
Sorry this took me a while to get back to you. I'll be frank with you, the reason why is because I'm getting burnt out dealing with issues filed because of the new-ish network mount feature. Because there are so many different ways a mount can be configured and some many different ways it can fail the problems are all over the place. To make it worse Home Assistant provides almost no feedback when something goes wrong, it just prints out an opaque error error message burried in the supervisor logs. I've troubleshot at least dozens of these problems with users and so far its never been something wrong with the addon, not yet. Its demoralizing.
Anyway, thanks for listening to my rant. Lets figure this out. The way the addon works is once a second it checks if it should make a backup by checking what backups exist and then asking for a new one if there aren't any recently created. Based on your description what I'd guess is happening is that for some reason HA can't see the backups it just made, so when a new backup is complete the addon checks if any exist and requests another right away.
I'd try the following:
The reason this is a good test is because the HA is what actually creates/lists/deletes backups. The addon just asks HA to create backups when it needs one and asks it what backups already exist. I suspect the problem is that for some reason HA can't actually see the backups it creates on your mount.
I recently added a NFS share to HA to save my backups to. The NFS Share is remote and is connected over a dedicated site-to-site VPN via routers. Since using NFS I have had many issues with this add-on.
This add-on was working fine before I added the NFS share. Local saves were fine. Now I'm getting massive performance issues because the backups run all the time.
Help?