# PSMDB Cannot backup cluster: "Waiting for backup metadata"

**URL:** <https://forums.percona.com/t/psmdb-cannot-backup-cluster-waiting-for-backup-metadata/13232>\
**Category:** Percona Backup for MongoDB\
**Tags:** mongodb\
**Created:** [November 25, 2021, 5:48pm UTC](https://forums.percona.com/t/psmdb-cannot-backup-cluster-waiting-for-backup-metadata/13232 "2021-11-25T17:48:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Antoine](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@Antoine](https://forums.percona.com/u/Antoine)\
**Post date:** [November 25, 2021, 5:48pm UTC](https://forums.percona.com/t/psmdb-cannot-backup-cluster-waiting-for-backup-metadata/13232/1 "2021-11-25T17:48:36Z")

</div>

Hi! I have a running installation of PSMDB. I created a manual backup with the following command:

```auto
cat <<EOF | kubectl apply -f-
apiVersion: psmdb.percona.com/v1
kind: PerconaServerMongoDBBackup
metadata:
  name: initial-backup
  namespace: psmdb-db-4-0
spec:
  psmdbCluster: psmdb-db
  storageName: mys3
EOF

```

But there is no backup pod, and the operator says:

```auto
{"level":"info","ts":1637862098.8842378,"logger":"controller_perconaservermongodbbackup","msg":"Waiting for backup metadata","PBM name":"2021-11-25T17:41:23Z","backup":"initial-backup"}

```

Here, the result of `kubectl describe perconaservermongodbbackups.psmdb.percona.com -n psmdb-db-4-0 initial-backup`:

```auto
Name: initial-backup
Namespace: psmdb-db-4-0
Labels: <none>
Annotations: <none>
API Version: psmdb.percona.com/v1
Kind: PerconaServerMongoDBBackup
Metadata:
  Creation Timestamp: 2021-11-25T17:41:13Z
  Generation: 1
  Managed Fields:
    API Version: psmdb.percona.com/v1
    Fields Type: FieldsV1
    fieldsV1:
      f:metadata:
        f:annotations:
          .:
          f:kubectl.kubernetes.io/last-applied-configuration:
      f:spec:
        .:
        f:psmdbCluster:
        f:storageName:
    Manager: kubectl-client-side-apply
    Operation: Update
    Time: 2021-11-25T17:41:13Z
    API Version: psmdb.percona.com/v1
    Fields Type: FieldsV1
    fieldsV1:
      f:spec:
        f:compressionType:
      f:status:
        .:
        f:completed:
        f:destination:
        f:lastTransition:
        f:pbmName:
        f:s3:
        f:start:
        f:state:
        f:storageName:
    Manager: percona-server-mongodb-operator
    Operation: Update
    Time: 2021-11-25T17:41:54Z
  Resource Version: 67912533
  UID: ad7f31b0-4d4c-499c-834d-377770f5e261
Spec:
  Psmdb Cluster: psmdb-db
  Storage Name: mys3
Status:
  Completed: 2021-11-25T17:41:49Z
  Destination: 2021-11-25T17:41:23Z
  Last Transition: 2021-11-25T17:41:49Z
  Pbm Name: 2021-11-25T17:41:23Z
  s3:
    Bucket: mybucket
    Credentials Secret: psmdb-backups-custom-secret
    Endpoint URL: https://endpoint
    Region: myregion
  Start: 2021-11-25T17:41:40Z
  State: ready
  Storage Name: mys3
Events: <none>

```

Did I miss something?

---

<div class="post-metadata">

**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:** [November 25, 2021, 6:44pm UTC](https://forums.percona.com/t/psmdb-cannot-backup-cluster-waiting-for-backup-metadata/13232/2 "2021-11-25T18:44:54Z")

</div>

Hello @Antoine ,

the backup pod is not going to be created, as backup is handled by the backup container which runs within the replicaset pod.

Could you please check the logs of this container?  
Anything in the `kubectl describe psmdb-backup initial-backup` ?

---

<div class="post-metadata">

**Author:** ![Antoine](https://avatars.discourse-cdn.com/v4/letter/a/7ab992/32.png) [@Antoine](https://forums.percona.com/u/Antoine)\
**Post date:** [November 26, 2021, 10:51am UTC](https://forums.percona.com/t/psmdb-cannot-backup-cluster-waiting-for-backup-metadata/13232/3 "2021-11-26T10:51:21Z")

</div>

Hello @Sergey_Pronin,

Thanks! I’m used to see a pod and not a sidecar container to do backups, sorry. The backup is OK now (the logs of the backup container helped me to find a permission problem). We can close this, thank you!