-
-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Time of regular backup doesn't fit #217
Comments
Would you please show the result of |
Here it is:
|
Looks good so far. Would you please show the exact name of the backup directory created by the backup? See here for the backup directory structure. My is called
How do you do this? According /etc/cron.d/raspiBackup and your screenshot you set the backup time to 2PM. |
Backup directory structure
Sorry, I changed the time between my posts to test something. The screenshot just should say, that the time of regular backup is different to the time mentioned here |
Hm ... frankly I'm now confused 😢 The contents of /etc/cron.d/raspiBackup tells us the backup should be created at 2PM. The backup directory name tells us that the backup was created at 2PM as defined in cron. So everything is OK. Where did you configure the backup should be created at 1PM? |
Okay, sorry for my confusing information, especially the screenshot. Give me a second, I will share a video with you! |
Please see the video... There you can see, that I configure the backup to start at 17:20 but it starts at 18:20. (You can skip the time from 1:00 - 1:40 ;)) |
Thank you very much for the video. I now got your issue 😉 You changed now the time to 17:20. Please check what's in /etc/cron.d/raspiBackup. Please check you have I found Why are cronjobs running at the wrong time?. Frankly I expect raspi-config to restart cron to activate the new timezone. But please check and follow the answers given on the page. |
You are right, in Gotcha! A reboot did the job! Thank you for your support, I will donate you a coffee sir :) |
No problem. It's a nasty raspi-config issue and I created an issue there. Maybe they add a restart of cron whenever the timezone is changed. |
First of all, THANK YOU for this amazing tool!
There is just one thing, I can't understand. RaspiBackup starts the regular backup process exact one hour after the setup time.
This are my current time zone settings:
Now, when I setup the regular backup to start at
13:00
, it will start at14:00
local time / time of my macBook. So there is an offset of exact 1 hour and I thought about time zone settings, but they seems top be correct.My information
PRETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"
The e-mail report says:
--- RBK0009I: raspberrypi: raspiBackup.sh V0.6.4.3 (d2acd2d) started at Mon 13 Apr 14:00:01 CEST 2020.
... (this e-mail is received at about 14:15 local time)
Best Regards!
The text was updated successfully, but these errors were encountered: