add backblaze's B2 cloud storage as backup destination

Bug #1523520 reported by wcchandler on 2015-12-07
120
This bug affects 24 people
Affects Status Importance Assigned to Milestone
Déjà Dup
Undecided
Unassigned

Bug Description

FEATURE REQUEST
======================

Under storage location, please add backblaze's B2 service. Support has been added to duplicity as of version 0.7.06 as reported by this bug: https://bugs.launchpad.net/duplicity/+bug/1498877

Alexey Zagarin (zagarin) wrote :

Hi,

I've made the patch to support B2 Cloud Storage. It works for me. However, further testing needed. Please, review and consider merging.

Erik Entrich (eentrich) wrote :

I just tested your patch, and the initial backup seems to work correctly until it suddenly switches from "Backing up" to "Cleaning up" and deletes everything uploaded so far after which it starts over from the beginning.
I'm not sure if this is a problem with duplicity or deja-dup, so I'm going to retry the backup with just duplicity. It might take a while to replicate the error though since the backup ran fine for around 2 days before it occurred.

Alexey Zagarin (zagarin) wrote :

There were improvements in duplicity regarding B2 backend since v0.7.6 so you may try to build it from git. I didn't hit the behavior you described even with v0.7.6, but had other issues so I suggest you update duplicity first.

Alexey Zagarin (zagarin) wrote :

This bug https://bugs.launchpad.net/duplicity/+bug/1529883 in particular prevented the successful backup in my case.

Erik Entrich (eentrich) wrote :

Thank you, I'll try that and do more tests using duplicity directly!

Erik Entrich (eentrich) wrote :

I finally got around to testing it with the release version of duplicity 0.7.7, and it worked well until the very end of the initial backup when it decided to delete all my uploaded files again. I'm not sure what happened since the backup had been running flawlessly for around 8 days at that point and I wasn't watching it. I stopped the backup a few times in between but it always resumed without problems.

I could see from the console output that there was an error message after it uploaded the last file, but when I tried copying it my terminal crashed... It contained an error about a missing file the message "This might be a bug", but I couldn't find any info about that online.

I tried recreating the error with smaller directories, but it worked without any problems.

I know is is probably a duplicity bug, but is there any way to make deja-dup not delete the entire backup when an error happens? I would hate for to lose my entire backups in a year or so just because uploading a file failed or something like that.

Marcos Alano (mhalano) wrote :

eentrich,

Could you test with Duplicity 0.7.08 and check if bug remains?

Thanks.

Erik Purins (epu) wrote :

I rebuilt with patch applied to rev 1563, with duplicity 0.7.09 installed first in PATH, and can enter B2 storage information (but not application key) into the dialog. When I try to connect, I am prompted for my B2 account information and application key. I entered them, and saved them using the remember checkbox. When I go to run a backup immediately, I get a Backup Failed dialog, with "FatalBackendException: Bucket cannot be created". This happens whether or not the named bucket and folder exist.

I'm not sure how to begin debugging the application. If it will help, you can contact me via e-mail and I can gather more information.

Michael Terry (mterry) wrote :

If support gets added to GNOME Online Accounts for B2, I'll add it to deja-dup too. But I'm trying to avoid adding new custom duplicity backend supports to deja-dup.

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

Changed in deja-dup:
status: New → Won't Fix
step21 (step22) wrote :

Sorry, but how does this make sense? This basically makes deja-dup useless, especially if also deprecating S3 etc. Services like Google Drive and Nextcloud which you (and GOA) seem to be focused on are not well suited to handle proper backups in my experience. And if going by https://wiki.gnome.org/Projects/GnomeOnlineAccounts/Providers is any indication, you might as well change "when Gnome Online Accounts adds support" to "never" as they only seem to support very end-user focused services.

Michael Terry (mterry) wrote :

I hear what you're saying. But (A) S3 support hasn't been removed and there are no plans to do so right now. And (B) Deja Dup has always been meant for more casual users that wouldn't otherwise make a backup. So we share GOA's end-user focus. (I've long wished our default cloud backup was easier to set up than S3 is.) There are plenty of other more advanced backup solutions for advanced users.

step21 (step22) wrote :

Thanks for still replying :) It has not, but it looks like it will be at one point. My point is that even as a maybe not-so casual user, I would still like a nice interface for my backup, especially as this (like for many users) makes it much more likely for me to actually do backups. Sure I can use rclone or duplicity directly but it's super annoying especially if you have to automate it. I do not mind the 'default' solution being somethign else (like dropbox?) or for a long time I have used it for local backup to an external drive. But now that better online options are available, it seems too focused on one specific audience if I cannot use those, especially with duplicity suporting them and somebody already having supplied/started a patch. And no, there are not really many options available, especially if you like a GUI now and then. Sure I could figure out how to set up duplicity or rclone via a cron job or something, but that is much more annoying and probably unreliable, especially on a laptop. Then there are enterprise systems but they are mostly proprietary and well, focused on enterprise. So I really think there should be some middle ground, especially with a nice DE like Gnome.

Michael Terry (mterry) wrote :

Yeah, I hear ya. But I have limited resources and my own focus is on the casual end.

Plus, restricting it to gvfs-supported backends lets us do fun stuff like calculate how much space the backup folder is taking up or actually know whether we will be able to connect through the vpn or weird network setups, etc.

So there is a real cost to supporting new backends. I'd consider a patch for an advanced mode that allowed arbitrary duplicity backends, but it would have to be carefully done (duplicity backends are very idiosyncratic) and come with sufficient warnings about not having all features/poor support/etc.

step21 (step22) wrote :

Sure. I might actually think about doing a patch like this, though no idea about a timetable.
At least it seems to be easier than adding backends to gvfs/goa.
The simplest duplicity backend would probably be something like vuplicity does/did (https://github.com/johansatge/vuplicity) where basically you just compose the terminal command. ;) Though I do not mean to advocate that as a good idea...

Wizek (123-wizek) wrote :

Whoops, sorry about changing the 'information type' field. It was an accidental miss-click, and I hope I was able to undo the change fully (I'm not very familiar with launchpad for the moment).

information type: Public → Public Security
information type: Public Security → Public
Michael (sparks305) wrote :

Please add support for B2 as a destination!!!!!!!!!!!!!!!

Thomas HERON (thomas-heron) wrote :

Please add support for B2 as a destination.

Alan (alanbix) wrote :

Please add support for B2 as a destination.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Patches