Can one bucket be used for multiple Mongo backup?

MongoDB Percona Operator for MongoDB
,
1

Hi, I will have a lot of Mongo instances provisioned from the operator. In the mongo CR, the backup.storages section mentions bucket, but in the operator code there is another field prefix.

So I wonder if one S3 bucket can be shared between multiple Mongo to store their backup? The path can be prefixed with the CR name for example? I don’t quite want to create one bucket for each database.

1 Like
2

Very happy to see your post, because I have the same needs
After testing, I found that the functions you need can indeed be achieved, but the operator will have some problems when deleting s3 backup. You need to comment in backup.yaml and make the operator not delete the backup in s3 when deleting the backup.
cr.yaml example:
backup:
storages:
s3-backup:
type: s3
s3:
bucket: < clusterName >
region: < s3.region >
credentialsSecret: < s3.credentialsSecret >
endpointUrl: < s3.endpointUrl >/< s3.bucketName >/< directoryName >

2 Likes
3

But the s3 bucket will keep growing right? That’s quite inconvenient.
What’s the problems does the operator have when deleting backup though?

1 Like
4

If finalizers.delete-backup is not commented in backup.yaml, the consequence of this configuration is that the operator will get stuck when deleting the backup, causing the deletion of the backup to fail.

Yes, the storage of s3 buckets will continue to increase. This is a compromise solution, because currently no matter what pxc/postgresql/mongodb operatort supports this way of use is not very friendly.
You can make a suggestion to percona about this usage requirement
Finally, look forward to percona getting better and better.

1 Like
5

Ah okay. Thanks for the information.
@Sergey_Pronin Sorry for tagging but do you think something like that will be supported?

1 Like
6

I’m not sure what the issue is.

It is possible to use one bucket with prefix:

backup:
  storages:
    my-s3:
      type: s3
      s3:
        bucket: some-bucket
        prefix: "some-prefix"
        ...

I tested and finalizer works normally with prefix. Is there any issue that you see?

1 Like