It would be helpful if Vykar provides a counter for consecutive errors/ failed backups on a per-repository basis.
This would allow e.g. to build hooks that notify users only after a certain amount of errors/ failed backups.
Use case:
- scheduled weekly/ daily/ hourly backups
- a certain amount of failures is expected - but not considered as a problem
- e.g. temporary failure of backups due to network problems
- e.g. temporary failure due to server/ maintenance
- e.g. removable disk temporary not attached
- Travelling with a laptop.
Background: I very much like to set up and forget my backups.
Regular backups are important, but I don't want to be notified at every little hick up.
However, I absolutely need to be notified, if there is a permanent problem:
- e.g. after 2 consecutively failed, weekly backups of my home-server
- e.g. 24 consecutively failed, hourly backups on my laptop
Implementation details:
- counter of consecutive failures on a per-repository basis
- set counter to 0 after a successful backup
- counter should be is accessible in hooks
- allow the user to reset the counter to 0 manually (e.g. via a hook, after sending a notification)
With a counter it would also be relatively easy to escalate notifications (e.g. via hooks), e.g.:
- at 2 failed backups: show a simple notification on the desktop
- after 10 failed backups: show urgent notification and send an e-mail
- at 20 failed backups: send notification e-Mails to the head of the IT-department
Perhaps there is a better solution than counters - but an accessible counter would provide quite some flexibility - e.g. in combination with hooks and apprise.
It would be helpful if Vykar provides a counter for consecutive errors/ failed backups on a per-repository basis.
This would allow e.g. to build hooks that notify users only after a certain amount of errors/ failed backups.
Use case:
Background: I very much like to set up and forget my backups.
Regular backups are important, but I don't want to be notified at every little hick up.
However, I absolutely need to be notified, if there is a permanent problem:
Implementation details:
With a counter it would also be relatively easy to escalate notifications (e.g. via hooks), e.g.:
Perhaps there is a better solution than counters - but an accessible counter would provide quite some flexibility - e.g. in combination with hooks and apprise.