duplicity vs Back In Time

Data is encrypted locally before being sent, and kept encrypted by a key that is never stored on the remote machine. So you might even store your data on a public space, people would still need your key or brute force it.

Duplicity uses the rsync algorithm so only the changed parts of files are sent to the archive when doing an incremental backup. For instance, if a long log file increases by just a few lines of text, a small diff will be sent to and saved in the archive. Other backup programs may save a complete copy of the file.

You can retrieve older versions or files you recently deleted locally even after having updated your backup.

Licensed under GNU GPL v2.

Duplicity does not make many demands on its archive server. As long as files can be saved to, read from, listed, and deleted from a location, that location can be used as a duplicity backend. Besides increasing choice for the user, it can make a server more secure, as clients only require minimal access.

Docker allows to run programs on any Linux without having to really install them, and allows to manage versions so it runs exactly the same on different machines.

Although highly customizable, Back in Time is also suited for people who want an easy tool to use that will back up their data. You can use BiT simply by configuring where to save snapshots, what folders to backup and when to do it.

Almost all functionality of the program can be customized. It's possible to set when snapshot get removed based on age, available disk space, quantity in a set time period, you can include and exclude files, folders and filetypes, you can defer backups when on battery power, you can ignore errors, you can preserve ACL, extended attributes and so on.