Backup Status seems not correct

Server
1

I have an instance of UrBackup with a windows-client that is configured to do incremental File-Backups every 7 hours in time window from monday-Friday/9-17h.

On weekends this PC is mostly not online, so no need for backups. However every weekend the status of the file-backups of this PC turns red. This wouldn’t be much of an issue maybe but I have monitoring in place and every weekend I get mails that the general status of the file backups of this PC is bad.

So first of all it seems a nice feature that Urbackup interprets the time window and interval into the general status - actually I would have expected that the status of a backup only turns bad if there really is a general failure while backing up. But it seems broken or maybe I am wrong with my interpretation of that behaviour?

I’m not at the latest version but I skimmed through the Changlogs and an issue like this was not there, neither I found this discussed somewhere else.

Wile writing of course it comes to my mind that this beaviour should also be there on other installations of mine and I could do some testing on this, but anyway I would would be happy about some Feedback from you others as well :slight_smile:

2

I’m appending further considerations:

  1. I tried different notation, Mon-Fri/9:00-17:00 instead of 1-5/9-17, no change
  2. Disabling File-Backup also let’s the status with “kein aktuelles Backup”, which maybe is not what I would expect
  3. cranking up the interval form 6 hours to 250 hours let’s the status turn to “OK” immediately - so it’s not that there is no connection between the status and the individual client settings…
3

I guess you could increase the interval on the weekend only… (currently it does not take into account the backup window).

4

Yes, thanks for the tip, will give it a try, good to know. Will you extend the scope of the status-display for the backup windows also or is there no plan to do so in the near future?

5

While christmas holidays already set in, another shortcoming gets clear: the way it is now it will never take into consideration downtimes that are off the schedule. So I really think the overall status off the backup should take the “online”-status of the client into consideration. Overall status because of a missed backup window / interval for a workstation that was offline seems counter intuitive and pointless :sunglasses:.