# Cluster with backup enabled CrashLoopBackoff only rs0-1 **URL:** \ **Category:** Percona Operator for MongoDB\ **Created:** [February 16, 2021, 12:48pm UTC](https://forums.percona.com/t/cluster-with-backup-enabled-crashloopbackoff-only-rs0-1/9299 "2021-02-16T12:48:17Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![gasenov](https://avatars.discourse-cdn.com/v4/letter/g/e9c0ed/32.png) [@gasenov](https://forums.percona.com/u/gasenov)\ **Post date:** [February 16, 2021, 12:48pm UTC](https://forums.percona.com/t/cluster-with-backup-enabled-crashloopbackoff-only-rs0-1/9299/1 "2021-02-16T12:48:17Z")
Hello. I don’t know if this is a bug or I’m missing something but every mongodb cluster I make backup container failed with “Unable to reach primary for set rs0”. cluster size 3 arbiter.enabled false shard false All the nodes of the mongo cluster are working correctly but only rs0-1 backup container log: > connect@src/mongo/shell/mongo.js:353:17 > @(connect):3:6 > 2021-02-16T12:44:05.298+0000 F - [main] exception: connect failed > 2021-02-16T12:44:05.298+0000 E - [main] exiting with code 1 > + exit\_status=0 > ++ grep -E ‘^([0-9]+)$’ /tmp/tmp.exfxQxes0t > + rs\_size= > + [[0 == 0]] > + [[‘’ -ge 1]] > + sleep 40 > + for i in ‘{1…10}’ > + ‘[’ ‘’ ‘]’ > + mongo ‘mongodb://backup:redacted@localhost:27017/?replicaSet=rs0’ ‘–eval= > (db.isMaster().hosts).length’ --quiet > + tee /tmp/tmp.exfxQxes0t > 2021-02-16T12:44:45.506+0000 I NETWORK [js] Starting new replica set monitor for > rs0/localhost:27017 > 2021-02-16T12:44:45.506+0000 I CONNPOOL [ReplicaSetMonitor-TaskExecutor] Connecting to > localhost:27017 > 2021-02-16T12:44:45.507+0000 W NETWORK [ReplicaSetMonitor-TaskExecutor] Unable to reach > primary for set rs0 > 2021-02-16T12:44:45.507+0000 I NETWORK [ReplicaSetMonitor-TaskExecutor] Cannot reach any > nodes for set rs0. Please check network connectivity and the status of the set. This has happened > for 1 checks in a row. thanks in advance! ---
**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\ **Post date:** [February 19, 2021, 9:04am UTC](https://forums.percona.com/t/cluster-with-backup-enabled-crashloopbackoff-only-rs0-1/9299/2 "2021-02-19T09:04:13Z")
Hello @gasenov , thank you for the request. I have tried to do a backup and restore and it works fine for me, but could you please share more details about your installation and steps you perform? 1. Please share the complete cr.yaml (it does not contain any sensitive data) 2. How do you take the backup? Is it scheduled? If it is manual - please share the backup.yaml manifest. 3. Is there anything specific about the installation? Kubernetes version, storage type, etc.? ---
**Author:** ![gasenov](https://avatars.discourse-cdn.com/v4/letter/g/e9c0ed/32.png) [@gasenov](https://forums.percona.com/u/gasenov)\ **Post date:** [February 19, 2021, 10:04am UTC](https://forums.percona.com/t/cluster-with-backup-enabled-crashloopbackoff-only-rs0-1/9299/3 "2021-02-19T10:04:02Z")
The issue is not during backup/restore. It just failed to start the backup container. Or maybe it start doing backups from the startup ??!? Actually it starts but because of the backup container (in the replica pod) timeouts the pod is shat down periodically. In a matter of fact after some time like the next day it was connected. When i watched it for hours trying to connect and couldn’t. Strange ---
**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\ **Post date:** [February 19, 2021, 1:13pm UTC](https://forums.percona.com/t/cluster-with-backup-enabled-crashloopbackoff-only-rs0-1/9299/4 "2021-02-19T13:13:17Z")
@gasenov yeah, this I cannot reproduce as well. Could you please share your cr.yaml?