Web Backup execution on wrong time

Dear,
on an our server, we have a strange problem about when the web backup execution start.
The server is a Debian 11, with the correct timezone:

Code:

root@X ~ # ll /etc/localtime
lrwxrwxrwx 1 root root 31 Dec  9 14:21 /etc/localtime -> /usr/share/zoneinfo/Europe/Rome
root@X ~ # date
Wed 10 Dec 2025 02:33:45 PM CET

on the php side, we have not set any different timezone, because that one is fine.
So also from the php side we see the correct time displayed:

Code:

Wednesday 10th of December 2025 02:40:19 PM

Also checking the script about backup cron /usr/local/ispconfig/server/lib/classes/cron.d/500-backup.inc.php
we see the regular:

Code:

class cronjob_backup extends cronjob {

        // job schedule
        protected $_schedule = '0 0 * * *';
[...]

and from the ISPConfig interface on the System -> Server Config -> Server -> Backup time we had 0:00h before (and now 23:45h in order to try a different time).
But for some reason, the web backup of this server, run actually at 09:45AM (so in the middle of our morning).
This is quite a problem because we need that this backup run on the night, not in the morning.

What could be the problem that rise that issue? Any suggestion to debug further?
Thank you.

 

Yes, but this is the problem. On this server we have just 1 website. And the procedure seems to start at 09:45AM. For example also the cron log /var/log/ispconfig/cron.log.1.gz is created at 09:46AM
On the others hand, on a server configured exactly as that one, that procedure start at 00:00AM without problem (so the backups are created something around 00:05AM).

 

Yes we have the default one on the crontab:

Code:

* * * * * /usr/local/ispconfig/server/server.sh 2>&1 | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done
* * * * * /usr/local/ispconfig/server/cron.sh 2>&1 | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done

 

We did a server reboot (because it was up and running) from years. And now looks like that the backup started again from the correct time (midnight).
We can mark this as solved.
ty