March 13, 2007 at 7:52 am
Has anyone noticed any strange issues with the timestamps on backup files after DST? We have applied all the patches, and I have the following happening:
On a SQL2000 box I have a job that backs up the master db at 11:45PM, with a timestamp as part of the file name. For my 3/9 backup, the file system time stamp shows 3/10/07 at 12:45AM, my 3/10 backup shows 3/11/07 at 12:45AM, and my 3/11 and 3/12 backups show the proper time.
I have the identical thing happening on a SQL 2005 box.
I also have a job that does a full backup of all DBs on the server and dumps the files to a SAN (and they are later put on tape), and all those timestamps are one hour later than when they actually happened before DST, and correct after DST.
I don't think this is that terrible of a problem as long as I am aware of it, but am just curious if anyone else noticed this happen. The one hour off problem doesn't suprise me that much, but the 12 hour off problem has me and our system admin. scratching our heads.
The Redneck DBA
March 13, 2007 at 8:15 am
I might be just missing something, but it looks to me like all the problems you are listing are one hour off, not 12. Your 3/9 backup actually occurred on 3/9 at 11:45PM, but after DST changed the time, this became one hour later (3/10 12:45AM). It's not actually 12 hours later because 12PM is noon and 12AM is midnight. I've seen similar things happen in our event logs after DST occurs, so I think you should be fine.
March 13, 2007 at 8:32 am
You are right...they are only one hour off. That makes me a lot less concerned. Thanks!
The Redneck DBA
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply