Not a real bugger but it will be more convenient if 20201020_235020 style format is used instead of current 10.20.2020_23-50-20 …
The time also does not take the current timezone/local time into account.
Type your comment> @bozden said:
Not a real bugger but it will be more convenient if 20201020_235020 style format is used instead of current 10.20.2020_23-50-20 …
The time also does not take the current timezone/local time into account.
Can you change to your local timezone finally?
Thank you for pointing it out. NTP & timezone was correct but RTC Time (hwclock) was not synched. I just assumed it was default and didn’t check before. This is basic Linux 
For reference (RHEL):
timedatectl
hwclock --systohc
nano /etc/sysconfig/ntpdate
Now fingers crossed for the next backup…
Type your comment> @bozden said:
Thank you for pointing it out. NTP & timezone was correct but RTC Time (hwclock) was not synched. I just assumed it was default and didn’t check before. This is basic Linux
For reference (RHEL):
timedatectl
hwclock --systohc
nano /etc/sysconfig/ntpdateNow fingers crossed for the next backup…
My system is Ubuntu, and the last command: nano /etc/sysconfig/ntpdate is empty and cannot be saved. What directive should put into the ntpdate?
[ Error writing /etc/sysconfig/ntpdate: No such file or directory ]