Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
All my backups ran outside of schedule
#11
(10-26-2026, 06:20 AM)admin Wrote: @Tungsten, this problem is indeed really strange. As @al3x mentioned, there might be a bug that's hard to find and reproduce. Could you provide us with screenshots of all the scheduling settings? We'll look into it further. Thanks.

Here are my screenshots. Hope they help.


Attached Files Thumbnail(s)
   

.zip   Task1_Screenshots.zip (Size: 129.93 KB / Downloads: 23)
.zip   Task2_Screenshots.zip (Size: 109.2 KB / Downloads: 27)
.zip   Task3_Screenshots.zip (Size: 63.04 KB / Downloads: 26)
.zip   Task4_Screenshots.zip (Size: 145.83 KB / Downloads: 23)
Reply
#12
(10-26-2026, 06:51 AM)al3x Wrote: @admin Have you read my "guess" in my second answer? Could it be related to the way HBS handles timestamps? I think that would at least explain the early rerun.

Thanks for the heads-up. I'll pass this along to the relevant developers so they can take a closer look.
Reply
#13
I also encountered an issue with a scheduled task that triggered incorrectly a few hours after the daylight saving time change in Spain.

The timing error isn’t straightforward. It’s not simply a matter of being exactly one hour off, but it affected some backups, while other tasks, scheduled further away from the 03:00 time change, were unaffected.

I suppose you could call it a minor issue, given that it only happens twice a year on specific, well-known dates.

I recall from my time working as an IT consultant that the customer’s administrators would shut down all the company’s Oracle servers for the entire night whenever the time change occurred, just to avoid any issues. It was an established, accepted routine.

Best regards,
Alberto
Reply
#14
@all,

We can confirm that this issue is caused by Daylight Saving Time. On the surface, it appears to be only a one-hour offset, but fixing it is not simple, because the time-handling portion of the scheduling code needs to be reworked as a whole. There is still enough time before the next DST transition, so we will do our utmost to fix it.

Have a nice day!

Best regards,
Reply
#15
Here is an additional report for this situation.

The unexpected running is not a concern for my schedules, but strangely it impacted one of my PC's and not another. Both are setup with similar schedules. DST ended here at 2:00 am on Nov 1 with clocks turned back to 1:00 am.

PC 1
- Full System backup, monthly, second Tue @ 5:20 am
- Incr System backup, weekly, every Tue @ 5:20 am (last was run on Oct 27
- the PC was rebooted many times on Nov 1 for various non HBS activities
- no unexpected backups on Nov 1 or 2.

PC 2
- Full System backup, monthly, second Tue @ 5:30 am
- Incr System backup, weekly, every Tue @ 5:30 am (last was run on Oct 27
- no unexpected backups on Nov 1
- PC was rebooted at 8:00 am on Nov 2 after license applied. An unexpected incremental backup was performed after the reboot
- this PC also does multiple Full and Incr File backups scheduled for every Saturday around 6:00 am. There were no unexpected backups on Nov 2 after the reboot.

Hope this helps rather than confuses the analysis.
Reply


Forum Jump:


Users browsing this thread: 5 Guest(s)