ProfN Posted April 2, 2005 Report Share Posted April 2, 2005 What is suggested to prevent any problems of confusion between Daylight Savings and Standard time in: --Backing up? --Restoring? --Duplicating volumes? Thanks for any assurances or tips. Respectfully, Norm Nager Quote Link to comment Share on other sites More sharing options...
ProfN Posted April 6, 2005 Author Report Share Posted April 6, 2005 Are there no more Retrospect problems when we switch between Standard and Daylight Savings times? I posted my questions on preventing problems the day before we made the switch to Daylight Savings. Now would be an excellent time for a response, please? Quote Link to comment Share on other sites More sharing options...
twickland Posted April 6, 2005 Report Share Posted April 6, 2005 I can only speak from my own experience, but the only problem I have noticed in the 10+ years we have been using Retrospect is related to the different way that Windows computers account for the DST change as compared to Macs. This means that at the time change, Retrospect on the backup Mac (running a normal, incremental backup) interprets all files on Windows clients as having changed, and so backs up everything again. Since this is going to happen anyway, we have been performing our backup set media changes to coincide with the time change. Almost all of our Restores have been of selected files, not an entire disk, and all of our entire disk Restores have been to Mac clients. We have never had any problems, though I'd expect that restoring files to Windows clients that had been copied in a different time regime would probably have their creation and modification time stamps shifted by an hour. I have never checked this, and in any case that I can imagine, such a shift would be of no consequence to us. Quote Link to comment Share on other sites More sharing options...
kazeeks Posted September 8, 2005 Report Share Posted September 8, 2005 We've been plagued by Retrospects confusion during the time shifts, costing us cases and cases of blank media, as Retrospect started backing up tens of terabytes twice a year. Bummer. All our backup systems, and our servers are all Mac, so I know it's not just related to how Windows deals with the time shift. Anyway, we solved the problem permanently by setting all our file servers and all the backup Macs to Arizona time, which effectively disables Daylight Savings Time. The rest of our workstations are set to local Pacific time. It's been flawless for two years now. Quote Link to comment Share on other sites More sharing options...
RastaKins Posted November 10, 2005 Report Share Posted November 10, 2005 The answer is so simple, I cannot figure why Dantz had not fixed this problem. Dantz needed to use UTC time only. Mac OS X and NT will then be compatible, you can change daylight savings and even move from state to state without negatively affecting backups. The nasty daylight savings time problem will still show up for the Mac OS 8,9 and Windows 95,98,ME people, but it'll be fixed for all the modern platforms. PLEASE, Dantz fix this ubiquitous and repeatable bug! Mike Quote Link to comment Share on other sites More sharing options...
waltr Posted November 11, 2005 Report Share Posted November 11, 2005 hi rasta, what do you think will happen if EMC releases a fix, and then M$ actually fixes the filesystem? what say they do it in longhorn? there is another thread here in which twickland suggests a more robust time/date selector. it's probably the only way to deal with this since none of us can say for sure what will come out of redmond. i'm sure EMC does not know either. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.