-
Notifications
You must be signed in to change notification settings - Fork 58
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
Add Backblaze B2 as remote provider #127
Conversation
7d25acc
to
3df1858
Compare
Hi @orgrim, Is Backblaze B2 remote provider something you can imagine merging into the Thanks :) |
3df1858
to
7271936
Compare
Hi, I'm currently afk for some days, I'll review the PR as soon as I can. Thanks for your patience |
Hi @orgrim, no prob, I will refactor the code in the next few days and work on the open todos. I will remove the draft when I'm finished :) |
7271936
to
72a86fa
Compare
d4655bc
to
7ba4522
Compare
Hi, so the tests run fine, I could run the docker tests locally. The docker tests are failing because github made a change on |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great PR, the code works as expected, I could test it with a B2 bucket.
If the region is not used by B2, the --b2-region
should be dropped. The --b2-endpoint
is not used in the code by it seems good to allow to configure the endpoint
c2d0695
to
4da6474
Compare
Signed-off-by: Dennis Urban ([email protected])
4da6474
to
c69a746
Compare
Hey @orgrim, is there anything else needed to get this merged? thx |
Sorry for the delay, the PR is merged. Thanks a lot for this contribution! |
Hi @orgrim ,thanks for merging. Is it possible to create a new Release with the changes? :) |
Hi, yes but I need to have a look at the CI action that fails first, I hope to do that next week |
Hi @dpunkturban , release 2.5.0 is out! |
Hi,
We use
pg_back
to back up and restore our databases to Backblaze. Currently we are using the S3 remote provider, which does not work very well with Backblaze, because sometimes backups randomly fail due to multipart upload failures. This is not a problem with pg_back, it is a problem with Backblaze (we find other tools on the internet that have exactly the same problem, such as wal-g/wal-g#1741 (comment)).To avoid these problems and to speed up backups to Backblaze, I implemented the Backblaze native protocol B2 for
pg_back
, which is insanely faster than the S3 implementation and works out of the box.Why Backblaze?
Backblaze is one of the largest blob storage backup providers, so I think it's very useful to support them. Other backup tools such as Restic also support the B2 protocol.
Todos:
pg_back.conf