# PBM can't create a full backup

**URL:** https://forums.percona.com/t/pbm-cant-create-a-full-backup/27824
**Category:** Percona Backup for MongoDB
**Tags:** mongodb
**Created:** [January 17, 2024, 2:24am UTC](https://forums.percona.com/t/pbm-cant-create-a-full-backup/27824 "2024-01-17T02:24:04Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![Linh\_T\_Khanh](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/linh_t_khanh/32/11294_2.png) [@Linh\_T\_Khanh](https://forums.percona.com/u/Linh_T_Khanh)
#### Post date: [January 17, 2024, 2:24am UTC](https://forums.percona.com/t/pbm-cant-create-a-full-backup/27824/1 "2024-01-17T02:24:04Z")

</div>

2024-01-13T04:26:26Z I [rs-db/mongod:27017] got epoch {1704763717 1}  
2024-01-13T04:26:27Z I [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] backup started  
2024-01-14T12:55:07Z I [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] mongodump finished, waiting for the oplog  
2024-01-14T12:55:08Z I [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] dropping tmp collections  
2024-01-14T12:55:08Z I [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] mark RS as error `check cluster for dump done: convergeCluster: get backup metadata: not found`:   
2024-01-14T12:55:08Z I [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] mark backup as error `check cluster for dump done: convergeCluster: get backup metadata: not found`:   
2024-01-14T12:55:08Z E [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] backup: check cluster for dump done: convergeCluster: get backup metadata: not found

When I run pbm backup, the full backup is not created. I need everyone’s help with this issue.  
Plzzz

---

<div class="post-metadata">

### Author: ![Mukesh\_Kumar](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mukesh_kumar/32/10698_2.png) [@Mukesh\_Kumar](https://forums.percona.com/u/Mukesh_Kumar)
#### Post date: [January 17, 2024, 4:48am UTC](https://forums.percona.com/t/pbm-cant-create-a-full-backup/27824/2 "2024-01-17T04:48:51Z")

</div>

Hi @Linh_T_Khanh,  
Welcome to the community!  
Regarding the error

```auto
2024-01-14T12:55:08Z I [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] mark backup as error check cluster for dump done: convergeCluster: get backup metadata: not found:

```

please share the pbm logs along with pbm status, from below command:

```auto
pbm logs -e backup/2024-01-13T04:26:26Z -s D -t 0
pbm status

```

Also, can you confirm if you have scheduled the pbm backup via cron and cleanup is also included after it?

Thanks,  
Mukesh

---

<div class="post-metadata">

### Author: ![Linh\_T\_Khanh](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/linh_t_khanh/32/11294_2.png) [@Linh\_T\_Khanh](https://forums.percona.com/u/Linh_T_Khanh)
#### Post date: [January 18, 2024, 2:14am UTC](https://forums.percona.com/t/pbm-cant-create-a-full-backup/27824/3 "2024-01-18T02:14:08Z")

</div>

[mongod@db mongodb]$ pbm logs -e backup/2024-01-13T04:26:26Z -s D -t 0  
2024-01-13T04:26:26Z D [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] init backup meta  
2024-01-13T04:26:26Z D [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] nomination list for rs-db: [[db:27017]]  
2024-01-13T04:26:26Z D [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] nomination rs-db, set candidates [db:27017]  
2024-01-13T04:26:27Z I [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] backup started  
2024-01-13T04:26:30Z D [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] wait for tmp users {1705119990 13}  
2024-01-14T12:55:07Z I [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] mongodump finished, waiting for the oplog  
2024-01-14T12:55:08Z I [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] dropping tmp collections  
2024-01-14T12:55:08Z I [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] mark RS as error `check cluster for dump done: convergeCluster: get backup metadata: not found`:   
2024-01-14T12:55:08Z I [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] mark backup as error `check cluster for dump done: convergeCluster: get backup metadata: not found`:   
2024-01-14T12:55:08Z E [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] backup: check cluster for dump done: convergeCluster: get backup metadata: not found  
2024-01-14T12:55:08Z D [rs-db/mongod:27017] [backup/2024-01-13T04:26:26Z] releasing lock  
You have mail in /var/spool/mail/mongod

# [mongod@db mongodb]$ pbm status Cluster:

rs-mbvbaoff:

- rs-mbvbaoff/db:27017 [P]: pbm-agent v2.1.0 OK

# PITR incremental backup:

Status [ON]

# Currently running:

(none)

# Backups:

FS /backup/pbm\_backup  
(none)

I have just sent more details.  
Yes, I have scheduled the pbm backup via cron and cleanup. Backup storage is always sufficient enough for next full backups.

---

<div class="post-metadata">

### Author: ![Mukesh\_Kumar](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/mukesh_kumar/32/10698_2.png) [@Mukesh\_Kumar](https://forums.percona.com/u/Mukesh_Kumar)
#### Post date: [January 18, 2024, 12:23pm UTC](https://forums.percona.com/t/pbm-cant-create-a-full-backup/27824/4 "2024-01-18T12:23:18Z")

</div>

Hi @Linh_T_Khanh  
I believe, you have scheduled the pbm backup and cleanup simultaneously. The cleanup command was designed to work not during backup.

Can you please share the cronjob of backup and cleanup?

Also, we could see pbm version is of 2.1 and we recommend upgrading it to the latest version i.e. [pbm 2.3](https://docs.percona.com/percona-backup-mongodb/install/repos.html).

Thanks,  
Mukesh

---

<div class="post-metadata">

### Author: ![charles.reily](https://avatars.discourse-cdn.com/v4/letter/c/f9ae1b/32.png) [@charles.reily](https://forums.percona.com/u/charles.reily)
#### Post date: [January 22, 2024, 7:37am UTC](https://forums.percona.com/t/pbm-cant-create-a-full-backup/27824/5 "2024-01-22T07:37:55Z")

</div>

The error mentions waiting for the oplog. Ensure that the MongoDB oplog is accessible and that there are no issues with its size or configuration. The oplog is crucial for maintaining the consistency of the backup. Use MongoDB diagnostic commands, such as `rs.status()` and `db.currentOp()`, to gather more information about the state of your replica set.
