why was support for backups to s3 dropped?

Asked by Paul Coleman

I've been happily using Deja Dup to backup my files to S3. Today's automated backup failed and the gui displayed a message saying "this storage location is no longer supported".

I wandered around the deja dup change log and discovered that support for backups to S3 was intentionally dropped, but I couldn't find the reason behind the decision to drop support.

Why was support for backups to S3 dropped?

S3 is a solution that works very well for me.

Question information

Language:
English Edit question
Status:
Solved
For:
Déjà Dup Edit question
Assignee:
No assignee Edit question
Solved by:
Michael Terry
Solved:
Last query:
Last reply:
Revision history for this message
Best Michael Terry (mterry) said :
#1

Hello! I did indeed remove S3 support in a recent development build [1].

Around 3 years ago, I deprecated the more "techy" cloud backends. This meant that those cloud options would not be shown in the UI by default unless you were already using them.

The intention was to focus on consumer-oriented cloud services (Amazon Drive not S3, Google Drive not GCS, etc). This matches Deja Dup's focus on being friendly and easy to use. The policy is described here:

https://wiki.gnome.org/Apps/DejaDup/Clouds

Recently, I redesigned the UI for Deja Dup. And I figured it was time to stop maintaining that code, rather than support it in the new UI.

You can always use duplicity directly to still access your backup.

[1] Those are more designed for testing than use by actual deja-dup users though. How did you install deja-dup?

Revision history for this message
Paul Coleman (brian549) said :
#2

Michael, thanks for responding so quickly.

Deja-dup has worked very well for me for many years. Thank you for writing it.

I'll find another solution -- either using a script or commercial solution.

Cheers!

Revision history for this message
Paul Coleman (brian549) said :
#3

To answer your question [1]:

I'm using the deja-dup package in Fedora 32.