# Cannot restore from incremental backup.PBM and PSMDB in the same pod **URL:** \ **Category:** Percona Backup for MongoDB\ **Tags:** percona, mongodb, pbm\ **Created:** [January 26, 2024, 9:42am UTC](https://forums.percona.com/t/cannot-restore-from-incremental-backup-pbm-and-psmdb-in-the-same-pod/28041 "2024-01-26T09:42:53Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Dmytro\_Zghoba](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/dmytro_zghoba/32/4721_2.png) [@Dmytro\_Zghoba](https://forums.percona.com/u/Dmytro_Zghoba)\ **Post date:** [January 26, 2024, 10:34am UTC](https://forums.percona.com/t/cannot-restore-from-incremental-backup-pbm-and-psmdb-in-the-same-pod/28041/2 "2024-01-26T10:34:57Z")
Hi @Iliterallyneedhelp , > Restore on replicaset “rs0” in state: error: check mongod binary: run: exec: “mongod”: executable file not found in $PATH. stderr: The error means that **pbm-agent** performed pre-checks and couldn’t find **mongod** binary in its **$PATH**. The “actual” restore hasn’t started yet. During Physical Restore, PBM agents shut down (remotely) the **mongod** process by sending `db.adminCommand("shutdown")`, copies backup files to the dbpath, and **exec** `mongod --dbpath=[...]` to perform “post-restore” actions. Make sure: - PBM Agent container has the same **mongod** binary as the PSMDB container. And its **$PATH** contains the **mongod** (i.e., **pbm-agent** can exec mongod process) - PSMDB dbpath is mounted volume (i.e., it’s accessible for other containers) - PBM Agent container has the same mounted volume as the PSMDB container (i.e., it can read/write the PSMDB dbpath content) - PBM Agent is run under the same User ID or Group ID as the PSMDB **mongod** process (i.e., it has the same permissions for read/write for the dbpath) --- _[View the full topic](https://forums.percona.com/t/cannot-restore-from-incremental-backup-pbm-and-psmdb-in-the-same-pod/28041)._