-
Notifications
You must be signed in to change notification settings - Fork 203
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
Backups to Cloudflare R2 (S3 Compatible) storage fail #954
Comments
Just an update here, I had "snappy" compression enabled for my base backups however once I changed the settings to use no compression the backups have succeeded so far. Other backups of very small databases seem OK (ie < 100MB) but this one uncompressed is about 600MB |
the same problem on R2 |
Could this be related to this issue: #957 We support S3-compatible object stores, and though providers outside AWS claim 100% compatibility, as you can see in the case of Linode, it's not always fully compatible. It would be good to check this for anything Cloudflare doesn't yet support. |
@andrewheberle @maxpain were you able to solve this, if you are using CNPG, with the suggestion in comment #957 (comment) ? |
Did you get that working in the end? I'm seeing the following error:
Config is:
|
I disabled compression for my full backups, which without looking at the code, I assume all means the parts in the multi part upload (except the last) are all the same size… I had a look at the documentation that Cloudflare publish about their S3 API compatibility and couldn’t see that they don’t properly implement multi-part uploads, but I did see they don’t support the headers related to server side encryption, but I’ve not tested this. |
Got it working. A wrong secret reported |
I'm backing up to S3 compatible storage (Cloudflare R2) from Cloud Native PG (CNPG) which uses barman-cloud-backup.
Backups are failing with an error of:
ERROR: Upload error: An error occurred (InvalidPart) when calling the CompleteMultipartUpload operation: All non-trailing parts must have the same length. (worker 1)
The above error is surfaced from barman-cloud-backup when attempting to complete the weekly full backup.
I've come across what seems like a similar issue when using Cloudflare R2 as a backend for a Docker registry that was resolved by setting a fixed chunk size for multipart uploads, however I don't know enough about the barman codebase to know if this is the same issue.
https://community.cloudflare.com/t/all-non-trailing-parts-must-have-the-same-length/552190/7
And this discussion here:
distribution/distribution#3940 (comment)
The text was updated successfully, but these errors were encountered: