goebbe

Just to put a data point. Using borg to backup my home directory on Linux Mint 21 (based on Ubuntu 22.04) - ~/.cache contains roughly 500 folders/subfolders with a total...

Correct, my last backup was yesterday, 2021-12-07 16:29:59 i.e. 14 hours before I tried to test the "Run missed backups" option as described above. So the "Run missed backups"-option rely...

Thank you - now I understand the logic behind it and see why the issue appears. A problem could be that this misses some corner cases - as reported above....

So we have at least two corner cases where the option does not just work as expected, i.e. the backup will not "Run missed backups after startup". This should not...

> New issue title : "Run missed backups option fails if the backup has never been launched." Thanks, this describes one issue, the other issue would be: "Run missed backups...

In my experience, borgbackup does a decent job after abortion/ network failures. Normally, borg can create a new backup (and finish the backup) just fine. So maybe the "run missed...

With respect to the original issue, I just tried to understand scheduler.py (keep in mind, I never programmed anything like this). Whenever the schedule is _changed_ by the user, then...

> I wouldn't add an artificial `last_run`. It will just take the actual last run from the profile. The user wanting a new schedule doesn't change the last run. E.g....

Sorry, I don't mean to offend anybody. If you outright reject the ideas behind the implementation, there is no point in testing this. But I see that there is an...

New issue title : "Run missed backups option fails if the backup has never been launched after setting or changing the schedule." **Goal**: Make sure that missed backups are always...