That’s good to know. Maybe the restore that didn’t need to restore 14 files also went cleanly?
Do you have any urgent need to force things back to a just-restored state? What is the need?
You can certainly attempt folder compares with WinMerge or some other tool to find changes.
Or you can probably force files back from the new area, but I’m not sure what the ideal tool is.
Possibly there’s no need to be subtle about it. Maybe just an overwrite, without any questions.
You can also get this if you checkmark-backup some deep files. Parent folders aren’t included.
This means that if the restore is from high, say at the top, intermediate folders may be created.
You can test this idea either with list/find command where files have sizes, folders end in slash
(symlinks might too), or look in database File table. -100 is a folder. If not there, it gets created.
You did this restore without permissions, unlike the first one (is that right?), so maybe a copy-over existing files would work better than a move. You might also need to get enough privilege to do so.
ACLs frequently just inherit down from above, so Duplicati may have no interesting data to restore.
Although an actual compare program is friendlier, you could try using timestamps to spot changes happened after the restore you worry about. File Explorer can do times. So can Everything search.
Duplicati itself does this to spot new and modified files, then you can decide what to do about them.
The COMPARE command
How I can see what files was added to backup?!
If you run a log-file at verbose level, it will tell you a bit more about why it decided to check out a file.
2024-03-11 07:52:30 -04 - [Verbose-Duplicati.Library.Main.Operation.Backup.FilePreFilterProcess.FileEntry-CheckFileForChanges]: Checking file for changes C:\PortableApps\Notepad++Portable\App\Notepad++64\backup\webpages.txt@2024-03-01_200051, new: False, timestamp changed: True, size changed: True, metadatachanged: True, 3/11/2024 12:54:07 AM vs 3/10/2024 8:51:04 PM