Error on progess pbm backup

MongoDB Percona Backup for MongoDB
1

Helow.
I am trying to test MongoDB backup using pbm- backup Backup fails with Error:
no progress from leader, backup metadata not found.*
I see an error message in bpm logs

get balancer status: run mongo command: (Unauthorized) not authorized on admin to execute command { _configsvrBalancerStatus: 1, lsid: { id: UUID(“2ed94c30-830-4ec8-803 9-e44eecefe182”) }, $clusterTime: { clusterTime: Timestamp(1696497792, 4), signature: { hash: BinData(0, C1D92DCCE1C8C28B991322C4D9D 01FAB41C2127E), keyId: 7246925759086854169 } }, $db: “admin”, $readPreference: { mode: “primary” } }

2

Hi @Natalya ,

PBM agents use the wrong user credentials or the user does have not enough permissions.

Ensure you have a MongoDB user with the proper roles/permissions for PBM Agent usage.
PBM Docs: Configure authentication in MongoDB.

3

Hi Dmytro,

the role and user pbmuser were created in mongod according PBM Docs: Configure authentication in MongoDB.

The following checks were performed on all primary nodes

pbm status --mongodb-uri “mongodb://pbmuser:secretpwd@localhost:27018/?ssl=false&authSource=admin”\

mongo -u pbmuser -p secretpwd --host localhost:27018 --authenticationDatabase admin

pbm tables were created in db admin all pramary nodes

pbmAgents
pbmBackups
pbmCmd
pbmConfig
pbmLock
pbmLockOp
pbmLog
pbmOpLog
pbmPITRChunks

pbm status
Cluster:

configRSinMem:

  • configRSinMem/mng10:27018 [S]: pbm-agent v2.3.0 OK
  • configRSinMem/mng11:27018 [P]: pbm-agent v2.3.0 OK
  • configRSinMem/mng12:27018 [S]: pbm-agent v2.3.0 OK
    InMemShard_1:
  • InMemShard_1/mng7:27018 [S]: pbm-agent v2.3.0 OK
  • InMemShard_1/mng8.27018 [P]: pbm-agent v2.3.0 OK
  • InMemShard_1/mng9:27018 [S]: pbm-agent v2.3.0 OK
    InMemShard_0:
  • InMemShard_0/mng4:27018 [S]: pbm-agent v2.3.0 OK
  • InMemShard_0/mng5:27018 [S]: pbm-agent v2.3.0 OK
  • InMemShard_0/mng6:27018 [P]: pbm-agent v2.3.0 OK

PITR incremental backup:

Status [OFF]

Currently running:

(none)

Backups:

FS /data/local_backups
(none)

4

Hi, @Natalya !
You’re using FS for the storage ( I suppose that it’s NFS ) so please make sure that this storage is accessible from all of the nodes of the cluster and mongod user has RW access to it