Salta al contenuto principale

TIB file creation time using Acronis Bootable Media

Thread needs solution

Since upgrading from ATIH2010 to ATIH2012, I've noticed that the creation time (MS Windows 7) of .tib files made from the bootable media (linux) version of ATIH is off by minus nine hours. According to a kb article I found (created in 2005, updated in 2010!):

http://kb.acronis.com/content/1516

bootable media makes tib files according to GMT. But where I live (Central Daylight Time) GMT is 5 hours AHEAD of me, not nine (9) hours BEHIND...!

1. What is ATHI2012 build 6154 using for time?

2. Why did ATIH2010 do this properly but 2012 does not?

0 Users found this helpful

Gretings tomf,
I created several back up images last week using Acronis bootable media build #6154. One set of images were save to a second internal data disk, the others were saved to a NAS locally.

I was in a rush and do not recall if my file creation date & time stamps were correct for my time zone (PST). I will not be able to verify this for you until this evening.

The boot media documentation does not state support for specifying that the current date and time or timezone (zoneinfo) be set using a startup parameter. I can't test at the moment I'm afraid. I do know that 2012 is based on v2.6 of the linux kernel. You may need to contact support in order to get an official response. Others here might also know if this is possible.

I would have thought that Acronis True Image used the system time, i.e. whatever time is set on your PC.

That's certainly what happens in my case. I use the Acronis True Image 2012 bootable Recovery Media, and its time stamps correspond to the time shown by Windows. Filename time stamp used to be correct, but since my country's recent one-hour shift from EST to DST, ATIH times are off by one hour, still using EST instead of Windows DST correction.

See my later post #6, below, for more information about file properties.

I recall this has been noticed on a previous build/version of TIH, the time zone was set as Russian Central Time, which is GMT + 4 hours.

Hi Tomf,
Back up created from boot media is running now. Saved to my NAS. I created my destination folder and TIB from #6154 bootable media. The destination folder has the correct date and time. The NAS is set to update with a time server regularly.

My TIB file does not have the correct time. It is off by -11 hrs. I am GMT -7.

Next I will test adding the @date@ and @time@ to the TIB name, but I suspect this will not change anything.

Results:

Adding @date@ - Displays as ...2012-04-16.tib

Adding @date@@time@ - Displays ...2012-04-16_2100.tib (file creation time shows as 11:52 AM) (Actual time 10:52 PM)

Adding @time@ Displays as ...2100.tib (file creation time shows as 11:55 AM) (Actual time 10:56 PM)

Allegato Dimensione
96708-100447.jpg 8.29 KB
96708-100450.jpg 8.65 KB

>My TIB file does not have the correct time. It is off by -11 hrs. I am GMT -7.

Thanks for confirming. I wonder why yours/my result is wrong, but tuttle's seems OK, as if there is a way to assert the correct time zone for the bootable media when creating it. Or maybe that's the magic--if the bootable media is created using the ATIH2012 application, then it is correct, if it is created using the downloaded .iso file from Acronis' web site, then it is "russian time" or some such that is wrong for us.

That is what I am using--the downloaded .iso file from my account.

Although I've bought three licenses for ATIH2012, I have not actually installed it to any Windows machine (yet)! Maybe I can find a suitable sacrificial lamb, er, I mean, installation candidate (or just do a Restore Point, install, make iso, Restore) and confirm my suspicion above.

‎The OP's first post was unclear. I thought he was referring to the date/time stamp ATIH writes into the filename, if the option "Generate name" | "Add time (@time@)" is selected. Now I think what he means is the "Created" date/time in the file properties.

Using the Acronis True Image 2012 bootable Recovery Media build 6154, I found the following in tests today:

"Created" time in the file properties is incorrect. Today, April 17 at 09:24 DST I began full backup. "Created" time in the file properties shows as April-‎17-‎12, ‏‎1:25:40 AM, obviously from a time zone which is not mine.

Interestingly, even the filename is incorrectly stamped. I chose the option "Generate name" | "Add date (@date@)" "Add time (@time@)" for the backup that begun at 09:24 DST (as shown by my Windows clock). ATIH named the file thus: 2012-04-17_0824.tib. That is exactly one hour earlier than the correct time. Most of the year I am on EST, but one month ago my country did it's annual one-hour jump forward to DST. Windows is set to EST and also set to automatically handle DST changes, which it did. It seems that ATIH 2012 bootable Recovery Media is taking the Windows EST time but not recognizing the current DST as correctly displayed by Windows.

So, both the time in the file properties and the @time@ filename stamp are incorrect.

Hello all,

Thank you for bringing this up to our attention.

The Knowledge Base article that tomf mentions in his post is no longer valid. I will update our KB team so that we can update it with the new information.

The bootable media builder uses the local computer time and the media downloaded from the Customers' Acronis accounts has GMT +4 because they are compiled in Russia.

Please let me know if you have additional questions.

Thank you.

Anton:

That explains why the file properties "Created" time is Russian time.

Why does the filename time stamp "Add time (@time@)" not recognize my current Windows system time, which is DST?

There are two separate issues:

1. The time stamp appended to the filename when @time@ is selected.

2. The Creation date/time written to file properties.

>‎The OP's first post was unclear. I thought he was referring to the date/time stamp ATIH writes into the filename

I beg to differ; I was clear enough. FWIW I don't use the ATIH file naming conventions.

It seems to me though Anton that the problem is still not defined. When I created my .tib at 1100am CDT, Russian time (GMT+4) was nine hours LATER than that, i.e. 20:00 hours. But the time stamp was nine hours EARLIER than 1100am CDT, it was 0200 (am) that same day.

And tuttle's example of 0924 becoming 0124 should have actually resulted in 17:24 (PM) i.e. later not earlier.

Someone correct me, if I'm wrong.

I just made a Bootable Media backup using my ATIH 2011 Netbook Edition, and the Windows 7 creation/modification date&time were correct!

2011 is not much different from 2012 afaict, wonder why one works and the newer one doesn't...?

Hello all,

Thank you for taking time to contact us.

tomf,

Are you able to provide us with a remote access to your system? This will help to localize the issue. 

We are awaiting for your response.

Thank you.

Oleg I have two ISPs but they both have "shared" IP addresses i.e. I don't believe there is any way to access this computer from your location. But if you tell me what specifically you need, then I will try to accommodate you (PM or email is fine too).

FWIW I did again this a.m make an image backup with ATIH2012b6154 (bootable media) at

created local time 6/4/2012 06:40 AM
modified local time 6/4/2012 06:45 AM

and the image appears in Windows Explorer as

created 6/3/2012 9:40 PM
modified 6/3/2012 9:45 PM

and of course at the hour of 640a CDT it is actually 3:40 PM on 6/4 Russian Standard Time afaict.