# Percona Mongo PBM Physical Restore fails with replicaset **URL:** \ **Category:** Percona Backup for MongoDB\ **Created:** [March 21, 2025, 6:18pm UTC](https://forums.percona.com/t/percona-mongo-pbm-physical-restore-fails-with-replicaset/37311 "2025-03-21T18:18:28Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![jared1](https://avatars.discourse-cdn.com/v4/letter/j/a4c791/32.png) [@jared1](https://forums.percona.com/u/jared1)\ **Post date:** [March 21, 2025, 6:18pm UTC](https://forums.percona.com/t/percona-mongo-pbm-physical-restore-fails-with-replicaset/37311/1 "2025-03-21T18:18:28Z")
Initially we achieved successful restore of a Physical backup of Percona Mongo using PBM using just one DB. Now, we have created a Replicaset with two Percona Mongo DBs and one arbiter. Backup works fine, but on restore, first PBM seems to be waiting for the Containers (Percona Mongo running in Docker) to be turned off, which is fine. But then after turning both the data-bearing nodes off, the restore procedure hangs. We just get this message repeatedly in the logs: E [pitr] init: get conf: get: server selection error: server selection timeout, current topology: { Type: ReplicaSetNoPrimary, Servers: [{ Addr: perconamongo8:27017, Type: Unknown, Last error: dial tcp: lookup perconamongo8 on 127.0.0.11:53: no such host }, { Addr: perconamongo7:27017, Type: Unknown, Last error: dial tcp: lookup perconamongo7 on 127.0.0.11:53: no such host }, { Addr: perconamongoarb:27017, Type: RSArbiter, Average RTT: 343041 },] } For a Physical backup restore, what are we supposed to do with a replicaset? If keep the nodes running, PBM seems to wait for them to be turned off. If we turn them off, then PBM complains that it cannot see them. Thanks. ---
**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:** [March 24, 2025, 11:07am UTC](https://forums.percona.com/t/percona-mongo-pbm-physical-restore-fails-with-replicaset/37311/2 "2025-03-24T11:07:46Z")
Hi, for physical restore you have to [stop arbiter nodes](https://docs.percona.com/percona-backup-mongodb/details/deployments.html?h=arbiter#supported-mongodb-deployments) before attempting it. Keep the other nodes running. ---
**Author:** ![jared1](https://avatars.discourse-cdn.com/v4/letter/j/a4c791/32.png) [@jared1](https://forums.percona.com/u/jared1)\ **Post date:** [March 25, 2025, 5:02pm UTC](https://forums.percona.com/t/percona-mongo-pbm-physical-restore-fails-with-replicaset/37311/3 "2025-03-25T17:02:12Z")
Thanks for your reply. We are still stuck. I am providing logs from our two Percona Mongo nodes. The arbiter has been turned off. We have tried different combinations of restoring to the Primary or Secondary. The Percona PBM on the Primary node seems to wait for the node to become secondary, and the Secondary waits to be shutdown, according to the Docker logs on the PBM containers. The documentation here says to turn off the nodes for Physical restore, so we have tried that too (even though I understood from the above that we should only turn off the Arbiter).. > **[Percona Backup for MongoDB - Restore from a logical backup](https://docs.percona.com/percona-backup-mongodb/usage/restore.html#restore-a-database)** > > To restore a backup, use the pbm restore command supplying the backup name from which you intend to restore. Percona Backup for MongoDB identifies the type of the backup (physical, logical or incremental) and restores the database up to the... 2025-03-25T16:16:45.000+0000 D [restore/2025-03-25T16:13:36.827616408Z] waiting to became secondary 2025-03-25T16:16:46.000+0000 D [restore/2025-03-25T16:13:36.827616408Z] waiting to became secondary 2025-03-25T16:16:47.000+0000 D [restore/2025-03-25T16:13:36.827616408Z] waiting to became secondary 2025-03-25T16:16:48.000+0000 D [restore/2025-03-25T16:13:36.827616408Z] waiting for the node to shutdown 2025-03-25T16:19:06.000+0000 E [pitr] init: get conf: get: server selection error: server selection timeout, current topology: { Type: ReplicaSetNoPrimary, Servers: [{ Addr: perconamongo7:27017, Type: Unknown, Last error: dial tcp: lookup perconamongo7 on 127.0.0.11:53: no such host }, { Addr: perconamongo8:27017, Type: RSSecondary, Average RTT: 349172 }, { Addr: perconamongoarb:27017, Type: Unknown, Last error: dial tcp: lookup perconamongoarb on 127.0.0.11:53: no such host },] } * * * 2025-03-25T16:13:37.000+0000 I got epoch {1742919217 4} 2025-03-25T16:13:37.000+0000 I [restore/2025-03-25T16:13:36.827616408Z] backup: 2025-02-20T11:51:16Z 2025-03-25T16:13:37.000+0000 I [restore/2025-03-25T16:13:36.827616408Z] recovery started 2025-03-25T16:13:37.000+0000 D [restore/2025-03-25T16:13:36.827616408Z] port: 27282 2025-03-25T16:13:38.000+0000 D [restore/2025-03-25T16:13:36.827616408Z] mongod binary: mongod, version: v8.0.4-1 2025-03-25T16:13:38.000+0000 I [restore/2025-03-25T16:13:36.827616408Z] moving to state starting 2025-03-25T16:13:38.000+0000 I [restore/2025-03-25T16:13:36.827616408Z] waiting for cluster 2025-03-25T16:13:48.000+0000 D [restore/2025-03-25T16:13:36.827616408Z] converged to state starting 2025-03-25T16:13:48.000+0000 D [restore/2025-03-25T16:13:36.827616408Z] starting 2025-03-25T16:13:48.000+0000 I [restore/2025-03-25T16:13:36.827616408Z] moving to state running 2025-03-25T16:13:48.000+0000 I [restore/2025-03-25T16:13:36.827616408Z] waiting for cluster 2025-03-25T16:14:03.000+0000 D [restore/2025-03-25T16:13:36.827616408Z] converged to state running 2025-03-25T16:14:03.000+0000 I [restore/2025-03-25T16:13:36.827616408Z] send to stopAgent chan 2025-03-25T16:14:03.000+0000 D [restore/2025-03-25T16:13:36.827616408Z] stop agents heartbeats 2025-03-25T16:14:03.000+0000 I [restore/2025-03-25T16:13:36.827616408Z] stopping mongod and flushing old data 2025-03-25T16:14:03.000+0000 D [restore/2025-03-25T16:13:36.827616408Z] shutdown server 2025-03-25T16:14:03.000+0000 D [restore/2025-03-25T16:13:36.827616408Z] waiting for the node to shutdown 2025-03-25T16:19:08.000+0000 E [pitr] init: get conf: get: server selection error: server selection timeout, current topology: { Type: ReplicaSetNoPrimary, Servers: [{ Addr: perconamongo8:27017, Type: RSSecondary, Average RTT: 710142 }, { Addr: perconamongo7:27017, Type: Unknown, Last error: dial tcp: lookup perconamongo7 on 127.0.0.11:53: no such host }, { Addr: perconamongoarb:27017, Type: Unknown, Last error: dial tcp: lookup perconamongoarb on 127.0.0.11:53: no such host },] } Further assistance would be greatly appreciated. ---
**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:** [March 26, 2025, 11:11am UTC](https://forums.percona.com/t/percona-mongo-pbm-physical-restore-fails-with-replicaset/37311/4 "2025-03-26T11:11:42Z")
Hi, a few clarifications: 1. there is no way of “restoring to the primary or secondary”. PBM restores ALL the members of the replica set to the same point in time. 2. The doc page you linked is about restoring from a logical backup and since you are trying to restore a physical backup you should be reading [this](https://docs.percona.com/percona-backup-mongodb/usage/restore-physical.html) instead. 3. the doc page about physical restores mentions stopping `mongos` router and arbiter nodes. Don’t stop primary or secondary. Also check instructions [here](https://docs.percona.com/percona-backup-mongodb/install/docker.html?h=docker) for running in Docker. If you still suspect an issue please open a bug report [here] ([Jira](https://perconadev.atlassian.net/browse/PBM-1482)) with full instructions to reproduce so the dev team can take a look.