rajiv Posted April 6, 2003 Report Share Posted April 6, 2003 hello all. i'm running retrospect 5.0.238 on mac os x 10.2.4. i'm in the united states, and on saturday night at 2 am, clocks jumped ahead by 1 hour. os x was nice enough to change my mac's clock automatically. however, i noticed that retrospect did not run my backup script at 7 am as i had set it to. instead, the backup ran at 8 am. has anyone else seen this problem? Link to comment Share on other sites More sharing options...
TtamTroll Posted April 9, 2003 Report Share Posted April 9, 2003 I'm experiencing the same situation on Mac OS X 10.2.4 client and Mac OS X 10.2.4 Server. I'm still trying to figure out how to get them to start "as scripted". Link to comment Share on other sites More sharing options...
CallMeDave Posted April 9, 2003 Report Share Posted April 9, 2003 Quote: I'm still trying to figure out how to get them to start "as scripted". Has Retrospect been quit and restarted since you noticed this? Dave Link to comment Share on other sites More sharing options...
TtamTroll Posted April 10, 2003 Report Share Posted April 10, 2003 Quote: Quote: I'm still trying to figure out how to get them to start "as scripted". Has Retrospect been quit and restarted since you noticed this? Dave Retrospect has been quit several times since this occurred. The machines have also been shut down and cold booted. The same problem still exists. I'm going to change the start times on my scripts to 1 hour later, save them, and then change them back to the original start times to see if saving new/modified scripts makes a difference. It's worth a try... Link to comment Share on other sites More sharing options...
rajiv Posted April 11, 2003 Author Report Share Posted April 11, 2003 Quote: Has Retrospect been quit and restarted since you noticed this? well i did not quit or restart retrospect. but the next day, it went back to the correct time. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.