Is Backblaze S3 storage supported?

MongoDB Percona Backup for MongoDB
1

Hi,

Not having much luck trying to use backblaze s3 as the storage backend. My config:

storage:
  type: s3
  s3:
    provider: aws
    region: eu-XXX-XXX
    bucket: {{my_bucket_id}}
    endpointUrl: https://s3.eu-XXX-XXX.backblazeb2.com
    debugLogLevels: EventStreamBody
    prefix: backups
    credentials:
      access-key-id: {{my_id}}
      secret-access-key: {{my_key}}
    retryer:
      numMaxRetries: 3
      minRetryDelay: 30
      maxRetryDelay: 5
pitr:
  enabled: false

This results in, from pbm log:

2022-11-22T12:48:15Z E [rs0/mongo:27017] [agentCheckup] check storage connection: storage: no init file, attempt to create failed: upload to S3: NoSuchBucket: The specified bucket does not exist: my_bucket_id
	status code: 404, request id: e7b379ac83590103, host id: adf5uoms/bmRvI3f3btw=
1 Like
2

Have you created this bucket?

1 Like
3

I am sucessfully using Backblaze S3, the only issue I had, was to tweak Retryer configuration as Backblaze sometimes fails with “ServiceUnavailable: no tomes available”

log says it can’t find your bucket, may be there is a typo?
I followed steps in Set up and configure - Percona Backup for MongoDB

my current pbm config shows:

pitr:
  enabled: true
  oplogSpanMin: 10
  compression: s2
storage:
  type: s3
  s3:
    provider: aws
    region: us-XXXX-XXX
    endpointUrl: https://s3.us-XXXXX-XXX.backblazeb2.com
    bucket: xxxxxx-xxxx-rs0
    prefix: data/pbm/backup
    credentials:
      access-key-id: '***'
      secret-access-key: '***'
    insecureSkipTLSVerify: false
    retryer:
      numMaxRetries: 20
      minRetryDelay: 3s
      maxRetryDelay: 5m0s
1 Like
4

for bucket you have:

bucket: xxxxxx-xxxx-rs0

For this value I just copied the “Bucket ID” from Backblaze. Just a string of letters and numbers. But I see you have -rs0 on the end. Is this your Bucket Unique Name?

I also tried this - {bucketid}-mongodb-rc-test but it did not work also. Is that because my unique name has hyphens in it?

1 Like
5

ok solved it, i needed to put the bucket unique name, not bucket ID

2 Likes