eduardogsilva
commented
4 months ago Hi @hellofaduck I just replicated what you reported.
- If you delete a backup before it completes or before the max retry exhausts, the backup lock will not be removed from that router. It's a bug. I will fix this as soon as possible.
When your backup fails, it schedule a retry to run in a few minutes. I believe that the default max retry count is 3 and the retry interval is 30 minutes. You can check this information in the backup profile. Open your backup details, and you will see this data in the debug information (fields with a question mark in front). The backup will keep trying until it reaches the max retry count. In this same screen, you can also check when the next retry will happen.
While the backup is not explicit marked as "error" it will be considered in queue and will keep trying until max retry is reached.
Regarding the monitoring: routerfleet It's not intended to be a NMS. The monitoring function is designed only to prevent spending time trying to reach devices that are unavailable, also, this setting reduces the chances of skipping a backup due to network issues, since the retry count will not be increased until the router come back online.
If your router is intentionally not responding to ping, just uncheck the monitoring option and the backups will be executed without checking if the host is online.
The monitoring feature here, is part of my plan to support a large amount of routers.
You did a great job, I see a lot of potential in this project! I noticed a couple of problems and have a couple of thoughts on how to improve the project. When I run a backup by force and it fails, I remove the cause and want to run it again manually to check, now it is not possible, it is not convenient. Moreover, if I delete the current backup and it disappears from all pages in the Backup section, it is impossible to make a new forced backup, it is blocked, only a complete deletion and adding the router again helps. And it seemed to me that the backup does not start until the router is not visible for monitoring, this is also not correct, access for ping is often closed, and backups should be done anyway.... Thanks for your work an time!