- Are filters required? What I mean is, if no filters are provided in either .duplicacy/filters file or on command line will the default be to include all dirs/files recursively in the repository?
- Given the following filters contents:
Does this imply that all contents and all children dirs recursively under ,subdir> will be backed up? What if / is later added following intial backup? Will its contents also be recursively backed up even if filters is not modified?
Not sure what you meant by
if / is later added following intial backup?.
- If they are required, what is the simplest way to achieve the described behavior mentioned above? It seems like adding every single path including parents could become quite cumbersome and error prone - especially if you forget to modify filters every time you add a new dir!
I would suggest using exclude patterns instead. Only exclude certain subdirectories that you don’t want to back up, so new dirs will be included by default.
- Once you have init-ed a repository and run a backup, what command can you use to list all files contained in a specified dir from the repository? the history command appears to allow me to show info for a given dir, but there does not appear to be a way to show similar information for the dir contents?
You can run the list command and then filter the output:
duplicacy list -files | grep path/to/some/dir
- Similarly, what command would you use to restore, for example, a given repository subdir and all of its contents recursively?
restore takes exclude/include patterns as arguments:
duplicacy restore -r 1 -- +/subdir* -*
- If I have a rather large repository that I anticipate will take many days, perhaps weeks, to complete the initial backup, what happens if that initial backup is interrupted - perhaps an unanticipated power loss or required system reboot - before the initial backup is completed? Will it have to start all over? Will it recover gracefully? Any important command options to include or special commands to use with this in mind?
An initial backup can be fast-resumed. You can try it yourself.
- It appears as if the global options must appear before the command (backup, history, etc), while the non-global options follow the command. Is that correct? I was surprised to see that order mattered this much?
That is right.
- When using the -background option, it is possible to query where the credentials are coming from/stored? Is it possible to remove them? Update them?
The -background option was mainly designed for the GUI version. The recommended way to force reentering passwords is to run
duplicacy list -reset-passwords.