mirror of
https://github.com/kees-z/DuplicatiDocs.git
synced 2025-04-26 15:02:28 +00:00
Update section on filters to talk about filter groups.
Also added some more examples and moved things around, hopefully in a way that makes things clearer.
This commit is contained in:
parent
58dd3daba4
commit
f895050314
@ -7,7 +7,7 @@ Duplicati 2.0 can include or exclude files and folders from your backup based on
|
|||||||
|
|
||||||
Duplicati's filter engine processes folders first then files. The reason for that behavior is performance. If a folder is excluded from a backup, the files inside that folder don't have to be processed anymore.
|
Duplicati's filter engine processes folders first then files. The reason for that behavior is performance. If a folder is excluded from a backup, the files inside that folder don't have to be processed anymore.
|
||||||
|
|
||||||
When filter rules have been defined the first folder is taken and the filter rules are processed one by one. The first rule that matches is applied and the following rules are not processed anymore. For instance, if the first rule excludes a folder, then this folder and all files within will be excluded from the backup even if following rules include this folder or its files.
|
When filter rules have been defined the first folder is taken and the filter rules are processed one by one. The first rule that matches is applied and the following rules are not processed anymore. For instance, if the first rule excludes a folder, then this folder and all files within will be excluded from the backup even if following rules include this folder or its files. Likewise, if the first rule includes a folder, then it will be included even if a following rule would exclude it.
|
||||||
|
|
||||||
It is recommended to write folder rules first and file rules afterwards. That way rules are written in the same order as they will be effective when Duplicati processes them and Duplicati's filters are easier to understand that way.
|
It is recommended to write folder rules first and file rules afterwards. That way rules are written in the same order as they will be effective when Duplicati processes them and Duplicati's filters are easier to understand that way.
|
||||||
|
|
||||||
@ -15,11 +15,41 @@ Per default, all files and folders will be backed up. That means, if no rule mat
|
|||||||
|
|
||||||
### Syntax
|
### Syntax
|
||||||
|
|
||||||
If you want to use file globbing to specify rules, `?` and `*` are allowed placeholders. `?` matches any single character. `*` specifies none or multiple characters. Rules can also be specified as regular expression. In this case put the regular expression (using .NET syntax) into hard brackets `[]`. Folder names always end with a slash `/` on Linux or Mac and a backslash `\` on Windows. For instance, `log` is a file, `log/` is a folder. In the UI a rule to include is started with a `+`, a rule to exclude is started with a `-`. Using the command-line there are specific settings to specify include or exclude rules. These are `--include` and `--exclude`. Using the command-line various rules can be specified using `--include` or `--exclude` repeatedly.
|
Folder names always end with a slash `/` on Linux or Mac and a backslash `\` on Windows. For instance, `log` is a file, `log/` is a folder.
|
||||||
|
|
||||||
|
If you want to use file globbing to specify rules, `?` and `*` are allowed placeholders. `?` matches any single character. `*` specifies none or multiple characters. For example, `*.txt` would specify all `.txt` files.
|
||||||
|
|
||||||
|
Rules can also be specified as regular expression. In this case put the regular expression (using [.NET syntax](https://docs.microsoft.com/en-us/dotnet/standard/base-types/regular-expression-language-quick-reference)) into hard brackets `[]`. For example, `[.*/IMG_\d{4}\.jpg]` would specify all files named `IMG_0000.jpg` through `IMG_9999.jpg`.
|
||||||
|
|
||||||
|
Duplicati also has several built-in filter groups, which define set of well-known files and folders for different operating systems. These can be specified by putting the names or aliases of the desired groups inside curly brackets `{}` separated by commas `,`, for example, `{SystemFiles,OperatingSystem}`. The following groups are currently defined:
|
||||||
|
|
||||||
|
- **SystemFiles**
|
||||||
|
Files and paths that are owned by the operating system or are not real files.
|
||||||
|
For example, `System Volume Information` on Windows and `/proc/` on Linux.
|
||||||
|
- **OperatingSystem**
|
||||||
|
Files and folders that are normally part of the operating system.
|
||||||
|
For example, `C:\Windows` on Windows and `/bin/` on Linux.
|
||||||
|
- **CacheFiles**
|
||||||
|
Files and folders that are known to be cache locations.
|
||||||
|
For example, Google Chrome and Firefox web caches.
|
||||||
|
- **TemporaryFiles**
|
||||||
|
Files and folders that are temporary.
|
||||||
|
For example, the recycle bin on Windows and `/tmp/` on Linux.
|
||||||
|
- **Applications**
|
||||||
|
Files and folders that are application binaries (i.e., installed programs).
|
||||||
|
For example, `C:\Program Files` on Windows and `/lib/` on Linux.
|
||||||
|
- **DefaultExcludes**
|
||||||
|
Meta group which contains all groups that are commonly excluded, which is currently all other groups.
|
||||||
|
|
||||||
|
### Using filters
|
||||||
|
|
||||||
|
In the UI, filters can be created using drop down boxes for common rule types. More advanced users can also use a textbox to specify multiple rules, with a rules to include starting with `+` and rules to exclude starting with `-`.
|
||||||
|
|
||||||
|
Using the command-line there are specific settings to specify include or exclude rules. These are `--include` and `--exclude`. Multiple rules can be specified by using `--include` or `--exclude` repeatedly.
|
||||||
|
|
||||||
### Settings
|
### Settings
|
||||||
|
|
||||||
Besides filter rules there are settings that can exclude specific files by their attributes. Those settings are `--skip-files-larger-than` and `--exclude-files-attributes`. The latter is able to exclude files that have any of the following attributes: ReadOnly, Hidden, System, Directory, Archive, Device, Normal, Temporary. Those settings are applied to all files of the backup.
|
Besides filter rules there are settings that can exclude specific files by their attributes. Those settings are `--skip-files-larger-than` and `--exclude-files-attributes`. The latter is able to exclude files that have any of the following attributes: `ReadOnly`, `Hidden`, `System`, `Directory`, `Archive`, `Device`, `Normal`, `Temporary`. Those settings are applied to all files of the backup.
|
||||||
|
|
||||||
### Common use cases
|
### Common use cases
|
||||||
|
|
||||||
|
Loading…
x
Reference in New Issue
Block a user