Aller au contenu principal

Incorrect back-up date stamps.

Thread needs solution

I'm having recurring problems where TI is creating back-up files with date stamps showing as being a number of days in the future. Here is one from today (24-06-19):

Back-up destinations are USB drives which are straight into the my laptop. This is running Windows 10 v1809 x64

This is on TI Build 17750 but it was happening on the previous build as well. I've carried out a fresh install and reinstated the back-ups. Date stamps all looked ok initially but within a day or two, the problem reappears. Not all of the back-up tasks I have show this odd behaviour. 

Any suggestions on what is causing this frustrating issue? Thanks in advance.

 

0 Users found this helpful

William, welcome to these public User Forums.

Have you checked the date/time stamps on the actual .tib files on your destination USB drive(s) to see if these show the correct information or if these are also incorrect?

The only times that I have seen date/time stamps change is when I have booted into a different OS such as Linux or from a bootable Live CD or DVD OS, but this has normally only been a time difference, not a date change.

Hello Steve,

Yes, I had checked the .tib files but forgot to mention that so thanks for the reminder. The .tib file is showing the future date as well - see screenshot below. It really is odd. Any backup that I command manually is stored with the correct date and time but somehow the scheduled ones appear to be susceptible to this issue. I've three scheduled back-up plans, 2 daily and 1 weekly. This issue has affected one of the daily plans (below) and the weekly.

William, please download the MVP Log Viewer tool (link below) and check if the log file(s) for this backup task shows the correct time stamp in the log messages or not?

Steve, both the tasks in question are showing up in the logs with the wrong (i.e. 'future') date.

Hmmm strange and stranger...!

The next logical check is to see if this issue is system wide or restricted only to Acronis?

Type 'Event' in the Windows search box and pick the Event Viewer then take a look at various categories of system logs and see if you have any future dates shown in the list?

 

No rogue future date events showing in the any of the various system logs. However, I did do a search on the laptop for any other files that were created/modified on the wrong date of the 26th. There are about 150 files showing but they all fall within a very tight time band of 2-3 minutes, covering 19:26-19:28, coinciding with the time aspect of the errant back-ups.

I've had a couple of window updates imposed upon the laptop recently. Is it possible that one of those has somehow temporarily interfered with the system date, been up long enough for a backup to take place using the temporary date before the system auto-reboots?

William, if there are other files all created with the same 'future' date then I doubt this was caused by the Acronis application but there may be some correlation to the Windows Updates involved?

I have not come across any issue like this previously so am guessing about what could have caused it or whether it is likely to occur again?  Only time will tell the latter.

Steve, in the absence of any other theories it does seem to have been some sort of Windows glitch. I reckon I should delete these rogue tib files via TI so that there is no risk of them interfering with the actual proper backups fom that date.

I'm going to keep performing back-ups manually for a day or so then turn back on scheduling to see if I can spot any other possible clues.

Many thanks for the support and advice Steve!