Possibly not just as you want, but question is a bit vague.
Timestamps affects decision of whether or not to read through the file to look for changes, and hash it. Sometimes files are kept open (databases might do this), so timestamp might not reflect the contents.
This case has an option to scan it anyway, but if you mean don’t scan an unknown new file, that would result in an incomplete backup as files are added. New files need to be processed. An exact duplicate would be fully deduplicated, so would not need any new content blocks. It might need new metadata…
Testing with File Explorer on Windows showed a copy and paste kept Modified time, got new Created.
You can experiment with things yourself. Here’s a test where I copied a file and made another backup:
ID Path BlocksetID MetadataID
2 C:\backup source\short.txt 4 2
3 C:\backup source\short - Copy.txt 4 3
FilesetID FileID Lastmodified
3 2 637453191320521051 2021-01-04 01:05:32
4 2 637453191320521051 2021-01-04 01:05:32
4 3 637453191320521051 2021-01-04 01:05:32
ID OperationID VolumeID IsFullBackup Timestamp
3 3 6 1 1609722340 2021-01-04 01:05:40
4 4 10 1 1609793048 2021-01-04 20:44:08
It’s the same content, so it can use the same blockset. Created time changed, so metadata changed, therefore it gets new entry in File view, however FilesetEntry only has Modified, so keeps original time.
A simple presentation format for your viewer could perhaps not worry about blockset hash or Creation, simply showing the path, modified time, and backup time. Or if immutable and paths never reused, the modified time becomes less interesting too, but it’s your dashboard, so you get to decide the display…
Here’s a line showing decision information leading to deciding that a file needs to be opened for exam:
2021-01-04 15:44:08 -05 - [Verbose-Duplicati.Library.Main.Operation.Backup.FilePreFilterProcess.FileEntry-CheckFileForChanges]: Checking file for changes C:\backup source\short - Copy.txt, new: True, timestamp changed: True, size changed: True, metadatachanged: True, 1/4/2021 1:05:32 AM vs 1/1/0001 12:00:00 AM
Here’s the metadata for the new file. To find it, match File MetadataID to ID in Metadataset table, match BlocksetID to BlocksetID in BlocksetEntry table, match BlockID to ID in Block table, and open it in