Daylight Savings Time Change Oddity

Discussion in 'Acronis True Image Product Line' started by stevech, Oct 31, 2006.

Thread Status:
Not open for further replies.
  1. stevech

    stevech Registered Member

    Joined:
    Feb 20, 2006
    Posts:
    12
    On Oct. 30, my daily backups that run automatically (Acronis 9) at 2AM show that they ran at 1AM. As if the Acronis scheduler doesn't know that the time changed in XP. I haven't rebooted XP nor have I restarted Acronis' scheduler since the time change. The PC's time was automatically correctly changed.
     
  2. foghorne

    foghorne Registered Member

    Joined:
    Sep 27, 2005
    Posts:
    1,389
    Location:
    Leeds, Great Britain
    Hi stevech

    that is almost as if the scheduler is using a relative timer rather than an absolute one. I.e. when running daily it runs every day, 24 hours after it last ran. Of course this does not make sense, because the scheduler needs to be able to cope with reboots etc.

    If it is true I would expect a 23 hour interval on the March changeover.

    F.
     
  3. shieber

    shieber Registered Member

    Joined:
    Oct 27, 2004
    Posts:
    3,710
    Could be the PC changed over the time while or just after the ATI task was initiated but before it gave it's time stamp to the file.

    sh
     
  4. foghorne

    foghorne Registered Member

    Joined:
    Sep 27, 2005
    Posts:
    1,389
    Location:
    Leeds, Great Britain
    This race condition would have been evident from the log entries I assume.

    F.
     
  5. stevech

    stevech Registered Member

    Joined:
    Feb 20, 2006
    Posts:
    12
    Time change was to be 2AM local time Oct 29.
    The backup problem I noted was Oct. 30.

    As if the Oct 29 backup scheduled itself to run 24 hours hence, instead of at the prescribed time.
     
  6. foghorne

    foghorne Registered Member

    Joined:
    Sep 27, 2005
    Posts:
    1,389
    Location:
    Leeds, Great Britain
    As I said it looks like a relative measurement. Well worth a support request. At least it should be easy to reproduce.

    F.
     
  7. shieber

    shieber Registered Member

    Joined:
    Oct 27, 2004
    Posts:
    3,710
    I've noticed that when my scheduled backups run after 11:00pm, even though they complete before midnight, the date shown in the name is the date of the next day. For ecample, this file name was given by ATI 10 to a backup that was scheduled for 11:15pm on December 16, 2006 and it completed at 11:30pm on December 15, 2006

    2006_12_16_00_21_58_990D.TIB

    So the time, or at least the autonaming function that uses the time to create a unique name, is definitely a bit wonky.

    I know some have said in the past that it's GMT. Hey, it's always some other time in some other place, but locally, the local time is not a matter of whimsy. This is the only program I know of that missreports the time. IF the correct date can be put in the file time stamp, why not in the autoname?
     
  8. CatFan432

    CatFan432 Registered Member

    Joined:
    Nov 1, 2006
    Posts:
    333
    Location:
    Topeka, KS, US
    It seems to add an hour, regardless of location.
    I ran this one at 16:15:54, Central Time, USA - 2006_12_16_17_15_54_593F.TIB
    Changed my time zone to 14:20:44 Pacific time - 2006_12_16_15_20_44_312F.TIB

    When I pull them up in the recovery process they each show the correct actual Central Time for the time each job completed.
     
Thread Status:
Not open for further replies.