Percona for MongoDB new PBM agent version

MongoDB Percona Backup for MongoDB
1

I updated the agent to 2.4.1 and used it to create the backup. But I got an error with restore.

Starting restore 2024-05-03T06:20:56.049824035Z from '2024-05-02T13:37:33Z'
.
.Error: waiting for start: cluster failed: waiting for start: cluster failed: failed to ensure oplog file 2024-05-02T13:37:33Z/multi-sa/oplog: no such file
- Restore on replicaset "multi-sa" in state: error: failed to ensure oplog file 2024-05-02T13:37:33Z/multi-sa/oplog: no such file

As far as I can see, the structure of the backup has changed and the oplog is now in a separate folder. Can you tell me how i can to resolve this problem?

My backup is stored in an AWS s3 bucket.
This is my PBM configuration

pitr:
  enabled: false
  oplogSpanMin: 0
  compression: s2
storage:
  type: s3
  s3:
    provider: aws
    region: us-east-1
    forcePathStyle: true
    bucket: my-bucket-name
    prefix: data/pbm/backup
    credentials:
      access-key-id: '***'
      secret-access-key: '***'
    serverSideEncryption:
      sseAlgorithm: aws:kms
      kmsKeyID: mrk-29b3e420db51446290e16f6b0cbc1a2f
      sseCustomerAlgorithm: ""
      sseCustomerKey: ""
    maxUploadParts: 10000
    storageClass: STANDARD
    insecureSkipTLSVerify: false
backup:
  oplogSpanMin: 0
  compression: s2

I had a few experiments with oplog settings, but it didn’t help.

I see the previous backup and there it looked like one file

1 Like
2

@Dmytro_Zghoba maybe you can help me here too?
we are just trying to switch to backups using your service, but I just can’t finish it because of some errors =(

Or maybe someone else has encountered this problem and can advise?
I will be glad to any advice

3

Hi all. That was my fault. The version of the agent on the shards was old, but on the config server it was new. I ran tests with the new version and everything is fine now. I apologize for this post.

1 Like