Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backblaze B2 backend #2

Closed
prologic opened this issue Aug 31, 2017 · 5 comments
Closed

Backblaze B2 backend #2

prologic opened this issue Aug 31, 2017 · 5 comments

Comments

@prologic
Copy link

So you don't forget :D -- I'll be more than happy to test this out!

Also consider re-using rclone which has backends for many more cloud storage providers.

@someone1
Copy link
Owner

someone1 commented Sep 5, 2017

Thanks for the tip, I had forgotten about that project. I noticed that the author chose not to utilize the hash verification upon upload (at least from my quick perusal of the S3 and GCS implementations). This would not make it an ideal candidate to use directly, but you can probably get away with using the supported file:// target in this project to point to a mounted path from rclone (e.g. using their FUSE mounting feature). I haven't tested this myself but I'd assume it should work?

@prologic
Copy link
Author

prologic commented Sep 5, 2017 via email

@someone1
Copy link
Owner

someone1 commented Sep 6, 2017

I'd be using the integration to b2 using this project: https://github.com/kurin/blazer

The project appears to be doing a good job integrating using BackBlaze's integration checklist, which is the best I could ask for other than an SDK from BackBlaze themselves.

Generally, I don't write any API integrations with a target cloud provider I'm working on integrating to the application. My integrations more/less just use the SDKs available from the cloud provider which implement best practices for integrating against their own services, this includes retry/backoff logic, resumeable or multipart upload logic, etc. I write simple wrappers for coordinating the uploads with the rest of the backup/restore processes and options passed by the user (e.g. max parallel uploads) and do my research to ensure I utilize all options available for a resilient and verified upload/download.

I'll hopefully have something in the next day or two for you to test! I'm sure you're already aware of this, but this sort of backup is block-level, not file-level like Crashplan is.

@someone1
Copy link
Owner

someone1 commented Sep 8, 2017

Release for B2 has been added with the latest release: https://github.com/someone1/zfsbackup-go/releases/tag/v0.3-rc1

Please give it a go and let me know what you think!

@someone1 someone1 closed this as completed Sep 8, 2017
@prologic
Copy link
Author

prologic commented Sep 8, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants