#602 Restoring single file sets metadata on all files

[Mark Bourne]

Areca 7.5. Restoring a single file to its original location changed the metadata on all other files to match the latest backup.

Having accidentally deleted a file which I wanted to recover:

• From "Logical view", right-click the file and select "Recover"
• Set "Location" to the root of the archive source (so it gets restored to its original location)
• Select "Ask before overriding existing files (it didn't exist, but just in case...)

After restoring the file, the "applying metadata" phase took a surprisingly long time. From Sysinternals Process Monitor, I could see the Java process accessing what looks like every file included in the backup. After the restore completed, looking at some other files which had been modified since the last backup, their "Modified" timestamp has been changed back to the last modified time they had when I last ran a backup.

It appears that Areca has gone through every file in the archive, not just the one I restored, and set the metadata to match the archive. As far as I can tell, the actual content of those files has not been affected, just the metadata. But that could prevent those modified files from being included if I run another incremental backup since the modified timestamp now appears not to have changed, unless they're modified again in the meantime.