Daylight Savings Time and Scheduling Jobs
Twice a year, we move our clocks around and either "gain" or "lose" an hour. This "Daylight Savings" can cause issues with scheduled jobs because an hour is either missed or repeated.In the U.S.A., we "spring forward" on the second Sunday in March and skip the 0200 hour; our clocks go from 0159 to 0300 and any jobs we had scheduled between that time DO NOT HAPPEN.
Can I emphasize that again? If you scheduled something for 2AM, like your backups, it DOES NOT HAPPEN.
Then, we "fall back" on the first Sunday in November and repeat the 0100 hour; our clocks go from 0159 to 0100 and any jobs we had scheduled between that time HAPPEN TWICE.
This just sucks all around, doesn't it?
What's an admin to do about it? Well, you can avoid scheduling jobs from 0100 to 0300, you can schedule the jobs and move jobs as needed when Daylight Savings Time approaches or you can avoid the problem entirely by running your systems on UTC.
As soon as I get a job where I can run all of my systems in UTC, I'll let you know.
Daylight Savings sucks.
Labels: daylight savings, linux, system administration, time
posted by Lachlan @ 11:22 PM
0 Comments:
Post a Comment
<< Home