Incorrect File Modified Time in Restored Files

[brianshmrian]

When I restore files from a backup, it seems that their modified time is set to UTC time as opposed to the local computer time. For instance, I tested backing up a file with a modified time of 12:48 pm today and when I restored it, the restored file had a modified time of 7:48 pm.

(Another oddity is that the created time of the restored file is always 12:00 am of the current day.)

If I look in the 1_c.zip backup archive, the modified time for the file is 12:48 pm. If I extract the file manually, it has this correct time.

This is for backup4all 9.3 build 428 running on Windows 10.

Thanks for any help!

[Adrian (Softland)]

Hi,

We were able to reproduce the problem and we will fix it.

[brianshmrian]

This problem still persists for me in version 9.4.448. I want to clarify that I'm seeing the problem when trying to restore from a smart backup.

As an example, I just backed up a file with a modified date of November 24, 2021 3:05 PM. When I tested restoring the file, its modified date was 11:05 PM.

The restored file also had a creation date of January 1, 1601 12:00:00 AM (which I guess is a 0 Windows FILETIME?)

The modified file time/date in the 1_c.zip file is correct.

[Adrian (Softland)]

Hi,

Do you still have the problem with build 9.4.460?
If yes, please send us to support[at]backup4all[dot]com the following:
- the last backup log
- the .bkc catalog file from the backup destination

[ha100]

I have this problem too in the latest version.
When restoring from an incremental backup it gives the date of when it is restored as date modified.
When restoring from a mirror backup it gives the correct date modified.
It did not do that in previous versions.

[Adrian (Softland)]

@ha100
Are you talking about files? or folders.

[ha100]

Files

[Adrian (Softland)]

Hi,

I cannot reproduce the problem here.
Please send us the .bkc catalog file for that job, the backup log and the restore log for that job, to support[at]backup4all[dot]com