# Mongod-failure-after-restore

**URL:** <https://forums.percona.com/t/mongod-failure-after-restore/39528>\
**Category:** Percona Operator for MongoDB\
**Created:** [October 10, 2025, 5:35am UTC](https://forums.percona.com/t/mongod-failure-after-restore/39528 "2025-10-10T05:35:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hemanth](https://avatars.discourse-cdn.com/v4/letter/h/7993a0/32.png) [@hemanth](https://forums.percona.com/u/hemanth)\
**Post date:** [October 10, 2025, 5:35am UTC](https://forums.percona.com/t/mongod-failure-after-restore/39528/1 "2025-10-10T05:35:32Z")

</div>

We are using a cloud infrastructure running on Ubuntu with three servers: one primary and two secondary. We are running Percona Backup for MongoDB (PBM) version v2.10. For backups, we use Amazon S3 as the storage destination.

However, when we attempt to restore, the mongod service fails even though the restoration process is reported as successful. After this, all three mongod services fail. I am trying to restore the data only on a secondary server.

Command used for backup:  
pbm backup --type=physical

Command used for restore:  
pbm restore --time=“2025-09-24T13:30:00Z”

# PBM status after backup:

pbm status  
Cluster:

poc:

- private\_ip:27018 [S]: pbm-agent [v2.10.0] OK
- private\_ip:27018 [S]: pbm-agent [v2.10.0] OK
- private\_ip:27018 [P]: pbm-agent [v2.10.0] OK

# PITR incremental backup:

Status [ON]  
Running members: poc/private\_ip:27018

# Currently running:

(none)

# Backups:

S3 ap-south-1 s3://mongo-percona-bk  
Snapshots:  
2025-10-01T12:13:21Z 33.59GB success [restore\_to\_time: 2025-10-01T12:13:24]  
PITR chunks [11.10MB]:  
2025-10-01T12:13:25 - 2025-10-02T02:53:23

# PBM status after restore:

pbm status  
Cluster:

poc:

- private\_ip:27018 : pbm-agent [NOT FOUND]
- private\_ip:27018 : pbm-agent [NOT FOUND]
- private\_ip:27018 : pbm-agent [NOT FOUND]

# PITR incremental backup:

Status [OFF]

# Currently running:

(none)

# Backups:

S3 ap-south-1 s3://mongo-percona-bk  
(none)

---

<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:** [October 10, 2025, 11:38am UTC](https://forums.percona.com/t/mongod-failure-after-restore/39528/2 "2025-10-10T11:38:28Z")

</div>

Hi hemanth, PBM is meant for full restore of all your nodes. If it’s only one node you need to recover, then you can trigger [initial sync](https://www.mongodb.com/docs/manual/core/replica-set-sync/#logical-initial-sync-process) process.

---

<div class="post-metadata">

**Author:** ![hemanth](https://avatars.discourse-cdn.com/v4/letter/h/7993a0/32.png) [@hemanth](https://forums.percona.com/u/hemanth)\
**Post date:** [October 15, 2025, 12:25pm UTC](https://forums.percona.com/t/mongod-failure-after-restore/39528/3 "2025-10-15T12:25:07Z")

</div>

Hello Ivan,

I attempted to restore on the secondary instance despite the Mongo service failure. The PBM status has been mentioned above. Could you please share the documentation or Linux commands for performing the restore? It would be helpful.