My spider sense is saying no, since the files do not exist any more on the client. I find it highly unlikely that the files giving us trouble are some kind of superhidden system files or similar, as the file names indicate that they are of the same type as files we can see in the same root folder.
I don’t know if this image is relevant or not, but on the left is the client folder in question that has not been touched since the March 8, on the right, an image of the resulting backup from March 22
What is interesting is that there are a number of folders that exist in the backup directory that are not present on the client, and the backup complains that it cannot find a number of files that are not present on the client, for instance:
Error getting complete file "1BwqRFofRk1lurv1eXp4|D/Profiler/PeterG.V6/AppData/Roaming/Mozilla/Firefox/Profiles/rsftfmm7.default/storage/default/https+++www.youtube.com/idb/1131144353LCo7g%sCD7a%tda2bdads.sqlite" from Radio1. Errorcode: CANNOT_OPEN_FILE (3)
This was an incremental backup, but not a resumed incremental backup. One thing that struck me was to test a full backup, I don’t know if this is a coincidence or not (the warning reported is most likely unrelated, the inability to remove a temporary backup folder from the server):
But I more and more suspect that there might be an issue related to persistence with incremental backups, even though it might need very special circumstances for it to show. I can’t find any other reasonable explanation right now at least.
Best regards
Alexander