I am having problems making the filters work, so I tried using the Commandline and Edit as Text options. That plus using the actual CMD test-filters option, I was able to figure out the exclude syntax. However, there is no way to save the job from within the Commandline page!
There is a button labeled
Run “backup” command now
Which threw an error and is not what I want to anyway, I just want to save it.
If you go to the “Commandline …” screen none of the changes you make there are saved. The intent of that subscreen is to make it easier to run some of the rarer commands without having to build the entire command line yourself.
You can edit filters in a text box method though. “Edit” your backup job, go to page 3 (Source Data), then expand the Filters section. On the right you’ll see a three-dot menu. You can click that and then pick “Edit as text”. Once you’re done you can go to page 5 and save your backup configuration.
You mentioned having gone to the Commandline after you couldn’t get filters to work, so what if we could get the filters to work in the GUI.
If you add an “exclude regular expression” filter in the GUI and give it this value C\:\\users\\keithdavis\\AppData\\Roaming\\Telegram Desktop\\tdata\\.* that should exclude the tdata folder from that backup job.
I’d probably just use \w\:\\users\\.*\\AppData\\.* to exclude the whole AppData folder, regardless of user or drive letter but that may exclude more than you want.
I’m a dev and a command-line person, I would much prefer to edit via a simpler interface, like Commandline. If I use the normal GUI, I have to go through all those steps each time just to add an edit filters.
Yes, I know that that works, but from posts I read on this form, “exclude folder” with this should work:
If you use `` back quote characters to surround code it will be treated as typed. The back quote key is to the left of the number 1 that is shared with the ~ symbol on a qwerty keyboard.
String surrounded \\path to nothing\\with extra slashes\\\\\\\\
Do keep in mind what drwtsn32 said previously about using the “Commandline…” option.
Knowing that a Duplicati filter for a folder on Windows ends in backslash, one adds the backslash.
Knowing that double quoting is needed to keep embedded spaces in word, one puts them outside.
The more odd Windows rule is that a backslash and a trailing double quote turns into a backslash.
You need to write a double backslash before the closing double quote to end word with backslash.
Example of what looks to me like standard Windows handling, which I think Duplicati uses as well:
C:\>ping one two\
Ping request could not find host one. Please check the name and try again.
C:\>ping "one two\"
Ping request could not find host one two". Please check the name and try again.
C:\>ping "one two\\"
Ping request could not find host one two\. Please check the name and try again.
C:\>
GUI needs no command line quoting and escaping, and Export As Command-line will add it for you.
It’s too bad GUI filter builder doesn’t work well. Double-check its work with three-dot Edit as text.