-
Notifications
You must be signed in to change notification settings - Fork 5
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
try out BackBlaze integration #270
Comments
I created a trial account for us to test with. Credentials and an application key are in our password manager. I created a "mediacloud-test" bucket to use for testing. BackBlaze does have a S3-compatible API. |
Doesn't look like Dokku supports multiple backup destinations. See the postgres plugin docs and an open enhancement issue requesting this features. |
Decided to try out BackBlaze via either (a) daily RSS file posting or (b) daily archive WARCs. |
Opened PR to allow archiver to write to both S3 and B2 at same time, and to support both s3://bucket/prefix and b2://bucket/prefix command line arguments to Queuer subclasses: #279 Needed:
|
Was able to use dokku |
Looking out for backblaze pitfalls, I went looking for API rate limits. Answer is hazy:
A backblaze person made it clear they don't publish any limit:
|
Update: switching RSS portgres backups to B2 from S3 |
Closing as done. Other switches will be their own issues. |
Initial calculations show switching some offsite backups to BackBlaze could save 60-70% of ongoing monthly storage costs. We need to test it out to see how it performs on something low-risk and redundant. Candidates:
This requires:
(split off from #260)
The text was updated successfully, but these errors were encountered: