-
Notifications
You must be signed in to change notification settings - Fork 43
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
Comments
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 |
Probably :) I just didn't want you to have to spend too much time
reinventig wheels; borrow from their code :)
I'm okay with zfsbackup-go growing it's own b2 backend as long as its
reliable.
I'm going ot be using this thing to replace my crashplan setup from my ZFS
NAS (ZOL/ZFSOnLinux)
|
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. |
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! |
Wil ldo! Thanks!
James Mills / prologic
E: prologic@shortcircuit.net.au
W: prologic.shortcircuit.net.au
…On Fri, Sep 8, 2017 at 4:35 PM, Prateek Malhotra ***@***.***> wrote:
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!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABOv-pWqacn6YL2IoVVxogWW4cHDyDoHks5sgc8xgaJpZM4PIN1q>
.
|
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.
The text was updated successfully, but these errors were encountered: