Not only did DST rob me of an hour of sleep this weekend, it’s also slowing down my content deployment jobs! Thanks a lot, Benjamin Franklin!
This KB article seems to explain the problem as beeing that the OWSTIMER has its own clock which is separate from the system clock. I scheduled a job for 11:17am this morning and it showed a status of ‘preparing’ until 12:17pm, at which time it ran smoothly.
A couple of solutions: set your jobs to run as if you were still in non-DST. Right now, that would mean that I would schedule a job for one hour from now if I wanted it to run immediately. Second solution: change your server time zone to a non-DST time zone and disable automatic time updates.
Update 2008-03-11:
Install SP1 to alleviate this problem! I assumed the server I was working on had SP1, but I was wrong. Running the update fixed the problem immediately.