Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addon Ignores Schedule and Other settings #982

Open
rj45jack opened this issue Jan 30, 2024 · 1 comment
Open

Addon Ignores Schedule and Other settings #982

rj45jack opened this issue Jan 30, 2024 · 1 comment

Comments

@rj45jack
Copy link

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.

  • No matter what I set the schedule to, it will just run whenever it feels like it. If I stop/start the addon it will run a backup within 10 minutes.
  • The Interval is once a day, it will run multiple times a day.
  • I want to have 3 NFS backups and 1 Google Drive. Nothing is being uploaded.

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?

@sabeechen
Copy link
Owner

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:

  • Turn off the addon if its still on.
  • Create a new small partial backup (so it completes fast) in Home Assistant UI ("Settings" > "System" > "Backups"). After it finishes, click "..." > "Refresh" and double check that the new backup shows up. If that fails there is something wrong with your NFS configuration.
  • Right after creating a backup and/or refreshing the list, monitor the supervisor logs for errors.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants