Timeout error while Taking PBM Backup

1

Hi Team,

We have recently upgrade PBM to 2.9.1 version but looks like ‘backup.timeouts.startingStatus“ doesn’t support anymore.

[root@ANVGAPDSIPMA02 yamlFiles]# pbm config --list
pitr:
enabled: false
oplogSpanMin: 10
compression: gzip
compressionLevel: 0
storage:
type: s3
s3:
provider: aws
region: us-east-1
bucket: mongo-db-prod
prefix: pbm/backup/petro-prod
credentials:
access-key-id: ‘’
secret-access-key: '’
maxUploadParts: 10000
storageClass: STANDARD
insecureSkipTLSVerify: false
backup:
compression: gzip
compressionLevel: 0
[root@ANVGAPDSIPMA02 yamlFiles]# pbm config --set backup.timeouts.startingStatus=14400
Error: set backup.timeouts.startingStatus: invalid config key
[root@ANVGAPDSIPMA02 yamlFiles]#

Backups:

S3 us-east-1 s3://mongo-db-prod/pbm/backup/petro-prod
Snapshots:
2025-08-20T12:36:06Z 0.00B <incremental, base> [ERROR: couldn’t get response from all shards: convergeClusterWithTimeout: 33s: reached converge timeout] [2025-08-20T12:36:41Z]

Backup Size is ~10TB.

Please suggest.

Thanks,

Sumit

2

Hi, check logs of pbm-agent on all servers for clues

3

Where can i find all the properties are available with PBM 2.9.1 similar like “backup.timeouts.startingStatus “.

Looks like documents mentioned very limited.

Thanks,

Sumit

4

I tried the same in 2.10.0 and it worked:

[mongodb@7b183bd46d8c /]$ pbm config --set backup.timeouts.startingStatus=14400
[backup.timeouts.startingStatus=14400]
[mongodb@7b183bd46d8c /]$ pbm config --list
storage:
  type: s3
  s3:
    region: us-east-1
    endpointUrl: http://minio:9000
    forcePathStyle: true
    bucket: mongo-backups
    prefix: rs01
    credentials:
      access-key-id: '***'
      secret-access-key: '***'
    maxUploadParts: 10000
    storageClass: STANDARD
    insecureSkipTLSVerify: false
pitr:
  enabled: false
  compression: s2
backup:
  oplogSpanMin: 0
  timeouts:
    startingStatus: 14400
  compression: s2
restore: {}
[mongodb@7b183bd46d8c /]$ pbm version
Version:   2.10.0

can you try that version?

5

Hi,

I upgraded o 2.10.o and it worked. Thansk for Suggestion.

So, I assume 2.9.0 is no longer reliable to use.

Thanks,

Sumit