# Error: wait for backup status: backup stuck at "starting" status, last heartbeat: 1783492554

**URL:** <https://forums.percona.com/t/error-wait-for-backup-status-backup-stuck-at-starting-status-last-heartbeat-1783492554/41037>\
**Category:** Percona Backup for MongoDB\
**Created:** [July 8, 2026, 6:56am UTC](https://forums.percona.com/t/error-wait-for-backup-status-backup-stuck-at-starting-status-last-heartbeat-1783492554/41037 "2026-07-08T06:56:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bacnt2](https://avatars.discourse-cdn.com/v4/letter/b/3be4f8/32.png) [@bacnt2](https://forums.percona.com/u/bacnt2)\
**Post date:** [July 8, 2026, 6:56am UTC](https://forums.percona.com/t/error-wait-for-backup-status-backup-stuck-at-starting-status-last-heartbeat-1783492554/41037/1 "2026-07-08T06:56:33Z")

</div>

Hi everyone,  
I use PBM to create backups in MongoDB community 8.0.24 and usually got this error:  
`[root@mongo-transaction-observation-01 ~]# pbm backup`  
`Starting backup "2026-07-08T06:35:31Z"............................................`  
`Error: wait for backup status: backup stuck at "starting" status, last heartbeat: 1783492554`

This is my PBM congfig:  
`storage:`  
`type: filesystem`  
`filesystem:`  
`path: /backup/`  
`pitr:`  
`enabled: false`  
`compression: s2`  
`backup:`  
`oplogSpanMin: 0`  
`timeouts:`  
`startingStatus: 600`  
`compression: s2`  
`restore:`  
`batchSize: 500`  
`numInsertionWorkers: 10`  
`numParallelCollections: 10`

And the logs:  
`2026-07-08T06:35:41Z I [tran_ob/mongo-transaction-observation-03:27017] got command backup [name: 2026-07-08T06:35:31Z, compression: s2 (level: default)] <ts: 1783492531>, opid: 6a4defb328aa87118f6ee293`  
`2026-07-08T06:35:41Z I [tran_ob/mongo-transaction-observation-01:27017] got command backup [name: 2026-07-08T06:35:31Z, compression: s2 (level: default)] <ts: 1783492531>, opid: 6a4defb328aa87118f6ee293`  
`2026-07-08T06:35:41Z I [tran_ob/mongo-transaction-observation-02:27017] got command backup [name: 2026-07-08T06:35:31Z, compression: s2 (level: default)] <ts: 1783492531>, opid: 6a4defb328aa87118f6ee293`  
`2026-07-08T06:35:50Z I [tran_ob/mongo-transaction-observation-02:27017] got epoch {1783482399 20}`  
`2026-07-08T06:35:50Z I [tran_ob/mongo-transaction-observation-01:27017] got epoch {1783482399 20}`  
`2026-07-08T06:35:50Z I [tran_ob/mongo-transaction-observation-03:27017] got epoch {1783482399 20}`

Can you guys tell me what are the problems and how to resolve it?

---

<div class="post-metadata">

**Author:** ![Ivan\_Groenewold](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ivan_groenewold/32/6299_2.png) [@Ivan\_Groenewold](https://forums.percona.com/u/Ivan_Groenewold)\
**Post date:** [July 10, 2026, 12:24pm UTC](https://forums.percona.com/t/error-wait-for-backup-status-backup-stuck-at-starting-status-last-heartbeat-1783492554/41037/2 "2026-07-10T12:24:49Z")

</div>

Hi, do you have a shared filesystem configured so all your replica set nodes see the same /backup ? (e.g. NFS) other than that, please check for clues on each node:

```auto
journalctl -u ppm-agent 

```