Backup to Amazon S3 with Duplicity
- Duplicity creates tar archives encrypted with GPG.
- Duplicity uses rsync to create the tar archives.
- Duplicity’s power comes from it’s ability to create backups stored on Amazon S3 Buckets.
- Duplicity is available from Available from the [http://fedoraproject.org/wiki/EPEL EPEL Repository]
- Python-Boto is available from the [http://wiki.centos.org/AdditionalResources/Repositories CentOS-Extras Repository]
- GPG (GnuPG) is available from the [http://wiki.centos.org/AdditionalResources/Repositories CentOS-Extras Repository]
Setup GPG if you have not already
- You can generate a new key for your backups, or import existing GPG keys.
Generate a GPG Key
Export an existing key
- The key will be listed according to the bits and the 8-bit hex code
- Specify the 8-bit hex id of the key you want to export: 3977EFB8
Import an existing key to use for the backups
- You need to validate the key to use it.
- Edit the key and use the trust command.
Duplicity Backup Commands
full: full backup even if previous signatures exist
incremental: files changed since the previous signature
verify: log a message for every file that has changed
restore: restore files
Backup to S3 Test
Create a directory and file(s) to backup
Run the Duplicity Backup Test
Look for the Duplicity Backups on Amazon S3
Duplicity Error: There is no assurance this key belongs to the named user
- Solved by validating the key with command: gpg –edit 5693592F