To generate a new key for duplicity: gpg -expert -full-gen-key Even if there is an existing private key for the server for other purposes I prefer to keep it completely separate from the backup one.

Python3 setup.py install Encryption/GPG Key You can then get a copy of the duplicity tar.gz file, extract it and run the setup: cd /usr/local/src The following packages were required: yum install rclone python3 python36-future python3-devel gcc librsync-devel The fix for this was to install the current release of duplicity release from source. For Debian and Ubuntu this was easy enough: apt -y install rclone duplicity RHEL 7įor RHEL 7 based OS’s the duplicity release is too old and it will result in an error: InvalidBackendURL: Syntax error (port) in: rclone://dropbox:/Duplicity AFalse BNone Cdropbox: Only two packages are required, rclone and duplicity. Rclone does not encounter the same problem with the access tokens (it will use a refresh token in order to get a short lived access token) and it ended up working perfectly. I had a look at the other backends available for duplicity and found that a Rclone backend is available. This is a problem for duplicity as it requires an access token to store the backup and with the token expiring after 4 hours it is next to useless. How ever, I came across one major problem – relatively recently Dropbox made a change which removes support for “long lived access tokens”. No requirement to store all previous backups on the serverĪfter searching around for a while I came across duplicity which met all of my requirements.Only backup the data that I specifically want.Stores backups in a Dropbox application folder (so each server can have its own folder not accessible to the others).

I was looking for a backup solution for some personal servers I had a few requirements in mind:

Dropbox desktop backup