How backups work

[ts678]

@lagethomas

I was wondering how these changed files and deleted files work and how to use.

I linked to the syntax, and I linked to the help which says you supply a filesystem watcher.
If you have none (which is quite likely), then it’s there in case somebody else may have it.

@kenkendk

The --changed-files option is planned to be used with a monitoring service. The idea is that “some program” (i.e. the Duplicati server) is running all the time and monitors the source directories. This monitor process then records a list of changed files, and when a backup is executed it inputs this argument to avoid the lengthy scanning process.

If you do have a filesystem monitor, then how to get it to feed the option in is the next hurdle.
–run-script-before changing options might work. Example script is on your system, and here.

@lagethomas

I am using these settings for now, they are how I managed to understand a little better.

Some are either a little risky (–auto-cleanup) or may slow the backup (–synchronous-upload).
Some are also at default value (see GUI for default), which can be good, but pointless to say.

If you like –auto-vacuum, you might consider using –auto-vacuum-interval to limit its run rate.

If the system is a bit tight on memory, –use-block-cache might make the memory load higher.