Hello, Thanks you for your response.
I’m using 2.0.3.6_canary_2018-04-23
There’s no log entry, instead I’m getting this error message after click on “Show log”: Failed to connect: SQL logic error or missing database no such table: LogData
@kenkendk (the main developer) has this to say about that message:
“That is just because the database is not yet created. Stupid error message, I know, but you can ignore it.”
Would you be able to make a 2nd backup job just pointing to a few local files and saving them to a local folder destination to see if that runs OK? If it doesn’t, then it’s possible there was a problem when Duplicati was installed.
Now I completely uninstalled my Duplicati installation and installed the new version 2.0.3.7_canary_2018-06-17. But the same error happens again: Error while running _Testfiles von C auf D --> ".*xyz.*[^\]" wird analysiert - Nicht abgeschlossener []-Satz.
Yes, I created a test backup job (see attached export file).There’s no log if this error happens because the job simply doesn’t start at all. There’s only a line in the export file that says: LastErrorMessage": "\".*xyz.*[^\\]\" wird analysiert - Nicht abgeschlossener []-Satz.
It seems there’s a slight confusion and erroneous behaviour in the filter settings:
Setting “Exclude files whose name contain”: Doesn’t work at all – see above error.
Setting “Exclude file” works, BUT it also filters FOLDERS, not only files.
If I set “Exclude file” to an example like “*xyz*” and save the job, it automatically changes to “Exclude expression”.
Thanks for the config export. I used it to import a new job and am able to get the same error you are getting.
If you change the exclude filter to be an “Exclude expression” of *xyz* (so in “Edit as text” it looks like -*xyz*) does it do what you want?
Note that I can confirm changing the filters on one of my jobs to be “Exclude files whose name contain” with xyz ( so in “Edit as text” it looks like -[.*xyz.*[^\]]) it also causes the error you are seeing so I have flagged this topic as #bug.
@kenkendk, are you aware of any changes to the Filters that might be causing this issue?
It didn’t happen in my tests, but I suspect #2 (“Exclude file” also excludes folders) would be considered a bug based on the the Filter documentation (Filters - Duplicati 2 User’s Manual) stating that “Folder names always end with a slash”.
For #3 (“Exclude file” with wildcards changed to “Exclude express”), I believe that is by design - once you’ve added a wildcard it is considered an expression so has to be parsed differently.
the generated regular expression is invalid. [^] escapes the ] which is then missing - this is correctly diagnosed by the error message. Use [^\] (escape the ) or use [^]] (which is not what you want - looks for no ] at end of name]
I think the forum software ate some of your text (it has its own backslash processing) so let me put the whole entry from you inside backticks. I think this is what you meant, and it makes sense to me as well.
the generated regular expression is invalid. [^\] escapes the ] which is then missing - this is correctly diagnosed by the error message. Use [^\\] (escape the \) or use [^\]] (which is not what you want - looks for no ] at end of name]
Here’s Google Translate of the original error message:
". * xyz. * [^ \]" is being analyzed - Unfinished [] sentence.