Sure! In the job run on 04th Feb., I found 72 occurrences of that search string.
They come from files in the safebrowsing folder of the used firefox profile in %userprofile%\AppData\Local .
There are additional entries for older job runs which might or might not be useful for debugging the linked issue:
2025-01-14 16:25:12 +01 - [Verbose-Duplicati.Library.Main.Operation.Backup.FilePreFilterProcess.FileEntry-CheckFileForChanges]: Checking file for changes C:\Users\user\Documents\VSCW\src\annotations\mapping.csv, new: False, timestamp changed: False, size changed: False, metadatachanged: True, 2024-08-23 5:16:09 PM vs 2024-08-23 5:16:09 PM
2025-01-14 16:25:12 +01 - [Verbose-Duplicati.Library.Main.Operation.Backup.FilePreFilterProcess.FileEntry-CheckFileForChanges]: Checking file for changes C:\Users\user\Documents\VSCW\src\annotations\exp.csv, new: False, timestamp changed: False, size changed: False, metadatachanged: True, 2024-08-23 5:16:09 PM vs 2024-08-23 5:16:09 PM
The metadatachanged detection is in so far correct, that besides the annotations folder, there is also an _annotations folder (I swap the names of both folders regularly to have different input configs for a report). The reported files in both folders are content-wise identical but had initially been duplicated from annotations to _annotations folder. Thus, their creation dates differ between the two folders. After swapping the folder names, Duplicati probably cannot know that another (yet content-wise identical) instance of each file is in the scanned annotations directory and thus assumes a metadata change. What still appears to be strange is that the same message does not occur for the files in the _annotations folder.
Even though I do not know whether the firefox related messages mentioned in the beginning are legitimate, I think they are not the (sole) cause of the performance issue. In the logs prior to the update I found comparable messages (at least for the safebrowsing folder), so at least for my installation I do not see a difference in behavior between the two Duplicati versions in that regard.
I know that this should not be the cause for a sudden performance drop after updating, but I tested today the effect of increasing the cache size to 20 MB. I’m glad to report that the processing time was hugely reduced from about 2 hours on Jan. 27 to about 40 minutes today. I will test whether increasing the cache size even more will bring me back to the processing times I was used to prior to the update.
That one could also still be verified - can you tell me which file(s) would be necessary to be excluded from AV rules? Is it the Duplicati.GUI.TrayIcon.exe?
Even though the setup is more satisfying now, let me know if there are other things I should test.
I also consider migrating to the first stable release 2.1.0.4 . Can you tell me how the upgrade path looks like for different source releases (2.0.8.1 beta & 2.1.0.2 beta)? Is there a need for or an advantage of updating incrementally? Should I follow the update instructions in the GUI? Or can I just download the stable release installer and run it, no matter which version (and from which channel) was previously installed? Should I change the release channel to “stable” prior to updating?