Scheduled Backups Fail

[Bisser]

I searched the forum but did not find the answer to this problem. I scheduled a backup and it didn't start at all like I haven't done anything. I read a message somewhere to check if cron is running and yes it is. I am using 2 versions 5.4.3 and 5.4.5. And it happens on both.

What I did in more details is went to the Datacenter\Backup node and clicked Add then selected all days all nodes and all VMs to backup within 15 min or so then I waited 30 min and nothing happened. I can't see any logs in the log window and I can't find any backups anywhere.

 

[Bisser]

I left the scheduled backup and it run 10 hours later than the scheduled time. My time zone is +10 the backup is scheduled to run at 00:30 but it actually run at 10:30 am. Is that normal? Is there a way to correct this so the backup runs at the time I have scheduled it for instead of running 10 hours later than the scheduled time?

 

[BobhWasatch]

You can set the system time zone in Datacenter>your-host-name>System>Time. Or from a root shell on the host ''dpkg-reconfigure tzdata''.

 

[Bisser]

You can set the system time zone in Datacenter>your-host-name>System>Time. Or from a root shell on the host ''dpkg-reconfigure tzdata''.

The Time Zone is set correctly already as I mentioned GMT +10. And the problem is not setting the time zone but the backup starts exactly 10 hours later than specified. It somehow adds the value 10 to the already specified hour for backup.

 

[BobhWasatch]

Which sounds suspiciously like the timezone is not set properly that the error is equal to the timezone offset. If you open a root shell and type ''date'', does it show the correct time?

 

[Bisser]

Which sounds suspiciously like the timezone is not set properly that the error is equal to the timezone offset. If you open a root shell and type ''date'', does it show the correct time?

Yes it shows the correct date and time. I will probably give it a reboot tonight and see if that fixes it.

 

[BobhWasatch]

When you reboot check what time zone is your hardware clock set to. Linux expects UTC. If you are not running NTP and the hw clock is in local time you could have issues.

 

[Bisser]

If it doesn't resolve I think I will just use it the way it works I will simply add 10 hours to the backup schedule and move on to my next challenge