# Release: 2.1.1.105 (Canary) 2025-10-10

**URL:** https://forum.duplicati.com/t/release-2-1-1-105-canary-2025-10-10/21415
**Category:** Releases
**Created:** [October 11, 2025, 5:07am UTC](https://forum.duplicati.com/t/release-2-1-1-105-canary-2025-10-10/21415 "2025-10-11T05:07:10Z")
**Posts on this page:** 1
**Showing post:** 9

<div class="post-metadata">

### Author: ![ts678](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/8491ac/32.png) [@ts678](https://forum.duplicati.com/u/ts678)
#### Post date: [November 2, 2025, 10:26pm UTC](https://forum.duplicati.com/t/release-2-1-1-105-canary-2025-10-10/21415/9 "2025-11-02T22:26:00Z")

</div>

Change off DST fell back an hour in Duplicati. I had hoped dailies would hold as in Spring.  
On night before, my 7 AM-ish daily runs were forecasting 6-ish. On next day, next are too.

I saved some server databases if they would help, but maybe dev could test this on a VM?  
I’ll probably move the jobs to their correct time soon unless somebody gives reason not to.

7:50 OneDrive backup ran at 6:50 (so Duplicati did 1 day interval as 24 hours – no adjust).  
7:20 Backblaze backup ran at 6:20.

In better news:

I set up a job to run hourly, starting 30 minutes before loss of DST. I expected a double run,  
because 2 fell back to 1, so 1:30 happened again but on standard time, not daylight saving:

```plaintext
2025-11-02 01:30:01 -04 - [Information-Duplicati.Library.Main.Controller-StartingOperation]: The operation Backup has started
2025-11-02 01:30:00 -05 - [Information-Duplicati.Library.Main.Controller-StartingOperation]: The operation Backup has started
2025-11-02 02:30:03 -05 - [Information-Duplicati.Library.Main.Controller-StartingOperation]: The operation Backup has started

```

---

_[View the full topic](https://forum.duplicati.com/t/release-2-1-1-105-canary-2025-10-10/21415)._