Group: Forum Members
That's unfortunate. In my opinion, this (control over how/whether to restore when the file already exists) is critical functionality in file backup software, and for many potential converts from other backup products, this may be a deal breaker.
I think that an option to not overwrite existing files if they are newer would capture your requested functionality to restore only files that are missing, while also accommodating additional use cases.
I believe that the reason such control is not (yet) available in Reflect may be related to the fact that they do the file backups at the level of blocks, not at the file level. So it would probably be difficult to figure out which file each block originally came from, and the information about last modified date of each backed up file is probably not even captured in the backup (although a compromise functionality would be an option to not overwrite existing files if they are newer than the date of the backup, rather than the date of each individual file).
Nonetheless, individuals who want to use this more granular restore option would probably not mind some modest performance penalty during the restore phase, when they select options that require Reflect to identify the individual files being restored.