I work in GMT-5 (Georgia, USA) and all but 1 of my backup jobs start at the correct scheduled local time. I have a job scheduled to start every weekday (M-F) at 7:15pm local time. It runs at the correct local time (M-T) but it doesn’t run on Friday since it considers 7:15pm local to actually be 12:1…

Well, I can tell you the general issue behind what you’re seeing but not specifics. Duplicati works with all dates / times internally as GMT and is supposed to convert the internal GMT time to the local time whenever going to actually display dates / times. Historically, what’s been reported is th…

JonMikelV, I do not use Duplicati’s schedule to start a backup. I use our RMM tool. So the actual run time is not an issue for me & I have not tested it. Yes, the issue I have as I depicted in my log example, is the logged start & end times being 5 hr ahead of my actual time on the applicable compu…

To be honest I was leaning towards your issue being the “display” problem we’ve seen elsewhere (so thanks for the confirmation :slight_smile:), but I’m not so sure about DLR’s problem.

Running Duplicati - 2.0.1.73_experimental_2017-07-15 My 7:15pm job (M-F) starts at the correct local time and, as everyone else has pointed out, records GMT times in the logs and reports. This could be overlooked as being a bug… This same job does not run on Friday at 7:15pm since Duplicati thinks…

[image] DLR: Now I would consider this a major issue… Agreed, which is why I poked kenkendk earlier as I believe he’s the most familiar with that part of the code. Oh, and thanks for confirming the version number you’re using.

[image] DLR: Now I would consider this a major issue… I think the problem is that the date is somehow compared in UTC instead of local time. This would explain how you gets the wrong date: duplicati/duplicati/blob/master/Duplicati/Server/Scheduler.cs#L240 …

Updated to Duplicati - 2.0.2.15_experimental_2018-01-03 The reporting times have been corrected, showing the actual local begin and end times. But the underlying problem of jobs not starting at the correct UTC time is still present. My Mon-Fri 19:15 and 19:30 jobs will not run on Fridays (Duplicat…

Is this issue ever going to be addressed and corrected?

Probably, but other items are higher priority at the moment.

I would think that having backups not run, or run when they’re not supposed to, would be pretty high on the priority list…Especially since this has been an issue for over a year, even before version 2.

Duplicati

Incorrect start time

Support

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled